Everyone and their dog is building a SaaS right now.
Can they scale it? Secure it? Fix it at 2 AM?
AI closed the gap on writing code. It didn't close the gap on building software that lasts.
20+ years in the game. I don't need to know your industry. You do.
You bring the knowledge. I'll bring the engineering. Let's partner. DM me.
Vibe coding was fun until I realized that everyone could put out the same product in a weekend.
There's no edge unless you already have customers or other products with an established user base.
Now I'm focused on building solutions around the domain knowledge I've gathered while working for several different clients in the past.
All of it, and AI actually helped me develop new skills. I’ve been a software dev for years. Can’t “vibe code” apps-in-a-weekend using c#, so I picked up some TS skills.
I wasn’t out there building apps as a side-hustle, so I never needed social media…and here I am - with my 46 followers.
@Raynerdtech Eventually, yes.
Immediately, no.
Nothing is stopping the vibe coder from reviewing and understanding the code, and then diving deeper into software development.
@maheshnani122 Have to keep building. But that first product (or first 3, like me) are the dopamine hit. The next products need to be really thought out and validated.
I started building what I thought was cool/fun. After 0 users and $0 MRR, that dopamine has worn off.
The SDLC used to be:
Requirements > Design > Build > Test > Deploy > Maintain
Now it's:
Idea > Prompt > Ship > Prompt > Ship again
We went from 6-month release cycles to 6-hour release cycles. The process didn't shrink. The human bottleneck did.
The devs who survive this aren't the fastest coders. They're the ones who still know WHY something should be built before asking AI to build it.
Requirements gathering didn't die. It just stopped being optional.
@feifei_qiu Those are the worst ones...
...but good for foundermetrics 🤣😅. You can always resurrect the project later.
Hmm, would it be a zombie project then? 🤔
@feifei_qiu It started off as a fun project to see how many "graves" we could get going across the world.
Seems like everyone has ideas these days, and I highly doubt all are still up and running.
If you've had any ideas fail, add a few to the map 😉
Old school devs, show your age. Name some books that shaped your career:
I'll start (in no particular order):
1. Clean Code: A Handbook of Agile Software Craftsmanship
2. UML Distilled: A Brief Guide to the Standard Object Modeling Language
3. Working Effectively with Legacy Code
4. Design Patterns: Elements of Reusable Object-Oriented Software
5. Domain-Driven Design: Tackling Complexity in the Heart of Software
6. Patterns of Enterprise Application Architecture
Bonus:
Raise your hand if you've ever modeled with UML 🙋♂️