I think AdSense rejection emails are one of the least helpful feedback in the tech field. They simply state, "Insufficient content." "Policy violation." They don't even specify the exact page, section, or rule.
When I spoke with bloggers who had this experience, I found the pattern was almost always the same. They guessed the reason, finished writing the post, waited two weeks, and still got rejected again. Some people even gave up after trying three or four times.
Has anyone here had a similar experience?
Did you actually figure out the reason for the rejection?
Being an engineer myself, I see that many people are outputting more code than ever. Some of it being generated vs. written, the volume of code being outputted has definitely risen. There seems to be a shift from "is this something we can build?" to "should we build this and ship it?" For people who have been recruiting or looking to recruit recently, what roles are you hiring for?
Role title (I've seen a rise in PM's and Designers personally)
What exactly can they do that AI can't (yet)
Specific signal that you look for when hiring
Are you moving headcount from one type of role to another? Would be interested to hear from other growing teams!
Was your product voted top 5 product of the day? Want to be featured in our new "Maker's Corner"?
Share the following in the thread below:
Your Product Hunt user name
Link to your Product Hunt Launch that hit top 5 of the day
An interesting tidbit of why the community would be interested learning more about you and your journey. If you are selected, we will contact you and feature your story here in our Forums and newsletter!
No-code has come a long way but I still don't feel it's an entire code replacement yet, especially when it comes to mobile apps. I want to be proved wrong though, what's the best no code builder for apps that you've used?
I build HIPAA compliant AI for healthcare, and last month I deleted a feature I had just finished. It was a journey analytics module in our internal dashboard: stage by stage funnel, cohorts, drop off between every step. The module worked as designed. I removed it anyway.
The reason is that I could not name one decision it had changed. I opened it, read the stages, agreed with them, closed the tab. It described the past accurately and left me where I started, because a funnel tells you where people stopped and never tells you which of the eleven things on that screen to cut.
Building in public and doing some research on my own scar tissue. I've rage-quit more finance apps than I can count YNAB three separate times, two spreadsheets I lovingly built and abandoned by week three, one app whose notifications made me feel like a parent was scolding me.
Every time it was the same story: the tool slowly turned into a chore, and one day I just... stopped opening it.
So I want the war stories. What money app or system did you rage-quit? Was it the manual data entry, the guilt-trip notifications, the endless categories to maintain or something else?
Whether you're a solo builder or part of a fast-moving product team, documentation always seems to lag just behind reality. Is it the speed of product changes?
Getting engineers or PMs to consistently update docs?
Someone asked here this week how to turn free users into paying ones. The answer I gave was half right, so here is the other half.
The easy half is that a free user has not decided the problem costs them anything yet. So you look for the ones with money already attached. A consultant, a tool they cancelled, someone's hours.
Hours are where it goes wrong. Every project I have been paid for was client work, priced before it existed. An hour saved there widened the margin, because the number on the contract did not move when the work got faster. That is why saving time reads as obviously valuable to me.
An agency billing hourly is the exact opposite. Every hour you save them is an hour they cannot invoice. Same job title, same daily pain, opposite reason to buy you.
