“we need more resources” is bounded by the rate at which you can incorporate new teams members without absolutely destroying your productivity, or having a bunch of untrained fools running around breaking things (of course the later is standard at many places already, so I guess it doesn’t always matter).

The right answer is usually : “No”. Or at least “Prioritize”. Or “This is what we need to get it done” at which point they might start to get software takes time to make decently, and they don’t want software that doesn’t work decently in the first place.

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

My personal hate is the word “settler”, which invokes an image of somebody taking previously useless land and making it fit for human habitation, but apparently has been redefined within the borders of Palestine to mean “armed invader”.

North American Natives probably resent that sentence…

It is very rare for no humans to make use of land at all. Whenever someone “settles” it, they are taking it away from someone else. Usually force gets involved at some point, even for nomadic tribes. It’s why colonialism has a bad rep these days.

Never touched it? A website? What about updating frameworks for security issues?

The closest I got to this kind of job., is the closest I got to running away. I’m much happier elsewhere now.

This, to a point.

Other things help :

• Unit test to help catch regressions. If you are confident in your test catching a good portion of bugs from refactoring, at least you feel confident refactoring. Worst case, at least you ensured your code is testable. There is nothing worse than refactoring untestable code.
• Self-documenting code and when it fails to self-document, comments or refer to a wiki page.

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.

I find the idea that the idea that people from another country tricked into conscription would get this benefit. If they got to this point by trickery, what’s to stop more trickery?

I mean as far as feeding the data to AI, isn’t Lemmy worse? Any data on the fediverse is as good as public and would just get gobbled up by AI or adtech in an instant?

It’s like a few lifetime’s worth of efforts went into defending this guy.

Sorry to hear about your hardship. You deserve a better system. Best of luck rebuilding and I hope things get better.

I don’t understand how people can work for sleezebag companies.

This is part one.

To this day I refuse to carry debt or even own credit cards tho.

I think this is part two.

It’s awesome that you do this, but if you can afford to avoid debt entirely you are probably somewhat priviledged compared to some. A lot of people in the US are working off student debts for degrees that didn’t quite deliver the jobs they were expecting. Or just were dealt a bad hand to begin with.

I think his point is about judges being corrupt. He has information useful to us and he’s not mentioned how he feels about his uncle. No point being mean to him.

Takes time to become ubiquitous.

And then y’all exported yer culture out to us via Hollywood.

Learning to deal with “unmaintanable” codebases is a pretty good skill. It taught me good documentation and refactoring manners. It’s only a problem for you if management does not accept that their velocity has gone down as a result of tech debt pilling up.

Code should scream it’s intent (business-wise) so as to be self-documenting as much as possible As much as possible is not 100%, so add comments when needed. Comments should be assumed to be relevant when written, at best. Git comment should be linked to your work ticket so that we can figure out why the hell you would do that, when looking at the code file itself. I swear some people seem to think we only read them in PRs (we don’t). Overall concepts used everyday, if they need to be reexplained, should probably be written down (at least today’s version). Tests are documentation. Often the only up to date one?

Git wasn’t used all that much in the 2000s. As far as I know it became popular in the 2010s (though it was always a thing in some circles I think) and then just supplanted almost everything else.

Also keep in mind some shops tend to follow larger tech companies (microsoft, etc.) and their product offering. So even new products might not have been on git until MS went in that direction.