top | item 45141402

(no title)

yacthing | 5 months ago

This reads like someone who works on a small and simple system.

"Deploy on every commit" lmao

"Shipping software and running tests should be fast. Super fast. Minutes, tops." hahah

discuss

order

dilyevsky|5 months ago

> "Shipping software and running tests should be fast. Super fast. Minutes, tops." hahah

You mean to tell me not everyone works on some SaaS product outside of critical path?

kragen|5 months ago

Charity's been running honeycomb.io, a SaaS startup with millions of dollars of revenue, for 9 years now, after being an early-stage engineer at Parse, a mobile backend-as-a-service startup that powered half a million mobile apps. She's talking about what she's made a reality at her company and its clients.

sampullman|5 months ago

Deploy to what? Staging on every merged PR (commit to stg), and prod deploy on every commit to main? That sounds reasonable to me, and I've done some variation of it on most projects for the last 10 years or so without issue.

yacthing|5 months ago

Well people aren't talking about not deploying to staging on Fridays.

And there are hints to what the author actually means, like "Each deploy should be owned by the developer who made the code changes."

That just isn't feasible in a system that's of any reasonable size.