5 ms·

Using source control tools as part of the deploy process really is a valuable innovation. It's not an "old fad". I think you're clinging a bit too heavily to t

Using source control tools as part of the deploy process really is a valuable innovation. It's not an "old fad". I think you're clinging a bit too heavily to the "good old days". It's ironic how this entire thread has turned into a mix of people either 1) complaining that modern technology is too complex and complicated or 2) complaining that modern job applicants have lost the skills necessary to run things

withinboredom 4y ago
That's an interesting take. But nah, I like some things the way they are now vs. back then. I love having cheap/easy CI that deploys to prod for me. I love having IDEs that are actually geared towards whatever language I'm writing in this year. I love having access to cheaper coloc space because most people aren't using it. I love having skills that most people don't even bother learning anymore when digging into performance issues. ... There is much I love about today and I look forward to the future. I was just stating my observations. And yes, `git deploy prod` is a fancy FTP, but probably even worse than FTP if the build actually happens on the production server (which is something I saw more than once) and causes a production outage (also saw more than once).
nonrandomstring 4y ago
> complex and complicated Complexity is not a virtue. It is a dangerous resilience anti-pattern and should not be lionised. Unless you're insinuating that things in fact remain simple but the complaints of complexity are down to the stupidity of commenters.
nikau 4y ago
> Using source control tools as part of the deploy process really is a valuable innovation. It's not an "old fad". Its only innovative in an 'Apple released it and now everyone is on the bandwagon' way. I've worked at companies that were using CVS for config file management in the 90s, the concept was already in play, it just wasn't as mainstream and didn't have a trendy infrastructure as code branding.

withinboredom 4y ago

That's an interesting take. But nah, I like some things the way they are now vs. back then. I love having cheap/easy CI that deploys to prod for me. I love having IDEs that are actually geared towards whatever language I'm writing in this year. I love having access to cheaper coloc space because most people aren't using it. I love having skills that most people don't even bother learning anymore when digging into performance issues. ... There is much I love about today and I look forward to the future. I was just stating my observations. And yes, `git deploy prod` is a fancy FTP, but probably even worse than FTP if the build actually happens on the production server (which is something I saw more than once) and causes a production outage (also saw more than once).

nonrandomstring 4y ago

> complex and complicated Complexity is not a virtue. It is a dangerous resilience anti-pattern and should not be lionised. Unless you're insinuating that things in fact remain simple but the complaints of complexity are down to the stupidity of commenters.

nikau 4y ago

> Using source control tools as part of the deploy process really is a valuable innovation. It's not an "old fad". Its only innovative in an 'Apple released it and now everyone is on the bandwagon' way. I've worked at companies that were using CVS for config file management in the 90s, the concept was already in play, it just wasn't as mainstream and didn't have a trendy infrastructure as code branding.