Explains the value of Architecture Decision Records (ADRs) for documenting technical choices and fostering a collaborative engineering culture.
A software developer discusses the importance of over-explaining requirements and details in development to avoid misunderstandings and ensure desired outcomes.
The original Django Book from 2006 is now available again online at DjangoBook.com, restored using modern AI tools.
Learn to auto-generate architecture diagrams and docs for .NET Aspire projects using GitHub Copilot, Mermaid, and AI agents.
Explains Architecture Decision Records (ADRs), their structure, and their importance for documenting key technical decisions in software projects.
Practical tips for writing technical documentation that is optimized for LLM question-answering tools, improving developer experience.
Argues that pull requests are a valuable form of documentation, capturing the 'why' and context behind code changes for future developers.
A senior software engineer shares key lessons from 20,000 hours of experience, covering learning, code quality, and career growth.
A guide on defining your target audience for technical documentation and books to create focused and effective writing.
Explores using Asciidoctor to write and maintain technical documentation alongside source code, comparing it to wikis and markdown.
A software engineer shares essential skills like documentation, clean code, and code review not taught in a Computer Science Masters program.
A guide outlining the responsibilities and expectations for a Project Lead role in a software development team, including planning, execution, and launch phases.
A guide to writing effective technical documentation that teaches users, not just tells them, focusing on programming languages and libraries.
Clarifies the correct Oracle support portal URL for accessing Metalink 3 service requests to avoid errors.
