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 - "team of one"
-
The moment an other team couldn't deliver for a deadline. CEO came to me, gave me 50 bucks told me to get a pizza and some hash and just work the night and deliver the damn app. So I did. Got a week holiday for free in return. One of the best guys I worked for.42
-
My classmate is a real SAVAGE!!
He (team leader) and his team participated in hackathons several times and kept losing.
He noticed something common about winning team, majority of those team members were women, even if they were non technical and their project was pure bs, they were winning in the name of women empowerment.
This time he came out with a plan, he fired his boys and invited women into his team, and even made one girl the team leader.
Result? HE WON!!!
NOT ONE BUT THREE HACKATHONS BACK TO BACK
AND
His so called women team was invited by Google to pitch their startup idea.
Now, if they gets funding, he's gonna kick out these women and bring back his teammates32 -
Just left a job where I felt like one of the best devs on the team. At my new job I feel I have so much to learn from the devs I work with. I'm so happy. :)9
-
From the time i became manager, productivity of the team has increased, one of the reasons is : after a 3 or 4 hour of working, we play online video game for about half an hour, then we continue. This way really had an impact on our productivity.10
-
This is why I love working where I work. I worked extra hours until 9pm to get an ITest environment ready for one of my customer teams. I came in this morning to a little prezzie and a thank you card signed by the entire customer team. This is what awesome culture looks like.10
-
We hired a new team lead. On his first day he wore green leather elf shoes. Yeah, the pointy kind.
He also ended up being one of my favorite people ever, but also one of the weirdest.3 -
A fresh graduate software engineer applied to the company and passed the coding exam.
Manager: Wow you got a very high score. Good job.
Applicant: Thank you sir. So am I hired?
Manager: Yes of course. You will be the team lead for one of the project.
Applicant: Wait wut????8 -
Latest from my team,
One of the Dev copied code from a stackoverflow question.
Got same exception as highlighted in the question and started complaining that his code does not work.3 -
when your boss tells you they hired you just to save money, and the job should actually be done by a team of intermediate/senior devs, but they thought one junior dev could do it in the same time span4
-
I was once at a hackathon and got into a team with some people out of the same company. They brought all of their fancy tools with them, which no one understood except for them.
They ended up doing all of the back-end and I designed a f***** logo, some slides and bored myself to death for the remaining 18 hours or so.3 -
fellow from the team was asked to do the estimate by manager - he said 2 weeks
then manager asked what if we add one more developer - he said, again 2 weeks and maybe add day or two
I was asked same question without knowing that they already asked fellow from the team same question - I said around two weeks, maybe day or two more! XD
as manager was confused and not satisfied with the estimates, goes to our team leader with the same questions - team leader said - 2 and half weeks and if you add one more dev to it, 3 weeks minimum
we didn't know that all of us were asked as manager did that behind our backs, in the end manager learned lesson in greed as we got to stick to team leaders estimate!
also that was very rude of underestimating someone's ability, same manager did had personal bias and frequently mocked us, for example when we said that that we will implement ML for cropping images at the right place (ie. crop part of the image where the face is) on the backend. Response was something like: 'You guys will do the ML? Are you shitting me? You're not /insert FANG company/!'
best team win ever!
second best team win ever is when whole team left the company in matter of weeks -
Since I started reading devRant the productivity of our team dropped a 20%(we are 3 people). Yesterday one of my teammates asked me what was going on and I showed him devRant.
I don’t think we will survive next split.1 -
Was asked to check the sales team server as it was running slow.
Apart from redundant processes and users with too much permissions I found a "Cobol" folder under one of the sales team member's home folder.
If it weren't the sales people I would immediately disregard this as trolling but with them it's quite possible that this is a real attempt to learn programming...
...most likely from the facebook ads with the hooded guys that offer to teach you to code in 10 days for $800.5 -
One of my previous managers would constantly make promises our team couldn't keep. "You want it in a week? Sure, we can finish it in a week! You want it tomorrow? Sure, we can do that!"
It got so bad that our team basically had to stage an intervention. At one of our standups, we flat-out told him that even if the entire team dropped all of our other tasks to focus on the one big project, we still would not be able to meet the deadline he'd promised the client.
And that fucker actually said, "Well, if you want to come in on the weekend to work some overtime, I don't mind." as if he was offering to do us a favor by "allowing" us to work more.
No overtime pay because we had salaries.
So glad I don't work for him any more. Of course, my next manager wasn't great either, it just took longer for us to figure it out because she wasn't nearly as blatant about it.7 -
I had an intern in for VBA programming on day one they realized that they were in need of an android dev, so the boss came to me and asked if I had any experience with android. I replied with yes a little, I had begun multiple projects but never finished only one of them. After 4 weeks of developing I presented my progress a pretty ugly but working app, after the meeting the boss told me that a other team of devs were building the same app but didn't made any progress in 1.5 years.
Ps: sry 4 my English.4 -
Being part of the team who did the initial investigation and analysis on the wannacry ransomware which took down our hospital. 100 hours in one week getting everything back online. Was intense but amazing!8
-
Casually Client Team Asked A Developer Team,
What is your favorite game?
**Blame Game**, One of the junior developer murmured. -
We had a manager that blind-sided the entire Team. During annual reviews, he gave everyone on the Team an unsatisfactory/not meeting expectations. Why? Because rather than rating us on the work we were being assigned, he rated us against what our job descriptions said, but you can't do work you don't have. Not once, during any of our monthly one on one reviews did he tell any of us that we weren't meeting standards. No one on the Team got a pay raise that year. But, karma. Several month later, the company decided to do a 360, which is where we get to rate our manager anonymously. We're still here; he's gone.4
-
Having to argue with team members inside my head.
I have a one-man startup, so I have all these imaginary team members who specialise in different things so that I can concentrate on whatever I am doing for that day.
But it seems my developer side of me hates the manager and UX designer these days for making changes half way through the project.
Oh yeah, and my accountant side thinks I'm spending too much. Fuck you, I needed that money.4 -
I didn't know any one of them, we just meet at the TADHack last week end. Because my team members apologies at the last moment, I joined one of them who forgot his laptop. The third came after five minutes asking "can I join"?
We established a team from three different backgrounds, and started the work. Each one built what he know, and we integrated all of it together.
Luckily, we won.... I enjoyed these weekend...5 -
You know how some people put those little badges in their readme files in GitHub?
Well, one of my team members didn't know how to make those work correctly, so they just plastered images of them to make our repo look good. In actuality we have no coverage, no testing, no nothing...6 -
When you group asks you to write some code to kick two people out of the team randomly.... and you are one of them :(5
-
Ugh, fxk. I got a promotion, I'm now a team lead for 4 developers, and I fxking hate it.
They never asked me if I wanted the position, they just threw me into it this week. They ripped me away from the team I had great chemistry with and put me on this other team with people I have no connection with.
To make matters worse, I'm also responsible for production servers of the clients of this team, one has malware even.
On top of all of this, they made me move desks for a new developer to fill my spot.
How do you demote yourself? Why would a company want someone to perform poorly (on purpose, I don't care) than to just keep their employee happy?
/end rant14 -
When I joined my team in august as a junior/trainee, we were 6 developers.
Now we are 4 left in the team.
By the end of june, we are 1.. I mean its me, myself and I.
Wtf did I do!? My code isnt that spaghetti. I think...
But its np, just me with a 20 years old database, 7 legacy systems and a new one planned.
Atleast my boss believes in me keeping this shit floating.11 -
One of the new guys on another team calls the Internet the Innernet because he doesn't hear the T. He both days and writes it as Innernet.
He told me today he wants to switch to our network team.9 -
At a former job, the company decided to replatform to Salesforce. The entire dev team was laid off. But it would take an outside agency a year to build the Salesforce site. The company wanted the devs to stay for an additional year.
The only severance was something they called a stay bonus. It was 30% of our gross income but it was still contingent on performance. And if they decide to let you go earlier, it gets prorated if you still qualify for the bonus. Not a good deal.
Each month a dev left. By the time I secured a new job and left, all that remained of the dev team was a junior frontend dev and two team leads (one FE and one BE) with no team to lead. Well, there were contractors, but they were only brought on after the Salesforce replatform announcement. I’m pretty sure the company had to hire even more contractors. No idea how much that cost them.
For me, I think it was serendipitous that I gave notice during their busiest time of year. They actually tried asking me to extend my notice. Karma was coming back to bite them. Not just for the Salesforce thing. But also for their lack of support when I was blindly accused of being both insubordinate and incompetent.4 -
At 4pm, after 6 hours of work of migrating from mysql to mongodb...
I am drinking coffee with my team.
Boss, comes from somewhere and asks...
what do you all want? (What he meant was, go back to work you all)
One of my team member- (angry and agitated) says-- a comfortable sofa.
Holy fuck, i laughed my ass out.
Guess what happend next...22 -
Our team changed to Linux about 3 years ago already and I can see some of them struggling to insert some commands when I'm talking to them.
How the fuck do you struggle to `cd` into a fucking directory?
Ok,ok... I've linuxing full time for 8 years already, I understand I've been through this... But come on! If some one said to me on day ONE "dude, you can cd /full/path/of/fucking/whatever" or " ~/ means home" I would be doing it from day one.
Probably I'm overreacting but wtf dudes? 3 years... Step up your game.18 -
This one guy on my team had like 10 commits to a single file over a day with all kinds of wild changes.
Build is broken most of the day (not mine but whatever).
Finally, at end of day he says it is fixed.
I diff the first and last changes.
Copyright changed...wtf2 -
I put a sticker under the optical mouse on one of my team mates then he started to rage when his mouse is not working. Then he started calling technical support and they, too, didnt know what cause the mouse to not working. I wanted to laugh so hard, but I must resist. Ahaaha xD2
-
1. Scripting out a team. I've built a collection of bash scripts to do what one of our teams does. Except the script does it in 30min and always does it well where that team used to take 4 to 10 hours and almost always missed something in the way.
2. Automate 70-80% of our BAU tasks with a single >4k loc bash script. Integrations with servicenow, lots of internal portals, predefined huge sets of commands to run on separate servers or lists of servers, do all sorts of diagnostics, schedule hw maintenance for DC folks, chase for approvals, track CHNG/CTSK tickets in a graphical chart so we would not miss any of them and lots lots more.
Finally we were able to afford time to make some coffee/tea.
These are the bau optimizations I'm proud of the most. And they have made significant impact on how our teams operate.
Whoever recognizes both company values in the tags and know what is that company - are they still using ´S´ in unix team? :)1 -
5 years ago i was working on a 2D game using C and we needed to use the sleep function (I forgot why ) .but however one of my team member did something new , for each second he did an empty for loop from 0 to 1000000 .You never know maybe that's how it's implemented (sarcasm)1
-
I’d heard rumblings from my friends in other parts of the organization that there were going to be layoffs coming, so I’d warned my little engineering team. One of my team was vacationing abroad.
When he came back, one of my teammates told him it was all over and we were going to get fired.
He told me that he’d been told that and I said that it probably wouldn’t affect us and that I wouldn’t worry about it (I was under the impression that the layoffs would only really hit customer-facing roles).
The member of my team who just got back from vacation, the one who I reassured, was the only member of my team who was part of the group laid off.
Goddamn it. -
Currently in the middle of quarterly planning (its been fun so far). Needs to be signed off by business today.
- My team has ~25 man weeks available in terms of capacity.
- Looking at only priority 0 tasks, last night we calculated the ask from product stands at 64.
- Including P1's, P2's etc. its well over 100 man weeks.
- Email was sent around from business with a list of tasks, asking which can be dropped, de-scoped etc.
Product (non technical) response this morning:
- This one can't take 2 weeks, its not that complicated.
- This one needs to stay, It was originally a Q1 task.
- Can we make this one smaller? (currently only a 3 week task)
- 14 comments on other teams items.
<extreme-sarcasm>
... ah perfect, that cut down the items by less than half. We are now ready for the deadline in 4 hours to have all this signed off on. Great job everyone. Thanks for all the insightful discussions. Go team!
</extreme-sarcasm>6 -
My instincts are telling me that i should resign from this company asap.
My team lead knows a to z of the project and he is the all rounder guy here. If my team lead leaves, I could be the one replacing him. But i don't want to accept this kind of responsibility.
My life goal is to not get sucked into the 9 to 5 life or work in this kind of environment.
The only pro i find is that i now have few more cool friends.
But I'd rather be be my own boss and work 24/7.
I now feel like living a lie going to work everyday..8 -
I just got four CSV reports sent to me by our audit team, one of them zipped because it was too large to attach to email.
I open the three smaller ones and it turns out they copied all the (comma separated) data into the first column of an Excel document.
It gets better.
I unzip the "big" one. It's just a shortcut to the report, on a network share I don't have access to.
They zipped a shortcut.
Sigh. This'll be a fun exchange.3 -
Today I got lectured by one of our Seniors that my automated test isn't useful because it always fails. Reminded him that it only fails because of a bug that's assigned to his team for four months now. He answered that I should remove the test case. Sometimes I honestly question why they even have a QA if they ignore at least 80% of reported bugs...3
-
This next one is dedicated to a couple of special people at my workplace:
- The person who uploaded internal-use-only code to a personal repository on GitHub
- The network team that has blocked any and all access to GitHub
- The obscured mass of management bureaucracy that makes it pretty much impossible for anyone at my level to make any sort of appeal
This one's for you:
*ahem*
WHY?!3 -
## 4 years ago:
- Principal Architect: We are using IO1 storage type. What if we used GP2?
- Perf team: IDK, let's test it!
*we run tests*
- Perf team: results are OK, but we're exhausting Burst IO capacity, effectively hard-limiting number of tests we can run per day
- PArch: ahhh, I see. Then Gp2 is a no-go.
## 3 years ago
*PArch quits. New one is hired*
- PArch2: We are using IO1 storage type. What if we used GP2?
- Perf team: We've already tested that a while ago, results were THIS and THAT
- PArch2: I see. Let's test it again anyway
- Perf team: *wtf???*
*we run the same tests, we get the same results*
- PArch2: I see, so GP2 is a no-go.
- Perf team: *you think....? How did that thought never cross our minds, we wonder...*
## 2 years ago
*new DBA is hired*
- DBA2: We are using IO1 storage type. What if we used GP2?
- Perf team: We've already tested that a while ago, results were THIS and THAT
- PArch2: We've already tested that a while ago, results were THIS and THAT
- DBA2: I see. Let's test it anyways. I've read somewhere that GP2 might be a better bet
- PArch2: you might be right, let's do that
- Perf team: *wtf???*
*we run the same tests, we get the same results*
- DBA2: I see, so GP2 is a no-go.
- Perf team: *you think....? How did that thought never cross our minds, we wonder...*
## 1 year ago
*DBA manager left; new one was hired*
- MGMT_dba2: We are using IO1 storage type. What if we used GP2?
- ........
Should we even bother bringing up the history.....?11 -
Are you a mango in Siberia?
Mangos seeds don't grow in Siberia. But if they are moved to a warmer climate they grow to be the King of fruits.
Do not beat yourself up if you are not doing good at one organization in one role. Analyze what is the problem and if it requires a change of team/organization, roles..just do it!8 -
Received devRant stickers today. First international package. :D.
One of this stickers is going on my bike or bike helmet. For others, waiting for new laptop. Thanks David, Tim and team devRant from Mumbai, India.13 -
When you're newly assigned to one of the most FUCKED UP team in the department and your manager said that ALL LEAVE REQUESTS from your team are AUTOMATIC DISAPPROVED for March until i see significant progress, hayyyy...poker face. I really don't know what to feel right know.7
-
Managers: Fullstackclown!!!! When are those features we poorly designed and spec'd going to be released to production!?!?!??!!
Juniors: WE SO DUMB DUMB REEEEEEEEEE HELP FULLSTACKCLOWN!!!!! WE PRODUCE GARBAGE CODE THAT TAKES MORE OF YOUR TIME!!!!!!!!
Designers: Hur dur, how can I export this stuff to png, help us, Fullstackclown!!!
Fullstackclown: * inhales sharply * AAAAAAAAAAAAAAAAAAAAAAAAA7 -
Not really a recruiter but at interview at one place I was given a printed code example and told that there was 8 bugs and that I shield treat it like a code review.
I found 16 bugs and 4 bad practices and explained them all to the director of software engineering and team lead (that set the test), they agree that I was correct; the director turned to the team lead and said ... Are you are your a senior
I tried not to laugh lol1 -
Best co-worker? One of my team who was cut from the same cloth. I could ask him to do anything without giving a how-to. I could then carry on with my work knowing he would deliver on time and at least as good as I would have done. We've been mates ever since.1
-
Product team having a proof of concept demo with client:
Sales to client: "Just for the record, we are not selling this to a rival company. Because we really want this technology exclusive to you"
Me (thinking to myself): "Oh really? We just had a demo with them last 2 weeks"
One of the core values of our company is Integrity, and I am not just seeing it. -
So my company finally decided to make the shift from using irc for internal chats to Slack.
After a month of patiently waiting for my team to make the shift, I went ahead asked one of my (young) fellow teammate why he hasn't shifted to Slack yet. His reply:
"What's Slack?"8 -
Boss: do you remember the other team? we need to fix one of their bugs
Me: amm, okey np
Boss: do it when you have time, but don’t forget to finish your things first.. and we need that fix by the end of the day.
Me: //what a beautiful monday <3 -
I have NEVER had a trust issues with a hard-working developer. It is always good to have someone you know would move heaven and earth to solve a problem, if demanded. It was a privilege to have worked with a handful of them.
PS: If your team doesn't have one such, either be one or change the team/company!5 -
Every year my team have an award ceremony for stupid things we do throughout the year. There is only really one worth highlighting this year
Alzheimer’s award- given to one of our DBAs for this svn commit message: “updated the comment block but forgot to make the code change”2 -
One of our team members would write his name in a comment before and after every line of code he writes!
Like we got version control we can see the changes that have been made and by whom there is no need for this narcissistic behavior.10 -
When you're the most "junior" person on the team and you're the one pushing for Git. How we've managed to come this far without any version control is beyond me. Especially with the fact that we've had to work alongside a 3rd party who handles a lot of the site dev...there have been a lot of "stepping on toes" over the years and no one ever thought "there has to be another way."
🙄5 -
Brought in a meeting a really good idea. One guy out of 9 sayd, that it's stupid and we could not use it.
1 week later the same guy proposes the same idea to the boss and team. Took all the merit and when I confronted him, he denied, that it was first my idea.
Fuck my life...2 -
Google cripples ad and tracking blockers: In January, Chromium will switch to Manifest V3 which removes an essential API in favour of an inferior one. As usually, Google is being deceitful and touts security concerns as pretext.
That hits all Chromium based browser, such as my beloved Vivaldi. The team argues with their own browser internal blocker, but that's far worse than uBlock Origin. One of Vivaldi's core promises was privacy, and that will go out of the window. The team simply doesn't react to people pointing that out. They're fucked, and they know it.
So what now? Well, going back to Firefox because that will include the crippled new API for extension compatibility, but also keep the powerful old one specifically so that ad and tracking blockers will keep working. Google has just handed Mozilla a major unique selling point, and miraculously, Mozilla didn't fuck it up.26 -
During QA for a huge project when our dev team was confident of the stability of the project, We started introducing small bugs, QA team use to raise bugs in Jira, we marked them as not reproducible.
Frustrated QA started coming to our cubes - at this point dev team worked in a perfect coordination like a man to man marking in hockey. While one dev asked QA guy to reproduce the bug in front of him while the other dev has already fixed it.
Continued for a couple of days till our team lead was satisfied with the revenge. -
Today a new person joined the team.
Started bitching about the entire team for not having documentation for our already written code and software.
Asks the manager for a new task that he can take up so that he can write documentation for all our already coded works.
Manager says Go On.
Troubles me with 400 questions every 3 minutes in the name of Knowledge Transfer for writing his documentation.
Sends a proud mail to the team for writing this new documentation that no one else had time to do.
He is a newbie and had no other task to do anyway.
I seriously don't know if I should feel proud of him, for writing new documentation,
Or if he's doing this to defame me.
The team is filled with snakes.15 -
I worked for months staying up till 3am almost every night in order to collaborate with a team on another time zone. No one ever praised me or thanked me or gave me a pat.
Yesterday two members of that team stayed up till 2am once for the first time in their lives to make a release. They got immediately labelled as the most dedicated employees.
Okay, sounds fair.7 -
The worst kind of team member is the one that won’t follow and can’t lead. So obviously can’t lead 🙄!
-
This is a somewhat old story. I joined a project in making a 2.5d platformer in Unity. A couple months in, the project manager had decided that this game would have two sequels, an MMORPG, a live-action movie and a web series. He informed the whole team of this decision. One week later, every member of the dev team had left. This scope crept forth from the depths of hell and ruined a simple project. Lesson learned: Keep the scope small and don't bite over more than you can chew.
Edit: I know that you should dream big, but don't make 4 games, a web series and a movie simultaneously.3 -
the dev team freaked our boss out by being overly nice and polite to him for a whole day .
Normally we're pretty laid back and tease one another, so he was pretty worried.
You know you have an awesome and tight-knit team when your boss threatens to fire all of you for being too nice and you can laugh about it.
#AwesomeBoss1 -
I am part of a team running a rather big Discord bot. One day last year late in October some dude tried to tell us that he and his "team" had breached our infrastructure. I noticed he was full of shit and started trolling him back, and actually putting him under pressure to develop a solution for us, pretending to want to pay them for it. At the end, our bold hero ended up "losing their job" AND "their house burning down" to get out of it again, lol wat.
The whole resulting conversation is available as a set of screenshots: https://imgur.com/a/vczyX
Enjoy!4 -
Getting tired of certain co-workers under-delivering. They commit an entire release to one feature and my team plans our release expecting we'll be able to use his changes by the end and then on the last day of development he decides more testing is needed and it won't be finished until next release. Come on, man!
-
[ ] be humble, but not unconfident.
[ ] Step out of your comfort zone. Don't apply to a job that is exactly like your last one.
[ ] A good team is the most important thing for a developer. Intelligent, and nice people to work with and to learn from is more important than the salary difference between jobs.
Try to 'feel' for a good team. Ask to be introduced or to look around when you finish the interview.2 -
the team gave access to the database to another team, and one of their guys did a delete cascade by mistake thinking it was theirs... everyone was scrambling for days trying to get a backup, thankfully there was one3
-
I'm soooo glad that the Google Drive team isn't one of those that always puts "But fixes and performance improvements." 😒4
-
Those weeks when you get calls from recruiters offering you up to four times your current salary.
I enjoy my job, love the atmosphere, team spirit, freedom (although sometimes there's a bit too much of this!), but I have a family and am saving to extend our house.
I don't want to let my team down, I'm the only programmer dev in a team of 3 (others do front end web design but not much JS), but sometimes I wonder if I should pursue one of these better offers...5 -
Looking at one particular job ad
“Experience with agile”
“Excellent knowledge of agile frameworks”
“Work with agile software development team”
Basically in the first few paragraphs it mentions agile about 10 times.
Then the first bullet point in the essential column
“Must have experience working to tight deadlines”
D’oh3 -
Soft rant...
So I'm working at the company for 8 months now. Best 8 months in my career, great team mates, great work, the best - a team leader who is one of the best developers I've ever worked with, but more importantly he is a good friend, brother like. We had great time, from the interview we understood there is a bro-mance there.
So why am I ranting? He got promoted and became a group leader, not even of my group. Now we don't have a TL and we're afraid they won't be able to get a swell guy like our exTL2 -
First Hackathon ends today. Long story short: I was the only programmer of the team, we only had 2 days to develop it (of which we spent the first day doing research, so 1 day of coding), so guess what it's shit.
I basically took a bootstrap theme, hardcoded some data. Put some js on top for interactions and a node js backend, to interface some APIs. Just by looking at the code you'll get cancer, but the others of the team where impressed, how good it looked an worked...
Let's hope the judges aren't familliar with coding as well (our challenge got two judges whereof one works at a bank as some guy whearing a suite and sponsoring stuff... Ao chances should be ok)
Honestly fuck this. Not one team (afaik) has pfoduced anything close to being finished...10 -
So how do you deal with the "brilliant jerk" who is the CEO's golden chlid?
Seriously - this is one of the biggest challenges of my professional career. I have team members that have begged to not be on projects with him and others that have threatened to quit if he ever moves into a leadership role.
Has anyone dealt with this?5 -
When you +1 one of your colleagues rants on devRant and realise the whole senior Dev team is on here. Hmmmm.3
-
Something that really irritates me is when someone requests a read receipt for an email. My team of 4 including my team leader has several apps that we own with several different product owners. Sometimes one of the product owners or someone who works for them sends an email and requests a read receipt. I feel like that is very cocky, like they are trying to exert control over me or something deeper. Maybe it's just me.5
-
After looking at @linuxxx and @AlexDeLarge 's rants with the face reveal, maybe we ought to do one of the team behind the masterpiece, @trogus and @dfox face reveal.
IF they are comfortable with it.
Or maybe do it on a special occasion. Like an anniversary or something?14 -
Why do people fucking do this? You're working in a team, ffs. Even if right now you're the only one working on that branch or whatever, that doesn't make it okay to have the most useless commit messages of all time.11
-
* KISS (keep it super simple)
* don’t try solve a problem you don’t already have
* admit if you messed up. We can solve a problem early and minimise the damage. People should never be scared to admit when they mess up. No one is perfect.
* voice your opinion. You’d be surprised how helpful this can be to your team, as we need to look at things from all angles.
* help your team. If you see something wrong, make the team aware of it.
* ask if unsure, don’t assume8 -
5 of us working for a larger team were tasked with doing some R&D, we blew everyone away and were given funding to start a new team and hire people to make the project come to life.
One of the high level sales / product managers we were reporting to, secretly had another team work on a similar idea because he needed it quicker (i.e. no time for research, just build it).
After forming new team, we were asked to work on his project instead because it was further along. 4 months later, big knob comes to a meeting and basically says "You know what, this doesn't look like we have enough features, we need more, but I don't know what".
Project blew up 2 months later, head of the unit kicked up a shit storm saying how badly everything was planned and canned everything. Now one of our clients is building nearly the same thing we were originally working on, the team no longer exists and i'm back on the R&D team.
Don't get me wrong, I LOVE the R&D team, actually didn't want to leave in the first place but was told I had to. But the sheer anger and frustration to see that walking cluster fuck strutting around like his shit doesn't stink, derailing entire teams, meanwhile we can't hire new staff due to lack of funding.
Heres an idea, fire the fucktards bleeding us dry ... then we'll have lots of funding. -
The University Professors are full of shitt !!!!!
Just ended up scoring less than my team-mates in 3 projects when I was the one who did the complete work !!!
Even I was the one who presented the projects. Soo tired of this randomly marking thing !! :/4 -
In order to reduce support costs, manager instructed his team to remove all logging/reporting of errors in the company’s CRM application.
Team’s support tickets went down 80%, manager received an award for his efforts, but mysteriously, DBA/support workload increased, bad/missing data,
increased support tickets in other areas of the business (shipping, etc. that relied on correct data from the CRM) and other side-affectual behavior.
Even after pointing this out this correlation, showing before/after code, no one believed the two were related and I was accused of not being a ‘team player’.
“You and the other teams need to learn from his example!”. As ‘punishment’ was I was moved to the team managing the CRM application.1 -
Team of developers suggest one of our legacy services is a nightmare to maintain, terrible to develop on top of and is fundamentally wrong in terms of data and application structure.
They are 100% correct and I fully endorse their request to redevelop it.
I'm less enthusiastic that their new version is much worse than the original...1 -
I wish I can fucking clone myself.
We have been providing digital marketing services for like 5 years without having a proper QA team. Well because we cannot afford to hire one. Technically I am supposed to check and control the quality of our operation team. But I have been juggling so many balls and couldn't do that properly.
So this year we decided that we have to seriously take care of that. But we are providing all kinds of services and creating a QA team for all those services is gonna be costly. We wanna solve it, but also doesn't wanna hang ourselves with another rope. So we have decided to just found a QA team with leaders from various departments mainly Sales and Customer Services. They are the ones who have talked with clients. So they should be able to judge the quality of the services our operation made.
It is a fucking nightmare. It is like we have doubled the amount of clients. And that extra half of those newly popped up clients are sitting in our office. -
A coworker asked me for help so they could finish their task on time. That meant that I had to be a bit late for one of mine. They blamed me for delaying the whole team because I didn't finish mine on time. 😕11
-
As a software house, we have many teams on different projects. One project was due to a Thursday, and the PM asked the team 1 week before if they could work over the weekend since there's a lot of things to do.
On the Friday before, one of the devs showed up a bit later than usual (around 10am), but ok...
After lunch he asked to talk to HR and also the boss. They talked for around 2h, then he started to say "goodbye and good luck" for everyone.
The project was on fire and he just... leave.
On the next 2 months another 4 people leave the company. All from the same team/project (but not with a big surprise like him).
Apparently, the team was constantly complaining to PM and boss about unrealistic deadlines and constant requirements changes, but they didn't did anything about it. Just when more than half this team had left the company they started to rethink this actions to this project and the others on the company.2 -
I wish the Congress would run all legislation by a team of programmers. Regardless of political leanings one thing is indisputable: We are very keen when it comes to finding bugs in a piece of code -- especially if we didn't write said code!
After all: What is the law if not code for people instead of processors?5 -
One day I will renovate our summer place, bring a top team of developers, spend the summer close to nature at a beautiful place where silence fucking exists and create something awesome.2
-
So I am assigned to a new team to take over the leading position because the guy who did it up till now quit. And there is this guy who today seriously shared his screen with my boss and the rest of the team to point out that I formatted something wrong...
Realy it was something like
super.doFunctionA().thenFunctionB() instead of putting it like
super
.functionA()
.functionB()
He said he wanted to call me out early to avoid spreading of this "wrong formatting"
He wants to start a war? This fuckhead can have it!
Soon I will be the one who writes his tasks... hf8 -
One of my clients got hacked.
FML. It was fucking bad passwords by a team member.
Google has now blacklisted the domain.
Removed the shady code, requested for review. Hope it recovers soon.
Any idea how long it takes for Google to remove the red warning page before you even enter the page ?2 -
God, don't you love it when your team COMPLETELY IGNORES all the work you do, dismisses it outright, and then acts rude to you? And then when they do take one of your suggestions, they say 'wow you ACTUALLY contributed' as if you haven't been trying to contribute the whole time only to get ignored?!9
-
Passionate programmer attends one of the toughest interviews ever and solves lot of algorithmic problems coding in different programming languages. Impresses the interview panel providing solutions with as much as efficiency as possible. Gets selected, completes induction and gets a nice Dev machine allocated.
Manager walks in and says we got to work with the production support team on fixing a UI bug.2 -
We are a web developer team of 4 people. The system we manage is huge because it's a huge organization.
We use php.
Requirements grow rapidly and debugging became a nightmare. So we decided to move from procedural to OOP to ease it a bit.
And we have this one guy in our team (joined recently) who doesn't understand the benefits of following OOP. He is the one who manages most side projects among us too.
We have tried hard to convince him and now we have almost given up.
So I am asking you guys, please give me some ideas of how we could convince him to learn and follow OOP.7 -
*in Sprint planning listening to my PM creating tasks*
PM (to Team): So this will be an MVP we can expand on in the future. Do let me know upfront if any tasks should not be in the Sprint.
Team Manager (to PM): Let's see... Yeah I think you've nailed it... Good.
Developer (to Team): Guys, I see the task for the frontend team to integrate machine learning doesn't have any details.
PM (to Developer): Ooh machine learning! Good catch!
PM (to Team Manager): This was one of the tasks we really needed this quarter, will we still be on track?
Team Manager (to PM): Yeah no worries we'll add it as part of the MVP design in Confluence.
PM: Okay assigning the task now. *Assigns to Developer*
*Team Manager goes on 1 month vacation*
Me (thinking to myself): Wtf3 -
I'm a junior dev in a scrum team with two senior devs: one actual senior and one average dev that's just been around for a long time. At stand up meeting, that average senior lists helping me as one of his task Every Single Day. 9 out of 10 times when I ask him a question we end up asking the senior senior together.2
-
I feel like resigning from a company that i joined 3 weeks back.
I don't like to code in PHP and the manager wants to stick on to that , no new developers joining the company and php is one of the reason. The code is a mess. Every now and then some other team come running for a change like one button to do some shit and then for a fix after 15mins of release.
So many database operations are happening manually. No innovation in the team. Developers are very boring , women being senior developers and team leads brings stability but there is no innovation , excitement or any enthusiasm. All my team members are very happy doing mediocre shit. Manager talks about agile development and they are following that at a level where every half a day some requirement changes.
I m tired of being a developer that fixes the same mediocre shit.
Its too boring.6 -
ComputerToucher: *opens Jira ticket* Dev team needs tokens for the APM for a new app with multiple tenants. Ezpz. Hey, developer. Do you want one golden token for all of your app tenants or would you like us to generate one token for each?
Developer: Let’s have a meeting to discuss it.
CT: It’s…an exceedingly simple question. One token or 4? Which does your app support?
Dev: Yeah I think we should discuss with this with the platform team, can you set up the call?
CT: (Internally) I am the platform team? Do you not know how your applica-never mind I’ll just ask the PM directly.
CT (in chat): I’ll ask PM to schedule the call.
*Goes back to Jira ticket, changes priority to 4, removes ticket from sprint entirely, picks something else to work on*6 -
The most recent that comes to my mind is from one of my previous projects. Our team is already overloaded and frustrated working for this garbage client. One fine day, out of the blue, the client once again revises the list of go-live critical development objects.
Our project manager takes this issue up with the client, and then with our management when the client does not listen.
The response he gets from our management is along the lines of, "But it's just forty development objects. Why are you complaining? Just get it done."
Needless to say, the motivation levels of the entire team went on a downward spiral soon after.1 -
Abuse "new" google meet background feature level : 999
- while in meeting take screenshot of one of my team mates
- mirror the screenshot and put is a background
- now pretending that I'm at their place
after half an year of lockdown... It was fun1 -
One time in college we had an android project for one of our courses. Then this one member of my team didn't want to install Android studio because he didn't want to install any unnecessary software and libraries to his machine. We wanted to do his part editing directly in github.5
-
I got recognized!
I'm new here and was mostly learning, but my team pushed through some bad issues and I got recognized as well. Even for helping whatever little I could.
For all the rants of bad bosses and clients and work. Here's a happy one. :)
I'm in good company in this company. -
>be me, working at IBM as CC operator
>onboarding freeze, people leaving team, not enough operators
>take extra workload to sustain monitoring
>no raise
>team gets merged with other CC team(different customers)
>take over of developing full workload automation project
>no raise
>sick coworker, have to take more extra workload to cover monitoring
>get tiny raise
>coworker gets the same raise for only one extra workload
>be expected to do both programming and monitoring for the little salary
>too autistic to quit
>too autistic to confront my mamager with this
What do, devRant?5 -
Today I told to my Project Manager that after one year of taking care ( explaining thousands of lines of codes) to an external team ( another company) to migrate our application from a monolith to microservices + react, that the React UI they build looks like shit.
He replied "at least it works".
Now I must find the courage to tell him that it doesn't work correctly because instead of a simple *migration* the external team rewrote some algorithms used in a bank application and now the data are wrong.
advices ?1 -
So do you have any co-workers or teammates who horde tasks and don't share knowledge? I hate those kind of people. Everytime I bring it in team's retrospective and that one asshole remains quite during the whole meeting, agrees to everything and continues to horde tasks again in the future. That affects the team performance and causes to form a single point of failure and recovery which is bad when working in a team. Share your experiences.10
-
Central team: No, your team must be doing something wrong. Our pipeline is super-configurable and works for any situation! You just have to read the docs!
Me: Where are the docs?
Central team: Uhh, well, umm... we'll hook you up with a CI/CD coach!
Me: Okay, cool. In the mean time, can you point me at the repo where all the base scripts are?
Central team: Sure, it's here.
Me, some weeks later: Yeah, uhh, the coach can't seem to figure out how to make our Prod deployment work either.
Central team: That's impossible! It's so easy and completely configurable!
Me: Well, okay... but, here's the thing: your pipeline IS pretty "configurable", in the sense that you look for A LOT of variables...
Central team: See! We told you!
Me: ...none of which are actually documented, so they're just about useless to me...
Central team: But, but the coach...
Me: ...couldn't make heads or taisl of it either despite him literally being ON YOUR TEAM...
Central team: Then your project must just be architected wrong!
Me: Well, we're not perfect, so could be...
Central team: Right!
Me: ...but I think it's far more likely that the scripts... you know, the ACTUAL Python scripts the pipeline executes... while it took me DAYS to get through all your levels of abstraction and indirection and, well, BULLSHIT... it turns out they are incredibly NOT flexible. They do one thing, all the time, basically disregarding any flexibility in the pipeline. So, yeah, I'm thinking this is probably one of this "it's you, not me" deals.
Central team: Waaaaahhhhhhhh!!!!!!2 -
Yup, sure our team of three devs will build you a fully functioning e-commerce site from scratch that grabs data from several APIs and uploads it to several more.
You need it in two weeks? No problem.
Me: Wait...what the...?!
One week in and I only have access to test one of the four necessary APIs as the client hasn't signed the necessary paperwork with other providers.7 -
3 time sheets: One for the company I work for, one for the parent company staffing us to clients, one for the client.
All three have to be handed in at different times, have different rules, are on different systems and have to fit hourwise.
A waste of hours per week.
And add an offshore team that checks all 3 to this.
Also once in a while they complain about something in it. (Audits, reviews,etc.) Forward to boss, he has to argue with them.
Waste of so much time.3 -
Leading a team of 10 people, 5 environments (3 non prod 2 prod) to support, 25 formal deployments per week, and all I have is one fucking repository in fucking svn.
-
Company's HR team has launched a eco drive. As part of the initiative they're asking everyone to use only one tissue paper (among other things) to save trees.
.
.
So they've printed that message on thick glossy papers and pasted them, at least four per washroom among other places.
Okay, I guess.8 -
I work in a very diverse team. I'm a white male, from the US and I have someone from Russia, one from China, and 2 from India. The best thing so far was a team building exercise, where we went to a AAA baseball game, and I got asked all kinds of questions, that of course seem strange to me.
How many pitches can the pitcher throw?
What happens if they hit it past the lines on the left and right?
Can they hit again if they strike out?4 -
Currently literally sitting in a meeting about meetings. Like for real, the topic the last 15 minutes has been what the difference between 3 of the daily team meetings is.
Then the dumbass who booked this for two hours says about one of the others "an hour is long"4 -
Real story :
There's this one colleague, who was a very good friend of mine. Always helped me in everything. That one friend in the team, who shares a lot of stuff with you.
And she suddenly, turns offensive when it comes to professional things and mainly competitive stuff in the team.
She becomes a completely different person when I get recognition for something in the team or when I become popular in the team.
She has that feeling that she should always stay in the lime light.
When I steal the show by doing something good, she starts to show faces.
Decided that it is a unhealthy friendship, as the friend i knew is no longer a friend when it comes into professional behavior at work,
And it started reflecting a lot in our personal friendship, outside work too.
Decided to cut the friendship and only be colleagues.
Did the same happen to someone else? Did you lose a friend because of things like this?4 -
I HAVE BEEN CALLED TO 3 OF THE FINEST HACKATHONS IN MY COUNTRY RN, 2 BEING ORGANISED BY HUGE COMPANIES AND ONE BY A COOL COLLEGE. I CAN'T GO BECAUSE FUCKING INFOSYS IS COMING TO MY COLLEGE FOR PLACEMENTS AND MY TEAM MEMBERS ARE NOW BACKING OFF. WTF.6
-
I am feeling little fucked up.
I talked to one of the female employees from my new company, I'll be joining next month.
She asked manager to hire a girl in the team, I know she casually asked but after knowing this, I know my interviews were surprisingly easy, I mean I know already that no one asked me to optimize anything... did the fucking hired me for diversity, pay is good, people are good, work is good but seriously if I'm getting hired for the fucking diversity my manager is going to have a good speech from me and I'll move from his team for sure.18 -
Manager asked suggestions to make any changes to work culture, because of the overall productivity issue of the team. The culture was so much toxic that no one was ready to speak.2
-
In my friend's company they score theirs team mates, but the form can be only submitted once and cannot be edited!
One of team members send it with the note "effectively analyze code" but it was truncated to "effectively anal..." -
A group of ten top software engineers is sent to a class for aspiring managers.
The teacher walks in and asks this question:"You work for a software company which develops avionics (software that controls the instruments of an airplane).
One day you are taking a business trip. As you get on the plane you see a plaque that says this plane is using a beta of the software your team developed. Who would get off?"Nine developers raised their hands.
The teacher looked at the tenth and asked, "Why would you stay on?
"The tenth said, "if my team wrote the software, the plane would not get off the ground2 -
This one is for @Fast-Nop
Both a rant and a joke/meme.
Its also funny because its true. Couple of teams (team responsible for orders and team responsible for accounting) are in seclusion in a meeting room right now cleaning up the web team's screw up.5 -
TL;DR The prodigal son returns.
A long time ago my partner in crime left the company. So I was a "one man army", until management gave me 2 newbies to train. We'll call them X and Y.
X was new to the company, while Y was moved from a different area. During the time I was training them I realized which of the two had potential, or at least was paying attention.
Some more time passed and X was showing signs of being a good candidate to join the team. Y, on the other hand, well there were stories from his previous team. Not good.
Guess who was added to my team. It wouldn't be a rant if it was the capable one. Y was added to my team, while X was sent to a completely different area.
Time passed and I suffered many misfortunes. But this week, I saw him sitting next to my desk, X is back. I'll probably have to get him up to speed, but my little prodigy is back! -
So I handed in my official resignation last week as I will be changing to a new job next month. So one of the last big things that I have been working on is a Jenkins server for the rest of the team to use and currently writing up the documentation for it.
However I haven't been told who I will be handing over my work to, but the bigger thing I feel is that even if I write all the documentation, no one will actually read it. Reason I think this is because I doubt anyone else in the team will even use the Jenkins server. The major issues are that no one writes unit tests and don't even understand what CI is!
So right now it feels like my final month of work will all be for nothing and makes me wonder if I should even bother writing documentation, especially if it isn't going to be handed over to anyone.5 -
Our QA team love writing really awkward bug tickets
No reproductions steps
and every time i see one appear all i can think of is this1 -
This is not a direct advice but something I noticed sometime ago.
In a company I worked at, one of the more senior guys was working on task and stopped to ask the rest of the team about something related to that task. One junior guy offered to help and started explaining and I saw the senior guy listening carefully giving him his full attention.
The thing I took out of this is to listen to those around us even if they seem to have less experience. You surely will learn something. -
One of our most essential functions was giving a weird warning: C4706. Turns out that one of our team member wrote if(count =! 0)... Yes, he's new here
-
I started my actual gig as CTO of construction group (Innovation Hub) a year ago. And it was a hell of a ride, implementing kind of a scrum-ban for project management, XP, peer-reviews, a git-flow, git commit message formats, linters, unit testing, integration tests, etc...
And it's the fun part because with the CIO we had to drive the board to do A LOT of changes in their IT/Innovation drive.
But in one year there is a lot of KPI that went up :
* Deployment: When I arrived it took three stressful days to deploy a new version of one application, once a month. Today we do it every week, and it takes three annoying hours.
* We had no test. NOTHING! Today we have 85% code coverage for the unit test, and automatic integration tests run by our CI server every day.
* We had almost no documentation. Today our code is our documentation (it automatically extracted and versioned).
* We had 0 add value in the use of git. With commit messages as "dev", "asked task", inside jokes and a lot of "fix" and "changes". Today we have a useful git, and we even use it to create our deploy changelogs (and it's only mildly annoying!).
* More important, the team is happy! They get their purpose, see betterment in their tech mastery. They started doing conception, applicative architecture, presentations, having fun.
There is still a LOT of bad things we are still working on, and trying to solve (support workflow and betterment). But seeing what they already did, I'm so proud of my TEAM! I'm a fucking asshole, workaholic, "just do it" kind of guy. But they managed to achieve so much. Fucking PROUD!! -
So I've been working as an operator in IBM for a year now. Two months after my onboard our team got an onboarding freeze. Since then more than a half of the team left and more are supposed to go, soo there is a problem covering all the workload. I volunteered to take 4th customers workload (out of 4 customers our team supports) because I already knew most of the work that is done there.
At a one-to-one meeting with my manager I asked for a little raise, because I have the 4th customer, I take other peoples shift anytime they need to take a free day, I update the documentation regularly, I write scripts for coworkers for installing software/automating what can be automated (and I'm the youngest here...) bla bla, telling him that I think I do a lot for the team and I deserve it. He told me that he would rather take away one of the customers workload. I rolled my eyes and went with it.
Two days later this asshole gave a raise to a guy, who was onboarding with me, because he wanted to motivate him. That very same day he told us that it seems like two customers are going to merge into one workload.
I'm so pissed because of this. I do my best all the time so I can get promoted to 2nd level linux team (I'm kinda one foot there) but the freeze is still preventing me to go. I'm already so tired of dealing with the bullshit of customer not knowing their own infrastructure, shitstorms of tickets during changes after level 2 didn't set maintenance mode again, repairing coworkers linux boxes because they don't know better and I'm so pissed at this un-initiative dickhead of a manager that gives a raise to lazy people. -
Someone asked "What's a sad reality for devs?"
Let me add one to that cuz I'm too lazy to find the actual thread.
A sad reality of devs is to be dependent on the management's mercy for them to be in the team/company. Your years of work can be thrown out the window just like that when management feels like it and there is almost nothing devs can do about it.
This sprung to mind cuz I experienced that today. My client cut my dev team in half to "make up for the recent losses the company faced". Obviously my team wasn't responsible for it.
This shit sucks man.1 -
This is how Scrum works:
Three coworkers are in a Scrum Team. One of them is also the Product Owner and the Scrum Master... The PO decided this Monday that they need to add a new feature for the Tuesday night release, which is estimated at 80 hours. I told the other two in front of a manager that this is not scrum. Nobody gives a shit.2 -
When you get into good company but end up in bad team. Worst thing to happen. I want to quit. But as of now I don't have any option.
I am way too triggered. Any one tries messing with me anymore at work, I won't be able to stop myself. I am gonna shout....take out all my anger. To hell with you assholez! I don't care if you get me kicked out of team or job! I can't take it anymore. FUCKING IDIOTS!!!!!!7 -
As a team lead, what would you do if one of your direct reports sent obscenely bad code for review? Like absolutely nonsensical, non-working, touching wrong parts of the project, doing wrong things… Terrible even by your company's standards.
Would you consider it an instance of stupidity? Tiredness? A resignation letter? An insult? A cry for help? A combination of those things?10 -
Sweet talker but Incompetent colleague/team lead has given estimate of 350 story points (1point =1day) i.e more than an year and half, for one module to refactor. Worthless manager seriously considered to proceed with these estimates and ready to accept proposal.
When presented these numbers/estimates with wider audience, one senior engineer reminded everyone that module was developed few years back, in <2 months by 3 engineers.
Shame shame!12 -
How many of you wear shades at work?
I started doing it after I faced some problems due to the extremely bright lights. It's such a complicated problem that no one in the management or admin team can do anything about it. 🙄12 -
That feeling when you're the only one of your team sitting at your desk and you cannot shake of that nagging doubt:
Did I miss a meeting?1 -
I've never had a bad interview but one turned mildly awkward when I found out that the whole Dev team had watched a video of me from when I was in a band. We used to just make random videos to keep fans coming back to our site. https://youtu.be/V5zQjjCu_V01
-
We had only one product UX designer in our team.
She quit and I habe accelerated my job hunt.
And when I quit too, the tech team will collapse with both of us gone.
Because then there will be no product manager and no designer, only tech who is arrogant and cocky to even built a simple button to refresh the fucking page.
God bless with this fucking tech team. The Tech Senior leadership is shit. They deserve it, but for now, it's us who are facing challanges.2 -
One of the colleagues I am close with is changing teams. They will still be around the company, in fact the office of the team they are going to is right by mine. It just sucks to lose a good developer and friend from the team.
-
Well, the project I've been working on is now being terminated.
As the lead dev, I found out by one of the managers sending a public message to the staffing team in one of the channels unrelated to development, which I don't normally check.
Apparently at no point in their "very long discussion" did they think they should let me know of this decision.
Tbh I'm not even suprised, I was barely ever told anything. The others aren't either.2 -
I got two, both my internships sucked.
First one, I got hired for a C++ job, did JS for most of it. Half the team quit while I was there lol. I was in charge of the whole frontend when I left.
Second one, again half the team quit while I was there, leaving me with only ppl in Europe to talk to lmao.1 -
I was hired to a working team that is full of experienced people who know how to code but half the team is awfull at solving problems, and all they do is blame each other... why cant they understand we are one team and rather work on solution for 30 minutes they spent deciding who fucked up...2
-
tl;dr; A co-worker and I had an disagreement on our package structure. They went straight to our team lead instead of trying to solve this in our team and by that letting me do my job.
Do I overreact by assuming that this was malicious?
A co-worker asked me to do their code review today. There was nothing really wrong there, mainly something a bad generator created.
However at one point we had a disagreement about the naming structure of the packages. We both agreed to disagree, so I thought we could bring that up in the next daily, as it's something the team should agree on.
Shortly after that, they told me on Slack, that they relayed the matter to our team lead to get their opinion. Wtf.
My role in the team is that of a technical lead. Even though I like to discuss such topics in the team and not straight up dictate decisions.
By going directly to our team leader, they basically circumvented the whole team. This really rubs me wrong the way.
Maybe I'm just overreacting?5 -
Oh my effing goodness...just went through the repo of an app we're working on and this new dev in our team saved his commits with, "ok", "done", "fixed", "another one", "arrggghhh!", "wow!"..."not complete"...for fucks sakes...DUDE!1
-
Can the devRant team move '++' and '--' to the right side of the post? I'm feeling it really hard to upvote the post while using my 20:9 aspect ratio phone in one hand.
- sincerely a first world user problem13 -
when you confirm with a friend that 2 different members of their team who left didn't contribute shit (one of which got into a meeting with management with them telling them to work) , but they also made more money than both of you and are now making more money in more successful companies in more senior roles
is it possible to learn this power /palpatine2 -
Last year in my job, I was temporarily assigned to another team to help out in their project as they were short-staffed. It was a massive project and of course there was a lot of code review to be done. But since I was only temporarily assigned, I still have to do code reviews for my base team, this other team I was assigned to, and for some reason, code review for another team that I barely know what their project is about.
There were times where all I was doing was code reviews that took anywhere between a few minutes to upto 3 days. The amount of mistakes and bugs I kept finding was phenomenal. But I think the one thing that got to me was finding the same bugs/mistakes that I kept pointing out to people to stop doing or to fix e.g DB queries inside a loop just to retrieve data.
To this end I still have to deal with the same issue, but thankfully now it's only to one team.1 -
i am at the point of deep depression again as a CS student. a few weeks back and forward is a busy weeks with a lot of team projects/research. as always, team project never be as smooth as i expect, I always who be the one who work in the project with the rest of the team and they doesn't even care what the project does.
also a few week forward there will be a Leadership Training, and i just quit from it, why ? because i need sleep. why again ? BECAUSE I AM THE *ONLY* ONE WHO WORK ON THE PROJECT YOU FUCKING DIPSHIT, i am the one who can't sleep everyday working on the project scraping the deadline and class hour.
why i drop important thing (Leadership Training) just to keep me from depriving my sleep and to keep the project up while the team disregard me? am i being too humble yet i just rant about "don't be too humble".
..i...i just... I just can't take it anymore. :( god help me15 -
I'm the youngest person on my team, and I mean significantly younger, most of my teammates have kids older then I am. So should I be bothered when one of them calls me "kiddo"?9
-
team lead/senior telling you that you're probably going to break prod and have to patch it for the next couple of weeks when working on one of the first migration epics on legacy monolith, but we'll get good data from it doesn't make it any less terrifying5
-
I'm doomed.
My first production worker script is making multiple active attribute of a user. My script should be able to deactive the old attributes if there is new one.
Months ago, this issue occured. My teammate from team A take over the script to investigate since I am busy working with team B.
Yesterday, I found out that I, myself, overwrite the fix my teammate made for that because of a new feature.
I have to clean up the affected records on production on Monday..and i have to explain to my manager. T.T
LPT: ALWAYS PULL REPO before developing new feature... -
I work in a big corporate world where I felt really out of place at first. I didn’t enjoy working there, I could not understand why people would work so hard to keep all the systems happy. No one thanked them, no one gave the smart people maintaining the important systems any credits. I did not understand. Why did they care so much for these systems?
My team split. We were too many with too many systems to care for. After this my team was a lot smaller and therefore I ended up in a more important role. I was forced to do these tasks the more senior engineers had done before me, in the previous team. This was the greatest thing that could happen to me, and I started to like coming into work. Now our team is big again but I’m one of the senior people in it. Not senior as in years active in the industry but senior as in knows the most about our systems and our work environment. I work hard to constantly share my knowledge and try to put the newer members in situations where they also have to take responsibility.
Don’t be afraid to put important tasks on junior or new people. They might fuck up but they will learn, as will you. Don’t hog your knowledge and your team will thank you.1 -
TL;DR: A new "process" for collaboration between teams was created in order to stonewall requests from my team.
A couple months ago, we created a new Dev team that specializes in writing internal tools. This team was staffed with internal developers, and got a separate manager. The whole point of this team was to collaborate with my dev team so we can both help each other develop tools that the company needs.
One of the developers that was on my team went over to this team while he and I were still working on a big application. For a few weeks, he still worked on this application as he normally would, and we'd sit with each other and work through features together whenever we needed a fresh set of eyes.
Well, eventually his new team got protective of him and created a new "process" for our teams to request assistance from one another. So now instead of just popping over to someone's desk to ask a quick question, you have to send an email to the team and request that you can borrow that particular developer for a question, and then the entire team sits down and discusses whether or not they're going to allow that person to answer your question. Then after a week of discussion, if they decide to allow it, they schedule a meeting for a week later, in which you will get the question answered.
So instead of just spending 2 minutes to ask and answer the question, you have to spend weeks in order to request assistance, and then schedule a meeting.
It's ridiculous, and it's all because his team got protective that he was working with another Dev team. Dev teams collaborate all the time, and work together. My team is constantly helping other teams, and we don't have this ridiculous process. We get asked a question, and we answer it. Simple as that.
Last week, I sent an email for assistance in completing a feature, and didn't hear back. I talked to the Product Owner for the team, and he said "Just send an email," to which I responded that I did and hadn't got a response. He said "Oh....." I then told my boss that this is an enormous bottleneck, and he seemed surprised hearing that this is a bottleneck.
A week passed and today I still hadn't got a response, so my boss reached out to the Product Owner to push him. Finally, I got a response and they scheduled a meeting to answer my question 3 days down the road. So it's going on 2 weeks to get this simple question answered.
Normally I'd just have the other developer come over and help, but apparently they yelled at him the last time he did that.
The issue is that the process was created with the assistance of our "senior" developers, who never work with this other team in this capacity, so they just nodded and smiled and let them put this ridiculous process in place.
Like, get off your high horses. You don't "own" him, he's allowed to collaborate with other teams. This question would've taken literally 10 minutes, but because of your new "process" you've turned it into a 2 week debacle and you've effectively delayed the app launch with your pettiness.
They say that this process isn't intended to prevent us from getting assistance, and that might not have been the original intention of the Product Owner/manager, but it's very clear that the developers on the other team are taking advantage of it and using it as a big stonewall so they can beat around the bush and avoid providing assistance when it's needed.
If this becomes a trend, I'm going to schedule a meeting (which apparently they love to do,) and we're going re-work this entire process, because it's extremely counterproductive and seems to only exist in order to create red tape.3 -
When I was in University, there's a group project on web development. We decided to make a simple game.
Out of 5 students (including me), one was missing for the entire semester.
Another one don't know anything about any kind of programming. We asked him to write us a json file of characters' attributes. Taught him how and gave examples. Turns out that most data is missing.
Luckily the other two was great. Altogether, we covered frontend, backend and design. Finally we got the highest mark :P
Best (and worst) team ever5 -
The company I work for now has so much tech debt. When I find an issue, I can’t necessarily fix it right away because I have other priorities. If something isn’t a site-breaking issue, then I only fix it when a user or staff member reports it.
The website is a mess because it was built and maintained by an outside dev agency. It was so expensive to outsource that my employer decided to bring development in-house.
That’s where I came in. I found so many issues. Tech debt. UX weirdness. Newish features that no one seemed to use. It goes on.
So I’m balancing new feature development, fixing bugs, and trying to lessen our tech debt. I’m a team of one.1 -
Got transferred on to a new team. The team I was on previously was successful, had great processes, and very smart people. New team was floundering, very late, no processes, and crotchety. Did my best with the (lack of) expectations and information given to me. No one gave me any feedback. Get called into a meeting to discuss my lack of performance and failure to meet goals. If I hadn't needed the money I would have walked out. Transferred teams a month later.
-
One stubborn (but not very good) dev working on one part of new project (Windows desktop application with C# underneath) decided he didn’t like the interfaces we were agreeing for the algorithmic code.
Instead of discussing with the team (we were still very much in design phase), he made his own interfaces with the same name but in a different namespace, and in his assembly rather than in the base library. He was senior to the rest of the dev team, so when we raised our concerns he pulled rank and just carried on.
I resigned not long after that. -
I work on many projects at work. There's divisions of teams and each team typically has one project. Each one of those projects have weekly Sprint meetings.
That's great! For the team. That means each team has one meeting a week so it's not too disruptive for those individuals.
Me on the other hand? I've got my hand in all the buckets. I'm on every team. I'm the only person on every team. This means I get to go to every meeting.
Let me rephrase that:
This means I -have- to go to every. Single. Meeting.
Which means I have a meeting every. Single. Day. Even if I didn't touch that project that week.
It is literally THE biggest waste of time. I sit there in a 1-2 hour long meeting saying absolutely nothing, not even being spoken to. I could be working on other projects.
And these meetings normally interrupt something I'm working on. Conveniently in the middle of me being in my zone. It makes me completely un-motivated to work for the hour before the meeting because why bother if I'm just going to get interrupted? And then it takes an hour to get back into everything after the meeting because everyone is fooling around or complaining about the meeting.
So that's three hours of my 8 hour work day completely wasted.3 -
Those days where you start to think of leaving a good job and a great team because of one insufferable cunt.1
-
The worst part of being a dev? Working in teams.
And I don't mean that in the "I'm the best ninja code wizard in the whole world and you're all holding me back" kinda way. I'm thinking more in the lines of someone who has to deal with that kind of attitude on a daily basis. As someone who recently was put in a leading position in a dev team, this is by far one of the worst experiences that came with it.
Some examples?
- One dev completely changed the naming scheme for variables in a class he worked on for one. single. bug fix. His reason? He just didn't like it!
- Another one noticed that data he was supplied with was not in the specified format. Instead of flagging this with the project leads, he just rewrote his parser to fit the data. A couple of weeks later the supplier noticed the error, fixed the format and suddenly everyone wondered why the software failed processing the data.
- Or that one senior dev, that just refuses to accept changes because "it was always done like this and it worked" No, it didn't. That's why it was changed!
Once a dev team reaches a certain size, people need to realize that stuff like coding rules and process guidelines are not there to annoy them but to help the whole team work as efficient as possible. I don't care how good a programmer you are, if you can't check your ego you don't belong in any kind of team-oriented development project! -
my first job is in a brand-new team, all team mate other than the manager are new grads from colleges. we r so engaged and dedicated our efforts to deliver something. and one day one of our team mate decided to resign due to family issues, we try our best throw him a farewell party, it is so emotional. now I have worked in a couple of teams, the spirit could not found after then.1
-
Hello, one of the other devs on my team insists that using:
<?=$myVar?>
In a template is super dangerous but:
<?php echo $myVar?>
Is safer.
Why? Is this valid in PHP 7.3?16 -
3 years ago,
Team of 3(team's first and last competition together). ICPC ACM Multiprovisional round.
1st question super simple. Teammate came up with the algo.
I was the one who wrote the code. Missed a brace after a 'if' statement.
Wasted 45 mins, debugging and coming up with new approaches. From a possible top 10 rank finish, we got 44th at the end of the competition.
If I wouldn't have done this silly mistake, our team wouldn't have failed. -
Rant
I was given a project to lead and develop with 2 other team members by the co-founder, I was told that I will need to deliver an initial demo within 30 days, 20 days in the project and I was told yesterday that they need a final release ready within the next 10 days !! Not just that but the co founder decided to assign one of my team members to another project!!!
I've worked today till 4am.
Guess who's working from home in the morning!6 -
New person joins client's team to handle one product on the website and asks me to restructure the whole site. Sorry, pal, but unless you have money to add to the project's already spoken-for pot of resources for features, you're gonna have to wait til next year.
-
Two years of my life I've kept in this project, sacrificed many weekends and peaceful thoughts ! worked my ass off to be an impact in the team and in delivering project...in spite of all that I still can't get ON SITE and all I get is some fucking bullshit appreciation from PM which he didn't even cared to tell one on one ...I hate my f**king life ! 😥😢2
-
Worst mistake I have made is accidentally wiping a database table by messing up a SQL script. This was caught after it had been deployed to around 30 customer sites, most of which had no technical staff on site, and we didn't have remote access to. I bought our support team cookies for fixing that one.1
-
Ooh what a nice feeling it is when you come back from a short vacation and everything is in the gutter... My team is divided into the two other teams... (I said divided but I ment everyone got assigned into team X... And I am the only one who was put into team Y)
Besides the whole team fiasco, I think my legacy project decided to role around in the garbage... Because I have no idea where all those bugs came from...
One positive thing is that I won't be working alone on that legacy project anymore, at the start of next week I get help from my new team... Now let's hope they don't suck!1 -
Killing people is bad. But, there should be a law to allow killing people who don't write proper unit tests for their code. And also those "team leaders" who approve and merge code without unit tests.
Little backstory. Starts with a question.
What is the most critical part of a quoting tool (tool for resellers to set discounts and margins and create quotations)? The calculations, right?
If one formula is incorrect in one use case, people lose real money. This is the component which the user should be able to trust 100%. Right?
Okay. So this team was supposed to create a calculation engine to support all these calculations. The development was done, and the system was given to the QA team. For the last two months, the QA team finds bugs and assigns those to the development team and the development team fix those and assigns it back to the QA team. But then the QA team realizes that something else has been broken, a different calculation.
Upon investigation, today, I found out that the developers did not write a single unit test for the entire engine. There are at least 2000 different test cases involving the formulas and the QA team was doing all of that manually.
Now, Our continuous integration tool mandates coverage of 75%. What the developer did was to write a dummy test case, so that the entire code was covered.
I really really really really really think that developers should write unit tests, and proper unit tests, for each of the code lines (or, “logical blocks of code”) they write.20 -
One of the devs on my team hates our PM. last week during standup while the pm was giving his update, he started clipping his nails and proceeded to do so until the guy finished. I almost died trying not to laugh. No one said anything.2
-
So someone from another team in the company asked on our public Slack channel if they can send a field they're sending for one client, for all clients, so they don't have to have a branch for that one client that sends it.
We're talking about a string of up to 20 chars, typically much less even connected to each record, of which we have let's say a million per month and each of those records has at least 30 columns, some of them being longer strings even.
A dev from my team responded that they shouldn't send it because, while no one uses it so it's not going to break anything, it will require extra storage.
This was not 20 years ago, this was today, in 2021.
I responded asking what storage does he foresee to be the problem, because I can't see where so I'd like to get more details.
Guess who got ripped to shreds because it's a bad thing to question members of the team in public....
This is just one in a long line of similar brainless idiocies I've had to deal with from this asshole.
And no, I'm not a junior dev or something, I'm transitioning out of the Principal Engineer role for that team (for this reason exactly, otherwise I'd stay as PE). And no, I'm not the transitioning the role to that asshole.
At least 3 people who have left the team because of this asshole.
Managers not helping either, responses like "Yeah, you're right, but you're reasonable, he isn't, so let's appease him until we can find a way to deal with him"...
I used to love being a developer, this asshole made me want to vomit at any mention of anything remotely dev related...
Hope y'all are reasonably happy with your jobs and, more importantly, don't have such an asshole around you! -
One hour before a deadline, one of my team members notified me he had completed his task and signed off. The only thing left to do for me was to merge our branches and submit the code for review. This was supposed go smooth with only a few changes made. But for some reason the build kept crashing and this ONE hour before the deadline and no way to reach my team member... This was a stressful situation to say the least.
And yes I am aware that you are not supposed to be merge branches one hour before deadlines. -
I have to finish team project within 13 weeks. Since most of my team mates are quite new to programming, I took first steps along with leader to make tasks as simple as possible for them. 2 weeks into the project and one of the members complains that she doesn't understand her task. So both me and leader tried to explain task to her. I guess we couldn't make it simpler. However she insisted that she will have to see our teacher. Ok, why not? So we are waiting for her magnificence to show so she can be officially dropped from the team and give her place to someone more competent.
WHY SHE EXPECT TO DO HER PART (OF LITERALLY CONSTRUCTING ONE FUCKING CLASS) FOR HER. AND SHE CALLS HERSELF A DEVELOPER!
Well, at least I did my part today to make a world better place :)
What about your experiences with working in teams? -
I don’t really have just one.
Ada Lovelace, she is the reason we have everything and she is the OG
Margaret Hamilton is badass and got Apolo 11 to the moon
Steve Wozniak, the real brains behind OG Apple. And his tech revolutionized computers. Plus have you ever just watched a video of him he’s so fucking pure and innocent. Like holy fuck he’s awesome and just hella intelligent.
John Romero + John Carmack. Two of the programmers on the original DOOM dev team. The team revolutionized the gaming industry and
Katie Bouman, just got added to the list for the black hole picture -
A tale of silos, pivots, and mismanagement.
Background: Our consultancy has been working with this client for over a year now. It started with some of our back-end devs working on the API.
We are in Canada. The client is located in the US. There are two other teams in Canada. The client has an overseas company contracted to do the front-end of the app. And at the time we started, there was a 'UX consultancy' also in the US.
I joined the project several months in to replace the then-defunct UX company. I was the only UX consultant on the project at that time. I was also to build out a functional front-end 'prototype' (Vue/Scss) ahead of the other teams so that we could begin tying the fractured arms of the product together.
At this point there was a partial spec for the back-end, a somewhat architected API, a loose idea of a basic front-end, and a smattering of ideas, concepts, sketches, and horrific wireframes scattered about various places online.
At this point we had:
One back-end
One front-end
One functional prototype
One back-end Jira board
One front-end Jira board
No task-management for UX
You might get where this is going...
None of the teams had shared meetings. None of the team leads spoke to each other. Each team had their own terms, their own trajectory, and their own goals.
Just as our team started pushing for more alignment, and we began having shared meetings, the client decided to pivot the product in another direction.
Now we had:
One back-end
One original front-end
One first-pivot front-end
Two functional prototypes
One front-end Jira board
One back-end Jira board
No worries. We're professionals. We do this all the time. We rolled with it and we shifted focus to a new direction, with the same goals in mind internally to keep things aligned and moving along.
Slowly, the client hired managers to start leading everything in the same direction. Things started to look up. The back-end team and the product and UX teams started aligning goals and working toward the same objectives.
Then the client shifted directions again. This time bigger. More 'verticals'. I was to leave the previous 'prototypes' behind, and feature-freeze them to work on the new direction.
One back-end
One conceptual 'new' back-end
One original front-end
One first-pivot front-end
One 'all verticals' front-end
One functional prototype
One back-end Jira board
One front-end Jira board
One product Jira board
One UX Jira board
Meanwhile, the back-end team, the front-end team overseas, all kept moving in the previously agreed-upon direction.
At this stage, probably 6 months in, the 'prototypes' were much less proper 'prototypes' but actually just full apps (with a stubbed back-end since I was never given permission or support to access the actual back-end).
The state of things today:
Back to one back-end
One original front-end
One first-pivot front-end
One 'all verticals' front-end
One 'working' front-end
One 'QA' front-end
One 'demo' front-end
One functional prototype
One back-end Jira board
Two front-end Jira boards
One current product Jira board
One future product Jira board
One current UX Jira board
One future UX Jira board
One QA Jira board
I report to approximately 4 people remotely (depending on the task or the week).
There are three representatives from 'product' who dictate features and priorities (they often do not align).
I still maintain the 'prototype' to this day. The front-end team does not have access to the code of this 'prototype' (the clients' request). The client's QA team does not test against the 'prototype'.
The demos of the front-end version of the product include peanut-gallery design-by-committee 'bug call-outs', feature requests, and scope creep by attendees in the dozens from all manner of teams and directors.4 -
That feeling when the team works so much overtime that one of your colleagues looses sight on an eye and starts wearing sports sun glasses when working to protect his one functioning eye :/3
-
!rant. Story from my college abt 6 months old.
We had to make projects for our course.
One team made a very nice project. One part of that was mobile no. verification using OTP.
And the student who was supposed to to that, did it by sending the required otp to the frontend page, and when user enters it, validate it using javascript.
The prof got mad about it and the rest of the class couldn't stop laughing.
Just remembered. Thought it would be worth sharing. -
In freelance world,
Some Computer Science degree holder (from client company) explain how good are they in Software development.
But when as soon as my team and I (after got criticized by this guy for the fact that my team and I don't have a degree in computer science) review their code, the code is a bunch of spaghetti! No proper Architecture, no documentation, and everything in one class?
Damn...4 -
Wowza..... Security certifications get expensive! Gonna have to spend half the week writing one hell of a business case for the certs my team needs!2
-
Attending in a local game jam with some friends.
One of the team members wrote the worst code I've ever seen. After him realizing that it's buggy as hell he left to sleep having me fixing his mess at 4 am to somehow get something done by the end of the event.
It resulted in me rewriting nearly everything he had done.
Guess which team didn't manage to have something playable in the end...1 -
So me and my team created an android application for "pet lost and found " . So one of my friend decided to troll us..
Bro you better don't do this is the production man... Hahahaha2 -
So I came from the Portal modding scene. And I know most other ones who did similar stuff.
Now there was a cool looking upcoming free mod and I somehow came in touch with the lead Dev. Now somehow I managed to get into the developer team and me and my girlfriend we're part of it. We got a level name and should start mapping it (TL;DR, we never finished one because we didn't know what to do).
I actually made a website for the mod. But sometime later we both left the team because the lead Dev (12 yo btw) was "hiring" (working for passion not money btw, that's fine in this case) everyone he got in touch with. They had no team structure just a huge list of people and a long story script. I'd guess the mod won't ever be done, although it has made it through steam greenlight (R.I.P greenlight). Just because they're not working on a team. -
I hate web development
I mean why it has to be everywhere and so important.
I joined college my friend calls 4 days before my quantum physics test. Asks if I wanted to do internship. My reply sure.
( Level of knowledge at that time no idea what API is, what react is but it's just making webpages ) made a nice homepage within 4 hours of YouTube 2 tutorials and 2 developing that. Friend appreciated his manager also liked.
But failed to deliver the complete e-commerce website's frontend.
Comes next, hackathon nothing related to Android specific( I like coding for Android) need webdev in one way or other. One senior asks if want to go together sees my GitHub and rejects politely by my skills ( I would have too).
Went on with my 2 more friends with thought of making an all Android app guys team, next week team breaks. I then got offer from a friend to join with them in web development I agreed now prepare for web development.
Team was rejected internal politics of organizers ( would take no all fresher's team).
Dropped learning webd.
Now started flutter and it feels good and comfortable but stability isn't permanent.
Now seeing GSoC
Sigh...Most requirements are for web , hacktober fest also had things related to web maybe I don't recall. Still thinking about it sigh...
Got selected for college app development team. The head had to be one with excellent webd skills.
Now college provides funding for projects and ideas, prototype requires making prototype. Most easiest thing to work on
.
.
.
.
.
web development.10 -
Had a university project with friends, got another guy (#1) in our team. Upon being asked if we would take yet another guy (#2), we were sceptical if he was a good developer... Turned out guy #2 is one of the best of us, guy #1 can't do shit.
-
I can't believe he chose the kid over me.
My boss decided he needs a new team leader, (he led it till now) at start he said none of the team members fit one guy is new, the other is young and this his it's first job after college.
After weeks dragging us, he chose the kid over me.
I am more experienced then him (10 years in the industry) and led the team most of the time.
As "consolation prize" he let me chose a professional course of my choice.
I am so disappointed from his choice and from myself, I just feel like drop it all off and go somewhere else.
I am 3 years there, and people are like "how can it be? You're one of the veterans in the company."
So embarrassing.
Should I stay or should I go
Thanks for reading this long rent.1 -
After an important meeting where you actually get to give feedback and share some of your ideas for new features or bug fixes, one of the managers sends a follow-up email to the team telling you to get features done, like they were his suggestions.
Manager “I'd like you to work on.... “
Me "Right, that's what I wanted to work on... "6 -
Working with one team takes the better part of a day...
try {
WorkWithUXTeam();
}
catch {
try {
WorkWithPlatformTeams();
}
catch {
try {
WorkWithArchitecture ();
}
catch {
Delay():
}
}
}
Man, that was annoying on a phone.3 -
Demo
Backend Team : No one want to listen to technical details. A short 2 min demo what we have done.
Shareholders : Have you done anything?
Frontend Team : half an hour demo of validators and fields that sum values from other fields
Shareholders: Wow that is awesome, great job, nice to see, great value, lot of progress.4 -
Once I went for this women-centric hackathon that had to have at least one female member in the team. On winning, one of the other winning (male) devs commented on how I was probably there just to complete the team even when I did most of the work.
Don't know if it's the fact that I have green hair or the fact that I'm a girl.2 -
When you have two managers and one of them is trying to screw you into a position on his team even though you have made it clear that you want nothing to do with that type of development.
I am looking for a new job now...3 -
Pro TIP :
If you have a lot of work and SOMEONE from your team is disturbing you every hour,
Move away (alone) to a meeting room, away from your stupid teammates for one day. For High productivity work.2 -
In a hackathon, my team decided to work on a Android app as a challenge to ourselves. It was our first Android app development and we were very excited at first. But after awhile, one of my teammate (the usual problematic one) gives up implementing the recyclerview after few hours of struggling, and decided to 'fk it' and watch YouTube linustech. As such, I have to takeover and implemented it within an hour by just googling and following some tutsplus tutorial. What do you do with this kind of teammate?1
-
Last year, 2nd year of Uni, we had to create an app that read from CSV file that contained info on the no of ppl in each class and things like grades and such and had to display graphs of all the info tht you could then export as a pdf.
This had to also be sone in a team. I, however, hate doing anything other than programming (no team leader, pm bullshit) so I tell them I want to be one of the programmers (basically split the roles, rather than each one doing a bit of everything like my professor wanted) and we did.
I program this bitch wverything works well, I am happy. Day of the presentation comes, one of the graphs is broken... FUCK. I then go past it and never discuss the error. We got a 70.
I swear to God it worked on my computer -.-
I also have to mention that our professor was the client and he had set an actual deadline until we can ask him questions. After the deadline I realized I didn't know what a variable in the csv file was for and when I went to ask him he said "You should've asked me this before. I can't tell you now". My team was not the only one that didn't know and he gave the exact answer to everybody else. Got the answer from another team. Turns out it was useless.
He was the worst client ever. Why tf would you put a deadline on when you can ask the client questions?! I should be able to fucking ask questions during production if you want the product as you want it >.<7 -
The fog of war over all that happened with my change of team is starting to dissipate.
3 people were involved and there were 4 different versions of the whole situtations, but from what I've been able to collect it looks like the company is expanding and one of the mail KPI for the current team leaders is how good they are at creating a NEW generation of team leaders, to take care of the new entries.
My previous team leader told me about all these new growth perspectives and the junior entries I could manage, knowing very well of the desire I have previously expressed of being a senior dev with my small group of juniors to teach.
I declined the offer, stating that this whole year has been exhausting. Every single time I've tried anything (using modules for new components on our old web client, tsdoc to document our types, suggesting technologies like ANYTHING BUT ANGULAR AND MONGO, telling how removing down migrations was a retarded move) my suggestions were either shrugged off or flat out refused. Let alone how every time I was proven right, except for angular but give it time and that will bite their tail as well.
Don't get me wrong: they are well withing their right when they take all those decisions, and more. But I DO NOT PLAN on selling a plethora of bad decisions to a new stack of devs as if they were the gold standard.
"I understand your reasons; you, as a company, need a well coordinated team all running towards a goal; loose cannons are harmful.
But now I need you to understand me: I do not agree with your technical direction. I never lied before and I will not start now. Promotions don't matter nearly as much as my integrity, and integrity in my world means speaking up about problems. Your position is perfectly valid, but mine is as well and they can't be reconciled. If I were you I'd make myself a favor and make sure IHateForALiving doesn't become a team leader; given your direction, I'm not the man you want right now".
As mentioned, one of the KPI for team leaders is how succesfull they are in finding new team leaders, and trying to turn me into one didn't end well; I love sharing knowledge, but being honest to myself is far more important to me. So this meant my previous team leader failed in a very big task, and thus was demoted? At the same time, I've been there for 2 years now so they're not really eager to replace me, but I'm under strict examination too as of now.5 -
I'm the one one in my team that uses git. In fact, they ask me to set a version control system to collaborate more efficiently... But then I'm the responsible to merge all the versions and spend a lot of time. It is burninge out...
-
one of my previous employers would just box up your stuff, if you were fired or transferred. Once, a teammate came back from lunch to find her stuff boxed up and thought she was fired, when she'd actually been promoted to another team for a job she'd applied to months before1
-
So, we're apparently going to build a sort of social media(with competitions) for our software engineering project. I thought of a productivity app that would follow the GTD methodology (with my own additions), but my team mates thought my idea wasn't big enough for a team of 10. One claimed that he would do it all by himself in a week/month(Don't know what he said). Oh, well. Anyways, I'm going to build that software as a side project with a friend or two. I hope that goes well..
PS. We need a team name. Any suggestions?
I thought of Team Sudo lol.. No one liked it..1 -
not exactly a hack but i started a prank war between us ( helpdesk team) and the pc team by pranking one of them with nirsoft and psexec.
at first he didnt really realize why his browser crashes and his cdrom opens and closes randomly. -
Developer in anger : I'm gonna leave this team and the manager/team will suffer for my loss and the project will fail.
In the meanwhile,
Manager to the senior manager : If one of the developers die or leaves the team, the project deadline extends by 1 month.
Senior manager : Great. -
1) What is the size of your team?
2) What is the size of your company?
3a) Do you have one on ones with your manager, tech lead and/or scrum master (insert whatever position you have one on ones with if you have them)
3b) How often do you meet?5 -
I use version control as a glorified backup. Only recently did we start branching at work.
This is why I need to be part of a proper team where I can learn instead of being a team of 2 juniors and no one else 😂 -
I just love it how team git & team TFS managed to migrate same fuckin project several times from one source control to the other and back.. and they all root for their source control as it's the bestest of them all.. yet when presented with specific conflict situation and asked how to most elegantly resolve it I get an 'ugh, I don't know, I've never worked with anyone else on a project let alone on intertwined parts so I never had to resolve conflicts.' -.- Dude, wtf?!2
-
I just realized that I may be hard to fire because I create a lot of apps. All other devs on my team work on the same big projects and maybe share code more.
But I tend to be the only dev for a lot of my work. In addition to building and deploying a few standalone projects.... That no one else has used. I write usage and design docs but nobody reads those.
And one application is very complex, has many parts. It even took me a while to pick it up at first and I've been the only dev on it for years... So built a lot of things on top.
Today I was actually talking to the business team that uses it and they were like when is feature A, B, C going to be done. And I finally said, has to be one at a time bc I'm the only dev...
Though last week I did ask for some help to look into one of them while I worked on another more complex one but I gotta train them. And well their part involves only a small part of the entire app. -
Leaving the company in 9 days (!!!)
Any suggestions for the last week?
Any ideas for a leaving session?
I updated the Wiki and documented everything.
I did the missions no one wants to do and a lot of dev tasks.
What else can I leave behind for the team?16 -
DEAR MOTHERFUCKING POSTMAN TEAM PLEASE JUST DIE.
I hope every single one of you die by swallowing Kevin Costners feces to dead in front of everyone you ever loved (except there is now one bc who would ever love bloody assholes like you).6 -
The conversations that come across my DevOps desk on a monthly basis.... These have come into my care via Slack, Email, Jira Tickets, PagerDuty alerts, text messages, GitHub PR Reviews, and phone calls. I spend most of my day just trying to log the work I'm being asked to do.
From Random People:
* Employee <A> and Contractor <B> are starting today. Please provision all 19 of their required accounts.
* Oh, they actually started yesterday, please hurry on this request.
From Engineers:
* The database is failing. Why?
* The read-only replica isn't accepting writes. Can you fix this?
* We have this new project we're starting and we need you to set up continuous integration, deployment, write our unit tests, define an integration test strategy, tell us how to mock every call to everything. We'll need several thousand dollars in AWS resources that we've barely defined. Can you define what AWS resources we need?
* We didn't like your definition of AWS resources, so we came up with our own. We're also going to need you to rearchitect the networking to support our single typescript API.
* The VPN is down and nobody can do any work because you locked us all out of connecting directly over SSH from home. Please unblock my home IP.
* Oh, looks like my VPN password expired. How do I reset my VPN password?
* My GitHub account doesn't have access to this repo. Please make my PR for me.
* Can you tell me how to run this app's test suite?
* CI system failed a build. Why?
* App doesn't send logs to the logging platform. Please tell me why.
* How do I add logging statements to my app?
* Why would I need a logging library, can't you just understand why my app doesn't need to waste my time with logs?
From Various 3rd party vendors:
* <X> application changed their license terms. How much do you really want to pay us now?
From Management:
* <X> left the company, and he was working on these tasks that seem closely related to your work. Here are the 3 GitHub Repos you now own.
* Why is our AWS bill so high? I need you to lower our bill by tomorrow. Preferably by 10k-20k monthly. Thanks.
* Please send this month's plan for DevOps work.
* Please don't do anything on your plan.
* Here's your actual new plan for the month.
* Please also do these 10 interruptions-which-became-epic-projects
From AWS:
* Dear AWS Admin, 17 instances need to be rebooted. Please do so by tomorrow.
* Dear AWS Admin, 3 user accounts saw suspicious activity. Please confirm these were actually you.
* Dear AWS Admin, you need to relaunch every one of your instances into a new VPC within the next year.
* Dear AWS Admin, Your app was suspiciously accessing XYZ, which is a violation of our terms of service. You have 24 hours to address this before we delete your AWS account.
Finally, From Management:
* Please provide management with updates, nobody knows what you do.
From me:
Please pay me more. Please give me a team to assist so I'm not a team of one. Also, my wife is asking me to look for a new job, and she's not wrong. Just saying.3 -
50% position (95 hours a month)
100% of my current compensation (~90k$)
In a company like the one I work in now: great team and great tech drive.
Rest of the time is for hobbies and family.2 -
The double-edged sword of teamwork. I'm an indie Game dev, so I have no choice but to work with others of completely different fields. I enjoy it and I get a lot of motivation seeing things done and learning many new disciplines, but team projects have so many downsides when you have to handle everything from programming to cinematography that someone else was meant to do.
My final team uni project I even had to do our music composing cause our sound effects guy did almost nothing in 6 months (he wrote 6 midi notes in 2 weeks at one point). -
Every one of our sprint "planning" meetings.
We would sit and be told to estimate a bunch of defects we had never seen before. And then we wouldnt actually decide as a team what to commit to because it was assumed that we had to deliver everything in the backlog every sprint. This is what happens when you try to apply scrum to a maintenance team. -
Two months in my new job, no task assigned to me yet. Not even one. There's been a budget reallocation, and the team just got dissolved. Will probably be moved to a new team (or not?). Part of me enjoys the free time I'm getting (I get to work on my side projects) but it's kind of depressing that I can't prove to the company how much I love building things while at the same time helping the company. 😔4
-
When you create a product that is a place for devs to rant, I excepted the product itself to be a target of the rants from time to time (after all, you are inviting "angry" devs)
I haven't noticed a single one so far! Kudos to the devRant team!!!5 -
High school robotics team. Total of three programmers and one coach who understands programming concepts, but not syntax or anything. One programmer, putting it bluntly, is incompetent and doesn't even bother to learn anything. The other one that isn't me is apparently fucking lead programmer and team leader (IM A SENIOR. SHES A FUCKING SOPHOMORE. WTF.) and she has done about 5% of the programming this year. I've done the rest with the help of a programmer from Ford whom we bring in. All she does is tell you to do shit for her, and if you don't, she pulls the authority card on you.
And I have maybe three days, after a full day of school mind you, until I need almost every part working on the robot code. Fuck me.1 -
Start a business, it'll be fun they said. One of those days you'll realise that you're in a situation where you'll have to fire a friend from your engineering team, there's no way around it..
People keep on thinking and saying
"You're so lucky, you can choose the clients and the team, and work whenever you want to.."
Yep. Highest highs and lowest lows go hand in hand. Thank god there's both.2 -
It seems like everyone else in my team except me and the cto are using dark theme. I see dark theme is the meta since Sauron. Am i one of the last ones to be using light theme?4
-
one more time, I proud of my team and MD too.
XYZ is our office boy. He completed his BSc IT from 3rd Grade college due to family condition and lack of knowledge, he has to work as an office boy.
So my team decided to teach him web development. We are starting it from very basic. We get total 1:30 hours of a lunch+snack's break so each one of us will give 1-day to teach him but It is not free. We will need good coffee in this deal. Our MD like this idea and promised us that once we gave him a green signal. He can do his first internship here. -
Am I the only one that hates working with other developers who think they are some kind of God? I mean it's good to have someone confident in your team but it's so frustrating when he or she starts changing code because "this is better".2
-
Today a member of an other team said that React would be better than Angular 2. Mainly because React allows HTML inside the components declaration and One-Way-Data-Binding.
Me then: Sure, but Angular 2 also has this features 😞18 -
My colleague was presenting a spec for a piece of software our team has to make. I point out some flaws. He gives some incorrect counter arguments. I give arguments for why those arguments are incorrect and point out the flaws again. This time some one from the team agrees with me
My colleague: "Oke, we should just do it like this anyway"
Me: *facepalm* -
I work out of HQ office of my org and perhaps the only one from my team.
My boss will be working out of this office as well.
He is currently visiting, before he relocates full time.
I have my first in-person meeting with him. I am super anxious and want to avoid it at all cost.5 -
The leader in a dev team should be the BEST DEVELOPER
Not the one with "leadership" or "strong ownership" skills and "team player" or "go getter" attitudes. This is euphemism for promoting someone just because you like them, or because of their charisma.
There are many other industries where charisma can play a role in leadership but software is not one of them. To build good software we need to be objective thinkers, not influencers.15 -
The coolest project that I have worked on is still a work in progress. It is a dashboard that uses signalR that integrates with team city, active directory and Google calendar. It's definitely one of the coolest things I have worked on to date.
-
It’s been at least a year since I was last on devRant properly. I’m neck deep in a big project with one week to go and about 5% of the CodeBase built. I have no other team members on this project and absolutely cannot miss the deadline.
It’s time to get on devRant again. -
Alert fatigue is likely one of the biggest problems.
When you add in unactionable or false-positive alerts to the mix it can drive a dev team insane.
Step up your DevOps game!
https://m.youtube.com/watch/...1 -
Slowly I am strongly considering changing the company. Somehow our management is losing its focus on reality. On the one hand, the management doesn't care one bit about what problems we have, especially when we have issues with other teams, which makes it impossible to finish our (necessary) features. But when the management wants something, everything has to be completed immediately and preferably yesterday.
We work in our team (and in almost the entire development) according to Scrum, so we are organized in sprints. However, our CTO thinks that none of this matters and that the whole planning has to be thrown out just because he wants a small (absolutely stupid) feature.
And then, our supervisor thinks he has to force us to do things that are entirely irrelevant for the team. We wouldn't have any advantage and would just be the henchmen of others.
And then there's a neighboring team that refuses to make any progress and keeps blocking everything. But somehow it's management's favorite team and can simply (unofficially) decide about other teams.
Honestly, I'm pretty pissed off now, and I'm not in the mood for that crap anymore.4 -
The bipolar nature of leading a startup tech team:
It's either no one needs you, or the problem is big enough to have you push 5 fundamental fixes from abyss to upstream.2 -
How to deal with "Code Nazis" ?
Don't know how you call this guys that see each and every PR as a possibility to annoy everyone else
Team of 4 Devs, all with lots of experience
But there is a special one, that spams each PR with an incredible amount of comments
Most of them are non-sense like "formatting of comments" or "inlining things makes everything unreadable" or "call this variable this and that" although a reasonable name was their
Rest of team including myself is pretty pissed of by him
How to get over that?5 -
My worst mistake was to not follow the commit process one time. I was multitasking a lot and forgot to run the tests for one of the commits I made. Next thing I know the whole Dev team started complaining that the Head of the branch was all messed up and blaming me. Long story short, it wasn't my change but I had to take the bullet and revert it for not following the process. It was deserved. Process is just as important as writing the code.
-
A peace of work to be done within 2 weeks for 3 devs
1 dev gets pulled off the team, the other decides now is a good time to take a 2 week holiday
So am the only one left and because the designs weren't even ready for the first week i only had a week to do it, i managed to finish it with some defect obviously, and testing oh yes the testing non, non whatsoever. Only test i had were snapshots. Other than that, nothing. So the demo seemed to please everyone and the whole team got praised for some gr8 work, work that was estimated for 3 but done by one and hah no testing...yet1 -
Our company is a team of about 10 people; all of us are salary. One of our developers continues to come in at 10-11AM rather than the designated start time of 8AM. Instead of punishing this person for their tardiness, our boss wants to install a time-clock and make us all use it and make us hourly...3
-
Rant: that moment when you don't want to drop one of your devs because he's been on that team since day one but HE DOESNT DO SHIT FOR THE TEAM!!!!!! I can count on one hand how many projects have been on time from this guy. RANT OVER.
-
I don't know how any company can keep on top of crazy npm package changes. I work in a REALLY SMALL team. We are still using bunch of deprecated packages and we keep building on top of those packages. Updating packages is always a nightmare. It's impossible to Google solution when no one is using the particular combination of deprecated packages. Fuck me4
-
Anyone who's been part of the community has probably noticed a little OS mud slinging. It's natural, as everyone cheers on their "team".
I just realized that no one is ranting/name calling/general mockery of the BSD crowd! They just get away without a scratch. Not fair 🚫10 -
!rant - Love the new pets but only shoulder birds show up in mini avatars on posts. Cats should be available on shoulders too. :) One of our team has a cat that walks on a harness, rides & sits on his shoulders around town and while he works.2
-
One of my seniors is leaving the team. Honestly, I did not talk about personal stuff with him but during this lockdown, he was the only one whom I talked to this much. My most projects are with him, so in the team I kind of only know him. And now he is leaving, I feel so heavy.
I was anyway feeling no interest in my work, and now this, I really don't want to work at all. I don't want to be in this team, really without his guidance I can't do good. And this reminds me now I don't have anyone in the team to guide me. It's the same feeling as you get old and now no one to support you and you need to support yourself and slowly others. It's frightening.
On a good note, I hope things will turn out to be good for him, he's a nice person after all :) Everyone respected him, and he was trusted so much.2 -
Doing another FE assignment these days. In this one they have some clear requirements and some not so clear ones ex. "make the existing code better". And it's for a team lead position so I have to pretend I know what I'm doing instead of just implementing the feature they want.2
-
One thing that's very frustrating about being in a globally distributed team is that you have to wait ages for someone to respond on Slack. You can't just walk up to them and ask for something. Most of my time is spent waiting for people to respond.1
-
One day, being new in the team i was not sure of all the DB column decodes, asked my senior member to send me decode of a column.
He sent me a 300 line SQL query. Took me 30min to understand it. -
Everybody's talking about the 50/50 for some reason, so here's my 2 cents. I've been trying to hire another senior front-end engineer for my team for over two months, and not one half-competent candidate passed our tests yet*. The first one to pass, and I don't care whether it's a male candidate, a female one, or a type of asexual sentient mushroom spore, will get the job.
We do prefer a female candidate because our team is all male at the moment. But that's not going to stop us from hiring a male one if we find anyone.
Also, out of 40ish candidates I've interviewed so far, I believe only 3 were female. Might be a fourth one I can't recall at the moment.5 -
I started working at a new company a couple of weeks ago as a Dev/Ops engineer, my first real ops position after years of being mostly a dev with two sys-admin positions sprinkled in.
I should have seen the red warning signs when, during the interview, a developer told me the old devops team was so bad they fired all of them last year. After I started, I learned that all four people on our team were totally new. Three were hired after the last guy from the old team left (without any notice) and one person use to be a developer who was transferred over to this new team (but not to lead it).1 -
When the big guy at the top for vanity sake changes the name of a git team, breaking every auto deployment and local repo needing updating for every fucking one. console.log("fucking shit balls")
-
Long one
So our newest team-mate has made a channel dedicated to make fun of or scrum master, then I send him a pm saying to cut out the childs play, and we need to act professional.
Then he tells me that our scrum master is okay with it, and really looks like he is!
SM said this making jokes about him brings the whole team together and makes us a better team!!
WTF...
Really WTF ... am I the bad guy for caring about my team??3 -
For me big list is there ;)
But recently one of the team in our internship has built a project where admin can add and update his own educational details into the project and no one can see admin personal information because of privacy :| -
Chronicles of UX struggles vol. 2
I ask the design team to do some sketches so I could see how they want the pages (2 pages), UX guy says he'll do the sketch for the page, and I ask to which one, the first one or the second one?
...
He answered me "Yes"...
Edit: he took over 3 hours to send me a new message after I tried to understand what he was indeed going to do... -
Rant two of monday!!
We are in a new office. Bigger than the previous one. Fine.
We are away from sales team (check previous rants about sales team and their hero #boringman)
Cool. We still hear him and them but it's better.
Boring man stops by tech team table to ask how many lines of code we have done today or in the last <period of time>.
We have solved nothing.
Boring man is veeeeery bored. -
Had the best team building day today.
So it happens that 5 of us have Oculus Quest’s 2. We stayed after worked, ordered bunch of pizza’s and played Population One. We didn’t plan this, neither did we called it a team building event, but essentially it was.
Damn, I love my current company setting.2 -
I got the news of my promotion in the middle of our Team Building feast, which was also the same week I won the singing contest at my office. Good week, that one.1
-
In one of my previous projects, most of the team members were pranksters. One time a team member who had newly joined the project left his laptop unlocked while going to the restroom. The others drafted a fake resignation letter from his laptop and emailed it to our entire team. And when he returned, we all spent the next ten to fifteen minutes nagging him to explain why he took such a "drastic step", before finally explaining everything to him.
-
Quietish team member sits quietly and creates the mother of all APIs, doesn't say much about it, doesn't document what he's done, falls out with the boss, leaves with 2 weeks to go before a beta release.
Already overworked dev/backend support team are plunged into manic bug fixing/business rule implementing/call standardising/chaos.
This is not how one devs.
Not one bit. -
Part of one of the workarounds for Dirty COW is to disable ptrace.
ptrace is generally needed by debuggers.
I am team lead for L2 support at a company which makes a debugger.
RedHat are now shipping this workaround.
*ducks for cover*2 -
When you feel that only you and maybe one other guy from the team care about product and do effort to actually refactor legacy spaghetti code while others just patch it up or even build changes on top of legacy spaghetti!2
-
I am being moved from one team to another in short periods of time. Just when I start getting comfortable in the technology in one product and decide that this is my life now, they put me in something else where I have to learn from scratch. Been a junior developer for 2 years now.
!rant because I love it that I get to learn different technologies. Also the opportunities to travel. -
It was on my last job before the one here. I met one of the other programmers in the team and it was an instant click. Really liked this dude. His name was Adam, he was older than me and we spent most of our time talking about code and listening to music (he was a hardcore Caifanes fan, which is one of the greatest Mexican rock bands ever) and he would show me the oldschool tech he used to work with. He was really cool and we still talk all the time :) another would be on a conference my current job sent me and my team to (all of my team are my friends as well) but we got to meet tons of cool people and we still talk to most of them.
:) good vibes man, nothing but good vibes.....and beer. -
effin management always commiting something they didnt think through and now the team suffers the consequences of their stupid actions, one of them is that they fucking commited a night of development phase for a major code revision fuck that shit cause that major revision also came for their fucking lack of analysis and mediocre mindset during the requirements gathering phase fuck that
-
Phase one of the project we assembled a team for rapid development. The client was enthusiastic about the progress that the team made in a short time. They specifically requested the same team for phase two of the project. Executives replaced everyone on the team except me.
I looked at the new team and basically everyone on it is less technical.1 -
So the people in charge of staff allocation came into our room the other day and straight up stole most of the front line support team for iOS. The team now has one member, and the manager of the team found out about it 15 minutes before it happened. This was done to fill requirements on other projects that they are struggling to get staff for.
Meanwhile I've been sitting here for months wanting to get out of this project and they cant find anything else for me. All because I wont travel 4 days a week... -
Improving the inviting feel and quality of my cube, one carefully placed and effective sticker at a time.
Thank you @dfox + team!2 -
So about a big problem I had earlier in the two last weeks, we were waiting for the expert of the team we work with if they have any idea. But we had to wait for him to get back from their one-week break.
We asked them about it
They have no clue
fuck. -
I suspect my more “senior” colleague on my team consistently thwarts my ideas and continues to make bad programming decisions because no one else wants to deal with the code we own and he’s just trying to have job security by making it so that he’s the only one who understands this bowl of spaghetti.2
-
After a week of designing an API to our system for another team followed by redesigning it because they 'know what they need when they see it' I think I understand the pains all of you guys who work directly with customers go through what leads to exactly one question : How did you manage to never kill anyone?1
-
It's refreshing yet odd when you go from a team with loads of meetings (mostly stand-ups and of that Scrum stuff) to one with only 2 weekly meetings.2
-
My current employer...
In 3000 coworkers they have many things, but a team is not one of them... Fuuck -
So I became a team leader ("promotion").
One of the team is a senior by title, but fuck he is just a refactoring machine. Seeks for architecture design in fucking everything. Even in fucking tests instead of just writing them he is inventing convoluted architectures and systems...
Fuuuuuuck - just write the fucking tests, no one gives a shit if you have a fucking factory in the test case! -
Team Lead (not my team, thankfully) sends outs a team-wide message (in their exact words):
"please DM me with the task link if you are adding any new tasks in Jira. This is to make sure that i am aware of any ad-hoc task coming up in the jira queue and also to make sure that all the task are following a common template."
Interpretation : "I'm just too lazy to look at each jira issue after the last one that I followed up on (which is my job BTW). So I'll add some extra work for you to explain everything to me on DM"
Way to go for killing productivity. ¯\_(ツ)_/¯
Thankfully, this is not my team. If they were my team lead, I'd be super furious. I'd even report it to upper management. I'd even offer to do their job and let them do mine. I think their job just got so easy if everyone was to go report to him like that.3 -
Most useless meetings I attended was in my previous company. Our f***king boss suggested that manager must have to take one morning meeting with the whole team about that tasks what needs to be done. And our bastard manager calls the whole team and wasted time all of us cause our work is not related to each other so he is explaining one on one and rest are looking at his face what type of species he is :P
-
Hey guys, I'm new to a dev management role. One of my responsibilities is to write tasks and do code reviews for the team. I keep getting issues in code due to the lack of contextual understanding of the codebase. How much detail should I include in a task? Should I expect my team to understand the context of the task/codebase?3
-
When a project is due next week Monday and the design team wants a lot of interactivity and you got the designs last week Thursday. What does one do in this situation?1
-
One of my Computer Science modules this year revolved around completing a team project, and one person in the team basically fucked it up for all of us in the last minute.
We had to create a simple task management app for a fictional company, the university did not care about how the program looked and all that mattered was if the app is functional or not. The app relied heavily on a database, so all we basically had to do was get, modify, and add data from a database. Now this person did his part of the programming, but with an outdated database model and did not even test his code as he said MySQL wasn't working on his home computer.
2 days before the final deadline is when we decided to merge everything together in the git repo (as that's when the rest of us finished our tasks), and that's when we found out none of his code worked. We then spent the next 48 hours with little sleep to try our best to fix everything, but unfortunately due to his tasks carrying a majority of the complexity of the program we couldn't fix it all in time and we ended up losing roughly 50% of the marks.
This all probably could have been avoided if one person in the team did look at his git branch properly, but this person was the programming lead of the project and didn't ask for any help at any point until the last moment when we merged everything together. Oh well though, at least I've learnt better for the next team project that I do2 -
Not something that's happening. Just remembered a debate I had with a coworker from a long time ago regarding hiring and diversity.
Assuming there are two candidates.
Objectively one is slightly worse than the other (let's say 10%)
but the objectively better candidate is more of the same as your team (In terms of stack, gender, ethnicity)
Obviously if one is a lot better (say 30%) I'd hire the one that scores higher.
However, in this scenario (~10%). I think I'd hire the person that offers a different perspective even though they may be less talented.
My reasoning is the team needs someone that thinks differently and looks at a problem from a different box. Otherwise it becomes too easy for my team to go down a path that we like but isn't necessarily better.
What say you?13 -
For our current project, we connect to three different OpenVPNs:
Our dev OpenVPN (to get Jenkins/Artifactory)
The ops team devops OpenVPN (to get to environment)
The vendor's VPN for single signon
All of them have different keys and one connects to LDAP and uses a password we can't change. -
The worst kind of people to work with are the ones that you tell a heads up, don't do this, it will cause problems, but happens anyway and in team meeting "I didn't know, no one told me" and it just makes you look worse to even argue it....
-
I am currently taking a cures in leadership and teamwork as part of my computer engineering education. One assignment is to write a text about how formal and informal leaders in a team creates problems. I am sure that some of you have been in a team where the leadership have created problems and I would love to have some stories from real teams to use in my text.1
-
Working on a CS370 (Software Engineering) project with 5 people; 2 of which feel like their time is more important than everyone else's so when we all meet as a group to go over presentations, documentation and other things we need to do as a group, they silently sit alone working on bits of code they should have done previously. Then when we can't get docs done and handed in on time, one of the two decides to spam our group chat at 2am when 2 of us are sleeping because we work in the morning, one of us is sleeping because of morning classes and the last one is doing god knows what. Like, I'm sorry. But failure to do your shit on time does not constitute an emergency on my shit. All of our weekly peer reviews reflect on how no matter what we say to these two; they refuse to work as a team.
!rant, more like dev hint
In a team, your time is not more important than team time. You can do things on your time whenever you want; but unless your entire team shares your schedule, team time might be a rare commodity and should be used as such. -
Some demented bagpipe at the microsoft SSIS team thought it was too much of an effort to build in the option to review all changes and to refresh all metadata with one click whenever the metadata changes.6
-
Using ReSharper is like becoming enlightened, or de-brainwashing oneself to see true reality. Of my entire dev team, I'm the only one who can see the fnords!
Unused identifiers, badly sorted modifiers, unused property setters, redundant `this`/namespace, redundant casts... Surely if they could see them too, such code would not survive! -
when you merge changes from other branch, made by other team, and see that huuuuge old project is now basing on dependency injection instead of one singleton- manager approach. Even merge conflicts look beautiful!
-
I work on a larger team where we do continuous integration so there is a high probability people will be working on the same files for different features. As a result, one of the best feelings is grabbing the latest files and not having to diff first thing in the morning.
-
Ok after numerous failure in perusing subordinates to use webpack-babel to bundle their code, I forced a new stack of React onto the whole team for the built-in bundling.
Now I am crying with joy when I revamp and bundle all the old shits into one single beautiful chunk myself. -
Manual tests (the only way of testing within my team) fails one after the other.
The fault was a manual misconfiguration.
Why the fuck in 15 years since he got this job that test manager hasn't improved this?3 -
You work in a team, for a team to move forward successfully the team should work in sync. A team always has a goal and a plan to get to it. There are times when the team needs to take a different direction therefore the set path should always be available for change because our environments dictate it.
We all have different styles of working and different opinions on how things should work. Sometimes one is wrong and the other is right, and sometimes both are wrong, or actually sometimes both are right. However, at the end of it all, the next step is a decision for the team, not an individual, and moving forward means doing it together. #KickAssTeam
The end result can not come in at the beginning but only at the end of an implementation and sometimes if you’re lucky, during implementation you can smell the shit before it hits the fan. So as humans, we will make mistakes at times by using the wrong decisions and when this happens, a strong team will pull things in the right direction quickly and together. #KickAssTeam
Having a team of different opinions does not mean not being able to work together. It actually means a strong team! #kickAssTeam However the challenging part means it can be a challenge. This calls for having processes in place that will allow the team members to be heard and for new knowledge to take lead. This space requires discipline in listening and interrogating opinions without attachment to ideas and always knowing that YOUR opinion is a suggestion, not a solution. Until it is taken on by the team. #KickAssTeam We all love our own thinking. However, learning to re-learn or change opinions when faced with new information should become as easy to take in and use.
Now, I am no expert at this however through my years of development I find this strategy to work in a team of developers. It’s a few questions you ask yourself before every commit, When faced with working in a new team and possibly as a suggestion when trying to align other team members with the team.
The point of this article, the questions to self!
Am I following the formatting standard set?
Is what I have written in line with official documentation?
Is what I am committing a technical conversion of the business requirement?
Have I duplicated functionality the framework already offers?
I have introduced a methodology, library, heavily reusable component to the system, have you had a discussion with the team before implementing?
Are your methods and functions truly responsible for 1 thing?
Will someone you will never get to talk to or your future self have documentation of your work?
Either via point number 2, domain-specific, or business requirements documentation.
Are you future thinking too much in your solution?
Will future proof have a great chance of complicating the current use case?
Remember, you can never write perfect code that cures every future problem, but what you can do perfectly is serve the current business problem you are facing and after doing that for decades, you would have had a perfect line of development success.1 -
One of team member was showcasing their time series modelling in ML. ARIMA I guess. I remember him saying that the accuracy is 50%.
Isn't that same as a coin toss output? Wouldn't any baseline model require accuracy greater than 50%?3 -
I have participated in a hackathon this weekend and one of the theme of hackathon was blockchain and being a blockchain dev i have created a DApps which follows token standard and other security standard but our UI was kind of basic cause we didn't have any designer in our team but one participated team's UI was far better than us but has serious flaws in the smart contract and guess what they are the one being selected and that's not it there wasn't a single judge who has basic knowledge of blockchain.I was using DApp term very often while presenting our idea and one of a judge literally asked us what is dapp? I mean WTF? Now i am regretting why did i participated in this shitty hackathon? On top of all that they juat give a single sticker for whole team. Wtf we are supposed to do? Cut it ? If you are a blockchain dev don't forget to see this beautiful function i found in the token contract of the selected team from the github.1
-
Sitting at my desk, happy tapping away at code, and one of our newer team members asks a general question (4 of us in the office)....
"Uh.. how do I undo a git revert?"
🤔🤦
FML... Very much looking forward to leaving this place next year.5 -
Intelligent Development class (yeah, that's how it's titled), teacher leaves us as first task to develop our own Database, because later we will make it a fuzzy database.
She gave us three days. Three (counting me) in the team. I began working on Interfaces (Java development) and so on, using GitHub for VCS and documenting each method.
This assholes didn't even ask what was missing or what should they do. One day before date, I told them "Hey, I think I can nail the underlying file management tonight, so, work on the language parser, please"
Stood awake until 1 A.M., waiting for their reply, but there wasn't any.
Next day, I'm the only one of the team and I tried to decline the presentation of my work, but a friend encouraged me, because it was my work and I worked hard.
Presentation went better than expected.
After the class, I have another with one of my team members, he asks "How did you do?", "Us? You meant me, because the other prick didn't go".
And that's all, not another single question nor explaining why did he didn't answered the DM's I sent.
Fuck those guys, fucking team of shit, I hate it when you can't pick your team, but I guess that's just a common place for all of us here, isn't it?3 -
How to manage this junior dev ? One of the girl from my team only eat my brain by asking some shitty questions.2
-
Twitter developers will authenticate half of their endpoints with some authentication method and the other half with a totally different one (which doesn't work) and their sales team will have the guts to contact you to check if you're still interested to access their API.
My only interest is feeding your corpse to the ravens.2 -
What is a good way of enforcing rules (particularly following release procedures, cut off dates) for a team?
Other than the rules need to be well defined and written down, I'm thinking there needs to be a consequence for violations....
Like must provide a valid explanation or buy the boss/team/whoever has to do extra work because of the violation a drink.
But not sure what's a good one, does it work out is this too Draconian?9 -
No one knows when the current pandemic situation will subside...But it's important to be empathetic towards your colleagues and team in this tough times. Every one has their own share of problems and all we can do is at least listen to at least some of them with open minds and little bit of sympathy.
-
Team I'm on consists of four devs, two being contractors who have hit their necessary month off period (something to do with contractual laws), one junior developer who is off on holiday for a while, and me, the person with most experience but busiest home life.
Next few weeks are going to be a real test of patience until I'm no longer alone on the team.1 -
Really don't want to work tomorrow. I have this PM who just constantly over burdens me. I'm in a tiny team of me and one other dev. Need a holiday soon! (Been 2 years) Currently doing the dev on 4 sites at once on my own.3
-
Anyone know some good social media bots or tools or whatever
My school's principal just put me (one of the least social people in the building) in charge (I need to build a team too 😢😢😭) of a social media infused project -
So I have this new role at work, still app development with some added responsibilities. Nothing major. But already I'm noticing what could be a pattern.
Zoom meetings that could have been phone calls or emails. Meeting was setup a week and a half or so in advance. Had real a meaning last week where a team member mentioned it and reminded the other team members of the upcoming meeting. We all confirmed that we'd be there.
I get a notification that the meeting is in 15 minutes. Meeting time!!! So I log on, only to see one person from the other company, two more people from said company log on then my team member. But to my surprise him and I are the only people from my team on zoom.
My team member then goes on to waste this poor man's time asking him questions that he doesn't really have the answers to and I'm here just wondering why.
Why isn't this meeting a 2 minute phone call?
Why am I in this meet?
Is my team member bored?
How does this make my company look in the eyes of these people?
Now I know why my other team member didn't log on. They smelled the rat and knew this would be a wast of time. And me being new to the team walked right into it 😐 -
Just reviewed one of the team members' PR and asked her to follow Semantic HTML, she said I'd rather not to, because I don't like to discriminate between tags! Honestly?
-
That time when the head of the developer team had the fuking idea of having the meeting of a meeting (he didn't understood the point of the previous one...) Half day lost in that shit. At least he is gone now
-
Would it be really bad if I just straight out asked my boss if I'm the most Senior person on the team?
I'm the youngest of all Senior Devs on the team... Though actually I just turned 30... Today...
Maybe this is another one of those moments triggered by my subconscience...3