• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle
  • “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.















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




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


  • The problem is, the way I see it, all energy use is connected. Basically the problem we have is energy consumption grows faster than clean energy production. So requiring more green energy in this context still sucks. Even where I live where all of our energy is green (at least in the grid), extra energy can be sold either via selling it to other provinces/states, or by making deals with companies to do their production here where energy is cheap and green.

    Energy is a commodity on a market. If you use it to inefficiently move people, you can’t use it for other things. Remember that to move a 150 lbs person in a car, you have to move about a ton and a half of car…