I run a career platform, so I spend a lot of my week looking at how people talk about their own work. "Tell me about yourself" is the question I watch go wrong the most, and it goes wrong the same way almost every time.

Most people treat it as a cue to recap the resume in order. They start at the first job, walk forward year by year, and land in the present a little out of breath. The interviewer already read the resume. What they're actually doing during that first answer is deciding what kind of story to listen for, and a chronological list hands them nothing to hold onto.

The fix is to answer with a throughline instead of a timeline. Pick the one thread that explains why you're sitting in that specific room, and let two or three points from your history hang off it. Something like: "I'm the person who gets handed the messy, undefined problem and turns it into something a team can actually ship. That's the thread through my last two roles, and it's why this one caught my eye." Then you stop.

That version does the interviewer's work for them. It tells them what to dig into, and it makes you sound like someone who knows what they're good at instead of someone reading their history back.

Something I've noticed from running a career platform: the people who stay lost the longest are usually the ones convinced there's one right path out there and they just haven't found the door yet. The ones who get unstuck mostly stopped hunting for the door.

What shifted for them was pretty undramatic. They quit treating the job as the whole career and started treating it as one holding in a bigger collection. You can have a steady paycheck and a small thing you're building on the side that might go nowhere, both at once, and neither one has to be The Answer. People actually worked like this for centuries, before the single-employer career became normal for a few decades and we all started assuming it was the only real shape.

Once your work is a few lanes you add and drop over the years instead of one giant decision, the pressure drops a lot. A bad guess stops being your life. It's just a lane you close while the others keep running, which feels nothing like standing at a fork sure that one wrong turn wrecks everything.

Honestly I think a lot of the "I don't know what to do with my life" weight comes from a premise that isn't even true anymore, that you're locking in one identity for the next forty years. Most of the people I've watched land somewhere good got there with a few different things going at once, built up slowly over years.

For those of you who stopped feeling lost: did it come from finally committing to something, or from letting yourself run more than one thing at once?

I just came across gptzero and boy, its capability to detect AI written texts is mind blowing. I'm sure there are other products doing similar things, but this one really hit me strong. Anyway, now I'm trying to reverse engineer its logic with Claude to see if I can produce content that is less likely detected as AI, because I'm pretty sure Google and other search engines also will be using similar methods or products and will penalize the ranking of sites with full AI generated content.

and here' how I tested it:

the text above is fully written by me, so it got detected 100% human

then the version below is written by AI, I asked it to retain the tone, and style, and just correct grammar and semantics, this is the result, and it was detected 100% AI:

I just came across GPTZero and boy, its ability to flag AI-written text is mind-blowing. I know there are other tools doing the same thing, but this one really hit me.

Now I’m digging into its signals with Claude, not to blindly game a detector, but to make sure AI-assisted content still sounds like a real person with actual thoughts behind it.

Google may not penalize AI content by default, but mass-produced, generic AI pages are absolutely the kind of content search engines will bury.

and then I asked AI to keep everything as much as possible and just correct grammars and it was detected 2% AI-written:

I just came across GPTZero, and boy, its capability to detect AI-written text is mind-blowing. I’m sure there are other products doing similar things, but this one really hit me hard.

Anyway, now I’m trying to reverse-engineer its logic with Claude to see if I can produce content that is less likely to be detected as AI, because I’m pretty sure Google and other search engines will be using similar methods or products and will penalize the rankings of sites with fully AI-generated content.

so it is not going to be an easy win publishing all contents with AI

for a long stretch I was sure the reason nobody stuck was the product, so I just kept polishing. better onboarding, another feature nobody actually asked for. signups would trickle in, evaporate a week later, and I'd go fix something else and tell myself that was the problem.

what finally changed it was embarrassingly low-tech. I quit staring at the signup number and went and found ten people who had the one specific problem I was building for, and just talked to them. not "would you use a tool that does X," more like walk me through the last time this actually bit you. the handful who ended up sticking around all turned out to have the same painful moment in common, and that moment basically became the whole pitch.

I build Joberney, so that's the lane I happened to learn it in, but every builder I've said this to has some version of it buried in their first year. the proof showed up before the product got good, not after. kind of backwards from how I assumed any of this worked.

