+972 52-548-6969
And on the first day, you push changes to production
time to read 1 min | 108 words
Originally posted at 3/22/2011
We recently got a few more employees to Hibernating Rhinos, and I noticed something that was very amusing. It wasn’t really intentional, really, but both new developers had pushed code that went into production on the first day on the job.
In contrast, when I got into my new job in 2005, I started a project that by September of 2009, still haven’t been able to go into production (and to my knowledge, still isn’t in production and likely never will).
It does make one more cautious, I’ll admit, but “every push is a production release” has paid up many times over.
Comments
Isn't it funny that just a few years ago people would talk about every check-in, or every commit. Now it's every push :)
Nothing worse (and abstractly safer), than being stuck in a non-published project; nothing better (and stimulating) than being a part of push-it-all team.
Do you have any web-based projects that users active use? If so, how do you publish them to production?
Would be interesting to know which kind of project they were working on...
Daniel,
RavenDB and UberProf
While there's definitely risk, it's far preferable to a scenario in which you have to sign paperwork, get a permit, pay fees, and sacrifice your firstborn child to get code into production.I view the ability to get code into production quickly as essential to short, adaptive development cycles.
Comment preview