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

help-circle








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







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





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