Perspectives
- Shawn West
- 22 hours ago
- 2 min read
Not everything worth writing is a how-to. Some of it is opinion, some is a field report from actually building things, and some is an honest attempt to read where the industry is going without the hype. These are the perspectives behind the practical guides — the "why we think this way" pieces, on building solo, on AI, and on making technology decisions when you don't run a tech team.
Building solo
The reality of building when you're the whole team: no QA department, no runway to waste, and every decision landing on you. The best software often starts as something the builder needed, but the graveyard of unfinished side projects is a scoping problem, not a discipline one — and staying in the game long enough for the work to matter is mostly about managing your own energy, not just your time.
AI, honestly
We've seen this pattern before. The hype, the gold rush, the utopian promises, the correction — the early web ran the same cycle, and it holds uncomfortable lessons for this AI moment. These pieces try to be grounded: what's likely real in five years, what a consolidation looks like, and why the actual bottleneck was never the technology.
Tech for people who don't run tech
You run a business, not an IT department — and the advice aimed at engineers rarely helps. These are for the founder or operator making real technology calls: what digital transformation actually means for a small business, how to choose software without a CTO to vet it, why you probably don't need an app, and how to respond when AI reshapes your industry.
Keep going
When you're ready to get concrete, the hands-on guides pick up where these leave off — Software Quality Engineering, Building LLM Applications, and Automation and Delivery. Perspective first, then the practice.