what got you your first ten that actually stuck around? something you built, or something you just noticed?

I build my side project nights and weekends and the day job pays for it (a career platform, Joberney, still tiny, barely any traffic yet). everyone warns you about the hours. the hours are real but I was kind of braced for those.

the part that actually gets me is the switch. I shut the work laptop and try to be a founder twenty minutes later and my head is still chewing on whatever I was dealing with all day, and the calls I make in that window are just bad. I'd sit down to decide what to build with my brain still in execute-the-ticket mode from work, which is about the worst mode there is for figuring out if a thing should even exist.

took me way too long to clock what was even happening. I kept beating myself up like i was bad at prioritizing, when really my head was just still back at the day job, deciding founder stuff on autopilot.

what helped was stupid and small. I stopped letting myself decide anything that mattered in that first hour. give it a bit, let the day drain out, then sit down. felt like productivity-guru nonsense when I started, still kind of cringe at it honestly, but its the biggest jump in decision quality I've gotten all quarter and it cost me nothing.

one thing I wasnt expecting and still chew on: the day job makes me less desperate with the product. I can tell a wrong-fit user no because rents already covered. cant decide if thats a strength or if im just hiding from the pressure of having to make it actually work.

anyway. anyone else building around a full time job, do you get this brain-switch thing? how do you shut the first one off at night, cause i clearly havent cracked it.

So I've been experimenting with AI for my entire marketing for the last couple of weeks for Joberney, and I can confidently say, it SUCKS. Yes, it expedites your activities, automates lots of things, but the main problem is people don't trust what is produced with AI and whatever you do to make it less machine-like, it ends up being the same way. I'm pretty sure there are use cases where you can automate the analysis of your content, but if you rely on it for making the content for you, you just waste your precious time. If you have done full marketing with AI and it has been successful, I'd like to learn what you have done and what part.

I've been building my thing on the side for a while now and it's about as far from what i do at my day job as it could possibly be, which honestly felt like the entire point at the start, because the whole appeal was getting to spend my nights on something that wasn't just more of the day job.

lately I'm a lot less sure that building Joberney was a smart trade, because a real chunk of every hour I put in goes toward just learning the basics of a world I don't actually live in, on top of an already full week, and when I look at the people who somehow keep a side project alive past the first year it's almost always something that sits right next to a skill they already use all day, so they started with this quiet head start instead of clawing their way up from zero the way I've been doing.

so now I'm sitting here wondering whether I picked the romantic version of this when the boring adjacent one would've actually gone somewhere, and whether all that distance i was so into at the beginning is really just a tax I've been quietly paying every single weekend without noticing.

for anyone here who's kept something going for more than a year, was it close to your day-job skills or completely different, and did that closeness actually make it easier or did it not really matter in the end?

I run a career platform, so I talk to a lot of people who feel stuck between staying put and trying something of their own. The thing that surprised me is how often the "stay put" isn't really a decision. It's a default they never questioned, and they think it's just who they are.

There's a pretty old idea in psychology that we learn more from watching than from being told. You watched a parent come home tired but covered. Bills paid, no surprises. You also probably watched somebody try something on their own and have it not work, and you watched what that did to them. Nobody sat you down and said "get a job and keep your head down." You just absorbed it. It became the normal-feeling option, and everything else started to feel reckless by comparison.

So when someone says "I'm just not the entrepreneurial type" or "I'm too risk-averse for that," I don't fully buy it anymore. A lot of the time that isn't a personality. It's a script that got handed down before you had any say in it.

The part that actually helped people I've watched get unstuck: you don't have to flip the whole thing. You can keep the stable lane that covers your bills and run the experiment small and cheap on the side, where failing doesn't cost you anything real. The risk you inherited a fear of mostly isn't the risk that exists anymore.

For anyone who broke out of the default they grew up around: what made you finally question it?

Honest one. I'm building Joberney, career and entrepreneurship platform, mostly solo, day job still paying the bills. For a long stretch the work was building: features, flows, the stuff I'm comfortable with because the problem is right in front of me and I can grind on it until it's solved.

