2025-02-28

Should managers still code?

Engineering managers should prioritize being actively involved in the codebase through code reviews, pair programming, and understanding architecture, rather than being primary feature implementers. The role of engineering managers has evolved post-pandemic, with increased expectations for technical engagement while maintaining core management responsibilities. Different approaches to staying technically engaged are discussed, emphasizing the balance between coding and management duties.

Original archive.is archive.ph web.archive.org

Log in to get one-click access to archived versions of this article.

read comments on news aggregators:

Related articles

Speedrunners = vulnerability researchers

Video game speedrunners unknowingly develop advanced cybersecurity skills through glitch hunting, using professional tools like IDA Pro and Ghidra for reverse engineering. These enthusiasts create sophisticated exploits and technical documentation comparable to professional vulnerability researchers, yet often don't realize their skills could translate into cybersecurity careers.

Your company needs Junior devs

An exploration of why hiring junior engineers is crucial for innovation and organizational health, emphasizing how coaching junior employees creates a culture of learning and psychological safety. The article argues against the trend of companies only hiring senior developers, highlighting how teaching and knowledge sharing are essential for innovation and challenging the notion that AI will replace junior developers.

The Ideal Candidate Will Be Punched In the Stomach

A person takes a seemingly lucrative job where they get punched in the stomach daily, leading to physical and emotional deterioration until they finally quit after 9 months of abuse, revealing deeper insights about toxic work environments and career choices.

Don't be Frupid

An exploration of 'frupidity' - the harmful practice of misguided cost-cutting that ultimately damages productivity and innovation in engineering organizations. The article examines how excessive frugality, coupled with bureaucracy, leads to hidden costs through reduced productivity, lowered morale, and lost opportunities, while providing practical strategies to combat this organizational pattern.

Best Simple System for Now

A balanced approach to software development, called 'Best Simple System for Now' (BSSN), advocates building the simplest possible solution that meets current needs while maintaining high code quality. The philosophy emphasizes writing code that is neither over-engineered nor under-developed, focusing on immediate requirements rather than speculative future needs. BSSN promotes evolutionary design through disciplined habits, courage, and humility, enabling faster delivery while maintaining code quality.

Software development topics I've changed my mind on after 10 years in the industry

An experienced software developer shares evolving perspectives on industry practices, highlighting shifts in views about simplicity, technology choices, and team dynamics over a decade. The insights cover technical aspects like database selection and programming paradigms, while emphasizing the importance of communication and mentorship in engineering.