How to learn software for startups (I will not promote)

[u/ssbprofound]

Hey all,

Undergrad engineer here. I've picked up Web Scalability for Startup Engineers and the Phoenix Project.

My motive isn't to drop out to start a company, but to get good at software for startups (as opposed to being a magnificent seven SWE, for example).

I've 'learned to code,' but not yet in the context of startups. My hypothesis is that I need to understand how to bridge this with sales, finance, marketing, not just go deeper into CS (though I don't understand what happened with something like Google).

For those who have worked on software for startups: if you're not working directly in / on one, what has been helpful for developing this understanding?

Thanks!

[u/oudeismetis]

Come up with a small idea (even a copy of an existing one). Then build it to completion. It doesn't have to make money or be used by anyone. But you need to see it through to completion and it should feel complete.

Then repeat that several times.

Get a feel for how hard that is. Things are always harder and take longer than you think. Learn how to descope and simplify. A finished single feature is better than 3 half finished ones.

Start experimenting with starting and finishing your own ideas (again, keep things tiny and small. Don't bite off too much).

Then start to experiment with getting real people to use these things you've built. Start with family and friends. Practice talking about your ideas and responding positively to negative feedback.

There is more, but I think this is a good roadmap that an engineer could do on their own. Don't worry about doing the above perfectly. Just live in the struggle and learn to get comfortable with small failures and feeling uncomfortable. Those are like weight lifting reps to strengthen your engineering mind for startup life.

[u/Swimming_Release_577 → u/oudeismetis]

Couldn't agree more. I've mentored beginners who know coding fundamentals but get completely stuck on a real project.

That full-cycle experience—from requirements and setup to debugging and deployment—is a totally different skill set than just "learning to code." It's something you only truly grasp after finishing that loop a few times yourself. Great advice!

[u/ice0rb]

Hey.

Startup engineer and former (long time ago) founder (and former big tech intern). Recently worked with two Stanford grads to raise 40M.

Startups look for a few things. The most important of which is an insane passion and drive to work really, realy hard. It's basically two things: raw intellect, and pure drive. Of course, the goal is that you're technically knowledgable in the area they need help in, too. But that's second to the first two. They just want to know you'll get shit done.

They're essentially asking you to match their rate of change-- their slope, not necessarily meet them at an intercept and fall off when you can't keep up.

But to be frank with you, I don't necessarily think all startups are great places to be. A lot of them are gonna just make you 60+ hours a week with no recourse and little upside when they go under. You will learn a lot, but don't expect much learning/mentorship, more: figure this out yourself, we're too busy for you.

[u/AmILukeQuestionMark]

Try to put together something with one feature that works fantastically well, and run it past your target audience.

Create discussions and leave it free so they're more patient with you in the beginning for you figuring it all out.

I'm on my 5th idea and nothing yet has stuck. There's lots of good indie hackers out there like Marc Lou you could learn from.