4 ms·
Why is "dev team" in quotes? Seems like an odd thing to get pedantic about. We have a BYOD policy, and several members of my team opted to get the new M1. They
by diveanon 5y ago
Why is "dev team" in quotes? Seems like an odd thing to get pedantic about.
We have a BYOD policy, and several members of my team opted to get the new M1. They were junior devs who didn't know better not be early adopters. I agree that it was a huge waste of time, and Docker was a major contributor to that.
Your analogy about starters doesn't really make sense. We aren't the driver, we are the mechanic, and we should know how the engine works in its entirety. Managing a local environment is a skill set, and frankly it is a skill set that many developers lack.
You can keep using docker if you want, I don't really give a shit. Its dead end tech that will be replaced in a few years by some new startup, while the *NIX systems using it will still be there and the developers reliant on docker will have to learn a new ephemeral skill set.
- deleted 5y ago[deleted]
- corobo 5y agoWhy are you assuming devs who use Docker don't know how to manage a pretty simple LAMP setup? It's easy, docker is a bit easier if you have multiple environments to deal with. If docker is gone in the next few years (lol) then we'll use the next one if it's easier too. > We aren't the driver, we are the mechanic, and we should know how the engine works in its entirety. I do agree with this though, which is why I once built a server from scratch (as in physical parts) and put a website on it to find what I was lacking in "full stack"* -> installed the OS -> install and configure nginx, php, mysql, mail, sftp, bit of Zabbix to monitor the whole thing -> built a website to go on it -> made it live. Just for a laugh. At the time the only trouble I had was CSS :) But aye, no skillset if docker dies haha * Which later turns out doesn't include any of the build/install/OS/monitoring apparently. Full stack my arse.