A developer shares personal advice for giving effective technical talks, based on their experience speaking at international conferences.
Tips for preparing and delivering effective conference talks, based on experiences from tech community leaders and speakers.
A developer's reflection on overcoming perfectionism and procrastination to finish personal tech projects like websites or apps.
The story of Open Research Computation, a journal promoting high-quality open-source scientific code, its launch, challenges, and eventual reorientation.
A programmer discusses common bad habits like leaving unused code, over-generalization, and OOP fixation, offering advice for cleaner development.
Analyzes the debate on politeness in open-source communities sparked by Linus Torvalds, using personal contributor experiences.
Explores teaching approaches: starting with general rules vs. specific cases, using regex quantifiers as a primary example.
A satirical guide categorizing different stereotypes of web developers, from 'Rockstars' to 'Pedants', based on their skills and approaches.
A developer's rant about software stability and the pain of backward-incompatible updates when migrating to new computers.
A report on enterprise open source usage trends, highlighting increased adoption, contributions, and challenges with formal policies and license management.
The CFPB accepted a typo fix from an open-source developer on GitHub, marking the first direct public collaboration on federal government code.
A developer's instinct and experience are valuable tools for navigating complex coding challenges and unexpected hurdles in software development.
Author shares excitement about being invited to join the ASPInsiders, a group of experts providing feedback on ASP.NET technologies.
A developer discusses the challenges of open-source maintenance and urges users to contribute code instead of demanding features.
A Debian developer reflects on their 10-year journey within the project, from packaging to release management and team leadership.
A developer argues against rigid 40-hour workweeks, advocating for flexible schedules based on productivity and 'flow state' rather than fixed hours.
A critique of the Visual Studio Achievements beta, arguing its current rewards promote bad coding habits instead of good practices.
A critique of modern programmers' tendency to complain about new languages and tools rather than engaging with them, using Go and Dart as examples.
Discusses the drawbacks of using too many programming languages in a project, arguing for a balanced approach to benefit operations and maintainability.
An inside look at Heroku's engineering hiring philosophy and process, focusing on cultural fit and practical skills over rigid steps.
