Here are a few entries from my readlog.
1. In Here’s How I Built and Launched a SaaS Company For Less Than $40k, Ryan Shank tells us how he built a SaaS product company in 6 months. Ryan describes:
- How he found a designer through Dribble (a community of designers)
- Created product requirements
- Designed deliverables
- Found a senior developer in India through Upwork
- Built and Marketed the Product
Enjoyed reading Ryan’s detailed account how a single person can build and market a SaaS product and start building a company.
2. Matt talks about a common dilemma technical founders face. In Should a CTO keep on coding? He discusses how to balance your desire to remain tech (by coding) with the need to do all the other things a founder CTO needs to do.
When you start as a technical founder, you are really a developer, quickly becoming a team lead. The team lead does leadership things but still codes and does very little management tasks. Then depending on how the company grows, usually you become a manager and now you have very little time to code.
Matt has some good advice and it was a pleasure reading the post.
3. More than one order matters was a refreshingly different article from the ones I usually read.
Order matters. In real life when you’re in a library or a city or in your kitchen. And in software development. Order, the right order, helps understanding. Where there is order orientation is easier.
Order is important but hard to create and maintain.
Order is helpful, even important. But often order is hard to create and/or to maintain. Why’s that? What’s order anyway?
“What kind of order does software need?” is a great read, if you are building software.