Then I shipped, and ran straight into the part nobody's comfortable with. Nobody is waiting for your thing. The build has a clear finish line. Distribution doesn't. You can do everything "right" and still wake up to the same flat numbers, and there's no compiler error telling you which line is wrong.

A few things I've had to actually learn, slowly, none of them clever:

1. Talking to one real person beats another feature almost every time. The hours I spent in a comment thread or a DM figuring out why someone bounced taught me more than a week of building did.
2. I built way too much before checking whether anyone wanted it. If I started over I'd put something up to gauge demand first and let that decide what to build, instead of building and hoping the demand showed up after.
3. Distribution is a daily habit, not a launch. The launch-day spike lies to you. The thing that compounds is showing up every day in the places your person already is, being useful, for months.

I'm not on the other side of this. I'm in it. The build muscle was already there. The distribution muscle I'm growing from zero, and it's slow and uncomfortable.

For the builders here who got past this part: what was the unglamorous thing that actually started moving the numbers for you? Not the viral post. The boring repeatable thing.

My son is really into fuse beads, and he likes building different patterns from various images. One problem we keep running into when trying to create a custom map is color matching.

A picture can have so many colors, but you can’t always find the exact matching bead color for them. A lot of sites that create fuse-bead maps don’t seem to match the image colors to a specific bead palette, or show a realistic preview of how the final piece will actually look with those bead colors.

I’m wondering if anyone else who does fuse-bead crafts has run into the same issue. If yes, what’s your solution?

Do you just accept the fate and go with the closest color, or have you found other ways to get better results?

I talk to a lot of people who are stuck in jobs they do not actually hate, and the word that comes up over and over is invisible. Passed over, unseen, doing fine work that nobody seems to notice. Almost all of them have decided the answer is a new job somewhere else.

Sometimes it is. But I have watched enough of these moves to notice that a lot of people land the new role, get the small bump in title and pay, and feel exactly as invisible six months later. The setting changed. The feeling did not.

What I see work more often is quieter. The people who stop feeling invisible are usually the ones who started building one small thing that was theirs. A side project, a bit of writing in their field, a tiny service for a handful of people. Not to quit. Not to grind at 11pm. Just so that their sense of being good at something stopped depending entirely on whether one manager happened to see it.

That is the part standard advice misses. It treats the job as the only place your worth gets measured, so the only lever it offers is "go get measured somewhere new." Having a second lane, even a small one, changes how the day job feels because the job is no longer carrying your whole identity by itself.

If you are sitting in the invisible feeling right now, I would get honest about which problem it actually is before updating the resume. Is the work wrong, or is one job just too small a place to hold everything you want to be known for?

For anyone who pushed through the invisible stretch, what actually changed it for you?

Everyone preps for the start. The idea, the stack, the launch post. But watching people who build next to a full time job, I run a career platform for exactly this crowd, so paying attention to where projects die is basically my job, the start is rarely where it goes wrong. Month four is.
By month four the project isn’t new anymore. The week-three dopamine is gone. The day job gets heavy again. Every guide you bookmarked was written for week one and none of it covers this stretch. Nothing is technically broken. You just stop opening the laptop, and the project dies without a decision ever being made.
I’ve had stretches like that building Joberney. Day job pays the bills, nights and weekends go to the build, and some weeks the whole thing feels like a second job that doesn’t pay yet. Two boring things keep it alive for me. I shrink the weekly goal until it’s small enough to hit on a bad week. And time off from the project goes on the calendar before work time does. The grind-every-evening version of this had me close to quitting more than once.
So, a question for anyone who’s killed a project: when did it actually die? Not the day you archived the repo. The week you stopped opening it. I’d bet a lot of honest answers land somewhere in that month three to five window, even when the post-mortem said no traction.

Honest one. I'm building Joberney, mostly solo, with coding agents doing a lot of the actual typing. Day job still pays the bills while I build. The agents are the only reason a one-person thing ships at all. But a few months in, the thing I didn't see coming wasn't a bug or a stack problem. It was what the agents did to my own judgment.

