Random Nuggets from the Tech Playground
I’m sharing a compilation of insights I’ve gathered from my [little] time in the tech industry. While these started as personal reminders, I believe they’re worth sharing. And although they are rooted in tech, they apply across many fields:
-
You don’t have to be perfect to get a job. You need to be able to solve problems, build a solution and ship it as a product. This skill is what will always be in demand.
-
A startup is more stressful than a big company. In the beginning of your career, that might be advantageous as it builds your stress tolerance. Remember, you’re building yourself to excel for as long as possible.
-
Your idea doesn’t have to be perfect before you chase it. Ideas are like books. You get to understand them better as you read (work on) them.
-
You can launch with a working product without it having the best tech stack or tools. People need you to deliver value not a framework debate.
-
Tech stacks are only useful in the sense that they make you build your idea. Use tested and trusted stacks with large communities as you start. It’s easier to meet like-minded people that way and get help. Conversely, if you’re more interested in working at the cutting-edge and having the potential to carve new ideas on the tech stacks as you build your product, go for something novel. The trade-off will be your time to shipping ratio.
-
The character of the people you’re working with will always remain the best predictor of the project’s success rather than just raw technical skills. Great human beings will shine anywhere, eventually.
-
The people that will decide your product’s trajectory are mostly non-technical - business leaders and customers. Having solid communication skills is the only way to bring them on your side. They won’t get convinced by hearing about how your backups are sharded using distributed auto-schedulers. Telling them their data is always safe might get it done.
-
Big management teams are usually not helpful. Key is having a visionary leader who trusts his colleagues. This is very important. Trust.
-
Titles are not important. Responsibilities are. Optimize for that.
-
Money is not the most important thing, but is the most useful tool. Resources are vital. Belief and discipline are most vital. Belief for optimism. Discipline for realism (you don’t feel great everyday).
-
A work schedule is mostly pointless. Optimize for delivery instead.
-
Collaborate with other companies and businesses. Don’t compete with them. It will mostly cost you. Help them to help you. Win-win.
-
Getting it to work is the first step. Getting it to work fine is the goal. This is the difference between a prototype and a product.