Misc

In teams of one to three people, continuity depends less on role separation and more on shared understanding, document granularity, and records that let the work be handed over when necessary.

A practical perspective on risk, contracts, and expectations when taking development work alone or in very small teams.

I do not follow development methodologies rigidly. Some environments break them entirely. What actually moves projects forward is adapting to the real constraints in front of you, not applying theory.

Solo development does not fail because of design alone. It fails when the shared understanding of what to build drifts. Use cases are the simplest and most effective tool to prevent that.

AI coding agents are useful, but they work from narrow context rather than stable architectural intent. That makes software design and compact feature boundaries more important, not less.

A practical reflection on how I use ChatGPT, Codex, and Copilot to design first, code second, and reduce the risk of AI-driven development.

A personal reflection on how ChatGPT, Copilot, and AI coding agents changed my workflow and why they may also change the structure of software development teams.

A practical account of the real implementation and maintenance problems I ran into while using AI agents for internal business system development.

A practical reflection on how AI changed my daily work, why coding agents raise both productivity and risk, and why design matters even more now.

A reflective analysis of how responsibility, incentives, team structure, and testing realities shape large development work in the Japanese-style contract engineering services model.