#ai-coding

Here's how I use the dangerous flag safely:

1. Environment Isolation For greenfield projects or major changes, I work in isolated environments. You can set up a simple Docker container specifically for Claude development:

This gives Claude a safe sandbox to work in without risking your main system. Because I love using Makefiles, here is the one I use for essential tasks:

2. Task Scoping The quality of your results depends entirely on how well you scope the initial task. Compare these approaches:

Bad: "Build me a financial analysis system"

Good: "Build me a financial data aggregator that does A, B, and C. Look in these specific files, follow this expected flow, create tests that validate each iteration you make, ensure changes are small and incremental."

3. Sensitive Data Precautions Never use the dangerous flag in directories containing:

API keys or secrets Production configuration files Important datasets without backups System configuration files 4. Review Strategy For longer autonomous runs, I often ask Claude to create documentation or a changelog as it works. This makes the post-work review much more manageable.

Some interesting subtle things he ever so briefly mentions that I think are notable:

• "Everybody uses all the products": This translates to each person deeply knows what each product does, it's use cases and how users use each product because they are users of the product. He mentioned this in the context of "developers just commit to other products" - They will just download the repo and submit a PR. He mentions the value of Claude in that process, which I know it is, but takes for granted the value of knowing the product.
• While I'm sure these products have complex coding challenges, they're all well defined and narrowly scoped. I think it's much harder to describe a complex application or set of applications using proprietary services with sometimes odd design choices, and integrating with external proprietary services. With that said, I find AI to be exceptional at helping to understand complex code across many services and frontend components - maybe even more valuable than writing the code. However, it still is non-trivial. It also doesn't help with knowing what to build for your customer.