Solo Web Dev

Solo Web Dev

@solowebdev.bsky.social

Software dev with decades of experience but still working on building my own thing. I’ll never be completely happy until I’m running my own successful business. Personal freedom is my goal. Building https://www.runbooky.com

400 followers1.6K following114 posts

Pinned

After years of failed startup ideas, I tried something different. Instead of building on a hunch, I let AI run a full market analysis to find a validated problem worth solving. Here's what I learned and how you might do the same. #buildinpublic

I’m a checklist kind of person, so to keep me motivated with my side project I hooked AI up to Linear and fed it my project plan (also created by AI). It created projects and tasks for me in the right order, and broke them up by day. It’s super motivating to be able to check a few off each day!

A work colleague and I re-purposed a work meeting that nobody else showed up to, to vent about some frustrating stuff going on lately. Meanwhile, Gemini was dutifully recording and summarizing everything we said… and sent to all participants at the end 🤦‍♂️ Luckily it wasn’t too bad, but be careful!

After years of failed startup ideas, I tried something different. Instead of building on a hunch, I let AI run a full market analysis to find a validated problem worth solving. Here's what I learned and how you might do the same. #buildinpublic

View full thread

If you're stuck on what to build, try this approach. Let AI do the heavy research -- but push it hard. Ask for sources. Validate technical feasibility. Check legal risks. Make it earn your confidence. Then build with conviction. I'll be posting updates as I go!

After years of failed startup ideas, I tried something different. Instead of building on a hunch, I let AI run a full market analysis to find a validated problem worth solving. Here's what I learned and how you might do the same. #buildinpublic

View full thread

Am I 100% certain this will work? No. This isn't a slam dunk. But I'm more confident than I've ever been starting something new. The research is solid, the problem is real, and I've personally felt the pain. That's as good as it gets before you start building.

After years of failed startup ideas, I tried something different. Instead of building on a hunch, I let AI run a full market analysis to find a validated problem worth solving. Here's what I learned and how you might do the same. #buildinpublic

View full thread

The data was compelling: $9,000/minute average downtime cost, $3.3B TAM, and most importantly -- Reddit full of engineers asking "Does anyone have a tool for this?" The problem wasn't theoretical. It was validated by real people with real pain.

Could I have done all this research myself? Sure. But it would've taken weeks, and I would've brought my own biases. I would've hit dead ends and convinced myself to ignore red flags. The AI did it in hours, objectively, and without attachment to any outcome.

After years of failed startup ideas, I tried something different. Instead of building on a hunch, I let AI run a full market analysis to find a validated problem worth solving. Here's what I learned and how you might do the same. #buildinpublic

View full thread

Next question: "Why wouldn't a big company like Atlassian just build this?" The AI explained the Innovator's Dilemma: the market is too small for them to care ($5-10M is life-changing for me, a rounding error for them), and their platforms are too horizontal.

I also asked about pricing strategy. Should it be per-user? Per-integration? Usage-based? The AI analyzed competitor pricing, researched willingness-to-pay studies, and explained why usage-based pricing creates perverse incentives for this product.

After years of failed startup ideas, I tried something different. Instead of building on a hunch, I let AI run a full market analysis to find a validated problem worth solving. Here's what I learned and how you might do the same. #buildinpublic

View full thread

But I didn't stop there. I asked: "Is this even technically feasible?" The AI researched GitHub, Notion, and Confluence APIs -- rate limits, webhooks, authentication. It came back with a full technical feasibility report. Answer: Yes, very feasible.

Then: "Would this violate any Terms of Service?" It analyzed GitHub's Developer Agreement, Notion's API Terms, Atlassian's policies. Found precedents like Glean and Raycast. Verdict: Low risk, as long as you use official APIs and respect data deletion.

After years of failed startup ideas, I tried something different. Instead of building on a hunch, I let AI run a full market analysis to find a validated problem worth solving. Here's what I learned and how you might do the same. #buildinpublic

View full thread

That was actually reassuring. It wasn't just telling me what I wanted to hear. It was giving it to me straight. And that's the benefit of this approach -- no ego, no confirmation bias, just cold, hard research.

One idea kept surfacing: runbook discovery for on-call engineers. The AI found Reddit threads like "Senior SRE who knew all our incident procedures just left -- now we're screwed" and G2 reviews complaining about scattered documentation.

