I completely agree. At the some point, businesses need to to have reason to say "no, what you want is feasible, and we won't risk the consequences of failure."
For safety critical applications, technical decision makers need to have reason to say "no, we can't do this, and we won't because my career and possibly freedom are at stake if we do."
Right now a huge portion of the risk of software failure to software builders is reputational. This can be sufficient, as pointed out in many cases in the article, but as we see in these examples is often not.
Professional services companies business is about selling/billing hours. Those involved in the sales are seen as an asset, those involved in providing the service are seen as a cost. They don´t care about the latter.
DXC, Accenture, Capgemini, Indra, etc...they are all the same.
I feel your pain, but beware, university degrees are not the solution to life problems. I´ve got one, supposedly a hot one, in C.S. and my life has been stuck in absurdity forever and I´ve been stuck in insanely shitty jobs (programming-related ones) for the last 7 years. The situations that lined up one after another to fk my life were extremely improbable but happened. Sometimes life sucks. But don´t give up, try to find solace in your fighting.
They just employed someone for a full time job because they needed to spend €x on someone to do Y work
Now they don't have to pay that money, which is fine, but they then need to find someone on a 14 month contract that will do it for the same salary as the person they just employed.
Then at the end of it they are left with paying an overlap from the contractor to someone new
First, a little nitpicking: one of the parents can take at most 12 months off, so there is no "14 month contract".
Second, the whole thing can be way more complex. In Germany a mother has her job secured for the moment she announces to be pregnant to until the child is 3 years old. So one could decide that will take the Elterngeld for 12 months but actually just go back to work 18 months, and the employer has no way of stopping it.
Third and final point: NONE OF THIS MATTERS! Trying to find the "fairness" in this is nothing but some incredibly naive exercise. Like most things in life, salaries are not determined by the amount of value produced but rather by market value of labor. Risks when dealing with labor force should be already priced in.
Sure, and the policy is good, but there is still an impact on the company. Most situations that will be a large company which can easily cope, but in small companies struggling to survive is can have an locally detrimental effect (despite the company benefiting from the policy as a whole)
What makes you think that the small companies are struggling to survive? And from all of the policies in Germany that exist to "protect" the employees (minimum wage, employer share of pension contribution, health insurance, etc) what makes you think that this particular policy deserves such special concern?
Enterprise web development (or any enterprise development) has always been dehumanizing. It´s the vertical organizational model applied to software development. The enterprise implementation of Agile is just the vertical model in new clothes (status meetings disguised as daily meetings, story points used for stack-ranking, etc). When you enter the enterprise you trade leverage for job stability and 9-to-5 working hours.
Startups and mid or small sized niche companies are a little more human. But here you tend to get long working hours and more stress, plus sometimes they are also "vertical".
There's an implied "other things being equal" in there.
Given the commits follow some normal distribution of quality and risk, it's less risky on average to apply one of those average commits than it is to apply a bunch of them.
But if you try to deliver one giant risky commit, you're doing CD in name only.
I would likewise like to know the basis behind these claims. There have been countless instances when I've been reviewing a PR and found changes completely unrelated to the task at hand (user story or bug). One commit often has a scattering of changes that get lumped into one git add * git commit. In a disciplined world full of mindful developers, I could see this being a thing. But I have little faith this could be sustained in a majority of dev shops.
I'm not trying to be negative Nancy but realistic Ron.
Procrastination is more about dreams, opportunities and possible outcomes than time management and emotions.
If you have the chance to win it big doing something you love you will find the time. If you have less of a chance or you don´t like it that much you won´t be able to find that much time. If what you have to do is something out of obligation or you don´t care at all you will procrastinate.
And it´s fine. It´s your inner compass trying to tell you that maybe this is not for you/wasted effort.
In the short term the best strategy for procrastination is to put your pants on and do it. In the long term is making sense about why you are doing what you do and evaluating if it brings value to your life or not.
The move from Pascal to Java made a transition from learning how to program a computer to learning how to build apps using java-like OOP and libraries. Most places where Java is taught don´t teach about computer registers, stack frames, pointers, memory management, etc, and how they work together. Or if they do it they do it superficially.
