Not Captain Obvious
A developer discusses overcoming the fear of writing about 'obvious' tech topics, arguing that sharing knowledge benefits everyone.
A developer discusses overcoming the fear of writing about 'obvious' tech topics, arguing that sharing knowledge benefits everyone.
A software architect shares 12 key lessons learned from successfully organizing and running a full-day virtual tech conference for over 500 attendees.
A discussion on defining a software team's 'critical path' by focusing on business-critical processes that directly impact revenue and customer experience.
An introduction to Git and version control systems, explaining basic concepts like CVCS vs DVCS and how Git works.
A software developer reflects on the need for continuous learning and shares a personal 'brag document' strategy to track accomplishments in the tech field.
A developer's personal notes and struggles while learning Go interfaces, including debugging a Stringer exercise from the official Go tour.
Explores the history of Braille as an analogy for iterative software development, highlighting how user-centric design leads to superior solutions.
A developer's personal journey learning the Go programming language, documenting notes, resources, and challenges encountered.
Discusses the shift from 'master' to 'main' for Git branches, arguing it's a small but meaningful step towards more inclusive language in tech.
A guide for software engineers on delivering effective remote software demos, focusing on preparation, customization, and engaging key stakeholders.
Compares Feature Teams and Product Teams in software development, explaining their structures, goals, and which type the author prefers.
A senior engineer describes how the Feature Lead role at Nested provided the growth and business impact he was missing as a senior developer.
Explores the challenges of developer onboarding documentation and proposes strategies like expert meetings to improve the process for new team members.
Survey results analyzing PHP developers' preferences for strict type systems versus dynamic typing, and how team/project size influences these views.
Explains how writing integration tests for C# APIs boosts productivity by catching bugs early and reducing manual testing.
A data scientist shares how adopting Scrum, despite initial resistance, improved project management and delivery for data science teams.
Explains the purpose and best practices for using a 'contrib' directory in open-source projects to manage community contributions.
An argument that technology cannot solve systemic human problems like racism, and that real change requires human action, not just code.
A technical guide comparing OBS Studio and other streaming platforms for delivering engaging tech talks and training sessions.
A survey analyzing the relationship between PHP type systems and project size, with results published on the author's blog.