Software Development Wheel 

Learning new development processes can be difficult, but switching to Agile doesn’t need to be complicated. Explore the theories behind Agile and learn how to make it work for you. In Agile Software Development Succinctly, author Stephen Haunts will guide you to a fuller understanding of Agile, its advantages and disadvantages, and how to get the most out of it. 

Eight Graphs That Explain Software Engineering Salaries in 2023
Tech professionals’ pay by programming skills, job functions, regions, and more
 

This project collects PowerShell scripts which help to debloat Windows 10, tweak common settings and install basic software components. 

Boost Downloading Using Libre Software

Persepolis Download Manager

For GNU/Linux, FreeBSD, PC-BSD, OpenBSD, Mac OS X and Windows

Want to hear how Stack Overflow uses ASP.NET Core in production? Come watch Nick Craver (Architecture Lead, Developer, Site Reliability Engineer & DBA) explain and take your live questions and answers! 

If you maintain an open-source project in the range of 10k-200k lines of code, I strongly encourage you to add an ARCHITECTURE document next to README and CONTRIBUTING. Before going into the details of why and how, I want to emphasize that this is not another “docs are good, write more docs” advice. I am pretty sloppy about documentation, and, eg, I often use just “simplify” as a commit message. Nonetheless, I feel strongly about the issue, even to the point of pestering you:-)