Podcast episode discussing the Theory of Constraints in software development and DevOps with guest Tom Hoyland.
Discusses the balance between too little and too much specification in software development, advocating for concise, intent-focused specs.
A software engineer critiques story-point-driven estimation in agile development, arguing it's often misleading and doesn't solve core estimation problems.
Practical advice for developers to improve their GitHub portfolio, focusing on quality projects, learning in public, and effective documentation.
A software engineer shares lessons on delivering constructive criticism and saying 'no' effectively in technical meetings and team collaboration.
Discusses the importance of context and team factors over hype when choosing software architectures and tools.
The author announces their new book 'TypeScript in 50 Lessons', a 450-page guide focused on the TypeScript type system.
Explains how building a simple prototype can be more effective than proposals for gaining stakeholder buy-in on tech projects.
Podcast episodes exploring Agile principles 5-12, covering team dynamics, communication, and technical excellence in software development.
The author announces 'Front Line PHP', a new book teaching modern PHP, best practices, and the professional web developer mindset, launching alongside PHP 8.
Explores the growing importance of writing vs. coding for senior tech roles, featuring insights from engineers and data scientists on communication and leadership.
Tips for making quality open-source contributions during Hacktoberfest, focusing on finding suitable issues and respecting maintainers.
A software engineer explains why he joined a union, drawing parallels to smoke alarms and discussing exploitation in the tech industry.
Explores how unexpected software behavior, or 'That's funny...' moments, are key opportunities for learning and improving mental models of code.
A developer shares strategies for tackling complex programming projects, using a personal app example to illustrate breaking down problems and starting with core functionality.
Explores alternative forms of feedback like body language, results, and emotions to improve in coding and other areas when direct feedback is unavailable.
Key considerations and best practices for successfully implementing Azure DevOps in an organization, covering projects, area paths, and identity.
A developer's chart on career priorities goes viral, sparking discussion on the evolution from making code work to valuing readability and avoiding over-abstraction.
A developer shares his personal productivity system, tools, and routines for balancing a full-time job, a Master's in CS, and side projects.
A developer critiques the use of time-consuming coding challenges in tech hiring, arguing they are unfair and exclusionary.
