So true. It takes a lot of patience because it will be like that at a lot of jobs and you don't want to piss off the wrong people.
Fortunately, most academic projects don't need to be maintained beyond the semester, much less from one week to the next. It might be a good topic for freshman to learn to use version control, but that would be a relatively small part of what someone goes to school to learn.
Really good advise about adding overhead. Trying to choose the perfect coding standard, tools, language, etc. should not be the thing to spend time on at this point. If that is the thing that interests you most, then just keep this as a hobby/self-guided project experience for future job interviews.
But for a commercial product - just choose tools/languages that you already know that are reasonably applicable to the task at hand. However it should be something mainstream that will be supportable: new hires will need to adapt to it, and you want to make sure it will be maintained in the future. You have to put your time into developing and selling the core product.
For choosing a coding standard, that will be a headache as you hire more people. It can be a potential ideological battle among your employees, and you have to really evaluate how much a particular standard will specifically improve productivity or quality in the long run vs. hinder or irritate your developers. Some industries already mandate specific coding standards such as MISRA or DoD specs, but for most companies that isn't a factor. My personal feeling is that if you are going to enforce coding standards, you could better spend that time and political capital with your employees by instead reviewing code for mistakes in general perhaps? When you find a particular bug, make sure you have drilled down and found similar cases, etc. Document so that you remember to look for this in the next code review. You will end up with a more robust process rather than imagined cases where code style is an issue.
Paid job experience can be very narrow and misleading as an indicator of future success in another technical job role. You can spend decades coding the same paradigms that happen to fit your employer's specific industry. Worse, you may fall into specific patterns and jargon specific to one particular employer. Formal education is specifically designed to handle a broader range of problem solving and knowledge; and it proves a candidate's basic work ethic.
Job experience helps to temper idealistic expectations to better understand what customers will pay for and how to deliver that effectively.
So I guess it depends what the job role is specifically.
Of course we don't have much in the way of soldiers, but we do have all the planes.
Your mouth is moving, but nothing is coming out.
There is the simple fact the women tend to gravitate towards professional jobs that are physically comfortable and safe, which tend to pay less. People that work in McDonalds and in Amazon warehouse represent less than a few percent of the total labor market.
At my time at UPS unloading trucks. There were a grand total of 4 women that worked with us out of 100+ people. The other dozen women that worked in the same unit were auditors, where the heaviest thing you had to lift was a clip board and a pencil. In 1989 the truck unloader started at $8 and could get up to $10 after the first year. The auditors made minimum wage, if I remember was around $4 at the time. They might see an extra 50 cents after a year. As soon as the "little girls" are willing to step up and do the hard dirty work, they will get paid more.
There are those that squealed like teenage girls when the President stopped by for a visit, but then the girls of the finance section are only a danger to you if you are a sugary baked good, the bulk of the rest of us would not tolerate the military turning on the civilian population.
Unlike in the rest of the world, we as civilians have access to just about everything your standard infantryman is issued.
"...Governments are instituted among Men, deriving their just powers from the consent of the governed, --That whenever any Form of Government becomes destructive of these ends, it is the Right of the People to alter or to abolish it, and to institute new Government.......But when a long train of abuses and usurpations, pursuing invariably the same Object evinces a design to reduce them under absolute Despotism, it is their right, it is their duty, to throw off such Government, and to provide new Guards for their future security
Personally I find the obsession to living in cities to be more than a little strange. Right now I'm living on the outskirts of Tampa, which is almost too close for me. Being stuck in DC or NY or San Fran again makes my teeth ache.
The fact that I am out in farm country with a triple digit symmetrical FIOS connection just tells me life is can be very good living even out in the boonies.
System: 2 shots on floor 1 room 1.
System: 3 shots on floor 1 hallway main
System: 15 shots floor 1 main commons
System: 5 shots floor 2 main stair well
System: 9 shot admin section
Sure helps a lot with those people getting shot doesn't it? Nothing will stop the shooter until the people with guns arrive on the scene.
This is nothing more than security theater. This will prevent nothing and is dubious as to how useful the info will be to the security responders.
Let's not forget this will do nothing to help with people walking around with Molotov cocktails or a bow/cross bow, or a blade, etc.
Arm the teachers, if they don't want to do it, then maybe they are not really serious about the welfare of their students.