Laughs in object

I am constantly fighting for more time coding. If you were to look at my calendar, there’s only ~5 hours per week of open time. My customers are our developers, however, so for the most part I am at least in meetings about code and SDLC rather than random feature refinements and such.

Hi friend, sounds like you should join us over in devops@programming.dev :)

It is important, and effective, to properly track and show to teams what effect their code changes have to the system and what “their team’s process” looks like to an outsider with meaningful data.

More here https://programming.dev/post/80365

Do not

There are deployment methodologies that exists to avoid downtime which I posted about in devops@programming.dev

Thanks for the content idea :)

TL;DR;

Rolling Deployment

Canary Deployment

Blue-Green Deployment

A/B Deployment

This aligns with my experience with enterprise contract work. Generally need to have a pre-existing relationship to get a foot in the door. For me this has come from building strong relationships with other devs at the same company. Some of those devs will move on and go down the management track, the higher up they get, and depending on your relationship, the more likely they would want to bring you in for a specific thing since “I’ve seen RandomDevOpsDude implement this successfully before, why not get him to do it again?” style.