• 0 Posts
  • 312 Comments
Joined 1 year ago
cake
Cake day: August 6th, 2023

help-circle


  • Well, there you go - the issue is with the company and the irreplacable boss. He is the weakest link obviously. Imagine he gets into a car crash, gets hit by a bus. Suddenly all his knowledge is gone, either for a while when recovering, or forever. Knowledge transfer is incredibly important. Things like tickets, scrum, kanban etc are used because they work for every type of person - they serve to transfer knowledge, the hierarchy in a team protects the programmers from shit they shouldn’t be dealing with (that’s the project manager’s role, to be a shield for the team, to curate the the messages comming from “higher up” and the ones sent out by the team). The most important thing to know is that “do the needful” is about as shitty of an ask someone can pose to a programmer. People doing that don’t know what they want, and instead rely on what they don’t want - once you actually implement something that remotely fits what they needed. As for clients not reading specs - it might be time for someone to have “the talk” with them (obviously not you). One thing you need to know is that shitty clients can be fired too, once the development starts breaking down, the communication is arse etc.

    For the people on the road - they probably took it as you trying to bail on them. But yeah, impulsivity when things are getting heated is never good, it’s better to stay silent for a few seconds and then say something, rather than immediately say something that can be taken very badly.


  • How long are you working as a software dev? Basically a lot of new devs want to “save the world” by closing tickets and using that as a metric if they’re doing well or not. The reality is that a software dev’s job is just about as much writing, as dealing with clients, going to meetings, etc. People might value you for things that you don’t think have value. For the cut out for this part - you most likely are. Imposter syndrome is normal, I had it too, even 6 years into my career. Been the “goto guy” for the team, multiple times a teamlead at 3 different companies / teams. Never had a problem I couldn’t google away. Yet in the back of my mind, there was always a “maybe you’ll encounter one on the next ticket? And they’ll fire you for it” etc. I managed to silence that shit and bury it deep behind all of my achievements.

    For the second part - some people are just idiots, some are governed by emotion, etc. Also, saying “it’s not so bad” is a shit way to deescalate the situation ^^








  • Who tests the useless survey? Everyone with regression tests. Like dude, everything you talk about has been written “in blood” from years of hosting production systems. If the useless survey is needed, then write a test for it, or a testcase to manually try it. Don’t just upgrade, see that the app is up and push to prod, that’s not testing, that’s asking for trouble.


  • Okay, let’s be angry at the company and frown a lot at what happened. Gurr, bad company, evil.

    And now think of what you’d rather have - a working system, or a reason to be angry? If you have something that integrated with something else, lock it down at a specific version so you control the upgrade and know those versions work 100% of the time together. “Latest” is just asking for trouble - be it in a docker image, in dependencies or elsewhere. It’s absolutely not a “best practice” if it isn’t even a code smell or an outright bug. You could’ve had a slightly outdated version, which won’t be “exploitable” - you wouldn’t have enough time to exploit anything in that time, especially with smaller companies and obscure exploits.

    Instead of putting out the fire, you could’ve been now looking into the upgrade, seeing on UAT or Test or whatever that forms aren’t supported, chilling till they are supported or complaining that they aren’t.

    Upgrades breaking shit is like programming / devops 101, and a huge reason for technical debt in very old projects. Leaving all that to chance is just irressponsible.






  • Ya, zero risk to everything once you get 7 or 8 police wielding them at the same time, per one violent person, in a crowded subway with potentially no walls to pin them down to, with the extreme possibility of someone just pulling a gun on you when you have both your hands occupied with a stick. Mancatchers work great on gifs and videos, but suck in the actual world. Especially when you get charged by a dude wielding a knife. You’ll 100% have the time to “break the glass in an emergency” and to deal with said person. Especially when the situation turns from “let’s run after this guy that skipped the fare” into “holy shit that’s a knife and I’m going to die”.



  • A lot of people learn this lesson sadly. It isn’t “sexy” to brag that you have a gold / platinum rated high quality PSU. People would rather add a “Ti” or a “10” to their graphics card and then lose it all when it goes. Same reason why I have an UPS for home PC - sure, overvoltage, undervoltage, electrical noise probably won’t harm the PC. But why risk it? Also having a battery to save your shit, or buy more electricity online when you run out on a prepaid meter is cool (speaking from experience, happened to me like 10 times already lol)