Joined devRant on 10/14/2020
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Mac fucking book pro! No! Just because I brushed up against you doesn’t mean I want you to boot up! Do you think I’m that eager to turn you on? Is the usual brain dead Apple user that fucking lazy to not wanna press a button to turn his computer on? And there’s no fuckin’ way to change this behavior!? I tried changing system variables but none of the suggested tips work. And you even have Apple support people ask: "why WOULN'T you want it to boot up if you sneeze on it?" FUXKKLK12
I’m rarely at the initiative of a meeting, but when I am, my approach is: what questions need to to be answered? Time spent in the meeting is answering those questions without beating around the bush. I request precise answers, no "we shoulds" or vague responses. Meeting usually ends with clear answers/resolutions written down and shared so there aren’t any "that’s not what we agreed upon"1
This was a long time ago when I was a pizza delivery guy (summer job). One of my managers could barely handle any pressure. He would often lose it during the dinner rush. He was disorganized and never gave clear directions to his team. One night he totally blew up. He threw a large pizza shovel across the kitchen. It went crashing into the oven in a loud bang. This was in full view of customers on the other side of the counter and several of us workers, all in shock.
It was my last night there as I had handed in my resignation letter two weeks prior. Boy was I glad to get out of there8
Anyone here use generator functions in JS? Seems like it could be useful but whenever I explore the possibility of using one, I usually end up going another route9
This was a pretty bad interview process
What’s funny is that they told me I lacked experience, but then within the following year they called me at least 5 times asking if I was available, as they were desperately looking for someone.
How do you guys deal with looking for a new job while still working at your current job?
I’ve been having to sneak out of the office for phone interviews. Not fun…4
The good ol’ days of devRant where one could get +600 upvotes for a corny joke
(I’m not jealous 😁)7
PM (on slack): "we’re about to deploy to production".
… I keep on working on a task / remain available for any post deployment issues …
PM (5 minutes later on slack): "deployment broke production! We need to handle this NOW!"
My dev colleague has already called it a day, but I’m still online
Me: "ok I don’t have access to prod, can you describe what’s going on? I can’t reproduce on any other environment"
10 minutes go by
Me: "anybody there?"
45 minutes later, I realize PM is offline
The following day:
PM: "ok we got prod running again" (turns out it was client’s fault for not updating a config we as devs can’t access)
PM: "but we’re REALLY UPSET! You guys need to be available to intervene for any issues following deployment to production! At least one of you should be available!"
Me: "but, but…" 14
Here I am for three months trying to implement TypeScript in this project that was a dump when I picked it up.
And then some morons get assigned to the project and just start adding @ts-nocheck everywhere?
Like, WHAT THE ACTUAL FUCK?
And then you wonder why the project is bug-ridden??
Me reviewing PRs lately:
"Should I fight it now, or should I let the abscess grow?"
But in my distress/demotivation it’s usually: peace now, pain later2
I had previously ranted about being assigned to a very messy project. I spent 3-4 months alone adding features and CLEANING things up.
Recently, there had been talks about a new major development phase on this project. But things lingered and the day before I’m to go on vacation, I get the news that this new phase starts in 2 days. Since I’m going to be on break they’re putting other guys on the project who don’t know anything about it.
Fast forward two weeks later.
I’m back from vacation.
I find out one of the guys has strong opinions about doing things certains ways… but unfortunately they are "ways" of unnecessary complexity, abstraction and verbosity.
After just a couple of weeks I’m already lost in the complexity of his code, which supports features of VERY LOW complexity. Fuck, has he ever heard of KISS? Has anybody heard of it where I work?
Now I have to spend my mental energy trying to make sense of this pile of crap rather than actually spending it getting things done.1
[Half question / half rant]
Would you rather work with a laid-back, humorous colleague who produces shit code and won’t understand advice for improvement?
Or would you rather work with someone who’s more serious, even slightly boring, but who takes quality seriously and is open to advice?
Yes I’ve worked with both types. Hands down I prefer working with the latter. With the first dude I’ll have good conversations and a good laugh at his puns and jokes. But at the end of the day I’m pulling my hair trying to make sense of his code and spending a shitload of time reviewing his PRs just to make sure he’s not fucking things up even more.4
Product owner (who is also the application administrator): please build feature to allow administrators to create automatic alerts to be sent to application users
Feature gets built, tested and deployed to production
Two months later:
PO: I've noticed in our monitoring tool that there haven't been any alerts sent out to users. What's going on??
Me: well have you created any automatic alerts?
PO: umm, no. How do we do that?
Me (inside): 🤦2
Improvement request: if search doesn’t return anything the search text is erased. It’d be nice if it didn’t so we can amend our search more easily.
Devs who use the array map method for purposes other than generating a new array, and who use an empty return statement to satisfy the linter, should receive a slap in the face. A gentle one, but a slap nonetheless3
Today was a bad dev day working on a shitty React project. Not that React in itself is bad, but it can be hell to work with when the code is a big pile a crap full of anti pattern code. I spent the day refactoring to try to fix a bug, but to no avail. It would take days if not weeks to put some order in this mess and to prevent such bugs.6
Ha ha ha ha. Fucking morons!
You brag about being a highly skilled company.
You tell me I don’t have enough experience despite three years of uninterrupted activity where I currently work
You’re willing to give me a chance (I just don’t know how to express my gratitude)
BUT among your super talented team members you can’t find anybody capable of conducting a technical interview?? And you’ve been looking for over a month for someone who could do it?
Thanks for wasting my time with three useless HR interviews you worthless DIPSHITS!2
I feel like some developers focus too much on concepts like clean code, software craftsmanship, TDD and so forth, to a point where they almost forget end user needs (ease of use, intuitive experiences, general UX principles).
Don’t get me wrong. I do my best to stick to a decent standard of quality and maintainability. However my solutions are adapted to the specific needs that are being addressed rather than the other way around.
I’ve heard some devs say things to the effect of ”well I know that’s not most intuitive behavior for the user but it’s the cleaner way to do it, so the user will just have to figure it out“. So in essence they’re just coding for their own pleasure rather than addressing user needs4
I’m sooo excited when any new frontend JS framework is available. Angular, React, more recently Vue, Svelte. Bring ‘em on. I wanna try them all.
As long as the tools at hand allow me to get the job done, keep clients and end users happy, I don’t give a fuck.
This meme is actually the epitome of what I hate with a lot of web developers I’ve encountered2
FaceBook, over the years you’ve proven that you can’t be trusted and you still have the nerve to ask for this type of personal data?5
Client project manager calls me up one day
PM: hey can you make some precise estimates on some items for a project you’re not working on? It should be easy. It’s very similar to the project you ARE working on and it’s only a handful of user stories, mostly front end stuff. We´ll need this to be done by tomorrow night.
Me: um, I guess if it’s just a few simple items. ok
PM: great! I’ll let you know when you get access to the backlog.
Me: sounds good
Link to project is sent to me. Backlog contains over 20 user stories, most of which are backend related. And it doesn’t have much to do with my current project.
I contact PM: this isn’t exactly what you announced when I had you on the phone. If you want precise estimates with a minimum of design, this could take up to a week. I could however proceed to some ballpark estimates (poker planning) for starters if you need this quickly for your roadmap.
PM: no I need PRECISE estimates down to the hour for each item.
Me: ok then, it’ll take up to a week.
PM: 🤬🤬🤬. You told me it could be done in a day. I’m coming to realize your word can’t really be trusted.
So the other day I randomly checked out a few job postings on some recruiting agency’s website. Didn’t even sign up or anything.
The very next day I get a call from them. The person on the phone tells me they noticed I had visited their website and was wondering if I was interested in applying to any of the offers. Even as a developer I was totally taken aback as to how they managed to track me down based on a single visit.
I believe I ended up on their website by clicking on a link on LinkedIn. I’m assuming it’s via LinkedIn that the managed to get my info (phone etc.). All in all I’m not extremely surprised. But to me it’s downright creepy and it makes me feel like I’m being stalked. Also it makes recruiters look totally desperate and I’m not sure I would want to entrust them with the responsibility of handling my career4
In my three years experience so far I can honestly say that 100% of the developers I've worked with are narrow sighted with regards to how they develop.
As in, they lack the capacity to anticipate multiple scenarios.
They code with one unique scenario in mind and their work ends up not passing tests or generates bugs in production.
Not to say I'm the best at foreseeing every possible scenario, but I at least TRY to anticipate and test my code as much as possible to identify problems and edge cases.
I usually take much more time to complete tasks than my colleagues, but my work usually passes tests and comes back bug free. Whereas my colleagues get applauded for completing tasks quickly but end up spending lots of time fixing up after themselves when tests fail or bugs appear.
Probably more time wasted than if they had done the job correctly from the start. Yet they're considered to be effecient devs because they work "fast".
Non tech hobby of mine: bird watching (you may have guessed based on my username). Although it’s a non tech hobby, there are so many great apps to help identify birds and learn about them. EBird, birdnet, Merlin, picture bird etc. I also have a few books about bird watching.
Crazy how many different kinds of birds you can see when you really start paying attention.5
So about two months ago in my consulting firm I was asked to replace a colleague on a project (node and Angular). The project is only a few months old but it’s already a total clusterfuck. DB is very poorly designed. It’s supposed to be a relational database but there’s not a trace of a foreign key or any key for that matter and I’ve seen joins like tableA.name = tableB.description (seriously, that’s your relation??). The code is a mess with entire blocks of code copied from another project and many parts of the code aren’t even used. He didn’t even bother renaming variables so they would make sense in the context they were shamelessly thrown into. The code is at best poorly typed if not typed at all.
During our dailies I sometimes express my frustration with my other colleagues as I very politely allude to my predecessor’s code as being hard to work with. (They are all “good friends" with him). I always get the same response from my colleagues: "yeah but you’ve gotta understand Billybob was under a lot of pressure. The user stories were not well defined. He didn’t have time to do a proper job". That type of response just makes me boil inside.
Because you think I have time to deal with this shit? You don’t think I’m working with the same client and his user stories that are barely intelligible? How long does it take to write type definitions for parameters going into a function? That’s right, 30 seconds at most? Maybe a minute if it’s a more elaborate object? How much time do you think you’ll save yourself with a properly typed function or better yet an interface? Hard to tell but certainly A LOT MORE than those 30 seconds you lost (no, the 30 seconds you INVESTED) in writing that interface!!!
FUCK people with their excuses! Never tell me you don’t have time to do a proper job! You’ve wasted HOURS of my time just because you were too fucking lazy to type your functions, too lazy to put just a little more thought into designing your tables, too lazy to rename a variable so that it’s name actually makes sense where it’s being used. It’s not because you were short on time. You’re just lazy!
Thursday afternoon. Client gives us the go to deploy the latest release to production.
Friday late afternoon; my colleague - "wait, did we ever deploy"? Me - "uh, nope".
"Alright have a good weekend"
Client: please be sure to let us know with enough notice if you plan on taking any time off so we can anticipate how to operate during your absence.
Me to client 4 months before vacation: "I’m going to be on vacation in July for such amount of time".
Client: OK thanks
Client 3 months before vacation: are you taking any time off this summer?
Me: yeah I’m taking such amount of time in July.
Client 2 months before vacation: are you taking any time off this summer.
Me: yeah I’m taking such amount of time in July.
Client a month before vacation: wait you’re taking time off this summer?
Me: yeah, in July.
Client: oh, we need to start figuring out how to manage your absence.
…client has enough time to figure things out.
Client two weeks ago: we’re switching you to a another project where you’ll be replacing someone who’s leaving; and you’ll be developing alone. You’ll be working closely with our software architect. He’ll be the one who can answer all your questions.
Me totally lost on new project as it’s barely documented, sql tables are a mess with barely any relations between them and data structures are totally inconsistent. Supposed to be getting info from partner APIs but I can’t test them and don’t know exactly what data to expect. Only the software architect has the necessary knowledge.
Client a week ago: hey don’t hesitate to reach out to us if you have any questions. We can’t afford to fall behind from schedule.
Me: oh don’t worry, I’m already flooding your guy with questions.
Me last Monday to client: hey do you know what’s up with your architect? I’ve been waiting for him to answer some important questions and it’s going to be hard to move forward without him getting back to me.
Client: you’re telling us you’re not going to be able to move forward efficiently until our architect gets back from vacation in two weeks?
Me: wait, he’s on vacation?
(on the inside: when the fuck were you guys planning on telling me he would be gone???)4