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
Search - "coworkers"
-
Be more passive
I always get involved in everything, at every company. Not to further my career through ass-kissing and overperforming.
I regularly piss off people. When C-level has a discussion about strategy, I'm usually ahead of them, ask too many questions, criticize every detail they've missed, cause frustration by making them look incompetent.
Can't help it, when I see retards destroy a great product I have to intervene.
Some people appreciate it. I often defend both devs and end users, when others don't dare speak up.
But fuck it, I'm getting older. I'm gonna coast a bit more. Sit back, relax.
If a product manager doesn't prepare enough tasks — that's cool, I still have a Factorio savegame to work on.
If another team designs an incredibly stupid feature — they'll discover the issues eventually by themselves. Maybe I'll warn once, just to be nice.
*Pours another chocolate milk*
Also gonna spend at least 4h/d with my daughter. She's a better human than most of my coworkers, and the work we do using her Legos is honestly more important for humanity than the Jira backlog.20 -
me: "ah, my scraper is nearly done - just need some final tweaks"
coworker: "JuSt FrOm LoOkInG aT yOuR ScReEn A fEw TiMeS tOdAy, I cAn TeLl YoU iT wOnT wOrK"
me, infuriated by his idiot mentality but not trying to start anything: "ah, its fine, I've already scraped 3000+ entities"
coworker: "but it wont work."
me: "but... its working..."
coworker: "but it won't work."
me: "ok."
sometimes its just better to just affirm the narcessistic assholes. make sure they are right.6 -
To the coworkers who won't read this -- If you have a question to message me, type the QUESTION ITSELF. Don't coyly request permission to ask me a question because you're worried you'll bother me, that just turns it into TWO questions. Let us put an end to saying 'hey, can I ask you a question' and then virtually walking away.10
-
I've been working with some new programmers now, trying to make this a place where people actually like working at. In my experience, most workplaces are bottom of the barrel shit, so I really wanted to try and make this the opposite, at least for the engineering team. When I hear them say how much they like working here, and how jealous their friends or family are at how much they are enjoying themselves and chilling with their coworkers and even their boss, it makes me feel so nice.
It might be a tiny company, but spreading happiness is great.1 -
How do you pronounce SQL?
"See for me, I just go my own way and pronounce it as ‘sqwool, or ‘sqwll’, which sometimes gets my coworkers (not db or programming people) calling it ‘Squirrel’. As such we have a custom written utility program which automates running certain SQL commands on various databases which is aptly named SQuirreL. Then we started to have fun with it: The ‘pre-defined’ sets of SQL are held in a ‘.nut’ file which you give to SQuirreL. When you want to see what scripts have been run, you check the SQuirrel’s .log to see what .nut files it has ‘eaten’. We thought about naming the log files .poop, but I felt that was too far. I know right now there’s people reading this cringing, but I say lighten up. My boss when presented with the tool, did not get ANY of the Squirrel/nut references… I mean the tool’s icon was a cartoon squirrel holding an acorn for crying out lout, but I digress.
So yeah, I call it Sqwll or Sqwool, but only when talking to people who don’t matter."
Source, in the comments: http://patorjk.com/blog/2012/...
I doubt this has ever been posted. =)9 -
Biggest challenge was to accept that no matter where you go, what you do, you will have to deal with stupid people.
They come in all ranges, starting from hr, interns, juniors, coworkers, code reviewers, seniors, managers, boss, clients.
And in order to grow in life, you have to learn to deal with them. Better even if you could make them a little less stupid.3 -
I got stuck with a small task for days, today I just have the courage to ask for help and a senior literally gave me the code for the problem! I'm not sure if I should be happy for finishing the task or embarrassed for couldn't solve the problem by myself. 😄😥6
-
I like like my boss and my coworkers and the place I work but for the love of goat cheese this org has the attention span of a toddler on meth.
Seriously, it's like this is your #1 priority, next week, wait we have a different emergency you have a new super critical urgent thing, then "hey team Y has a vendor coming in next month to integrate these two pieces and they need you to have half of it wired up by then so make sure you get that done." Like SERIOUSLY SERIOUSLY
HERE"S SOME LIFE ADVICE IT DOESN'T MATTER WHAT YOU PLAN OR SCHEDULE OR PRIORITIZE IF YOU END UP CHANGING ALL OF IT EVERY WEEK!
It's like painting a mural of a field, and then 10 minutes in you decide you'd rather paint a space ship, then you realize you don't like the space ship so instead you decide to change your painting to Elvis with a mullet, and you keep doing this. The end result is not beauty it's the mad deranged scribbles of a man past the point of sanity.
But for the love of Haliburton if they ask me why X or Y wasn't done I'll probably end up going full BOFH on somebody.3 -
I just don't get my coworkers. They tweak designs, they tweak functionality, but no task is made.
They just simply update designs in Figma, without notifying anyone or just msg me on Slack what to change...
How the fuck do you guarantee that all those tweaks will get reflected to the app? How do you guarantee I won't forget? How do you guarantee QA will test your stupid tweaks?2 -
Why the hell is JS so terrible, and why do so many people resort to using is as a back end. So many packages, so many outdated dependencies. My coworkers and friends have heard me rant about my constant frustration with this terrible setup.
I understand the need for dynamic html but why have we bastardized this language to the extent we have.
Keep your projects up to date, it saves people a lot of trouble in the future.11 -
"Biggest challenge you overcame as a dev?"
Overcame? I wish! I'm in the midde of fixing the worst legacy code clusterfuck I have ever seen...
Yes, it's even wayyyy worse than WorstPress...
There are days where my coworkers hear profuse laughter coming out of my lone bureau, some of them might already be thinking that I've gone mad. Maybe I have... bwahahahaha3 -
If I had to name one attribute that dominates the software engineering ecosystem, it would be “arrogance” especially among young programmers. I think software engineering would be a much better place to work if people were more empathetic than being ginormous assholes trying to have a leg up over all their peers. Collaboration is much more rewarding than competition. It feeds your soul and feels a lot more natural.
Collaboration over Competition.
Have a peaceful day at work guys!5 -
I think I've reached some kind of job nirvana. My coworkers and I all complain about our work. We're overworked, underappreciated, underpaid, and and have to deal with all sorts of bullshit all the time. Pretty much everyone who has been on the team longer than a year is talking about quitting.
But I started at this company as a level 1 tech support phone technician before I transferred into the DevOps side of things, and that tech support job was SO much worse. Way more stressful, way less pay, mandatory overtime, horrible scheduling, being forced to remain calm while people hurl insults at you over the phone, and it was a dead-end job with a high turnover rate and almost no opportunities for advancement of any kind.
And every time I think back on that job, I realize that what I have now is actually pretty great. I'm paid well (still underpaid for the job I do, but catching up really fast due to my current boss giving me several big raises to keep me from quitting lol). I deal only with other tech people like developers and data scientists so no more listening to salesmen insult me on the phone. I'm not in any sort of customer service role so I can call people on their bullshit as long as I'm professional about it. I'm salaried so they can't make me work horrible shifts. 99% of my days are a normal 9-5 workday. I actually have a reliable schedule to plan around.
People treat me like the adult that I am.
I'd get a similar experience at other, better-paying companies, for sure, but what I have now is still pretty great.
I'm sure I'll be back in a few days to rant about more nonsensical bullshit and stress, but for now I'm feeling the zen. -
Worst: being forced back into the loud distracting office, to add on to the badness the covid restrictions were not taken very seriously
Best: getting a new full time remote job and an awesome company with some awesome team mates
Bonus is I now work from home fully but can still hang out with my great former coworkers -
I am finally again at a company where I enjoy working and my coworkers are great that makes it easy staying motivated. Besides that need to provide for my family.2
-
Is the CS field creating terms for the sake of creating terms?
Someone mentioned a "closure" in another post. I instinctively knew what they meant by that based upon the code I saw. I had heard the term thrown around before, but it had not yet connected in my mind. I wondered why I had not been exposed enough to care.
So I thought: What does C++ have as far as closures?
I found that C++ has lambdas. Those are definitions for function objects. They do not exist at runtime. But a closure does. The analog is you have classes. They are definitions and do not exist at runtime. But instances of classes do. So at runtime the instance is what you are working with. This is the same as lambdas vs closures in C++. The closure is the runtime counterpart. Why a separate term for what essentially is an instance? Is it because it captures data and code? As far as I know the closure is all data that gets passed around that calls a function. So it is essentially an instance of a lambda.
Another term: memoization. I have yet to see this added to any dictionary in online tools like a browser. Is the term so specific that nobody cares to add it? I mean these are tools programmers use all the time.
My guess is these terms originated a long time ago and I have just not been exposed to the contexts for these terms enough. It just seems like I feel like I have been in the field a long time. But a lot of terms seem alien to me. I also have never seen these terms used at work. Many of the devs I work with actively avoid CS specific terms to not confuse our electrical coworkers. My background started in electrical. So maybe I just didn't do enough CS in college.6 -
So... This is something that happened some time ago.
I went to my company's end-of-year celebration party. Since I've done mostly contractor stuff, I didn't really know anyone and thought this'd be a good chance to meet my peers.
My coworkers ended up being mostly HR people, and I couldn't find even one person with common interests.
It was a 2 hour bus ride away, and I had to stay over at a friend's place for the night, but that wasn't bad.
The party itself well...it started at 7pm and ended at... 4 am During that time I just wanted to be somewhere else. I felt alienated and out of place. I couldn't even play phone games since I had lost my phone the day prior.
The one conversation I had was forced upon me by a smug bastard who probably worked at HR or management. Wanted me to agree with him on something while I just wanted to go drink alone. He kept redefining words and moving goal posts every time I disagreed.
Most of the "party" was people 10-20 years older than me dancing to music I hadn't heard since I was in middle school.
The food was bad and sparse. The drinks... not even good either. Cheap pub drinks. No decent mixes.
To top it all off I couldn't leave early.
Just felt like ranting about this4 -
When you get more managerial corrections on your projects and approaches to things than your coworkers do BECAUSE YOUR WORK IS SO MUCH HARDER AND MORE TECHNICAL THAN EVERYONE ELSE’S but you still end up looking dumb because you’re the only one being corrected on stuff.
-
i feel like a fucking failure, I am so tired of programming, i dont even like it anymore, and all my coworkers are programmer gods. I feel like a burden. Part of it might be imposter syndrome but for the most part its true.11
-
My fucking lazy-ass coworkers haven’t made meaningful progress on anything for months. I’m brought in as the tech lead and these stupid fucks didn’t work on any meaningful shit for literal months. Their manager was asleep at the wheel and their old tech leads apparently need months to make a couple of minor database changes.
So I’m brought in to fix it, and… surprise! They’re still lazy pedantic assholes. And they’re shocked - shocked - that people expect them to start completing a project or two per quarter. Like these dense motherfuckers thought that they could be the most annoying pedants this world has ever seen, and also do no work.
I could have done their whole 5 month project myself in a month. No joke. It’s incredibly simple. But somehow the overhead of coordinating people who A. don’t work very hard and B. assume that every ticket needs special attention and 6 hours of ponderous thought has eaten into the time we have.
I don’t respect them in the slightest. They’re such shitty developers. Whoever signed off on their hire was fucking high.5 -
I’ve been interviewing at a few companies lately. I’m a dev with ~6 years of experience with a specific language. Most of the experience comes from working in companies that developed their own software, not talking about cms stuff. Analytical, data tracking systems. Now working at a fintech. I’ve got an offer to work as a senior developer in a smaller tech team, with more salary. I’ve approached the current company about the offer and they told me that they don’t think I’m a senior dev and rather a strong mid level dev. The Hr also told me to think about if I’m really a senior and if the other companies expectations would be met. They would increase my salary, but not quite match it. It’s not too far off though. Their reasoning for this was that you need a lot of experience with their product (which does not correlate with seniorness of a developer, only the worth of specific employees for a company IMHO) and system architecture design. The problem is that we don’t see any tasks that could implement any system design for as log as I’ve worked here, so I don’t see how I could work into a senior role at this company. Of course imposter syndrome kicked in and I’m triple guessing myself if I should join the other company as a senior now. How should I aproach this? The current company is stressful to work at because of big workload, a lot of my coworkers think the same thing about the workload.11
-
(No punchlines just a rant sorry, very angry at this person. Can't leave the club. Talked to seniors about it. Talked to coworkers for some voluntary help. No help here ;-;)
Yesterday: we need to have a meet to plan things out. 3 PM?
Rainbow eating monster: Yes
Yesterday 5 PM: Reminder
Rainbow shitting monster: I can't I have important things
Yesterday 5:01 PM: Children eating monster (in group): hey yall watching the event going on rn
Yesterday 5:02 PM: is this what you're busy with?
Rabbit pooping monster: this of course I can't miss. And anyways I have 5 more things to do: thing that I've already done, this club meet that you asked me to do yesterday and I said I'd have done, a meet with a friend, I'm having lunch now, and a meet with you. Hence I can't meet with you.
...
Today (in group): Kidney stealing monster: @me (irrelevant to discussion) can you meet for other thing that *I* was supposed to do a week ago?
Will you be available @me at 5 PM?
Okay everyone, assuming @me is available, tentatively we meet at 5 PM.
Today 12 PM: i wake up to this faeces3 -
On Friday, 2 of my coworkers asked for help on a concourse issue, it wasn't building correctly, and they had been trying to figure it out all day. It was an old VB project, which was built very weirdly. We made some progress, but didn't get passed the error. I recommend asking in slack if anyone had gotten the error before, but the refused, saying that they could fix it.
Monday morning, and at standup they mentioned that they still haven't solved the issue and were going to work on it today. I once again mentioned that (blank) could help them.
Monday afternoon, and they are still stuck the same issue they had friday morning. I give up and contact (blank) myself, who mentioned they have seen this error before and shows them how to fix it. Five minutes later and they are back on track, past the issue.
Why are people so adverse to help, it should not have taken 2 days and me introducing them to accept help... 🙃1