2,242 karma · joined July 15, 2010
Perhaps inside IR35 and perhaps for a low rate. Big corps mostly do umbrellas these days.
I find it similar to having kids. Most of adults have them, but the impact they have on their lives is so different. It all depends on financial situation, support from the rest of the family, friends, health situation..
In many cases this is not a different league, but an entirely different game with different rules and goals.
The article calls the lack of pro-activeness a CBF, but that is a symptom and not a cause. The fact that you CBF might not necessarily be a problem with you. It could be that you are in a different frame of reference compared to some other people who "do things perfectly".
Maybe moving maximum amount of Jiras into a done state is valued more than delivering this excellent refactoring. Maybe skipping unit tests and dropping feature branch to testers is perceived as a more pragmatic approach. Maybe your perfect commit will be unrecognizable a couple months later, because company is "moving fast".
People with great jobs in great companies will not understand this and call it laziness, procrastination or any other thing that will put you at blame. Just like people with great families will not understand what it means to have abusive parents.
Software development is about processes, but often developers have no say in setting up those processes, there is no feedback loop. Some naive manager will push to maximize some theoretical metric. In some cases you can adapt, circumvent certain obstacles, but sometimes you just CBF.
Russian fascism runs for multiple generations. Russia never was democratic. Russian mentality is to have an aggressive leader ("бьёт - значит любит").
Navalny is perceived as an alternative to Putin, but he supported Crimean annexation and Georgian war. There is no evidence the remedies that worked for Nazi Germany will work for Russia.
And because of this, software has poor standardization practices.
Engineers in other sectors could prove their qualifications by showing certification diplomas, even education and years of experience would count. In software your qualification would be determined by some random dude and how well you fit his CS fetish of the month and that is it. Experience and education is only important while filtering CVs. If you designed a chip, an aircraft or skyscraper it is immediately impressive. If you built an FX trading platform it means almost nothing if you are a bit skeptical about pair programming.
It also applies the other way round. If project uses microservice architecture, what exactly does that mean? The result would be a wildly different if you compare such projects at FANG and some investment bank. How software is tested and released will be different in any team. And how that affects the poor developer will vary too. What is a good software? We can have an opinion, but there is no formal definition.
And because of this fragmentation and fluidity software as and industry is doing very different things. It will learn in some cases in others it will be incredibly ignorant.