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 - "teamleader"
-
tldr:
everyone got the same hardware because senior dev liked it
So my project team was allowed to buy some hardware (monitors/keyboards/mouses etc.) so teamleader asked what we want.
senior dev: i need 1 monitor because i like to work with 1 monitor. i prefer this 27' zoll 4k monitor for around 1k dollars. since i work with multiple pc's i like this bluetooth keyboard and mouse because u can pair them with them and switch witch a click between the pc's costs around 300 dollar (1 setup of this costs 1'300 dollars)
me: so i like to use 2 monitors because i tried out multiple setups and this works for me the best (also what i have at home). but they dont need to be fancy. 2x 24' zoll montitors for each 200 dollar are enaugh (together 400 doller)
i also only work with 1 laptop and would like to have just a simple keyboard and mouse with cable because everytime they dont respons or battry runs out im fk triggered. so for me its okey if its this 30 dollar keyboard and 20 dollar mouse. it would be cool if i could get this mechanical keyboard for 80 dollars but not really needed. i only prefer mechanical keyboards a little bit more. and also i would like this mousepad i really like. it makes the mouse super responsive it's also just 10 dollars (this setup cost 510)
so at the end the teamleader was like. ah u know what senior dev has more xp and knows whats better for coding so we only buy this for every dev. but that 10 dollar mouse pad is okey u can get this extra its not that expensive.
WTF why u dont give me the cheaper setup which i more like. and why u even ask.4 -
TeamLeader: I need you to stop disagreeing with the decision of the management, the people in there are taking their decision for a reason.
IHateForALiving: When integration tests were failing, the management decided to comment out the ingration tests; god knows how many bugs slipped by.
When users had problems with the idiotic migration process the management designed, the management decided to remove down migrations; it took two weeks before the QA team started screaming, as all their machines were filled with garbage data.
I was writing type definitions for my code, you removed it. You effectively ensured the only person capable of working on that particular piece of code would be me.
I have been proposing for 8 months to make a unified scheduled jobs system, you all decided to create at least 5 different -and incompatible- implementations, at least 4 of them are total garbage with setTimeout, there's no way to ever unify them and God willing they never break, if they do there's NO WAY to find out even where tf they're hidden in the code.
Every time you were making one of those bad decision I was the only one warning you of the problems you were creating. The idiotic change of the day is going MongoDB+Angular: I can keep a low profile if you want, but when this blows up you can be damn well sure I'll handle my 2 weeks notice because there's no way on earth I'll be stuck with the aftermath of you lot taking technical decisions you are clearly unable to manage.11 -
I missed a week of school while I was sick, and in that week my teammates made a deal with the client to have a prototype for him in 3 weeks, AFTER asking me (teamleader) how long it would take (4 weeks min.). Why don't they FUCKING listen to their teamleader!! They're gonna have a bad time in the future...
And now I have to spend my whole night writing a prototype because THEY told a wrong estimate...3 -
Teammember left. I did his three tickets yesterday. Before that I created and applied new rescue procedure for broken deploys on production and deployed the app manually. Took me about 6 hours to do this right, find the cause, and solve it, and document what I did. After that my teamleader bought me a launch :)
It wasn't his, my former teammate responsibility to bring back prd to life, it was me being good and engaged employee. His tickets, on the other hand, were his duties. Took me one hour to code them. He was working on them for two weeks. I can't wait for the performance review, im definitely going to ask for a nice rise :)1 -
This happened yesterday during 1-2-1 meeting
My dear teamleader telling me.
"You're just a stupid consultant"
Well, this 'stupid consultant' has had enough of your bullshit and will look for future endeavors elsewhere.
You are free to consider your options and make the bad decisions, dear team 'leader'.
Cry at the sheer amount of work 'your' project really entails and I will revel in your failure
I'm done with this guy.
Team leaders should be ousted if they fail their team members and the projects they are responsible for.6 -
A (work-)project i spent a year on will finally be released soon. That's the perfect opportunity to vent out all the rage i built up during dealing with what is the javascript version of a zodiac letter.
Everything went wrong with the beginning. 3 people were assigned to rewrite an old flash-application. Me, A and B. B suggested a javascript framework, even though me and A never worked with more than jquery. In the end we chose react/redux with rest on the server, a classic.
After some time i got the hang of time, around that time B left and a new guy, C, was hired soon after that. He didn't know about react/redux either. The perfect start off to a burning pile of smelly code.
Today this burning pile turned into a wasteland of code quality, a house of cards with a storm approaching, a rocket with leaks ready to launch, you get the idea.
We got 2 dozen files with 200-500 loc, each in the same directory and each with the same 2 word prefix which makes finding the right one a nightmare on its on. We have an i18n-library used only for ~10 textfields, copy-pasted code you never know if it's used or not, fetch-calls with no error-handling, and many other code smells that turn this fire into a garbage fire. An eternal fire. 3 months ago i reduced the linter-warnings on this project to 1, now i can't keep count anymore.
We use the reactabular-module which gives us headaches because IT DOESN'T DO WHAT IT'S SUPPOSED TO DO AND WE CANT USE IT WELL EITHER. All because the client cant be bothered to have the table header scroll along with the body. We have methods which do two things because passing another callback somehow crashed in the browser. And the only thing about indentation is that it exists. Copy pasting from websites, other files and indentation wars give the files the unique look that make you wonder if some of the devs hides his whitespace code in the files.
All of this is the result of missing time, results over quality and the worst approach of all, used by A: if A wants an ui-component similar to an existing one, he copies the original and edits he copy until it does what he wants. A knows about classes, modules, components, etc. Still, he can't bring himself to spend his time on creating superclasses... his approach gives results much faster
Things got worse when A tried redux, luckily A prefers the components local state. WHICH IS ANOTHER PROBLEM. He doesn't understand redux and loads all of the data directly from the server and puts it into the local state. The point of redux is that you don't have to do this. But there are only 1 or 2 examples of how this practice hurt us yet, so i'm gonna have to let this slide. IF HE AT LEAST WOULD UPDATE THE DATA PROPERLY. Changes are just sent to the server and then all of the data is re-fetched. I programmed the rest-endpoints to return the updated objects for a very reason. But no, fuck me.
I've heard A decided (A is the teamleader) to use less redux on the next project and use a dedicated rest-endpoints for every little comoutation you COULD DO WITH REDUX INSTEAD. My will is broken and just don't want to work with this anymore.
There are still various subpages that cant f5 because the components cant handle an empty redux state in the beginning, but to be honest i don't care anymore. Lets hope the client will never find out, along with the "on error nothing happens"-bugs. The product should've been shipped last week, but thanks to mandatory bugfixes the release was postponed to next week. Then the next project starts...
Please give me some tips to keep up code quality over time, i cant take this once more.
I'm also aware that i could've done more, talking A and C about code style, prettifying the code, etc. Etc. But i was busy putting out my out fires, i couldn't kill much of the other fires which in the end became a burning building (a perfect metaphor for this software)4 -
teamLeader: We can't release because your change doesn't work, it breaks on the machine ABC123
iHateForALiving: I diagnosed the issue and I still don't know what's related to. BUT I'm 100% sure it's not related to my change, or anything that has changed in the last 24 months. Anyway we can take a look at this, just give me admin credentials for this machine.
teamLeader: no we can't.
iHateForALiving: ... Wait what? How am I supposed to reproduce the issue? Why can't I access the machine?
teamLeader: It's in use by the testers.
iHateForALiving: What for?
teamLeader: ... Educational purposes!
They report some issue on some particular machine, then refuse to give us access to said machine to reproduce the issue because they have "educational purposes", me and God know fuck kind of education I have in mind for this circus but as soon as I get my hands on them they'll get a hint.1 -
Continuation of the events ranted here: https://devrant.com/rants/9895220/...
In a turn of events and very emotional moments of human admissions, it turned out that the team leader in question is in fact suffering a lot on a personal level. Not to detail here but suffice to say that, if his story is true, is enough to make everyone have a very short fuse.
He - eventually - admitted his wrongdoings, asked/begged me to stay, promised on his life and soul to never communicate unprofessionally ever again, to take a long vacation to mourn and reflect and will consider relinquishing the position of team leader for my team and just focus on the other one he manages.
I considered this a win. I stood my ground, made very clear the terms on how I continue working in the organization, the project, and with him, and kept my client and money rolling.
That being said if it ever happens once more. I immediately resign and he will be left without any chance of recovery. -
BACKLOG REFINEMENT
TeamLeader2: why did you rate this task so high? It should be easy enough
TeamLeader1: you guys have never worked with Angular. We have just started using it seriously and it's really complicated, I know it looks easy from the outside but trust me this whole framework requires a lot of work even for trivial tasks
What's that I hear in the distance? A phone ringing? Someone better pick that up, because I FUCKING CALLED IT
https://devrant.com/rants/9108342/...3 -
My Teamleader is such a dick, he has mental and isn't able to act as a normal human being. The year started with his disappointment that we didn't worked for the company during the holidays! Sorry, but my family has higher priority than the company, especially during the jolly days, you lonely nerd without any interest beside sitting in front of your computer all day long.
He managed to get me thinking about moving to another company. I need the harmony in the team and won't fight every single fucking day. I noticed that I get very nervous when he enters the room. Everyone in the team is hating to discuss things with him because he knows it better.
The problem is that we're a small team with big responsibilities for each developer. Loosing one team member is quite hard to compensate.
Should I still try move? I guess the harmony with all your teammates is evenly important as it's in a good relationship, right?4 -
TeamLeader : "Come two seconds"
TL : "I'd like you to check that out when you do that"
Me: "But it's your job to do this"
TL: "Yeah, but I'd like you to just check in case I forgot"
THEN DO YOUR FKING TASK PROPERLY WHATS THE POINT IF YOU FORGOT AND I DO IT
Edit my english sucks1 -
A year since the Group Manager stepped into the position, 4 team leads have moved to other companies.
He is known to be politician/manipulative..
Guess what, Now there's a new Team Lead position and I was offered it.
It will be a step up for me, from senior engineer, and in other circumstances I would take the job in a heartbeat.
I guess it is not the time to step into leadership role.
What would you do?4 -
My teamleader blabbering about how I shouldn't listen to late shows with my earbuds while I work is rubbing me the wrong way.
"How can you focus while listening to them hurr durr", as if we didn't all do 20 tasks at once on a daily basis anyway.6 -
TL;DR: idiot 'team leader' does mindless merge to master. Precious time wasted in a high pressure deadline environment.
So, i work currently at one of Belgiums largest consulting company's at brussels airport, we are moving their analytics platform to the cloud.
We use puppet to manage the systems.
When i started i noticed immediately that their 'development workflow' is hardly to be named as such, because they simply change stuff directly on server , manual 'temporary' fixes everywhere, hardcoded stuff, non validated code... Basically the way one would develop in their garage, not in a consulting company as this one. But that is just the beginning.
A month ago i did a major effort to equalize all the discrepancies between the codebase and the server. Ensured entire codebase to be validated, syntax checked, parsed, tested... It works. A 'great codebase overhaul' commit was PR'ed to master and got merged.
Yesterday the team lead, i'll call him 'B-tard' from here on, has also 'equalized the discrepancies between codebase, server and the restnof the stale branches on the repo' . i was doing my other work on my branch so no fucks given. This is where i should have given some fucks.
Anyways, today. The day starts every day with merging the master branch into your working branh because you need the latest working codebase, right?
Wrong!
This fucking dipshit smug b-tard has done a mindless merge of the entire codebase, effectively removing ALL validated working code for provisioning servers. Control blocks, lookup functions, lambda's... Basically everything he did not understand.
At the same time the project is already way beyond the allotted budget in pkney and time, so there is a huge pressure to have a working 'production' environment TODAY!
THIS MOTHERFUCKING B-TARD JUST MADE THAT IMPOSSIBLE.
i'm loving this assignment, i'm loving the PM, the collegues, the environment, the location... everything. All but this fuckibg b-tard that somehow got his position by sucking dick or licking ass or both...
I wanna get out asap.
Oh... While typing this and arriving at the room of the office... It is locked, i have no key.
Fucking asshole!1 -
This is more of an advice seeking rant. I've recently been promoted to Team Leader of my team but mostly because of circumstances. The previous team leader left for a start-up and I've been somehow the acting Scrum Master of the team for the past months (although our company sucks at Scrum generally speaking) and also having the most time in the company. However I'm still the youngest I'm my team so managing the actual team feels a bit weird and also I do not consider myself experienced enough to be a Technical lead but we don't have a different position for that.
Below actions happen in the course of 2-3 months.
With all the things above considered I find myself in a dire situation, a couple of months ago there were several Blocker bugs opened from the Clients side / production env related to one feature, however after spending about a month or so on trying to investigate the issues we've come to the conclusion that it needs to be refactorised as it's way too bad and it can't be solved (as a side note this issue has also been raised by a former dev who left the company). Although it was not part of the initial upcoming version release it was "forcefully" introduced in the plan and we took out of the scope other things but was still flagged as a potential risk. But wait..there's more, this feature was part of a Java microservice (the whole microservice basically) and our team is mostly made of JS, just one guy who actually works as a Java dev (I've only done one Java course during uni but never felt attracted to it). I've not been involved in the initial planning of this EPIC, my former TL was an the Java guy. Now during this the company decides that me and my TL were needed for a side project, so both of us got "pulled out" of the team and move there but we've also had to "manage" the team at the same time. In the end it's decided that since my TL will leave and I will take leadership of the team, I get "released" from the side project to manage the team. I'm left with about 3 weeks to slam dunk the feature.. but, I'm not a great leader for my team nor do I have the knowledge to help me teammate into fixing this Java MS, I do go about the normal schedule about asking him in the daily what is he working on and if he needs any help, but I don't really get into much details as I'm neither too much in sync with the feature nor with the technical part of Java. And here we are now in the last week, I've had several calls with PSO from the clients trying to push me into giving them a deadline on when will it be fixed that it's very important for the client to get this working in the next release and so on, however I do not hold an answer to that. I've been trying to explain to them that this was flagged as a risk and I can't guarantee them anything but that didn't seem to make them any happier. On the other side I feel like this team member has been slacking it a lot, his work this week would barely sum up a couple of hours from my point of view as I've asked him to push the branch he's been working on and checked his code changes. I'm a bit anxious to confront him however as I feel I haven't been on top of his situation either, not saying I was uninvolved but I definetly could have been a better manager for him and go into more details about his daily work and so on.
All in all there has been mistakes on all levels(maybe not on PSO as they can't really be held accountable for R&D inability to deliver stuff, but they should be a little more understandable at the very least) and it got us into a shitty situation which stresses me out and makes me feel like I've started my new position with a wrong step.
I'm just wondering if anyone has been in similar situations and has any tips or words of wisdom to share. Or how do you guys feel about the whole situation, am I just over stressing it? Did I get a good analysis, was there anything I could have done better? I'm open for any kind of feedback.2 -
Context:
I recently joined a team and we are working on a fairly large mobile app using RN, they started a month ago. And I noticed, they don't have any fucking tests and static typings like Typescript.
I have this pretentious team leader that acts like he's the BeSt dEveLopEr in ThE woRld, and act like he always know what he's doing. But in reality, he code like crap, the formatting is shit because the ESLint config is not working, he's not even aware of it until I've fixed it. He's using every BAD Practice available, unused variables and imports are scattered everywhere, etc. And the directory structure is crap and no consistency.
How can I convince this ignorant mofo to use tests and typescript? He believes that adding those will take us longer and cost more money to the client, based on my experience, this is not the case, it's only slow on the first 2 weeks and it is worth it in the long run.13 -
Me in outsourcing sending questions to teamleader to confirm some details in task.
Respond: can we call via skype
Well ok. So we connected and started talking.
TL - "So rest of task connected to the database will provide my co-worker"
Soo the business analityc sold me the view of what user have to see. We disconected and then it hit me.
He tricked me. He was so good with his sell skills that he covinced me to understand when I actually knew less than before call
My lang skill still are so bad but "learning in progress" -
Teamleader : just add TypeScript.
Me: Uhm okay?, someone has expirience with that?
Teamleader: No, just do it .
After 15h of trying adding TypeScript to the React / Redux App I ve to tell him that i couldnt do it.
So now I think that i am stupido as fucko..4 -
Me start reporting at Standup about my recent work. My Teamleader start talking the same time, saying he has seen the commits and I don't have to go into details anymore.
Thank you asshole for disrespecting me and my work.3