3 ms·
> Yes. Because local development environments...break ALL THE TIME. This seems like more of a process problem than a technology problem. Our company has a sim
by ARandomerDude 4y ago
> Yes. Because local development environments...break ALL THE TIME.
This seems like more of a process problem than a technology problem. Our company has a simple rule for this: you break it, you fix it -- immediately. As a result, our development process is very stable.
- and0 4y agoI don't think it's quite that simple. Everywhere I've worked with Javascript, Python, or Ruby you run into a bunch of random issues that happen with a specific MacOS update or some other crazy context. Or the documentation just isn't the company's priority. However I do agree that web-only seems a bit much. Just last night I was doing some company work on my laptop while my power was out (no internet). The nice middle ground is dockerized development containers in VSCode, IMO. Very excited to set that up when I get a chance. And they translate right into all these fancy web IDEs (like Github codespaces) so you can have a dev env in the cloud if you really want to, and snag it for a plane or train ride etc.
- ARandomerDude 4y agoAgree with you about the MacOS update problem, though this seems to have gotten much better lately. With rbenv, asdf, etc. plus pinned gemfiles, package.json, etc. I really haven't experienced anything like the frustration that surrounded Ruby and JS 10 years ago. YMMV I suppose.
- didibus 4y agoWhy don't they have devs use Linux laptops? Problem solved. Just let them run the same OS as prod no? Or have them use VMWare or Docker.
- PetahNZ 4y agoCause an OS update has never broken docker before right. And prod doesnt run linux with a gui.
- Lutger 4y agoYou break it, you spend days on fixing things instead of being somewhat productive, and if you break the codebase, then we wait while you try to fix it, before we need to step in and do it ourselves. This was sometimes my experience working with and leading teams with devs of varying experience but always full freedom. Nobody actually likes it.
- formerly_proven 4y agoIf it takes days to figure out problems with the dev/build environment... uhm... you're having a huge problem, regardless of where files are edited.
- simonw 4y agoHow many hours a week on average do your engineers spend fixing something in their own environment that they broke?
- enriquto 4y agoSounds like well spent hours. Why would you even consider working with engineers that cannot even fix the simple tools they break?