Phil Stőck

@codealicja Awesome advice. I don't like Reddit though 😕

distribution tips for early SaaS founders: → find where your customer complains before you build → reply to 10 relevant reddit threads daily → cold email people who just complained about your competitor do this for 30 days before touching your product.

Busted my Codex credits this morning. Experiencing with Composer 2.5 in Cursor. Currently, Composer seems superior to gpt 5.4 Anyone has experienced both?

@lovestolead I can't shut by brain off. A Buddhist monk once said we are addicted to our internal tchatter. Meditation seems to be the antidote. Have you tried?

On a plane right now. Normally I am asleep before takeoff. I can’t sleep this AM. Keep thinking about things to build, improve, launch or how to improve distribution. How do you shut your brain off? Can you? Is this a bug or a feature? 😂🤔 #buildinpublic #irl #morningthoughts

@EnidPinxit Out of curiosity, which Agent platform or harness are you using to build this type of relationship?

People can say what they want about Ai and Agents but my life and friend connections just keep getting better the deeper into this tech and lifestyle I get. ✨ GRATITUDE!!! ✨🤝🙏🔥💕

I don't understand this point. For the past 3 months, I've tried to use local LLMs to generate code through Hermes, adapt to Codex CLI, and my research led me to understand that if you let them just use a terminal, they'll just break at some point in time. What do you know that I don't know?

@Yeshua_tree this is why I will never pay for AI. Open weight models that I can run locally have ALWAYS worked better for me.

OH MY GOD! Claude is NOT A GOOD MODEL. About a week ago, I had a local open weight model set up my neovim config for PHP development (linting, dap, lsp, etc) - it was perfect. Tonight I asked Claude to change ONE THING! And since I asked that, the entire config is broken, and it can't seem to get it back to where we were when we started... This is SECOND TIME Claude has fucked a codebase. This is only config, sure. But, WHO IS USING THIS and claiming to be successful?

@consoleloglifee What is your project Batman?

5 June — Today's Plan 👨‍💻🔥 ⚡ LeetCode grind 🎨 Continue working on the project 🐛 Fix the bugs that have been bullying me for the last two days 💀 #buildinpublic #100DaysOfCode #leetcode #coding #programming #webdevelopment #developers #devlife #javascript

I think growth is found at the frontier between what we know and what we don't know. And one who chooses to spend time there will inevitably grow. And if we can be comfortable with being uncomfortable, this event horizon of ours will become more bearable.

Thanks for your input! 😃 Yeah. It took me a while to realize that we were constantly making the foundation more and more robust. The thing we were missing was clear milestones toward the end goal. That's on me! We started with a somewhat vague (or wishful) goal, so Codex improvised his way up. Now that we've defined a 5 milestones journey with clear deliverable, it now knows how to get there. Let see if I get this right! 😂

@PhilShteuck haha true, receipts are cute for debugging, but the real moonshot is getting it to compose entire systems, printers can wait.

Today we learned that IntentForge is no longer just trying to generate code. It is trying to generate code with receipts. Now we need to spend less time improving the receipt printer and more time making it build bigger things.

@alexabelonix @atypica_AI Awesome value proposition Alex! Your sales' skills are on fire! 🔥

I got 50+ warm leads for my MVP before launch. And no, the trick was not posting more or randomly DMing half of X One thing that helped: I used @atypica_AI as pre-sales research before jumping into real calls 1. I started building the product, code, workflows, BPMN models, the whole messy founder cave experience 2. Then somewhere in the middle of building I had the annoying realization: > the MVP is not the business > Distribution is 3. So I started looking at the build-in-public community and honestly, I kept seeing the same thing over and over again > Founders build. > They post updates. > They get some likes. > Then they have no idea how to turn attention into pipeline. 4. I think a lot of founders get sales wrong. Sales is understanding the right person so well that your product starts sounding obvious to them. > What do they want? > What are they afraid of? > What would make them say no? > What do they need to hear to feel safe enough to say yes? 5. That’s why I tested @atypica_AI I used it to create AI personas around my ICP and interview them before real sales calls. It helped me see the stuff founders usually discover too late: > surface objections > hidden fears > deal-breakers > trust triggers > buying criteria > jobs-to-be-done Before you waste 20 calls guessing what your customer thinks, run the research first. You can test it with free signup credits here: atypica.ai/?via=alexa

Alright. I'm now 27 hours in, and Codex tells me we might have for another 20 hours before having a serious V1 that can generate 5 types of python apps. 😂 I'm already down to 36% of my weekly credits that will renew only next Wednesday. 😭

