Trailer is https://www.youtube.com/watch?v=7wjJYqUkHd8
You can watch the documentary on Tubi https://tubitv.com/movies/559438/silicon-cowboys
Trailer is https://www.youtube.com/watch?v=7wjJYqUkHd8
You can watch the documentary on Tubi https://tubitv.com/movies/559438/silicon-cowboys
I was in the "TABs are superior" camp but only for the initial indention of code blocks.
But somewhere along the way, editors added features that let you see invisibles, and let you set up smart tabs so that you could hit tab, but it would interpolate 4 spaces (or whatever you set) into the document, and let you shift+tab back the indention or TAB the indention, but put in spaces.
More importantly, the mass of people who all coalesced on using the same editor in the web development sphere, Sublime then Atom then MS Visual Studio Code, has made it easier to just say "set your editor to do this".
I have changed my mind to using SPACES now because the editor lets me fake using TABS.
I recently read a quote, paraphrasing, Orthodoxy is a poor man's substitute for moral superiority.
Unions could only make that worse.
But is it equal? It is hard to scientifically to prove, but it sure seems like companies have way more leverage than a lone developer.
I am not trying to antagonize you, btw, I am just seeing where you come from in your points.
Most of the issue is that there's too much administrative policy (whether the imposition is internal or external doesn't matter) for us to effectively communicate and collaborate. Unions would only add to that while collecting fees from us. Most of us are intelligent enough to know this which is why we never form them.
Question for you about this. Is the balance of power in negotiation equal between a lone developer and a company?
I ask, because in my little world, it sure seems like the company has way more of the cards than a developer does.
I think humans are fundamentally flawed in not being able to see alternate history. If they have to pay a union, they will not see all the benefits, and only focus on the 50 dollar union fee.
I do not think most people think of themselves as being "ageist", but it manifests in their actions. Usually a department will be filled with a group of young people, and in the interview process, someone will say, "I do not think this person would be a good culture fit". But they do not realize that they just do not want an old person because they seem different then what is already in the team.
I also have a hunch, that "leet code tests", in the hiring process has a hidden agenda of weeding out "older people". Those kind of tests are usually on knowledge one might have learned in a college course and subsequently forgot about. Or, if you are juggling a family, you may not have time to go do all day knowledge crunch study to get the algorithms into your head.
Companies do not want to come right out and say "we do not want to hire old people", but they selfishly want the most value for their buck. They want to drive down wages and extract value. What is more valuable to a company? A middle aged programmer who has to go home at 5pm to help take care of the kids? Or do they get more value out of a young person just out of college who has something to prove?
I have seen perfectly reasonable people pass over hiring older people because they do not want to hire someone who might know more than they do, or someone who might push back on decisions. They want someone young who will just do what they say.
As a society, I do not think we address such issues well.
I worked in the industry before flash, during flash, after flash, and in my little corner of the world, the iphone not supporting flash was the biggest factor in the decline of flash. Every executive and bigwig could not drop their blackberries fast enough, and grab the newest status symbol iphone. Once management all had iphones, then flash just would not do, and the directive came down to make the website "good" for iphones, which usually entailed adding excessive white space, large lettering, and big buttons.
Microsoft had C#, at one point IBM pushed SmallTalk. C++ for these environments is doable but going to slow you down at development a lot, as well as being much harder to secure.
At that time the dynamic alternative was Perl, and that remained true basically until Rails came along.
I would say that many things in IT are not chosen on technical merits alone. You have people that do not want to accrue any blame. Back then, by choosing what IBM endorses or what Microsoft endorses, you absolve yourself of fallout from if and when things go wrong.
Back in the 90s, it felt like IBM, Redhat, Sun kind of, sort of, got together and wanted to keep Microsoft from taking over the Enterprise space by offering Java solutions.
Trailer is https://www.youtube.com/watch?v=7wjJYqUkHd8
You can watch the documentary on Tubi https://tubitv.com/movies/559438/silicon-cowboys