Details
-
AboutJust the ++ fairy of devRant. Real life skills: Getting myself into complicated stuff. Losing friends. Languages: Georgian(native), Russian, German, English(chronologically). Have a nice day!
-
SkillsC#, Python, ProcessingJS, JavaScript, JQuery, HTML, CSS. Mostly online courses...
-
LocationSomewhere near a lake called a sea...
Joined devRant on 2/24/2017
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
-
When I started off working on this particular project under a new technical manager, I used to love working overtime because the work and the problem we were trying to solve was really interesting. My technical lead was also a really awesome dude and I was able to learn a lot of things under his guidance. A couple of times, I didn't even mind working on the weekends too in case we wanted to meet some strict deadlines. I wanted to make sure that my team's brand name does not get spoiled and we deliver on what we promise.
It was all good until all the management started taking our overtime and weekend work for granted. It took me some time to realize this. Now it almost became a part of standard expectations. It was getting irritating. Managers could see this uneasiness but chose to do nothing.
The work increased, so did the team and the communication channels. The newbies in the team now worked overtime and on weekends. And everybody started acting as if it was normal. That's when it stuck me that I am responsible for inculcating this unsustainable and life sucking culture in the team. I stopped working overtime and started questioning the set deadlines, often asking them to postpone things. Management got furious and changed their focus on the newbies who'd work overtime, often rewarding them to reinforce the behavior.
I tried undoing it, asking managers that the team will not work on weekends. There was friction and managers would agree but the old bad habited cultural spore would pop up tume and again and the team would go back to the regular overtime and working weekends thing. As more time passed, the managers would circumvent me and start talking to others in the team, giving them work and deadlines directly because I started to say 'No' when I felt the need to do so. I tried to protect some folks in the team who would not be able to speak up but were frustrated. I started caring less about the team's brand and more about colleagues who were suffering due to such unethical (and illegal?) practices being normalised in the team.
Trying again and again to get back to 'normal', I failed everytime. Unsure of how far I'll be able to go on with this without getting severly burnt in the process and seeing no respite, I decided to move on. I put in my resignation two weeks back and want to start a fresh in another company.
I feel I am responsible for bringing this into the team without realizing the repurcussions of my working overtime. Staying in the team for more than 3.5 years, I could actually feel how managers have no fucks about your personal life and work life balance (despite showing oh so much concern about the well being of my family) and would reward anyone who works as per their whims and fancies. I wish I never get to work for a management such as this.2 -
25 phrases you wish you could say at work more often
(Warning: Contains naughty words...:-)))
1. Ahhh...I see the fuck-up fairy has visited us again...
2. I don't know what your problem is, but I'll bet it's hard to pronounce.
3. How about never? Is never good for you?
4. I see you've set aside this special time to humiliate yourself in public.
5. I'm really easy to get along with once you people learn to worship me.
6. I'll try being nicer if you'll try being smarter.
7. I'm out of my mind, but feel free to leave a message...
8. I don't work here. I'm a consultant.
9. It sounds like English, but I can't understand a word you're saying.
10. I can see your point, but I still think you're full of shit.
11. I like you. You remind me of me when I was young and stupid.
12. You are validating my inherent mistrust of strangers.
13. I have plenty of talent and vision. I just don't give a damn.
14. I'm already visualizing the duct tape over your mouth.
15. I will always cherish the initial misconceptions I had about you.
16. Thank you. We're all refreshed and challenged by your unique point of view.
17. The fact that no one understands you doesn't mean you're an artist.
18. Any connection between your reality and mine is purely coincidental.
19. What am I? Flypaper for freaks!?
20. I'm not being rude. You're just insignificant.
21. It's a thankless job, but I've got a lot of Karma to burn off.
22. Yes, I am an agent of Satan, but my duties are largely ceremonial.
23. No, my powers can only be used for good.
24. You sound reasonable... Time to up the medication.
25. Who me? I just wander from room to room17 -
If Programming Languages Were Girls:
Java: Your current girlfriend, you've been going steady for a while now. Things are okay.
Kotlin: The girl Java finds you cheating on, she's just amazing, and you wish you'd met her sooner.
Visual Basic: The girl you accidentally started a relationship with because you didn't know how to say no. But quickly realised your mistake and regretted it.
JavaScript: A childhood friend you occasionally hook up with. But you could never settle for a relationship with them.
Python: A bossy, manipulative girl who quickly turned things sour. But everyone else loves her because of her huge libraries.
-----------------------------------------------------
My and a co worker were joking the other day about what programming languages would be like if they were girls. This is what we came up with (Original inspiration: the Distracted Boyfriend meme (Feel free to add your own!)).49 -
I will start my own companies:-
A.I. Job Centre (true A.I. would get bored of their employer and search for greater challenges)
A.I. Counselling (dev life)
A.I. Pornsites (because all A.I. should have a binary life of work and play <3)
A cake factory (so the cake is not a lie)
A.I. devRant (to lower their work efficiency)
I then use the funds from the above to hire a team and we'd develop a flawless Wannacry for A.I. (for a dementia like effect)
You can all have your jobs back and you're welcome. -
A programmer is walking along a beach and finds a lamp. He rubs the lamp, and a genie appears. “I am the most powerful genie in the world. I can grant you any wish, but only one wish.”
The programmer pulls out a map, points to it and says, “I’d want peace in the Middle East.”
The genie responds, “Gee, I don’t know. Those people have been fighting for millenia. I can do just about anything, but this is likely beyond my limits.”
The programmer then says, “Well, I am a programmer, and my programs have lots of users. Please make all my users satisfied with my software and let them ask for sensible changes.”
At which point the genie responds, “Um, let me see that map again.”4 -
A physicist, an engineer and a programmer were in a car driving over a steep alpine pass when the brakes failed. The car was getting faster and faster, they were struggling to get round the corners and once or twice only the feeble crash barrier saved them from crashing down the side of the mountain. They were sure they were all going to die, when suddenly they spotted an escape lane. They pulled into the escape lane, and came safely to a halt.
The physicist said "We need to model the friction in the brake pads and the resultant temperature rise, see if we can work out why they failed".
The engineer said "I think I've got a few spanners in the back. I'll take a look and see if I can work out what's wrong".
The programmer said "Why don't we get going again and see if it's reproducible?"1 -
'It's just...' is the biggest lie any co-dev can give you!
If it's just a small change why don't they do the god damn work and spend the next 2 days wading through an undocumented shit storm.
Next person to say 'It's just x, y & x', that ticket will be going up their tail pipe sideways! -
Working code?
Or fake compiler?
Fix a problem?
Or buy a new computer?
Bring a flash drive?
Or bring a hard drive?
Use water cooling?
Or use an ice cube on top a processor and memory?
Drink some coffee?
Or eat a healthy breakfast?
Do you make hardware?
Or software?
These are the problems programmers face from old people as employers or relatives trying to find something to relate to. -
Happy birthday to the best community for developers. Thanks for all the laughs, friends and good times you have brought us all.
-
A variable walks into a bar. Constant bartender: "We don't serve your kind here!"
Variable: "What kind?"
Constant: "You know, sluts!"7