Boris Tane

> consensus best practice I'm not sure I agree with this. I don't think there needs to be a whole spec & documentation process before plan mode. There is alternative thought leadership that the waterfall approach for building out projects is not the right Agentic pattern[1]. Planning itself can be such an intensive process where you're designing and figuring out the specs on the fly in a focused manner for the thing the agent will actually develop next. Not sure how useful it is to go beyond this in terms of specs that live outside of the Agentic loop for what should be developed now and next. I've evolved my own process, originally from plain Claude Code to Claude Code with heavy spec integrated capabilities. However, that became a burden for me: a lot of contextual drift in those documents and then self managing & orchestrating of Claude Code over those documents. I've since reoriented myself to base Claude Code with a fairly high-level effort specific to ad-hoc planning sessions. Sometimes the plans will revolve around specific GitHub issues or feature requests in the ticketing system, but that's about it. [1] https://boristane.com/blog/the-software-development-lifecycle-is-dead/

The beginnings of that sustainable approach is already out there: https://boristane.com/blog/how-i-use-claude-code/

I'd been using this workflow for a while, but this post I found on HN a couple of weeks ago really solidified it: https://boristane.com/blog/how-i-use-claude-code/ > The workflow I’m going to describe has one core principle: never let Claude write code until you’ve reviewed and approved a written plan. This separation of planning and execution is the single most important thing I do. It prevents wasted effort, keeps me in control of architecture decisions, and produces significantly better results with minimal token usage than jumping straight to code.

I use the same approach, derived off of https://boristane.com/blog/how-i-use-claude-code/.

- you most certainly also wanna read this one https://boristane.com/blog/the-software-development-lifecycle-is-dead/

I think it was edited with an LLM - the voice flits from human to bot but various tells are present. The heterogeneity of sentence structure is the clearest signal. Here’s an older article from the author from 2024: https://boristane.com/blog/learnings-from-starting-building-and-exitin…

The author wrote about the topic before: https://boristane.com/blog/observability-wide-events-101/ He used to work for https://baselime.io/ which was aquired by Cloudflare.

Really? Cloudflare isn't solely a CDN anymore. CDN and DDOS-protection were the most logical "first" products to build based on their SDN ( Software Defined Networking). A cloud is the next thing and there's a lot of money involved with the cloud. I see them as the only real competitor/challenger to Azure, AWS, GCE, ... because they aren't bound to regions ( less DevOps) For example, what you might not know about Durable Objects => https://boristane.com/blog/what-are-cloudflare-durable-objects/