The loop is really good at making you feel busy. You prompt, something appears, you tweak, something else appears. It's the same pull as a slot machine: fast feedback, variable reward, the next pull always feels one prompt away from the thing you wanted. I started calling it the productivity casino in my own notes. I'd close the laptop after three hours genuinely tired, then realize I'd shipped a pile of stuff nobody asked for and skipped the one boring thing that actually mattered that day.

A few things I changed:

1. I write down what "done" looks like in one sentence before I open the agent. If I can't, the agent will happily generate motion until I figure it out, and that motion bills me in hours.
2. Boring beats clever. The agent makes clever so cheap that I overbuilt constantly. Default now is the smallest version a real person can react to.
3. I track shipped-and-used, not shipped. A lot of what I "finished" was never going to get touched. The speed hid that from me, because finishing felt like the win on its own.

None of this is anti-agent. I couldn't build solo without them. It's more that the speed quietly moved the hard part from "can I build this" to "should I, and is this even the thing." That second problem is harder and it doesn't announce itself.

Anyone else building mostly with agents hit this? Curious how you keep yourself honest about what's actually worth shipping.

When I started a career platform, the question I expected least turned out to be the most common one people arrive with: should I find a place to work, or build my own thing. People ask it like they are waiting for a verdict on what kind of person they are. Employee or founder. Safe or brave.

That framing is the trap. It treats a timing-and-tolerance decision like a fixed identity.

Here is what I actually see in the people who move. They stop asking "which type am I" and start asking "which kind of not-knowing can I live with for the next couple of years." A job hands you a known paycheck and unknown meaning. You find out slowly whether the work matters to you. Your own thing hands you the opposite, known meaning and unknown money. You care about it from day one and have no idea if it will ever pay. Both are uncertain. They are just uncertain about different things.

So the real question is not job versus venture. It is which uncertainty you can carry without it eating you alive. Some people are wrecked by financial unknowns and completely fine with boredom. Some are the reverse. Neither is the braver person. They just have different things they can tolerate, and most people have never actually asked themselves which one they are.

The people who get unstuck fastest usually figure out they do not have to answer it permanently either. You can take the job that covers the financial unknown, then use that stability to test the venture in small, cheap ways on the side. The "or" was rarely as hard as it felt. It was usually an "and" with an order to it.

If you are stuck on this right now, drop the question of which type you are. Which kind of not-knowing can you actually live with?

First time traveling to Bali, do I need carry cash or credit card should work in most places?

Disclaimer:

1- this is a long write-up so buckle up.

2- this isn't for everyone in this sub. I'm sure many of you have never gone down this path and you are way more realistic than me. But I'm also sure many have fallen into this trap over the last couple of years, or might be thinking about going down it, so I wanted to share my own experience.

I'm a TPM at a big enterprise company, and like many other PMs in those companies, you feel comfy in your job and many things become just another routine. Writing a PRD, building marketing slides, customer meetings, you name it, and you keep doing it over and over in hope of promotion or switching to another company like a guinea pig running on a wheel. to be clear, I don't want to trash the PM job, and it has been one of the best roles that I've worked. But, this is a reality of working as a PM in a big enterprise. I've never been in a startup environment also, and I'm pretty sure this is different there, but in a startup you work for reasons other than money. It's for the vision, and eventually money that you hope pays off big.

Anyway, like many other PMs in a similar situation, I started exploring my options at other companies. As I went through one interview after another, I felt exhausted and found the whole process overwhelming. Many shiny roles where I made it to multiple rounds and then got a call at the end saying I wasn't picked. Others were good teams but couldn't afford the compensation, though that part was rare tbh. So I gave up on that. And since the team I work on keeps changing leadership every other year, it has become a kind of internal job change for me anyway. I need to align with new managers, strategy, etc. So far this has been the regular part for many PMs in the same situation.

Then comes the age of AI and all the excitement, and you find yourself as a PM with a magic wand in your hand that turns your words into something you used to have to beg your UX designers and engineers to build for you, even as a prototype. You walk into meetings with way more confidence, and the moment engineers start questioning your proposal, you pull out that wireframe you built with vibe coding like your lightsaber and fight for your life hard.

