Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)S
Posts
0
Comments
29
Joined
3 yr. ago

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

  • Takes time to become ubiquitous.

  • Sure, we are terribly behind schedule and will take losses for it (in what form I do not know, but for sure it won't be pretty).

    But we need more and more energy and will need more, and even that growth in that graphic is not enough to prevent fossil fuel use from growing. At least until people wisen up that we'll just need to learn to make do with less energy per capita... I'm not convinced that part will ever happen.

    Not to mention I'm not sure how much wind and solar you can do at the same time in the world. At some point everyone will need the same materials...

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

  • Professionals should care about their client's privacy though. That shouldn't be a debate.

  • Except that instead of an authoritarian government using it to totally control the learned populace, they are showing you ads.

    We've still got a way to go before 1984. If it did happen, you wouldn't be able to discuss it.