http://sijinjoseph.com/programmer-competency-matrix/
Describes the different areas and requirements to becoming skilled in computer science. Very valuable as both something to strive for and personally evaluate against, and also as a manager to look for these characteristics in your reports.
https://www.linkedin.com/pulse/7-things-make-great-bosses-unforgettable-dr-travis-bradberry
This was a great article for management, but also for developers. Providing feedback to a manager that they are or aren't following some of these tips can be extremely valuable in both directions.
https://blog.codinghorror.com/hardware-is-cheap-programmers-are-expensive/
The above link is very ancient but still relevant in companies that are trying to cut the wrong corners. Every developer should be given a very capable machine. Always. No excuses.
https://blog.codinghorror.com/the-programmers-bill-of-rights/
The above is also very rudimentary (and even older), but is a solid read. It's slightly dated (it references a fast internet connection as a requirement but it's hard not to get one of those now), but is still relevant for setting (and managing) expectations in the professional world.
http://www.disciplinedagiledelivery.com/
http://www.scaledagileframework.com/
The above are my order of preference for Agile frameworks. The assumption is that you know what Agile is, what the manifesto is, and that Agile in general always has to be tweaked to fit the current organization and its needs. The LeSS framework is my preference but DAD seems to be gaining momentum and taking over.
https://www.visualstudio.com/en-us/docs/work/scale/scaled-agile-framework
With the previous set of links understood, the above link defines how to implement and run Agile within Visual Studio Team Services (VSTS). This is ideal as it shows what the general principles are and what to do on a regular basis within VSTS, regardless of your role.
https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/inside-a-program/coding-conventions
If you are using .NET then the above should be adhered to. Note that tools like R# and others may lead you astray with out-of-the-box rules that are close-but-not-perfect. Setting up a shared profile for these rules is a must for any organization, and this concept is true for any language.
https://angular.io/guide/styleguide
The style guide for Angular is also a good read. The main theme here is to ensure that you know the coding and naming conventions for the languages you're using, and have a strategy to ensure the enforcement of said concepts.
[Citation needed]
Ensure that you also know the appropriate architectural, design, and implementation patterns for the platforms, frameworks, and languages you're using. These vary widely in scope so a single link would be inappropriate.
https://hackernoon.com/from-engineer-to-manager-keeping-your-technical-skills-40579cc8ea00 https://blog.ycombinator.com/ask-a-female-engineer-how-can-managers-help-retain-technical-women-on-their-team http://www.paperplanes.de/2017/3/24/productivity-workflows-for-managers.html https://www.linkedin.com/pulse/7-innocent-habits-failing-managers-bernard-marr
The above are decent reads related to management. They also work well as a developer approaches leadership roles, and is also useful for general human interaction--something that developers aren't necessarily great at on the whole.