View on Substack
I’m your average mid-twenties software engineer whom, in the past couple years, managed to find himself in a director of engineering role at a crypto startup.
My personal hobbies have nothing to do with tech. I love to do anything & everything active. I’m an avid weightlifter and try to mix things up from time to time with boxing and hiking.
Today, I decided that I want to start a blog.
The Why
I generally don’t like to read articles related to software / tech. I find that existing content typically have low information-to-word ratios. This blog will attempt to challenge the status quo by attempting to deliver the most information in the fewest words possible.
That’s the value prop for you, the reader. However, I’d be lying if I were to say that this blog serves me no benefit. You can freely skip the rest of this section if you don’t care.
As someone who manages multiple people in a fast-moving startup, I’m bombarded with inputs and spend my days making decisions for myself and on behalf of others. I characterize this as “high frequency” work. Taking time to write these blogs is an opportunity for myself to consolidate my thoughts and derive insights from my otherwise hectic life.
To help achieve this goal, I’m taking the opposite approach from the content writers of the post-ChatGPT world by not consulting AI for content. The only exception to this rule is the AI-generated tl;dr’s that I will include with each article, which is done only as an experiment to see the evolving summarization capabilities of the latest LLM’s.
The How & What
This isn’t going to be a “tutorial” based blog. Nor is this going to focus on a particular realm of software engineering. Expect an amalgamation of:
- Deep-dives on technical topics across the software engineering stack (on anything from mobile to smart contract development)
- Reflections on my experiences with team management and product strategy (specifically in the crypto space)
- General thoughts on the state of the industry and cutting-edge technology
I want each article to be insightful (so that you benefit by gaining knowledge) but never drudgingly academic (so it doesn’t feel like you’re reading a textbook).
That’s a Wrap
If you’re reading this soon after the article is published, then I hope that you’ll come along for the ride. If you’re reading this in hindsight, then I hope that this gives you insight into my motivations and thought processes 🙂.
See you in the next one.
Top comments (0)