As time goes by, something starts itching in the back of your brain. It's a voice that whispers first and then keeps getting louder and louder, and that voice is saying: what if I start "my own business" as a side. You feel confident that you've been prepped your entire career for this moment, and the thing that builds the product for you with just prompting was the only missing piece in your toolbox to make you the next Fortune 500 CEO. So I started to venture around. I built a couple of tools here and there like kindnesssender or htmlblogmaker just to taste the water, and you see those are cool tools for the circle around you, and you're seen as someone different than other team members.

Then comes the moment you decide to take the leap. Going from a weekend one-page project to a full-stack multi-feature product. And that's where you face the reality. With my job hunting experience, access to this magic tool called AI, and a couple of small projects under my belt, I saw myself as a foolproof entrepreneur. So I thought, what if you build something for both job hunting and entrepreneurship? Ironically both very crowded markets, but I thought I found the perfect niche: people like me who want to stay employed and work on the side until they feel safe on one of them, then switch completely.

So I started entering the trap.
It was a cold night in the middle of winter when I opened VS Code and typed the prompt into GPT, then copy-pasted it into the VS Code file. All those agent coders came a couple of months later, so I was doing the manual labor format of coding. The prompt was: "I want to have a table to track my job application, and in the meantime I want another one to track my side hustle." That was the simple idea for Joberney, but I never knew that simple prompt would become the next 18 months of typing prompts and developing code up to 3 AM, on weekends, on vacations, and any time that I'm out of work.

It was fun for the first 3 months. But as time goes by and you go down this rabbit hole, you feel more and more lost. You can't go back up because you've put too much into it, you can't pause either. There's this insane drive that's like taking something that releases substantial dopamine in your head whenever you see your prompt turn into something real on the UI, even though you have to prompt 100 times just to fix bugs. The commitment gets to a level where you think this is it, this is what I've been dreaming of my entire life, and I just obtained the only missing piece.

But the reality is something else. You grind day and night to finish the project. You miss important events in your life, and even at work. You hope you aren't let go while you're working on the side project, but nothing in you is driving you to put everything into your career or climb the ladder. You try to do your job well, but that's it. You don't ask for promotion. You get numb and take on more projects and responsibilities without expecting anything in return, because you just want to stay employed and your head is somewhere else. And you finally launch with the hope that everyone will jump on the product, but that's where you see reality once the fog clears. You realize that as a PM, you're lacking way more important tools in your box than you thought: people who sell the product or market it, partners, connections, brand, and many other factors are involved that you hadn't thought about or cared about because you thought you knew it all. You find yourself jumping into an ocean when you had just learned to swim in a pool with max 8 feet of depth.

That's where you look back. Part of you is proud of what you've done and what you've learned. Part of you regrets the opportunities and the things you've missed. And you're left with a hard decision: keep going and take the sink or swim path, or go back to your home pool and live the rest of your life there.

I know there are still so many things to do, and there are so many other things I could have done differently, like user interviews, testing product market fit, many things in the playbook. But when you get your hands on AI and see its magic, you're like that 5-year-old kid taken to a magic show whose first move after is to beg their parents to buy them one of those magic sets. After a week or two you realize you're not a magician, and the show you watched was way bigger than a magic toy set and one week of practice.

You're in a fight between accepting that the magic was just a show, and that reality is at least 6-7 years of hard work, and you don't know whether you're ready to do it or not.

If you've made it to the end of this, I hope my experience helps you make better decisions with vibe coding, and helps you navigate the temptation of becoming the next entrepreneur who starts with VS Code and a magical box that you feed words into and watch rabbits jump out the other side. (That magical box is called AI.)

For those who took the leap and made it work, what did you have that I'm missing? For those still in the pool, what's keeping you there?

I’m a sucker for business stories, especially the ones no one tells.

If you were on a podcast, talking about your journey from grinding in the dark to that moment you finally felt “we made it”, what was that turning point?

What actually worked in the end?

I’ve recently launched my SaaS and it’s still just a dot under the internet map pin, but a friend actually used it for real not just test it as a friend. he gave a lot of great feedback, but he also genuinely loved a couple of features and was telling me how easy it made his work. Now I’m wondering what the best move is to get the most promotion out of this?? a blog? video isn’t a realistic ask. any suggestions?