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.
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.
That said, working from home has so far saved me a lot of both time and money. This is a thing to consider as an employee when considering who to work for (or if your boss takes it away, if you still want to work there after essentially having a benefit revoked unilateraly).
Public transit pass. Actual time for transit which for me was around 90 minutes a day (7.5 hours a week!), more complex lunch logistics (time or money), etc.
A quieter workplace, no need to book rarely available rooms to take calls/meetings. There were upsides.
My first remote job had almost no issues at all. We already knew each other and we still took time to discuss issues via calls. New job not so much. We tend to be pressed for time so only focus on obvious “work” and then works suffers because of a lack of communication/common vision.
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.
We need a new paradigm for social media. And no, I’m not satisfied with Lemmy either (privacy issues).