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.
Challenges the view that management is a promotion and engineering a demotion, arguing for cultural change in tech organizations.
Discusses problem-solving philosophy in tech, advocating for avoiding problems entirely rather than patching them, using API versioning as an example.
Discusses the critical importance of budgeting for 'trust and safety' work to combat online abuse, framing it as a necessary 'internet tax' for tech platforms.
A software developer uses a personal story about walking in high heels to illustrate the importance of seeing the 'big picture' when implementing features.
An analysis of Hacktoberfest's challenges, focusing on low-quality contributions and strategies for maintainers to manage them effectively.
Discusses common pathologies in bug tracking and proposes improvements for responsible bug management in software development.
A guide for engineering managers on making strategic hiring decisions to scale a tech team effectively, based on experience at a fintech company.
Advice for aspiring open-source contributors: focus on solving your own problems and building skills, not just contributing to popular projects.
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.
