Fix Like No One’s Watching
An article discussing the importance of fixing hidden technical debt and friction in software development, even when it's not immediately visible.
An article discussing the importance of fixing hidden technical debt and friction in software development, even when it's not immediately visible.
Reflects on the end of Moore's Law and the passion-driven era of garage computer builders, drawing parallels to modern tech culture.
A software developer argues that writing less code is a key skill for creating maintainable, efficient systems and solving problems effectively.
A discussion on the shift from traditional error-only logging to structured event logging in modern distributed systems.
A guide to implementing effective logging in Python applications, covering best practices, the logging module, and using daiquiri for better configuration.
Explores adapting Agile/Scrum frameworks for data science teams, covering effective practices and necessary adjustments for the unique challenges of data science work.
Explores the concept of 'governance on demand' for open source projects, suggesting formal structures be established only when conflict arises.
A developer argues that writing 'dirty code' is acceptable and beneficial in certain situations to overcome blocks and foster creativity.
A developer explains the benefits of using older, well-supported hardware for software development and empathizing with users on limited systems.
The article argues that true coding proficiency comes from struggling with problems yourself, not just following tutorials.
A developer's experience returning to Windows for software development after six years, focusing on WSL, Vagrant, Hyper-V, and Docker performance.
A guide for college students on the benefits and application process for Google Summer of Code (GSoC), an open-source software development program.
A developer announces they are transitioning to full-time work on their free and open-source software projects, funded by community donations and subscriptions.
A guide on defining the core idea (What), purpose (Why), and delivery method (How) for an effective tech talk.
A software developer reflects on 2018, highlighting organizing internal tech knowledge sessions and delivering workshops on container technology.
A developer lists programming topics they don't know, challenging the expectation that experienced engineers must know everything.
A developer's 2018 review covering personal milestones like moving houses and professional achievements launching three tech projects/books.
First post in a series on preparing tech talks, focusing on finding your personal motivation for speaking.
Explores the diverse reasons developers create R packages, from practical tools to experimental research, and discusses their varying lifespans.
Author shares the collaborative process and statistics behind writing the second edition of 'Laravel: Up and Running'.