- Abstractions should be deep not wide
- Some data on podcasting
- API services should always have usage Limits
- Using Python & Poetry inside Docker
- Timing
- Real vs Theoretical Engineering Productivity
- Too much documentation is harmful
- Engineering stack
- Engineering Guardrails
- VCs are anti-personas for a B2C startup
- Bad and good ways to test code
- The different layers of a web applications
- The biggest impact of ChatGPT
- Social media and burglar bars
- 5 reasons package.json doesn’t scale
- Why I prefer Obsidian for taking notes
- Low code
- React Native
- Indeterminate Progress bar is an inferior UX design
- The two-step approach to big code modifications
- Programmable Money and value capture
- Closeum – closed-source in disguise
- Startup founders: How not to write an email
- The “key” problem in cryptocurrency
- Server vs mobile development: Where the code runs matter
- Apple vs Google: Naming of flagship Android vs iPhone
- The Internet and the City Advantage
- Consumer Internet: why audio can’t be as big as text, photos, and videos
- 90% vs 99%
- When aggregation works and when it doesn’t
- The Android-Chrome merger saga
- Startup valuations
- Voice Interfaces: The Missing User Interaction Element
- File size should always be of “long” type
- Standardization
- When marketplaces work and when they don’t
- Thoughts on Tizen
- “Material design” and Google’s strategy
- Thoughts on Bitcoin (part 2)
- Internet activists, the advent of snap judgement and Internet’s permanence
- Thoughts on fixing tech recruiting
- Why Nokia’s (rumored) Android phone is doomed
- Three reasons why Intel might lose server market even faster than consumer
- Thoughts on Bitcoin
- Thoughts on Snapchat’s snafu
- FOSS (Free and Open Source Code) Licensing FAQ
- Cablegate and the aftermath: a few observations
- Nokia and the smartphone era
- The decline of Microsoft and Intel in Internet-centric Smartphone-supplemented era
Tech thoughts