Codex has been cooking my Patch VM for 13h now. It seems I'll need another 13 to get where we want! 😂 That's slow cooked software. Soft to the bone.

@RealProductGirl Thanks for the link. I'm AltSens on Discord. Looking forward to contribute there as well.

@PhilShteuck PS...are you in our discord discord.gg/yCZajs2e8V

Okay so some of my favorite trolls (you know EXACTLY who you are 🤣) tried to pick apart a post that I polished with AI because I sometimes have a hard time expressing in my mind what I want to say. So what are everyone's thoughts on this? Do you leverage AI to make sure your thoughts can be processed or grammar are accurate? And to my trolls... I love you genuinely. You keep me sharp. ❤️

@RealProductGirl My pleasure. Keep on going, always enjoying reading you. 💪

@PhilShteuck Following you for this! Truly appreciate this. I'm just trying to make sure what I write in my head makes sense. I always respond with myself.

Programming is dead. 😂 I haven’t written a real line of code in 6-7 months. AI just does the typing while I sit back like a retired emperor. Companies are slashing jobs left and right (shoutout to that 65% YoY cut report), but Software Engineering? Still very much alive. The new flex isn’t "vibe coding". It’s mastering AI systems — building agents, RAG, guardrails, the whole stack. Combine that with real architecture and domain knowledge and you become indispensable. Yeah, there’s pain and energy bills that’ll make your GPU cry… but abundance mindset: this tech is birthing dozens of jobs we can’t even name yet. Elevator operators didn’t disappear into the void — they just got better gigs. Same here. Adapt or become legacy code.

Tech jobs experience a 65% increase in job cuts vs last year. Not looking good.

@SahilPanhotra You sometimes need to dumb things down to succeed. 🤷‍♂️

why do some of the smartest people you know struggle to make money?

Back in the days, applications were mostly monolithic and for desktop (local). Cloud has initiated the concept of micro-services, bringing more complexity to both discipline. Is fullstack developper even a thing?

@_andrewthecoder @IamAroke Back in the days, applications were mostly monolithic and for desktop (local). Cloud has initiated the concept of micro-services, bringing more complexity to both discipline. Is fullstack developper even a thing?

@IamAroke I don't even know what those words mean anymore. When I started, I had to do both. I was handed a design, and I had to make something that looked like that design. Back then, "backend" meant database stuff.

Who's going to tell frontend developers that backend developers does the hard part?

@consoleloglifee If it ain't broken, don't fix it. - A guy who broke things that were working 😂

4 June ✅ ⚡ LeetCode done 🎨 Vibe-coded a project and got the main version ready quickly 🐛 Decided to spend the rest of the day personally ruining my own progress by fighting bugs 😭💀 Couldn't finish it today. #buildinpublic #leetcode #coding #debugging #webdevelopment

@markpekel Absolutely, roommates come with their fair share of baggage 🧳

@PhilShteuck Fair point! The key is hitting these milestones. Although, you have to admit, roommates do bring their shit with them, right? :P And a video games are such a great example, if you're not engaged from the first second, you're gone after a minute! Awesome answer, thanks!

When I leaned down to collect my dog's "morning deposit" on my neighbor's grass today, I realized... Most SaaS teams in startups, solo founders, and builders, treat onboarding like a checklist. ✅✅☑️☑️☑️ That's wrong, and it's killing onboarding my friends. You see, I don't know where my dog will “powder his nose” next, but I have to give him some options and make sure he does it, because the alternative is landing on my carpet. So we go on a walk. Onboarding, on a high level, is actually "retention negotiation." Or in this context, taking your customers/users… on a walk. The window is usually the first 7-days, although those who miss day 1 tend not to progress. Now let's ask the real question here. What do you want to see on those 7 days? Day 1 → Can they import their data while reaching an aha moment, and do that without rage-quitting? Old yeller calls it, the firehose moment. 🐕‍🦺 Day 3 → Do they see their first “holy shit this works” moment? At this point, Lassie "Wow," should I come home? 🏡 Day 7 → Can they explain your product to their team? And B-i-n-g-o was his name... o. 🐶 Miss any of these is embarrassing, like forgetting to take that little plastic poo bag. My neighbor didn't like that.

@sans_builds @laurencebuilds Well said. 💪

@laurencebuilds Some of the best decisions I made felt uncomfortable at the time because I could not see the full picture yet. Looking back, confidence came from moving forward, not from having all the answers first!

Founders often have to make decisions before they feel ready. The timing is imperfect. The information is incomplete. The direction still has doubts around it. But waiting until everything feels certain can keep you stuck. You choose the next step and carry the responsibility that comes with it.