4 ms·

In 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 pessimist

In 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 ago
There 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 ago
  Software 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...