A software engineer shares essential skills like documentation, clean code, and code review not taught in a Computer Science Masters program.
A software developer draws parallels between keeping a clean kitchen bench in cooking and maintaining a tidy codebase and workstation for better productivity.
Applying digital minimalism principles to software development to reduce clutter, optimize code, and improve maintainability.
A developer argues that writing 'dirty code' is acceptable and beneficial in certain situations to overcome blocks and foster creativity.
A developer shares 10 frequently violated clean code principles, covering naming, comments, duplication, and formatting.
A detailed case study on refactoring a JavaScript function for handling API responses, focusing on reducing cognitive load and improving maintainability.
A guide to building a reusable JavaScript validator service to clean up data validation logic and adhere to DRY and SRP principles.
A guide to writing clean, readable code by using clear and explanatory function naming conventions, inspired by Shakespeare's prose.
Explores best practices for writing clean, small, and maintainable functions in JavaScript to improve code quality and reduce complexity.
A talk arguing for the importance of code comments, debunking common arguments against them and providing a framework for effective commenting.
Analyzes the time investment and value of code comments, covering initial writing and maintenance costs versus long-term benefits.
A developer argues against committing commented-out code, explaining why it harms code readability and maintainability.
A detailed categorization of code comments, exploring their types, maintenance, location, and alternatives to improve code clarity.
An interview discussing the importance and ongoing debate around commenting code, challenging the 'comments are a failure' clean code perspective.
Applies the 'keep your bench clean' principle from cooking to software development, emphasizing clean code, atomic commits, and removing unused code.
A developer argues for the importance of clean, high-quality code comments and clarifies their relationship to documentation.
A passionate rant arguing for the importance of writing clear comments in code, even when the code itself is well-structured and 'self-documenting'.
A programming article advocating for structuring code like a newspaper, with the most important information at the top for better readability.
Analyzes the debate between using single vs. multiple return statements in methods, focusing on readability and modern coding practices.
A review of the 'Systems' chapter from Robert C. Martin's 'Clean Code', covering principles like DI, AOP, and incremental design.
