https://www.octomind.dev/blog/on-developer-dogma-3-never-ship-on-fridays

octomind logo
 
docs
 
pricing
 
blog
 
about
#
# 
go to app
 
[6488aa5d7c6bc8d56e]github-logogithub-logoDocsPricingBlogAboutGo to
app

never ship on fridays #3

Since we created Octomind we've released 64 times out of which 9 were
on Fridays. We don't refuse it, but we value our developers' time
off. My take #3 on a popular developer dogma.

[654b9dccfc]
an octoneer enjoying its weekend

There is a strong opinion in software development about NOT releasing
on Fridays. Friday deadlines (often the end of the work week or
sprint) are pushing developers to rush to finish tasks. The
temptation to push deployments through without adequate checks is
high. What can go wrong?

Compromised quality : A tendency to bypass proper testing or ignore
test failures leads to unstable releases.

Weekend recovery: If something goes wrong, devs have to give up their
weekend to fix the issues, leading to burnout and dissatisfaction.

Lost context: Developers who have shifted focus may not recall all
the details. Troubleshooting gets more difficult.

homer deploying on a Friday programmer meme
source: Coding Forest

 Allen Holub stands firmly on the other side of the argument.



Allen Holub tweet screenshot 1.

Allen goes on to say that your code quality must be inadequate if you
refuse to release on Fridays. While I generally hold Allen's opinions
in high regard, the statement is quite bold.

Allen Holub tweet screenshot 2

Being completely averse to Friday releases can come across as
dogmatic. Yet, I disagree with Alan on 'no Friday releases' being a
sign of inadequate quality.

I have released on a Friday. Bugs can occur any time or weekday and
Fridays are no different. It's fundamentally about setting
expectations with your team. If there's an opportunity, however
small, to reduce the likelihood of a weekend rollback or hotfix, I'm
taking those odds any time. Because I value my own and my fellow
engineers' weekends.

Sure, bugs should ABSOLUTELY be found before ever reaching
production, but that's not a 100%. I don't see the issue with pushing
a bigger release to Monday, if there's no business need to get it out
on Friday.

Daniel Draper lead engineer at Octomind
Daniel Draper
lead engineer at Octomind

Read more about dogmatism in software development:

 
December 5, 2023
Daniel Draper

Test your code!
#4

Software testing is littered with strong opinions and i'm no
different. What, when, who, how and if to test at all is the subject
of heated discussions. About the one dogma I'm guilty of - testing
what you've built.
software development
testing
 
November 7, 2023
Daniel Draper

Navigating TypeScript Gymnastics #2

Take #2 on popular developer dogmas and an attempt for reconciliation
between TypeScript lovers and haters. I'm firmly in the TypeScript
camp. However, using typescript is also not an absolute.
software development
see all blogs

Don't waste your time testing wrong. Build instead.

Octomind is open  for users in early access mode with a direct
channel to our devs. Try our UI test set-up or go to the app and
we'll get in touch. If you're not quite there yet, here is how you
stay up to date with the newest feature releases.
[                    ][sign me up]
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
octomind logo
 
docs
 
pricing
 
blog
 
about
#
# 
go to app
 
[6488aa5d7c6bc8d56e]github-logogithub-logoDocsPricingBlogAboutGo to
app

sitemap

 
Home
 
Docs
 
Pricing
 
About
 
Blog

contact

 
contact@octomind.dev

legal

 
Terms & Conditions
 
Privacy Policy

Octomind, Inc

c/o German Accelerator
325 Forest Ave
Palo Alto, CA 94301
United States

Octomind GmbH

Unterer Lussweg 5
76227, Karlsruhe Germany

follow us

####
[6475f35f39a2a45a9]
Copyright (c) 2023 OctoMind GmbH