3 ms·

I would hate to work somewhere that my changes are deployed within days of writing my code. CI/CD lets you iterate faster and it encourages best practices like

I would hate to work somewhere that my changes are deployed within days of writing my code. CI/CD lets you iterate faster and it encourages best practices like proper testing. That said, if you do CI/CD without proper testing then you're going to break production.

seanwilson 6y ago
Wait until you have to work with clients that don't even have staging environments let alone automated testing. Source control, CI/CD, automated testing, pull requests, code reviews, feature flags, linters, good logging etc. might be the norm on HN but not everywhere, especially companies where tech isn't the focus. It can also be a tough sell to make process improvements like this when the old way got them this far and they want new features now. I've worked with clients that don't even use source control, do all edits on production and there's no way setup to develop locally.
- pletnes 6y ago
  Although my current day job is very professional about this, I’ve seen the other side, too. «We have some code from 5-10 y back, can you compile it?» and only half the files are there. It would be great if HN had some content on «moving from random files on a network drive to git and basic automated testing» - it’s not an easy job and others would benefit from such writeups.
  - oblio 6y ago
    Joel on Software: go through the "Rock Star Developer" section of his archive.
lmm 6y ago
> I would hate to work somewhere that my changes are deployed within days of writing my code. Did you miss a "not" here? For me an environment where my changes are deployed and used quickly is a lot more fulfilling than one where I work on something that may only see the light of day weeks or months down the line.
rutthenut 6y ago
> I would hate to work somewhere that my changes are deployed within days of writing my code. You think waiting days would be hateful. Having to wait months is more frustrating. And more risk for the business.

seanwilson 6y ago

Wait until you have to work with clients that don't even have staging environments let alone automated testing. Source control, CI/CD, automated testing, pull requests, code reviews, feature flags, linters, good logging etc. might be the norm on HN but not everywhere, especially companies where tech isn't the focus. It can also be a tough sell to make process improvements like this when the old way got them this far and they want new features now. I've worked with clients that don't even use source control, do all edits on production and there's no way setup to develop locally.

pletnes 6y ago
Although my current day job is very professional about this, I’ve seen the other side, too. «We have some code from 5-10 y back, can you compile it?» and only half the files are there. It would be great if HN had some content on «moving from random files on a network drive to git and basic automated testing» - it’s not an easy job and others would benefit from such writeups.
- oblio 6y ago
  Joel on Software: go through the "Rock Star Developer" section of his archive.

lmm 6y ago

> I would hate to work somewhere that my changes are deployed within days of writing my code. Did you miss a "not" here? For me an environment where my changes are deployed and used quickly is a lot more fulfilling than one where I work on something that may only see the light of day weeks or months down the line.

rutthenut 6y ago

> I would hate to work somewhere that my changes are deployed within days of writing my code. You think waiting days would be hateful. Having to wait months is more frustrating. And more risk for the business.