gfs78

Why are we so bad at software engineering? Because most software comes without any liability.

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.

Agree.

It´s buying what doesn´t add much value/differentiation to focus on the things that are important to the company.

but they still need to get his job done

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".

On continuous delivery: "Given that all of the changes deployed are individual commits, the deployments are low risk and cause less bugs".

I would like to know the source of this claim. I guess someone did an study on this...

KISS + YAGNI + constant refactor. Code is a means to an end and I suck at futurology.

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.

Agree. But in the past it was also taught in no so serious places. Today it does 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.

I find the wording of your last paragraph a little insulting.

Please answer: do you think aerospace, embedded and relational DB engines is dated work that has not evolved?

Not an easy problem to solve. And this is why, given the odds, a career in tech is probably a bad decision.

To avoid ageism while being an IC you need to find a job in a niche where the domain is CS and/or ENG based (as in embedded, aerospace, or even relational database engines) and these jobs are far and in between.

Beware: jobs like Facebook seem to be CS based but they aren´t (that´s why their programmer average age is 27). The CS problems they have are due to arbitrary complexity and they are short term. Companies like these are media companies.

Where do they go?

A-Management.

B-Consulting.

C-Stagnation.

D-Endure a string of jobs where they are mobbed because they are seen as a threat until they retire from the industry.