It's pretty common to have quick unit tests so you can cycle thru TDD without having to recompile the world and start-up/reload the application. You can get a few hours of work done with TDD without ever opening the actual application.
In legacy enterprise, you're rarely doing green field work. You usually spend time reading coding and planning a safe edit. When you do change a line and have to recompile the world, its common to actively read and plan your next change while waiting.
Changing on the Job: Developing Leaders for a Complex World by Jennifer Garvey Berger
This is my current mind-changing book. Its a great framework for explaining how different types of people handle complexity, and how/why people react the ways they do. I really like how the framework is framed around 'complexity' rather than maturity. I've gained a much more constructive approach to handling disagreements rather than a 'smarter/better than thou' approach.
I don't agree with forced medical procedures at all. I think the world should be upset with Canada, with CPP, and all the other cultures who are doing it. I agree, regardless of your cultural background, you have every right to be upset with genocide/racisim/terrible thing in another country and in your home country.
I don't want to tamper anyone's disgust. I would like to add that it happens in my home country and it breaks my heart.
There are increasing number of reports in Canada that Indigenous Women were forcefully sterilized in the last few decades. Women who gave birth in hospitals had their tubes tied after giving birth. I agree this is a one of "the worst forms of racisim/ethonicide/genocide". And yes, I dont understand why more (white) Canadians are not aware of this, and why there has not been a larger out cry over this.
https://www.cbc.ca/news/canada/saskatoon/report-indigenous-w...
[Edit] I am against forced sterilization by anyone on to any one. I want to highlight that sterilization has happened in recent years in Canada. As the message above me points out, there is very little outcry in North America. Here is a data point where sterilization has happened in Canada and there is very little public outcry or knowledge of the situation.
It depends - I don't think there is an true answer to this question.
I've worked both in early stage startups and in companies that are established and are still using their original startup code base. I've seen some terrible design decisions coupled with quality code that survived 15 years because the company had amazing market fit. It cost the developers a lot of extra time to work around the poor design decision, but the company was profitable enough to make up for the dev cost. That's the most common situation I've seen.
The best codebase I've ever worked with was beautiful because the company had long lead time on sales(avg deal took 12 months) so the developers had time to refactor as needed. This company is still alive, so I consider them a success!
The other factor in code quality + business success is team size. With a big team and poor quality code, it spirals down much faster, each new bug/feature gets harder and slower to implement. If its bad code but its always the same 2 developers, they will be consistent enough in their own styles that the code base will not degrade nearly as fast.
I dont have an exact book or course to recommend, but rather how to approach school courses...
I'm Canadian, and went thru post secondary in Canada. This is coming from someone who did not program for fun in highschool, had no family support/introduction to IT, no extra curricular programming introduction, etc.
I went to a collage instead of university. My first year computer courses had lab sessions where our teacher helped with programming assignments. There was ~10 kids in class. Uni classes were a few hundred kids in a single class and lab sessions were ~30 kids. They had TAs (teaching assistants, graduate students with no industry experience) instead of their professors during programming lab sessions. I got the same course credit, much cheaper tuition, and a much more practical programming education. I transferred to a university to finish my degree and I was embarrassingly ahead of everyone else when it came to programming.
Whatever course you do take, look for passionate people with a teaching background and a small class size.
I liked how to worded "emotional separation"
The reduction in my stress has been amazing, especially considering we've been in the middle of covid. My moods are way better regulated now. I'm no longer trying to ignore my angry office mate who's muttering under his breath. I didn't realize how much upset people influence my own mood. I thought I was good at ignoring angry people, but the action of ignoring took up a lot more energy than I previously thought. My biggest worry about back-to-office is how I'm going to managed my increased stress levels.
It's pretty common to have quick unit tests so you can cycle thru TDD without having to recompile the world and start-up/reload the application. You can get a few hours of work done with TDD without ever opening the actual application. In legacy enterprise, you're rarely doing green field work. You usually spend time reading coding and planning a safe edit. When you do change a line and have to recompile the world, its common to actively read and plan your next change while waiting.