A practical, tool-agnostic checklist of essential best practices for designing, building, and maintaining reliable data engineering pipelines.
A reflection on the concept of 'theoretical software engineers' and the tension between ideal best practices and pragmatic, real-world development.
Argues that politeness markers like 'please' weaken technical documentation and should be replaced with direct, actionable instructions.
A guide to writing clear and structured Git commit messages to improve code history readability and maintainability.
A humorous guide to common code review antipatterns that hinder development, written from a 'dark side' perspective.
A guide to writing effective Git commit messages, focusing on essential information and reasoning over minor stylistic details.
Argues against blindly following software development best practices, advocating for user-centric and context-specific approaches instead.
The article argues against rigid 'right vs wrong' thinking in software engineering, emphasizing context, trade-offs, and subjectivity in technical decisions.
A critique of the 'considered harmful' mindset in programming, using a popular Laravel critique as a starting point to discuss self-reflection and best practices.
A web developer argues against mocking beginners and explains the technical reasons behind a common HTML/JSX nesting issue.
Introduces the 'Code Review Pyramid' concept to prioritize important aspects like functionality and performance over style in code reviews.
A guide to crafting effective error messages for developers, focusing on context, the error itself, and mitigation steps.
Explores the three key components of effective error messages for developers: context, the error itself, and mitigation steps.
Explains fundamental software engineering principles like DRY to help developers write cleaner, more maintainable code.
A critique of blindly following software development 'best practices', arguing for more thoughtful discussion and application.
Explains the security and performance differences between Docker's COPY and ADD commands, recommending COPY for safer image builds.
Explains how to enforce test naming conventions through automated checks, ensuring consistency and acting as living documentation.
The article argues for simplicity in design and technology, using examples from film and web development to show how complexity often creates more problems.
A guide explaining four types of files you should avoid committing to a Git repository, including project-irrelevant files, generated code, libraries, and credentials.
Advocates for writing descriptive, story-like Git commit messages to improve codebase history and debugging efficiency.
