Parameterized Tests in JUnit 5
A guide to using parameterized tests in JUnit 5, including code examples and a demo repository.
A guide to using parameterized tests in JUnit 5, including code examples and a demo repository.
A guest post about productivity and 'getting the gist' of topics without becoming an expert, featured on 'Human and the machine'.
A guide for developers on how to start contributing to open source projects, covering finding projects, selecting issues, and open source etiquette.
A developer shares personal git tips, branching strategies, and best practices for efficient version control workflows.
A reflection on teaching basic cryptography to children, highlighting the importance of usable security through historical ciphers like the rail fence and Caesar cipher.
A guide to disciplined C programming, emphasizing maintainability, simplicity, and avoiding dangerous patterns for writing robust code.
A review of 'The Pragmatic Programmer' book, assessing its timeless principles and relevance in modern software development.
A guide for developers on using personal side projects to learn new technologies, practice skills, and stay current in the fast-paced tech industry.
A developer critiques two flawed technical hiring tests, analyzing C trivia and a C# coding challenge, highlighting issues with time limits and scoring.
Developer shares personal achievement of receiving the 2017 Microsoft MVP Award for Windows Development and thanks the community.
Explores the concepts of 'bikeshedding' and 'honeypots' in software, introducing the idea of a 'bikeshed honeypot' to manage feedback.
A web developer shares personal strategies for overcoming decision paralysis in design, coding, and content creation.
A software developer suggests humility as a personal strategy to combat feelings of Imposter Syndrome in the tech industry.
Explores how Deep Work techniques can help achieve a state of Flow, leading to greater satisfaction and improved skills.
A tech leader shares his core management philosophy: be a multiplier for your team and reduce friction to help engineers succeed.
A software developer summarizes key lessons from 'On Writing Well' to help fellow developers improve their writing skills.
An open source maintainer argues that users should fix bugs and add features themselves, not just request them, and provides guidance on how to start contributing.
A developer draws parallels between a design museum exhibition and software development, exploring coding as an art form and the importance of feedback loops and simplicity.
A critique of 'cute coding' practices that sacrifice code readability and maintainability for clever, terse syntax.
Advocates for writing descriptive, story-like Git commit messages to improve codebase history and debugging efficiency.