Read on Twitter
In the past 18 months, I went from being just an HTML/CSS designer to learning full stack development to launching two SaaS products with a modest but growing batch of paying customers.
A few things I learned:
A few things I learned:
Having been at this bootstrapped business thing for over a decade, I see the value in being able to design, build & ship any idea “at will”.
As much as I felt like backend dev was/is “over my head”, this goal drove me to keep at it.
As much as I felt like backend dev was/is “over my head”, this goal drove me to keep at it.
The key was being able to devote full-time hours and focus to this goal.
Having built a productized service business and optimized it to run without me in the day-to-day made this possible for me.
Having built a productized service business and optimized it to run without me in the day-to-day made this possible for me.
I decided early on to commit to a “tried and true” stack rather than a “hot and trendy” one. I landed on Ruby on Rails.
Mature framework features, huge community, tons of educational resources.
Mature framework features, huge community, tons of educational resources.
You’ll need to get through some “101” courses and books to learn what’s what. But these only scratch the surface.
Real learning begins once you try to build real products.
Start trying *before* you feel like you’re ready.
Real learning begins once you try to build real products.
Start trying *before* you feel like you’re ready.
As soon as you can build basic stuff, make sure you learn how to write tests—then aim for close to full test coverage on everything.
It adds time and heachache, but immensely worth it as your codebase grows.
It adds time and heachache, but immensely worth it as your codebase grows.
Leverage your non-dev skills to make you a better developer.
MVP approach (can this code be simpler?)
Talk to customers (will building this solve someone’s problem?)
Focus on design (is this how users expect this to work?)
MVP approach (can this code be simpler?)
Talk to customers (will building this solve someone’s problem?)
Focus on design (is this how users expect this to work?)
Newbies like us have a hard time remembering basic syntax/processes.
Document your own cheat sheets for frequently used commands, new project setups, etc. so that your “noobness” doesn’t slow you down.
Document your own cheat sheets for frequently used commands, new project setups, etc. so that your “noobness” doesn’t slow you down.
As you do more projects, try and stick with more/less the same stack and implementations. Makes it a lot easier/faster to reuse stuff from project to project.
Work with mentors. Pay someone. Ask friends for help and advice. Pair program.
Books and courses can’t provide what a pro’s real-world experience can.
This has been huge for me, but I should be seeking more of this.
Books and courses can’t provide what a pro’s real-world experience can.
This has been huge for me, but I should be seeking more of this.
It’s a super power. Have fun :)
