Details
Joined devRant on 11/3/2022
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Talent Acquisition/HR: 🤪
Dev: 🤪
Technical Interviewer: 🧐
Dev: 🧐
Hiring Manager: 🤡
Dev: 🤡
This strategy has yielded some dishearteningly successful job application results this week.6 -
Interviewer: I don't understand. With a resume and portfolio like yours you shouldn't be applying to companies like us. You should be setting your sights on companies like Google/Meta. You'd be bored here after everything you've done so far. I know we're offering more money than your current position but you're worth more believe me. I'm going to keep looking, and so should you. But you need to aim higher.
Dev: ...
Well fuck me I guess?21 -
People that say they want things ASAP. But really mean "no rush, whenever you get to it". Can go fuck themselves.3
-
*In teams meeting with client*
Manager: Yes we can do all of that and it will be actioned very quickly. We will make all of these feature requests top priority. We will set aside everything we are currently working on in order to get this done!
Dev: ...Are you writing any of this down?
Manager: I don't need to, I always remember everything!
Dev: Just so you are aware, I'm not writing anything down. You're going to need to create a ticket with requirements spelled out for each one of these promises you're making otherwise they won't get actioned by the team.
Manager: I know that!
Dev: ...
*Later that day*
Ticket Title: Action client feature requests TOP PRIORITY!!!
Ticket Description: *empty*
Dev: ...10 -
Today we interviewed a _very_ good Angular1 Dev, by chance we showed him the forked ngRouter module we use, after some debate he explained that we were using it incorrectly.. I asked if he'd used it before to which he responded:
"Yeah, I'm the guy who built it"
😅26 -
Got a senior dev at work.
The guy is good at his job, no doubt, but his insecurity drives me up the wall.
- Constantly double checks work done by non-seniors.
- Setup a policy where only seniors can code review.
- Tells non-seniors not to give out advice as they don't know what they're talking about.
- Edits pull requests for you.
- Demands unobtainable quality for insignificant pieces of work.
- Patronising teams messages on the regular.
We're all just trying to get work done and he's always acting like we haven't got enough stripes on the badge.3 -
How my year has gone so far...
Management: Bobby, we are replacing your old hammer.
Me: Ok cool.
Management: Well actually there's so much going on...here is a wrench instead.
Me: But, this isn't a hammer.
Management: Yes we are aware but we are busy and cannot buy a hammer for a several more months.
Me: How the fuck am I suppose to hammer nails with this?
Management: Oh gosh you are right. That sounds difficult. We will grind down one side of it so you have a flat surface to hammer in those nails.
Management: Oh and by the way, those nails are super important so don't screw anything up.12 -
17,000 USD a year?! That's outrageously high (for a Philippino)!! This dev must either be a god or they're ripping us off!
-
At the data restaurant:
Chef: Our freezer is broken and our pots and pans are rusty. We need to refactor our kitchen.
Manager: Bring me a detailed plan on why we need each equipment, what can we do with each, three price estimates for each item from different vendors, a business case for the technical activities required and an extremely detailed timeline. Oh, and do not stop doing your job while doing all this paperwork.
Chef: ...
Boss: ...
Some time later a customer gets to the restaurant.
Waiter: This VIP wants a burguer.
Boss: Go make the burger!
Chef: Our frying pan is rusty and we do not have most of the ingredients. I told you we need to refactor our kitchen. And that I cannot work while doing that mountain of paperwork you wanted!
Boss: Let's do it like this, fix the tech mumbo jumbo just enough to make this VIP's burguer. Then we can talk about the rest.
The chef then runs to the grocery store and back and prepares to make a health hazard hurried burguer with a rusty pan.
Waiter: We got six more clients waiting.
Boss: They are hungry! Stop whatever useless nonsense you were doing and cook their requests!
Cook: Stop cooking the order of the client who got here first?
Boss: The others are urgent!
Cook: This one had said so as well, but fine. What do they want?
Waiter: Two more burgers, a new kind of modern gaseous dessert, two whole chickens and an eleven seat sofa.
Chef: Why would they even ask for a sofa?!? We are a restaurant!
Boss: They don't care about your Linux techno bullshit! They just want their orders!
Cook: Their orders make no sense!
Boss: You know nothing about the client's needs!
Cook: ...
Boss: ...
That is how I feel every time I have to deal with a boss who can't tell a PostgreSQL database from a robots.txt file.
Or everytime someone assumes we have a pristine SQL table with every single column imaginable.
Or that a couple hundred terabytes of cold storage data must be scanned entirely in a fraction of a second on a shoestring budget.
Or that years of never stored historical data can be retrieved from the limbo.
Or when I'm told that refactoring has no ROI.
Fuck data stack cluelessness.
Fuck clients that lack of basic logical skills.4 -
Third World country: *has power outage because of corrupt government*
Our outsourced devs: Hey sorry boss, we will not be able to work today because there was a power outage. We'll make it up for it during the weekend! We're saving up for a power generator so this doesn't happen again!
Manager: These lazy @#$@ (racial slur) are so lazy and stupid!8 -
AWS has identified suspicious activity on my account.
I'm using it for the first time in 2 years. That's the suspicious activity.5 -
To all the data engineers in here: WTF is going on in your field?
I've worked closely with a dozen data engineers in the last 5 years (and talked to friends and internet strangers about this and get similiar responses), mine if them seem to know how to use a computer!
They don't understand git, ORMs, best practices, how to use a terminal, DAGs (important for using modern ETL scheduling tools like airflow and prefext), etc
Guys with 10 years of experience on their resume and they can't wrap a model into a flask app with 1 endpoint. They'll reference local files on their machine in w jupyter notebook and are shocked it won't work on other computers!17 -
Our IT team keeping our PET Production server alive by resizing partitions on the fly.
#living-on-the-edge
#caveman-practices
-
Don't you just hate it when the government decides you have to pay a new tax, and its backdated too !
There goes $5k USD.. :-(
Lucky I had just over that saved up !
Today's wisdom = keep money aside for a rainy day.16 -
I am a junior / new grad and I am working at my first job out of school. The software team is very small (around 5 people) and we maintain a very large project. Since the project is so large, each member of the team is responsible for a specific part of the project.
Other members on the team work on embedded and low level programming. I am responsible for only the web interface to the project.
I recently just figured a solution for a problem that I had been exclusively working on for almost 2 months.
I tried asking for help from other members of my team when I was working in this problem. However, most of them told me that they do not have the time to become familiar with the my codebase inorder to help.
As a junior, what am I supposed to do in this situation? I know I could’ve asked a question on stackoverflow but I thought that if members of my team helped me, it’d be a beneficial mentorship experience.
What are your thoughts?7 -
4+ years ago, in an interview, I was asked if I was familiar with keeping backups of my code on Google Drive.
When I asked them to explain what that is, they said that after a deployment, they make a ZIP file of the project and keep it on Google Drive.
When I asked about using GitHub/BitBucket they said they don't know what that is and neither do they intend on using it.
So yeah .....12 -
> Manager gives me new ticket.
> This seems like a ticket Dingus would do.
> Remember Dingus got fired a month ago.
> Realize I’m the new Dingus.4 -
Is this really what tech-startup culture is?
A year ago I wanted to make a change and joined my friend who is a VP at a startup. She and my team are great even up to the C-suite level. But after a recent encounter with the core developer team here… I’m at my
breaking point.
This dev team is extremely tribal. It’s as if they view other tech teams as “others” and it’s “us vs. them”. My team works on a different vertical so I’ve never interacted with them before and a timeline of events is below. Is this kind of behavior a normal thing at a tech startups?
/story
Here’s some highlights from the last month…
- Customer demands a deliverable because it’s in a contract signed a year ago.
- No one in dev can be troubled to lift a finger (holiday season). I get called in to support.
- This isn’t my code - I’ve never seen or used it before.
- None of dev’s documentation is up to date.
- Find out dev hasn’t touched client’s project in a year.
- Spend weeks working with it. Find fundamental flaws which could have put us in legal jeopardy.
- I realize dev never finished this project because it doesn’t even have basic functionality to do what customer needs.
- Spent entire Christmas/New Year working.
- Create dozens of bug tickets and merge requests.
- Barely squeeze by and save multi-million $ contract renewal.
So what happens next?
- Reprimanded by the dev lead. He tells me I’m “hurting people’s feelings” by pointing out so many problems.
- A PM in a public Slack channel told me I was “passive aggressive” for a Jira issue where I wrote (verbatim) “Can we enable code highlighting in this text box? It’s difficult to show steps to reproduce the bug.”
- get told by VP to stop talking to them
- a bunch of merge requests rejected without explanation
- weeks later I see someone in dev run into a bug I found. I sent him the fix. They accepted his MR in the same day and it actually added another new bug.
- I lookup the recent commits of the lead-dev who chewed me out, he’s been working on adding colors to his console log output for print debugging. This is a time-critical application and he adds 30% overhead with logging debug information in production.
- Meanwhile dozens of major bugs exist and are ignored.
- The CTO at this company loves these people - though he hasn’t brought in any new business (literally) ever.
- My team is about to close a new contract and we’ve spent 15 days to work on it.
- The CTO said my team is slow and doesn’t fit with the business model of the company.
My team has never dealt with these devs before, so I checked Glassdoor for other experiences, the dev team apparently…
- uses “vulgar slurs for women”
- talking about technical issues “resulted in a lot of resentment”
- has an apparent “desire for revenge”
/ end story
This last month really shocked me because for my career so far I’ve never dealt with this kind of behavior. I could see a startup accepting this kind of culture if was bringing in a lot of revenue but they aren’t. They dropped the ball so hard we all lost our bonuses this year. It’s made even worse with the fact that they are constantly producing complete dog poop code (I’ve kept that opinion to myself though).
I’m really left wondering if this is just how it is in the high-stakes startup world.
Sorry - this started out as a question but ended up another dev rant.10 -
Dev: Why do you have an identical if statement right below this one?
Manager: Because I want the code to double check, obviously.
Dev: …22 -
Hiring process is fucking broken ok?
We all do have something else to do, nobody wants to do "homework" for 4 fucking hours. Which let's be real, isn't 4 hours. It's always more. I try to squeeze it in a least amount of time which means mistakes will be made. I always try to show my knowledge of the language and it's features. But, you didn't do X. That's it, that is a no from us.
Dude, I just wrote a high production grade small project with 90%+ test coverage and you are telling me that those 2 small shit I made is a big deal? Fuck off
Most companies I worked with have a code full of shit and here I present to you, with a poetry and it's a no because of X?
My bet is that if I ever started to work there I would find a code that isn't tested and is in shit state
\rant4
