The roles of the development manager

I have had the title of development manager now for 13 years. It has had slightly different meanings throughout this period; I find it best to talk about different roles I have served while having this title. I think the following list of roles is fairly complete, although the naming can be improved upon.

• Project manager - I have lead various business (revenue generating) projects. This is strictly not a role for the development manager, but I belief it is often the case that some project management work accompanies the title.
• Process maker - the development process needs to be designed and deployed. It is important to be proactive, but the work is necessarily done in cooperation with all stakeholders.
• Process guardian - this is the process policing, making sure the processes are followed (teaching/guiding/finger-pointing). This also includes managing internal documentation/data.
  
• Infrastructure owner - responsible for keeping the IT infrastructure operational (and cost effective). Including the CI/CD tool-chain and dev/test/staging environments.
• Release manager - making sure that release schedules are kept, enforcing code-freeze dates, managing release testing and delivery/hand-over to Service.
• Human resource manager - hiring, firing, training, conflict resolution, setting up teams, office managing (w.r.t. seating, equipment)
• Dev(sec)Ops manager - enabling team decoupling and team empowerment.
• Liaison to external developers - providing test environment and managing communications.
• Liaison to intra-company dev-teams - facilitating knowledge transfer with dev-teams in other departments.
• Technical manager - facilitating and (sometimes) initiating discussions on architecture (monolith to micro-services), framework (angular, vue, react, e.g.) and tool selection (UI libraries e.g.). 
• Asset manager -  this is perhaps covered by the other roles, but I think worth mentioning. This is the management of (digital) assets of the department, such as data in shared network drives, in wikis, in issue management tools, videos (Stream), collaboration platforms (Teams/Sharepoint), and software licenses.
  

Making (new year's) resolutions - a framework/categories, take II

Approximately a year ago I posted on this same subject. Now a slightly different take, perhaps a simplification.

 The following categories are useful to setup the right goals (resolutions):

• Basic skills ('the engine') - the foundation that the rest builds upon. I need to keep the physical and mental facilities well maintained. In my case I will be focusing on running and meditation.
• Mastery. It is important for my self-worth to gain mastery. I actually think I have done so in many subjects but I have not capitalized on it yet and my primary focus will now be on identifying it.
• Purpose. 'Higher purpose' if you like. Last year I focused on my 'micro' environment (friends & family). Now I am considering on expanding, adding a 'macro' component related to nature and fellow humans. Not going full-on altruistic, but in that general direction.

I would like to focus on a certain values to guide me through the day-to-day decision making. I will keep the ones I had last year.

P.s. Perhaps you can see a similar pattern here to the one in Drive by Pink: Autonomy, Mastery, Purpose.