We just build and test everything every time. Maybe it costs us more $$$ on CI, but it costs far less in developer time. That being said, I mostly work at startups and larger companies will certainly cross a threshold where this isn't feasible.
>>> larger companies will certainly cross a threshold where this isn't feasible.
Nope. Worked at the largest US bank that happens to be mono repo. They had compute grids with thousands of cores running tests 24/7. It's not sizable compared to the costs of the developers writing and maintaining software.
> The problem is that those people went through their schooling being told that they were awesome and should be a professor (by people who successfully became tenured professors, and who didn't experience failure).
IMO it's still on them if they didn't do the research on what their outcome might look like. I absolutely loved physics in high school and chose to study computer science because I knew it would pay my bills. 8 years later I am not regretting my decision at all.
> IMO it's still on them if they didn't do the research on what their outcome might look like. I absolutely loved physics in high school and chose to study computer science because I knew it would pay my bills. 8 years later I am not regretting my decision at all.
This is that corrosive individualist idea that the community has zero responsibility for its members, so we get to wash our hands of each individual's failure. It's wrong. Often the individual can't "do the research" to accurately estimate their outcome, such as when they're so disadvantaged they don't know where to start, or when they've been lied to.
I have a good manager right now. If that person hasn't had a good manager ever, then it might be one of those cases "if it smells like shit everywhere you go, check your own shoe".
I'm a senior dev who could cross over if I wanted to, but when I see what the managers are doing on a day-to-day basis I realize I'm perfectly happy doing what I'm doing and making pretty solid money while I'm at it.
You are looking to save yourself a week of time a year and then 3 years later for some reason or another you will HAVE to upgrade and good luck making that change when the world has moved past you.
Same experience as you. Thought I would always use sublime but my coworkers were so adamant about VSCode that I finally gave it a try. I don't even know that I can point to any single reason for it being better than Sublime -- feels like everything just works a little more seamlessly.
If that takes you forever, consider that it may also be your lack of familiarity as much as the lack of type system/compiler. Despite my preference for the back end, I have spent plenty of time on the front end and can pump out changes very quickly.