After years of failed startup ideas, I tried something different. Instead of building on a hunch, I let AI run a full market analysis to find a validated problem worth solving. Here's what I learned and how you might do the same. #buildinpublic

View full thread

The AI came back with 7 initial ideas. But I didn't just pick one. I asked it to validate each with real evidence: Reddit threads, G2 reviews, market data. It provided actual links -- not vague claims. I could verify everything myself.

Here's the thing: I had my own ideas too. I pitched a few to the AI, expecting it to validate them. Instead, it shot them down hard. Explained why the market was too crowded, why the problem wasn't painful enough, why I'd struggle to compete.

After years of failed startup ideas, I tried something different. Instead of building on a hunch, I let AI run a full market analysis to find a validated problem worth solving. Here's what I learned and how you might do the same. #buildinpublic

First, a caveat: ChatGPT won't cut it for this. You need an AI that can independently research the web, pull real sources, and come back with evidence -- not just confident-sounding hallucinations. I used Manus AI and gladly paid the $40/month for this.

My initial prompt was simple: "I'm a Ruby developer who wants to build a B2B SaaS. Analyze potential opportunities, validate market need, and recommend ideas with real pain points." Then I pushed it to go deeper on each recommendation.

Last week I put in 70 hours of work (excluding working through the previous weekend) because it was literally the only way to meet an insane timeline. I was hoping that it was a one-time slog that would cause things to get better. Instead, they just want more of the same with unrealistic deadlines.

View full thread

This left me with zero time for my indie hacking, which left me even more frustrated and drained. Something inside me broke. No more pouring my heart into my day job. All they’ll get from me now is an hours-for-dollars trade. No more “above and beyond”. This is how innovation (for them) dies.

Last week I put in 70 hours of work (excluding working through the previous weekend) because it was literally the only way to meet an insane timeline. I was hoping that it was a one-time slog that would cause things to get better. Instead, they just want more of the same with unrealistic deadlines.

I don’t want praise or a shout out. I want leadership to make a change so that it never happens again. Instead what I got was hinting that it was my problem for not setting boundaries. How am I supposed to do that when the guy that signs my check is asking for these deadlines?

One interesting takeaway for me is that I’m grateful for the salary I currently have. I had a feeling that I was paid higher that the typical salary for my position, but this confirms it with more than anecdotal data

Solo Web Dev@solowebdev.bsky.social

Can I get your brutally honest opinion of my POC? Is it useful enough to be exciting to you? Why or why not? Especially if you are a software engineer or manager, I would love your feedback, whether good or bad! #buildinpublic dgaxik927ls9y.cloudfront.net

View full thread

What I’m trying to confirm is whether this is: A) Sort of interesting in a passive way, as in you look at it once and move on with your life Or B) Interesting and useful enough to be something you would come back to periodically and share with your friends/co-workers

The best code is no code at all. If you must write code, keep it as simple (architecturally and syntactically) as possible. The fewer lines of [readable/maintainable] code, the better.

Took the last week off to relax and have fun for a bit. My idea of fun: hacking on a new idea I was so excited about that I couldn’t sleep last Friday night. Got to play around with a bunch of new (to me) AWS tech and architecture. It’s going to be really hard going back to my normal job next week.

How do I silence these voices in my head that tell me that the new idea I just thought of would be way more fun or successful than the one I’m already working on? It’s a vicious cycle.

Finally getting past my old guy “get off my lawn” attitude with AI. My teenage daughter is getting into coding, and I have a feeling I need to nudge her toward working closely and fluidly with AI instead of treating it as a simple nice-to-have bonus tool.

Solo Web Dev reposted

In 5 years, you’ll disagree with some of the things you currently believe. And you’ll know things that right now you don’t even know you don’t know. So, be more open to new ideas — one of those revelations might be happing right now.

I went a little crazy following a bunch of interesting tech and indie startup starter packs, but now my feed is instantly overflowing with all the stuff I love to read. So cool! I already don’t miss or feel nostalgic for that other place

Solo Web Dev reposted

Bluesky now has over 20M people!! 🎉 We've been adding over a million users per day for the last few days. To celebrate, here are 20 fun facts about Bluesky:

My advice for anyone who feels like they don’t have a good grasp on design patterns: just search “<your favorite language> <specific design pattern you want to learn better>” (for example “ruby factory design pattern”) on YouTube.