We don’t have time to wait for kids to grow up before doing what we can. Ah, sorry. Before putting all of that responsibility on them and screaming “NOT IT!”

We need a new paradigm for social media. And no, I’m not satisfied with Lemmy either (privacy issues).

Yeah, firefighter mentalities are terrible.

That said, as someone in software development, wouldn’t there be some optimization work you could do? Keeping up with the technology? Preparing training material? Figuring out the next steps for the next improvements to be done to the system? Looking at solutions to better monitor what is going on? Scripts to automate tasks?

I find it hard to believe that things are so static.

the problem is you can’t easily go get another job because all the other jobs require a stupid amount of qualifications that don’t really relate to what they are offering in anyway shape or form.

Job postings are a wishlist for an ideal candidate. Only some of the stuff is actually required, For the rest, it varies based on how scarce people able and willing to work in that field are.

To see through the fog, you have to try reaching out. Either apply at places or try to build yourself a network. Sadly I’m not great at it myself. Alternatively, if you have the time and inclination to learn new skills, that’s a thing you can do.

I think this depends on the crowd. Unfortunately, the intelligent crowd and the crowd with money and power is not exactly the same. Though hopefully there is overlap.

I think this points to a large problem in our society is how we train and pick our managers. Oh wait we don’t. They pick us.

Which distro?

If a TODO passes code review, more than one person fucked up.

1. Those apps are simple
2. Those apps target a wide audience, hence have more budget as a result
3. Those apps are made by large, well oiled (you’d hope at least) companies. You don’t want my honest opinion on most small software development boxes. This industry grew faster than mentors became available for the newbies, so many devs including seniors still don’t know what they are doing.

It has literally been tried. You don’t control the world. China, North Korea, Iran and India get to do what they want. They have their own interests too look out for and could care less about a European country being invaded by another European country.

I was under the impression that even in other countries, activism is generally separate from the political parties and it’s more like activist groups putting pressure on candidates and organizing for them if they are more favorable, and sometimes getting something in return.

I’ve seen exceptions, but I gather they are rare (and we can already see some change as the party is under pressure to become more “normal” and “competitive”).

deleted by creator

Those are really stupid managers.

If you don’t have docs it’s a tough competition between having your more knowledgeable devs re-explaining what they know X times to X new hires, or letting new devs figure it out on their own which is both costly in terms of their time and more importantly, risky as hell.

Bad managers love risk though. Since it usually is a choice between speed now and risk later, it only blows up in your face later, and quite spectacularly, and everyone looks like heroes while they are putting fires out on overtime.

That said good managers probably don’t tolerate that shit from bad managers under them and can sniff out a firefighter culture pretty quick.

I guess what I meant to say was, managers that value doc do exist. If they really do, they’ll let you know.

That is different than for layoffs, which generally is less about rooting out toxic people and more about lowering costs. And people know it usually.

That said, anyone causing trouble for management or viewed as not pulling their weight will be the first on the list since management won’t have to justify firing them.

Expect this from corporate and political types alike.

Maybe it’s because it creates such nice little echochambers.

Protip: Your argument has more weight if you use modern examples if you can find them, rather than the Weimar republic. Sounding like you are escalating to the end of Godwin’s law does not help your point.

Which is annoying because I agree that it can backfire if done wrong.

This. Especially if your team does not follow SOLID principles (as then someone fixes a bug in a base class method that shouldn’t be shared. This fixes an issue in a subclass but introduces one in another. Rinse, repeat.

Yes and no. I mean sure, if you are going to leverage this to gain a significant edge in the market, that works.

If you add a tool to the project, that you need to understand to maintain some parts of it, which adds to the learning curve of someone joining said team, then the gains have best be worth the effort.

We adopt so many librairies/plugins/tools over time that adding more complexity than you need this way is just terrible.

Yeah, but it’s easy to overuse it. If your for loop is much longer. For a few lines I’d agree, don’t bother using something longer.

Code should scream out it’s intent for the reader to see. It’s why you are doing something that needs to be communicated, not what you are doing. “i”, “counter” or “index” all scream out what you are doing, not why. This is more important than the name being short (but for equal explanations of intent, go with the shorter name). The for loop does that already.

If you can’t do that, be more precise. At the least make it “cardIndex”, or “searchIndex”. It makes it easier to connect the dots.