31–40 of 52 posts
Well, having experienced ageism in software engineering the last three plus years I entirely guarantee you this point #1 is totally untrue. I am at my best, at leadership, management, architecture, security, compliance, SRE, testing... And my salary is worse than 12 years ago (and way worse than a few years ago) and my workload way higher.
So, I stopped reading.
Earlier quoted context omitted.
I was afraid that one would sound too arrogant. But, I figured, society frequently implies that management or the CEO are "above" the workers, and everyone seems OK with it. Personally, I want a different mindset, although it's hard to maintain.
Is something wrong with treating other people as equals in a partnership, instead of cultivating a superiority complex?
Unfortunately, for salaried employees, early delivery is usually rewarded with more work, often with no compensation.
As for the workplace, be loyal to people, never to a company. The company will kick you out at their unfeeling convenience, but people can and will respect you and support you.
Found many of the points helpful. Does anyone know what "Don’t rewrite. Go to the problems." would mean? There wasn't a way to contact the author. Because I think rewriting is essential in a lot of cases.
"Face the problems" might have been clearer, but this point is inspired by a time where, in hindsight, I should have got up from my desk and physically gone to another building to talk to the people who could fix the problem. I also should have spent more time reading and and changing legacy systems instead of avoiding them. It means, to me, to get close to the people and systems involved with the problems (or who are causing the problems). Sometimes the problems aren't that hard to fix, but to fix them you'd have to learn a legacy system written in another language, or contribute to another team's project, etc, and so I think of it as going to the problem, you just need to be where the problem is.
Earlier quoted context omitted.
I was afraid that one would sound too arrogant. But, I figured, society frequently implies that management or the CEO are "above" the workers, and everyone seems OK with it. Personally, I want a different mindset, although it's hard to maintain.
Is something wrong with treating other people as equals in a partnership, instead of cultivating a superiority complex?
Earlier quoted context omitted.
Is something wrong with treating other people as equals in a partnership, instead of cultivating a superiority complex?
Thought precisely the same thing and I think the author's disposition is deeply ethically for this reason. Other convictions expressed in the piece are similarly flawed. For me, many of the views expressed are anathema to how to be a good professional.
Found many of the points helpful. Does anyone know what "Don’t rewrite. Go to the problems." would mean? There wasn't a way to contact the author. Because I think rewriting is essential in a lot of cases.
Source: Much experience with surgical refactoring/ re-engineering/ rearchitecture.
Plus observation of the after-the-fact results of many less experienced teams "writing" or "rewriting" software.
Earlier quoted context omitted.
I was afraid that one would sound too arrogant. But, I figured, society frequently implies that management or the CEO are "above" the workers, and everyone seems OK with it. Personally, I want a different mindset, although it's hard to maintain.
Is something wrong with treating other people as equals in a partnership, instead of cultivating a superiority complex?