4 ms·
2010: edit html button 1. install ftp/sourcesafe 2. connect to url and authenticate 3. edit button 4. upload 2023: edit html button 1. install git 2. set
by 5350-uiop-1130 4y ago
2010: edit html button
1. install ftp/sourcesafe
2. connect to url and authenticate
3. edit button
4. upload
2023: edit html button
1. install git
2. setup git credentials in terminal
3. setup git ssh key in terminal and browsers
4. use internal bootstrap tool to install node
5. macos no longer supports bash, spend 10 mins switching everything to zsh
6. install npm
7. try to clone and install the code with npm i
8. 20 different node js errors, deprecation and dependency warnings
9. embark on a bunch of side missions to resolve all the node issues
10. try to start local environment
11. local requires docker
12. install docker
13. docker requires sudo permission
14. request sudo from IT
15. fill an IT form explaining why you need sudo
16. get lectured by condescending IT dweeb about how you're being monitored and to use sudo ONLY for approved things, have to try drag in manager to explain why sudo is needed
17. finally install docker (requires a giga f*ckton of ram to run and slows down your machine)
18. start the local environment
19. docker starts installing a bunch of crap and updating
20. try to edit the html button
21. the local server not refreshing or your change is not reflecting
22. turns out this repo is just for the button only, to update the copy requires another f*king repo (go back to step 7)
23. finally done, try to commit changes
24. your changes are 10 commits behind the branch
25. try to merge automatically, cannot be merged
26. make a PR
27. smug know it all "senior" developer with 2 years experience, gives a bunch of nitpicky comments on the PR and refuses to merge it
28. stare into the abyss
- frabjoused 4y agoIn other words, set up your dev environment? And if you were just setting up your dev environment your working tree wouldn't be dirty. Your impossibly pessimistic scenario is sadly impossible.
- nh23423fefe 4y ago> smug
- kerkeslager 4y agoThere literally is not a problem on this list I have not run into in my real life career. If setting up your environment requires all this, your environment is too complicated. But unfortunately, many production projects require environments this complicated.
- deleted 4y ago[deleted]
- piva00 4y agoSoftware has a multitude of tools. All scattered and disassembled. I'm getting close to 2 decades working with software, every shop I worked that had at least some investment in streamlining tooling/developer experience has been invigorating. They are too few and far apart though. Larger companies tend to develop layers and layers of tooling when striving for streamlining the dev experience. Unfortunately they become opaque boxes to obfuscate the complexity of the machinery. Leaky abstractions are inevitable and you will end up having to debug some internal tooling, going into the deep rabbit hole of figuring out how the machinery actually works to fix your issue. It can be frustrating but a little rewarding the first few times, later it just becomes extremely boring as the knowledge isn't even transferable. The smaller companies with good automation are some the most fun places I worked at. It's easy to be more creative when you aren't debugging a strange error code and the last mention to it is in some lost chat of 4 years ago. Always a fun time...
- Donckele 4y agoHa! thanks for the laugh.