Books for geeks
A GitHub employee shares a curated list of recommended books for hackers, geeks, and open source developers on technology and business.
A GitHub employee shares a curated list of recommended books for hackers, geeks, and open source developers on technology and business.
A developer shares three powerful mindset principles from a Thoughtbot podcast: strong opinions loosely held, nothing is set in stone, and rejecting 'because we've always done it'.
A talk arguing for the importance of code comments, debunking common arguments against them and providing a framework for effective commenting.
A guide on how to ask clear, specific, and well-researched coding questions to get faster and better answers from experts.
A product manager shares twelve key responsibilities and daily activities based on their experience at GitHub, focusing on accountability, team leadership, and user advocacy.
Mike Ash announces a hiatus from regular blog posts to focus on completing his book, 'The Complete Friday Q&A: Volume II'.
The author explains their decision to publish their book 'Laravel: Up and Running' with O'Reilly instead of self-publishing.
A comprehensive talk and demo covering JUnit 5 features, architecture, migration from JUnit 4, and advanced testing techniques.
Explains the benefits of using language-agnostic automation scripts in software projects to simplify onboarding and CI/CD processes.
A software engineer discusses the concept of defect prevention, analyzing root causes of bugs and suggesting process improvements to avoid recurrence.
A developer recounts a massive, poorly-scoped code review and the strategies used to salvage it, emphasizing best practices.
Explores the terminology and lifecycle of software bug reports, discussing the tester's role and team dynamics in defect management.
A junior front-end developer shares lessons on teamwork, communication, and tools for integrating into a new tech team.
An invitation for students to join Google's Summer of Code, submit project proposals, and get paid to work with open source communities like KDE and openSUSE.
Argues that product design should focus on the core 80% of users, not power users or edge cases, to avoid feature creep and improve the out-of-box experience.
A developer asks for community help on several open-source projects due to increased time constraints from other work.
A review of the Topconf Linz 2016 software conference, covering its organization, speaker lineup, and attendee feedback.
A candid look at the realities of being a Product Manager, emphasizing data gathering, customer interaction, and team dynamics over high-level strategy.
A programmer reflects on the nature of programming, the value of learning multiple technologies, and the importance of passion and teamwork for a sustainable career.
A developer discusses common logical fallacies used in tech arguments, like the 'gospel' and 'Luddite' fallacies, to justify choices or disparage others.