I've already pushed to production twice today! Who's rocking it with me?
Come on board the "Friday I'm in LIVE" club (a tribute to one of my beloved bands).
If you're still not sure about deploying on Friday, I'll drop more information in the comments.
Bob has left the building.
I'm now officially on the #ProLeisureCircuit
Proud of what I've achieved in 9.5years at the company, as small excerpt from my leaving email today below. Also threw in the "Stay Fresh Cheese Bags" at the end.
And yes @jerry I did a #FinalFriday #DeployOnFriday to production.
mazedlx
Steve Fenton ➜
Fresh Manager
Andy 'Bob' Brockhurst 
Number of pull requests raised: 12,297 (~5 per working day)
Number of lines of code changed: 6,034,527 (added and removed)
Number of malicious requests blocked: ~50Million (probably much more, a quiet day is 90k blocked now)
Number of slippers worn out: 14 pairs
Number of Operating Systems replaced: 4
Number of Infrastructure rebuilds: 3 (total replacement of most components. (And no one noticed!))
Litres of coffee drunk: ~2338 (352 basketballs or 1 king sized bed for the Americans)
Litres of tea drunk: ~1164 (2 large chest freezers or 1 double bed)
'You build it, you run it'.
But 24/7 is not something you just slap on an existing 8/5 team. On-call comes at a cost, which is on the org to solve, not the employee.
https://deployonfriday.com/2024/10/06/oncall-or-not-oncall.html
One of the prevailing DevOps mantras is “You build it, you run it!”. While I agree to the overall concept, it’s not one that comes without several very important prerequisites. I’m not running anything unless those are not met. Let’s take a look at what they are.
The number one reason people are afraid to deploy on Friday and how to address/mitigate it:
https://deployonfriday.com/2024/10/06/why-people-dont-deploy-on-friday.html
Before wondering how we are going to address the problem of people being afraid to deploy on Friday (or any other day of the week for that matter), we should first understand WHY people are afraid. You can’t fix what you don’t understand. The ‘never deploy on Friday’ statement is not just a blanket statement, it’s also just a patch to fight a symptom, not actually addressing the root causes(s) that are underneath. And there are quite a few underlying issues, so let’s start with the most important one and work from there, shall we?
Alternate #pushit
https://m.youtube.com/watch?v=Pmd3UiNfNkA
Or maybe
#java records and #spring JdbcClient work pretty well together:
https://deployonfriday.com/2024/09/06/java-records-spring-jdbcclient.html
Added a roadmap for the blog.
https://deployonfriday.com/2024/09/05/the-road-ahead.html
I intend to run at least one article per week, which I think is doable as long as I keep things small and simple like I promise. ;)
Let me know what you think!
Deploy On Friday! is live again!
https://deployonfriday.com/2024/09/04/a-new-beginning.html
Getting a new blog up and running in 2024 is as simple as creating a new GitHub repo from a template and push it.
Checkout this post from Chad Baldwin to see how:
https://chadbaldwin.net/2021/03/14/how-to-build-a-sql-blog.html
Took me less time than setting up a VPS and WP install. A lot less.
Lars Rosenquist
Graham Watt
