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
-
I hired a woman for senior quality assurance two weeks ago. Impressive resume, great interview, but I was met with some pseudo-sexist puzzled looks in the dev team.
Meeting today. Boss: "Why is the database cluster not working properly?"
Team devs: "We've tried diagnosing the problem, but we can't really find it. It keeps being under high load."
New QA: "It might have something to do with the way you developers write queries".
She pulls up a bunch of code examples with dozens of joins and orderings on unindexed columns, explains that you shouldn't call queries from within looping constructs, that it's smart to limit the data with constraints and aggregations, hints at where to actually place indexes, how not to drag the whole DB to the frontend and process it in VueJS, etc...
New QA: "I've already put the tasks for refactoring the queries in Asana"
I'm grinning, because finally... finally I'm not alone in my crusade anymore.
Boss: "Yeah but that's just that code quality nonsense Bittersweet always keeps nagging about. Why is the database not working? Can't we just add more thingies to the cluster? That would be easier than rewriting the code, right?"
Dev team: "Yes... yes. We could try a few more of these aws rds db.m4.10xlarge thingies. That will solve it."
QA looks pissed off, stands up: "No. These queries... they touch the database in so many places, and so violently, that it has to go to therapy. That's why it's down. It just can't take the abuse anymore. You could add more little brothers and sisters to the equation, but damn that would be cruel right? Not to mention that therapy isn't exactly cheap!"
Dev team looks annoyed at me. My boss looks even more annoyed at me. "You hired this one?"
I keep grinning, and I nod.
"I might have offered her a permanent contract"45 -
Since past two-three years, Indian Government has been organizing a Hackathon called Smart India Hackathon for college students. And Luckily our team was selected this year.
This team had 5 Electronics Student and 1 Computer Student. Guess who the Computer Student was? Yea, Me.
They Knew nothing about Android Development. And the idea was about an Android Development. I was the only person who could code.
The centre for our hackathon was Varanasi and we live in Hyderabad. So we had to go there. I have not really travelled a lot in the trains (especially not this far from Hyderabad to Varanasi ). During the whole 37 hours journey, I was not able to sleep cause I am not accustomed to sleeping on a train.
The moment we reached Varanasi the hackathon had started which was 36 hours long. Normally team members switch places so that they can sleep but not ours. Cause I was the only one coding and it had to be done in this 36 hours. So add this up 36+36 hours of no sleep, I must have rarely slept for 3-4 hours in that 72 hours.
After the hackathon, I slept like a Snorlax whereas the other went for a trip around Varanasi ('_')
18 -
The Perfect Storm:
My worst coding mistake? Yeah, let me tell you about that. I pushed a simple JavaScript/HTML change without knowing that the stupid header was shared with another "not so important" section of the site called "My Account" where people go to pay for their services. I call it the perfect storm because I left early that Friday for a weekend cruise and right before leaving I pushed the change, sent the request to push for production and left. When they noticed that clients were complaining about not being able to pay they started reversing most changes of all teams trying to fix it but they never touched mine because they knew I wasn't working on the backend. My whole team worked over the weekend trying to find the issue while I was having fun in the cruise. They ended up reversing all changes by Sunday night and it took us about 4 more days to figure out that my simple JavaScript/HTML change broke the site and prevented 30 million customers from making payments that weekend plus it broke the whole 2nd release of the month.... yeah, nothing major.
21 -
If your IDE found
10 errors
and 47 warns
would you correct them
or let them slip.
YO ...
His palms are sweaty
Knees weak, arms are heavy
The tests are failing already
Code spaghetti.
He's nervous,
But at his laptop he looks calm and ready
To squash bugs
But he keeps on forgetting
What he wrote down, the whole team goes so loud
He opens his file, but the code won't come out
He's chokin', how, everybody's jokin' now
The deadline run out, times up, over, blaow!
Snap back to reality, oh there goes file integrity
Oh, there goes documentation, he choked
He's so mad, but he won't give up that easy? No
He won't have it, he knows his whole header's code
It don't matter, he's dope, he knows that, but he's broke
He's so stacked that he knows, when he goes back to his mobile home, that's when its
Back to the office again yo, this whole rhapsody
He better go capture this moment and hope it don't pass him
Note: All credits to the original owners of these phrases.5 -
So I've been screaming for months that push notifications are not reliable enough to build critical functionality on top of. Management won't listen and keep pushing ahead with making teams use it because its cheap and easy.
Been debugging an issue on/off for several weeks. Turns out someone in management asked the backend team to cut the expiration time of items down to 5 minutes to increase throughput (without telling mobile). Notifications are regularly taking +4 mins to get to the phones, leaving our users with barely any time to react. They are now complaining.
I swear if there is a single IQ point available between the whole team i've yet to see any evidence of it8 -
Fuck stupid client.
Sorry:
Boss: client want to white label the solution.
Me: ok. They just need to create A record and send as SSL certificate and I will do it.
Client : here is your SSL certificate.
Me: spend whole night to make the transfer and setup server and check whole solutions one by one for reference to our company.
Next day wake around 2 pm to 100 whatsapp message, call from client and noss.
Turns out client IT team revoked the certificate without informing and the product stop working for all people.
Me: go to back to sleep.6 -
$ rant --ridiculous
So today my beautiful and glorious presence was asked to a meeting, I was supposed to present the hosted platform for a project, well, the meeting took place in a building I had never been in so I got lost, when I arrived the design team were presenting a completely different design that what they had given me, which I had spend 10+ hours cleaning and organizing and integrating with the code, and during the whole time I was there I was never involved in the conversation, so basically I was pulled out of my coding liar for nothing oh and because who doesn't like a good ending ... I crashed on my way home after the meeting. Cool day huh?3 -
Today after 1 year of taking shit I sat down with my manager and completely tore the whole fucking company apart.
I absolutely slammed my colleagues, obliterated my team lead, went on and on about how no one understands the basics and how everything we have is copy paste procedural code and the only way to fix what we have is to delete it. I then insinuated I want to quit because I cba with the struggle anymore.
Result? Fat promotion. Not sure what just happened here lmao.
14 -
My team handles infrastructure deployment and automation in the cloud for our company, so we don't exactly develop applications ourselves, but we're responsible for building deployment pipelines, provisioning cloud resources, automating their deployments, etc.
I've ranted about this before, but it fits the weekly rant so I'll do it again.
Someone deployed an autoscaling application into our production AWS account, but they set the maximum instance count to 300. The account limit was less than that. So, of course, their application gets stuck and starts scaling out infinitely. Two hundred new servers spun up in an hour before hitting the limit and then throwing errors all over the place. They send me a ticket and I login to AWS to investigate. Not only have they broken their own application, but they've also made it impossible to deploy anything else into prod. Every other autoscaling group is now unable to scale out at all. We had to submit an emergency limit increase request to AWS, spent thousands of dollars on those stupidly-large instances, and yelled at the dev team responsible. Two weeks later, THEY INCREASED THE MAX COUNT TO 500 AND IT HAPPENED AGAIN!
And the whole thing happened because a database filled up the hard drive, so it would spin up a new server, whose hard drive would be full already and thus spin up a new server, and so on into infinity.
Thats probably the only WTF moment that resulted in me actually saying "WTF?!" out loud to the person responsible, but I've had others. One dev team had their code logging to a location they couldn't access, so we got daily requests for two weeks to download and email log files to them. Another dev team refused to believe their server was crashing due to their bad code even after we showed them the logs that demonstrated their application had a massive memory leak. Another team arbitrarily decided that they were going to deploy their code at 4 AM on a Saturday and they wanted a member of my team to be available in case something went wrong. We aren't 24/7 support. We aren't even weekend support. Or any support, technically. Another team told us we had one day to do three weeks' worth of work to deploy their application because they had set a hard deadline and then didn't tell us about it until the day before. We gave them a flat "No" for that request.
I could probably keep going, but you get the gist of it.4 -
My whole team was a circus:
- Dev 1, the senior: he will be spent his days coding his personal projects and will convince management that everyone else needed to prove themselves so he will have nothing to do and we will do all the work.
- Dev 2, the junior: he was convinced that his mission in life was to be friends with his team. He's desk was far from the rest of the team so he will show just right after lunch EVERY FREAKING DAY with a list on his phone of random things he wanted to talk about like music, artists, art, news, etc., he really thought I didn't notice the list.
- Dev 3: the vegan: you will hear on every chance how she was so awesome for being vegan.
- Dev 4, the expert: if you ask him anything he will stare at you in silence to make you feel like you are a stupid for not knowing the answer and then turn around like nothing.
- Dev 5, the ghost: he will show early every day, code without mouthing a word and leave at 5pm, I think I heard him saying "hmmm" once but I might be wrong.
- Dev 6, the coder by accident: he was a graphic designer and ended up doing front end so he hated his job.
- Dev 7, me: the one who didn't care about anything but doing his job and leave.
- The project manager: she didn't knew anything about technology but will attend meetings with clients on her own, commit to deadlines and then inform us that the project that we estimated for 8 weeks will have to be done in 2 with new additions to the features.
You know the drill, here's your potato :/
5 -
Got together with my old dev team (5) who all left the same company at the same time almost two years ago. (Thats a whole other story).
One of them told us he left and went to a new company that measured performance by the amount of commits a dev would to per day. Of course he didn't know that when he signed on.
Three months into the job he had a week where his first commit wasn't until a wednesday and he got called in by the manager to explain his lack of commits and how he was going to improve.
He quit on the spot. Had a new job in less than a week.
Other devs at the company were fixing typo's and just commiting them one at a time to create a lot of commits.10 -
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 -
My first programming job started at a fairly small gamming company. We were pretty close because we were so small and sometimes jokes were a bit too personal. Anyway, during my 3 months probation period, the team lead invited the whole company at his house for a party. Long story short, I got wasted, and when the CEO arrived I went to him and told him something like: Yo dawg, let's drink, don't be a pu**y. The sad part is that I cannot remember doing that and apparently I shouted outloud. I had some pretty interesting meetings the next days. Came too close to being fired 😅.4
-
Today is deadline day. So my Project lead decided to remove a key column because "it wasn't necesary".
He didn't tell anyone about the change and no commit message explaining it.
When confronted by the whole Team about his stupidity. His excuse Was: "I didn't know we had a deadline".
Holy badger fucking horsecum guzzling excuse of a potheaded flat earther!!!3 -
Yesterday, the whole dev team went out to lunch and we ate a lot and we drank a lot until we all got drunk! Since we are paid for the number of hours we work, we all decided to go back to the office and work.
WE WERE DRUNK WORKING! Drunk coding ftw
Result: The server is down right now because someone fucked it up and I think i ruined my code yesterday because I wasn't really myself. The whole team was crazy as fuck. One of us just came back from Poland so we were drunk and high from all the polish chocolate we ate.
I hope they fix the server so I can check what kind of bullshit the drunken me did yesterday o.O8 -
FUCK GOOGLE.
FUCK THE GOOGLE PLAY REVIEW TEAM.
FUCK THEIR BOT GENERATED EMAILS.
FUCK THEIR DEVELOPER SUPPORT.
I am trying to launch a fucking action game. There will be fucking guns and muzzle flashes shown in the screenshots. Stop fucking rejecting the app. There is no blood in the icon or screenshots. Stop sending me bot generated emails and tell me what content is being flagged.
A little information on the whole scenario: My game was rejected so immediately I contacted the support as to what was the issue. The guy told me 2 screenshots were flagged because they had the muzzle flashes and damage indicator (call of duty type which tells the direction from where the bullets are coming from). So I removed the screenshots and still the game was rejected. FUCK THESE ASSHOLES. SAME GOES FOR APPLE.9 -
Every fucking time its the same shit:
Our nontechnical managers meet with the client and try to pass technical requirements to us..
These pieces of shit don't get that this only makes things worse.
Making everyone waste fucking time trying to understand requirements that would be a lot fucking easier if any of us were is any fucking meeting.
But nooooo... We have to fucking be the whole team in fucking meetings with these cock suckers so they can realize they didn't get shit and the back and forth bullshit begins:
We ask questions
They don't know
They schedule meeting with client
They ask their moronic way
The client answers
They schedule meeting with us
We ask questions...
And this fucking loop goes on for-fucking-EVER!
Fuuuuuuck this!!7 -
A major bank had a bug in their system that triggered multiple postings of transactions in all of their clients' accounts. When they found out the root cause, they just had to mention that the programmer was a female. Like that was any bearing to the problem. It's not like they have like a whole fucking team of QA testers that should have checked that shit before it went to production.14
-
Worst. Fucking. News. "Your work is going to start getting outsourced. It's only $10/hr in India. Yes your job is at risk. Yes this includes the whole team of 10 people." Fuckkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk9
-
Working really hard, finishing tasks, upgrading servers. Cancel some useless meetings to finish up features, working till 2am to get a database migration working. Half of the platform is transformed, both customers and team are very happy about their accomplishments.
Boss: "OK, I think we're on the right path with these changes, but productivity and morale is honestly disappointing. Are you guys sleeping enough? You all look very tired and unmotivated!"
Attend all meetings, call boss at 7am to discuss random purchases like a whiteboard, run around the office holding a (broken, lol) MacBook, looking very busy & slightly worried. I shout random things at people across the office like "Nice work Gary!" and "Damn, you are on a roll Angela!". I initiate smalltalk with department heads, only to immediately disrupt the conversation by checking my phone saying "Oh I really have to take this one" (empty battery, lol). No one writes a single line of code for four weeks, and nothing new has been deployed by the whole team.
Boss: "I think it's commendable how productive the team has become this month. You guys are all so active and involved. A real improvement!"6 -
I just had a 2 hours long company lunch followed by a 1 hour meeting with the whole team. And I still have a big problem to discuss with two colleagues. Too much social interaction for one day for me. Damn, how my head hurts.27
-
Fvcking project manager wants me to commit my partials code to the master branch just to let our employers know that we did something today! That's why you are there to relay our predicaments to them, you piece of shit!
Now he is insisting it the whole team. Fvck! Are you nuts? Do you really understand what version control really means? Why master branch, why can't we just create fucking different branch and push it there if they want reference! Commits are supposed to be a fix code or update not a broken and unfinished piece of codes! I will fvcking cross my finger after messing up the master branch. Now it looks so disgusting to me.9 -
Visual studio just forced update on my friend's whole team, boss just let them all go home early and pray that it finished updating by tomorrow... Good job Microsoft3
-
#TheCoronaEffect
Before Corona: (Work From Office)
Boss: Let's have a call.
Me: Sure, allow me some time I am assisting the team on a new feature in the app.
Boss: Ok, ping me as you get free.
----------------------------------------------------------
Now: (Work From Home)
Boss: ***Calls for the 15th time in a day...***
Me: (With Bleeding Ears) Yes sir, am here...!
(Having to pick up every single time as he knows you've got nowhere to go 'coz the whole city is in LockDown)
Boss: ***Talks for another 1 hour with screen share***
My Boss is a bigger threat to my health than Corona now!!!
#GoCoronaGo3 -
Taught my whole team that you can enter cmd/bash commands directly into windows explorer in the location bar.
No point in opening git bash to just clone a repo or open cmd just to run a php server.8 -
hey there, long time no rant.
remember that manipulative, sociopathic angry manchild turdface PM, the kind that gives you a never ending rant inspiration? the one that got immortalized in like 90% of my rants?
well... it's time for the final update.
i decided to leave the team some months ago. my boss reacted very cool and supportive and suggested topics i could work on instead. when i told my colleague, he decided to leave the team at the same day. we both also complained at HR and added some papertrails about PM's shenanigans.
shortly after, another guy from the team quit and left the company, and i know that it was 100% because of this PM.
so, there were 2 devs left from originally 6 in PM's team.
some other people in the environment of this PM quit, one of his subordinates and someone from a greater project in which the PM's project was embedded.
after some internal investigations and discussions, the PM's team was completely kicked out of this greater project, since after ~ a year, this team was neither able to deliver anything useful nor to define what it actually was what they wanted to provide. instead, they actively blocked the project, solution finding and cooperation between teams. and this is quite very much PM's fault.
the final move came this month when PM got fired. i think, management finally realized that he is a total fraud who has no clue about the whole matter (neither what devices we build nor about software development). or management. or leadership. and that all he can do is produce hot air and bullshit people for some time to make them believe he knows something.
not sure how long he'll still be around, but i'm happy when i don't have to see his face ever again. i'm just sorry for the next company he'll be moving to...4 -
When the whole dev team desperately tries to convince the boss to get Linux on the new servers instead of windows.6
-
Rant from my old company:
CEO decided he could cut costs by outsourcing to cheap devs in other countries.
Does this, the new hires are super incompetent. We're now paying for a whole team that is adding work cause they keep fucking up.
Leadership is super happy with the "savings" (which is basically just the team here working harder to fix everything).
All the smart people start leaving, leading to a downward spiral.
Last I heard, one of my junior co-workers had been promoted to senior (he hardly had any coding experience).
Fuck them all8 -
So I had to work in a team for a CSS & HTML uni project with two others and the criteria was the web site had to be something funny and related to the university. So I talked with my so-called teammates about the project idea and what the web site would be about when one of them said "Let's make it about cats!". Okay I guess, not really sure what we could write about, but we'll manage. Then these fuckers just up and disappeared, leaving me to design and make content for the whole fucking thing. I lost sleep searching for fucking pictures of cute kitties because these stupid idiots couldn't find a minute of their oh-so important life to make a single commit! And guess what? One of them finally figured out that he won't get graded if he donesn't contribute and had the audacity to make the single most horrifyingly disgusting excuse of an HTML & CSS page I have ever seen. Divs with no closed tags, selectors like 'el1 > el2 > el3'. Classes? Who even uses them, right? I shit you not, seeing that, I was actually on the verge deleting his whole work and telling him a big 'fuck you'. Instead, I just suggested make a few edits and rebuilt his whole page from the ground up.
So that was my team. My gang. A fucking retard that made more work for me and an asshole that didn't even clone the repository. Even then, my project got the most points. But no, it got third place because first and second place worked alone!
Fucking cocksuckers! Working with a team of incompetent fuckwits is ten times harder!
https://shuily.github.io/CatUni/...9 -
Today:
9 am - 2:30 pm - customer mtng
2:45 pm - 3:25 pm - team mtng
3:30 pm - 5 pm - sprint planning mtng
Anyone ever literally be in a meeting the WHOLE day? ... 😢 🔫11 -
How the fuck am I expected to salvage a fucking project that has been handed down to me with.
- No fucking clear architecture
- No fucking documentation
- Fucking shitty ass code base with no fucking coding standards
- The previous team was fucking learning a whole fucking new technology stack *Not fucking kidding* making fucking mistakes left and right
- No code reviews
- Mixing fucking local and cloud enviroment together
- No fucking testing
- Feature that were supposed to be implemented and are not working
- No configuration all the stuff are hard coded
- Full responsiblity for the whole stack
- Only one other guy with me
- And this fucking project has been delayed for a year
- MUCH FUCKING MORE WHERE THAT CAME FROM
Like what the fuck am I expected to do? I took the job thinking that people knew what the fuck they were doing and surprise surprise that was a fucking bust.
the problem is also I am the junior and these fucking people have more experience than me, what the fuck happened to over seeing people's work, PM doesnt give a shit, developers dont give a shit nobody gives a shit.
But when I got this surprise surprise now everyone is interested in finishing the project
BULLSHIT11 -
When you learn your project will be launched Monday in an email sent to the whole company, just before the weekend...
I'm not even kidding. No one on our team was consulted if the app was ready or not.
There was no infrastructure in place to even deploy the app. Everything had to be done in a hurry over the weekend to deploy something half baked, thanks to that idiot project manager who told his boss everything was ready.
Two colleagues ended up doing this work over the weekend, but looking back, if I was the one having to get something deployed over the weekend, I would have just refused and come back to work as usual on Monday and watch that idiot explain why it's not live. -
I'm gonna have a serious talk with my bosses the day after tomorrow. We have so much to do, we are basically at 150% workload. Problem is: they don't pay us for overtime.
This has been going on for 18 years in the company. It will not be easy. But they either start paying our overtime or I am out (and probably taking the whole dev team with me.)
Wish me luck!20 -
PM was on vacation the whole sprint.
this sprint was so much more... convenient. i really liked what i was working on.
Also, team lost some of its bureaucratic discipline along the way.
colleague replacing him, in today's daily: since the sprint is basically almost over, i can really recommend to the whole team to wrap up your work of this sprint, so you have something *done* that you can deliver or show in next week's sprint review.
team: ...
oooohhh boy, let me get a shitload of popcorn for the sprint review when PM is back 🍿🍿🍿🍿🍿🍿🍿🍿2 -
Been assigned to the team by management.
Management and I both know team members are junior/early-medium levels.
Management expects outcome.
After few weeks I clearly communicated that these engineers are unreliable. I can grow and coach them, but outcomes can't be guaranteed.
I was told it's my responsibility to deliver outcome anyway.
I was told they know it's unfair - but if whole team fails, it's on me to fix everything.
And most importantly: of course IT IS NOT MANAGEMENT FAULT OF ASSEMBLING TEAM OF WEAK ENGINEERS.
... placing me there should fix it "somehow"6 -
Thanks to Devrant I've learned about rubber duck debugging. Never heard of it before! It reminds me of a story many moons ago when I worked for a certain multinational company as a business analyst. The company brought in some consultants who basically stole the work my team was already doing on a big project (a horrendous series of spreadsheets linked to data coming from the core systems) and sold it back to the company for an insane amount of money as their idea.
When they launched the new product, the team I was in was asked to test and review it. It took my colleague ten seconds to bring the whole thing to its knees and trigger a corrupt data export back into the core systems. Bearing in mind this external company somehow managed to charge tens of thousands of pounds. So what did my colleague do? Hack the system? Some kind of complicated sabotage? Nope. He typed "FISH" into one of the spreadsheet cells! Thus the FISH test was born.
That day I learned several things: it's easy to break things with a fish; the importance of validating your input; and the satisfaction of showing up the smug bastards who stole your ideas and work.1 -
Post Anger Rant (Beware, Long rant ahead)
So there is this project we have been working for months, most of the devs involved are jr students so I was leading them in the architecture and what to do and they were doing it, the progress was slow but safe and fun.
On the team there was this guy, someone I trusted and in who I had special interest for his skills, so I let him own the github repo.
So the day of the first demo I pull the backend changes ( I had been working on front end ) and I realize that the code was different, so I started using my super awesome forensic skills to find what happened,and when I say different I mean a totally different architecture different database connections, different service pirts, basically other project, so during my criminal investigation I found out this guy I trusted had never really worked with us, from the beginning he went solo working on his own project and changing everything because of some tutorial he found on the internet, so I decided to reset to the previous version just to find out that he had already deployed the code and that a lot of fixes that we should have were only on his version.
So I went and confront him telling him that he did wrong and he had to learn team work and that I was trying to teach them good practices and he waits and asks me "so, my code was wrong?" Seriously what da hell dude? I'm talking about team work and all you can think about is your code.
Finally he admitted his mistake and repented (I think), but seriously how arrogant must you be to ignore a whole team, specially when on your first real project.8 -
A while back our whole team was really frustrated with the marketing department.
In retaliation we made a new branch for our project called marketing-bs, which was used for all of marketing feature requests.
It's the little wins that keep us going.1 -
Today was epic.
I made the first formal demo of the mobile application I have been working on for the past three months, and the whole team of the start-up I work at were all psyched about it. I got compliments from everybody.
Since I am the only tech oriented employee, what I do is pretty obscure to the rest of the company and I was not expecting such reactions and it was awesome. I'm proud of what I achieved, and the undivided validation made me feel like I own the world, even if I have still much learning to do.
6 -
Apple iPhone testing without being on the app store is so annoying, I had to sign up some people to test the app I've been working on and had issues on my end, it really is this whole security bullshit, really it isn't needed.
I couldn't get the team provisional certificate thing to show up because when I clicked the account the team certificate settings would disappear, only after right clicking and hitting help then clicking the team while it was selected could I go to the right window.
I don't see why it's so damn hard to do this crap.
Yet with Android, it's so easy.
I really have issues with the testing for this iPhone app, I went through so many different ways to try and get it to work.
Anyways all done, crashlytics is an awesome testing tool if you can get around that small issue I had.4 -
sprint retros with PM are a fucking farce, it cannot possibly get any more grotesque.
they are held like this:
- in the meeting, PM asks each team member directly what they found good and bad
- only half of the team gives real negative feedback directed towards the PM or the process, because they are intimidated or just not that confrontative
- when they state a bad point, he explains them that their opinion is just wrong or they just need to learn more about the scrum process, in any case he didn't do anything wrong and he is always right
- when people stand up against this behavior, he bullshits his way out, e.g. using platitudes like "it's a learning process for the whole team", switching the topic, or solely repeating what he had just said, acting like everybody agreed on this topic, and then continue talking
- he writes down everything invisible for the team
- after the meeting he mostly remembers sending a mail to the team which "summarizes" the retro. it contains funny points like "good: living the agile approach" (something he must have obviously hallucinated during the meeting)
- for each bad point from team members, he adds a long explanation why this is wrong and he is doing everything right and it's the team's fault
- after that happens the second part of the retro, where colleagues from the team start arguing with him via mail that they don't feel understood or strongly disagree with his summary. of course he can parry all their criticism again, with his perfectly valid arguments, causing even longer debates
- repeated criticism of colleagues about poor retro quality and that we might want to use a retro tool, are also parried by him using arguments such as "obviously you still have to learn a lot about the scrum process, the agile manifesto states 'individuals and interactions over processes and tools', so using a tool won't improve our sprint retros" and "having anonymous feedback violates the principles of scrum"
- when people continue arguing with him, he writes them privately that they are not allowed to criticize or confront him.
i must say, there is one thing that i really like about PM's retro approach:
you get an excellent papertrail about our poor retro quality and how PM tries to enforce his idiocratic PM dictatorship on the team with his manipulative bullshit.
independently from each other, me and my colleague decided to send this papertrail to our boss, and he is veeeery interested.
so shit is hitting the fan, and the fan accelerates. stay tuned シ16 -
I am quitting my job in the next couple of weeks. I don't even have a job lined up. I can't deal with doing Design work as a developer when you have a whole ass design team. Like what the fuck. Then I nearly do development. Oh and your gonna bitch at me when I mess up in design, then threaten to fire me? Well you can shove that shit all up your entire ass. Fuck this Job. I am doing my own thing. I don't care if I become homeless cause Fuck I'll be more happier I did that then be at this concentration camp. I am gonna live my life and own. Cause fuck everything corporate Jobs is fucking life sucking. Please Fire me. I GIVE NO FUCKS ANYMORE. Sick of being depressed and stressed. I want to be a real developer!!!! argghhhhhhhhhhhh9
-
He fails at managing his time and can't finish his tasks in work days ... suggests to work on the weekend and drags the whole team with him.
Sorry mate, but I ain't fucking working on weekend !
Team lead my ass 😡😡9 -
So the story start like this, 6 months ago i left my job in a big company for an oportunitiy to work on a new one without all the bureocracy and shit and with better benefits , the first months were wonderful we were using a nice stack of technologies and the team that was assembled was a nice one with smart and hard working people with a few exceptions, but overall very good. One day out of the blue the manager started to presure us to release a project that was on time and wanted us to make extra hours and work on saturdays, sadly we blindly did because we cared for what we were creating, fast forwarding to yesterday, the whole team was called to a meeting and our contracts were terminated without previous advice because the company could not afford to pay us for more time and blahblahblah..., soo here i'm feeling used and sad but with renowed feelings about starting my own business!!20
-
Literally what I do 80% of the time at work.
I am the only one that:
Knows CSS properly
Knows SCSS
Understands how to set up a proper front end workflow
Etc
Etc
Fucking etc
I AM the css dude at work and I FUCKING HATE working with CSS, at the same time I take it upon myself to push through the projects because my team is shit at it and I would rather work with it than to have someone else do it and then fix their shitcode.
As a whole....i dislike design. Badly.8 -
11:00 AM
Boss: *autistic screaming* Make this module not shit.
Whole team: Alright we'll have a meeting to discuss changes at 6:00PM
5:00 PM
Me: I'mma fiddle just a bit with this module.... *fiddles a lot* *makes it not shit*.... cool, I'll just notify my team I fixed it.
LiterallyAtTheSameTime:00 PM
OtherDudeFromTeam *in my dm-s*: AY YO DUDE I FIXED THE PROBLEM LOL 😂😂😂
Me: iGiveUp.exe5 -
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 -
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 -
My internship is coming to an end and I think my boss is testing my limits.
So, in the beginning of this week, he assigned me a non reproducible bug that has been causing trouble to the whole team for months.
Long story short, when we edit or create a planned order from the backend, once in fifteen, a product is added to the list and "steals" the quantity from another product.
Everyone in the company has experienced this bug several times but we never got to reproduce it consistently.
After spending the whole week analyzing the 9 lines of JS code handling this feature, reading tons of docs and several libraries source code. I finally found a fix by "bruteforce testing" with selenium and exporting screenshots, error logs and snapshots of the html source.
This has been intense but was worth the effort, first, I fix a really annoying bug and second, I learned a lot of things and improved my understanding of Javascript.6 -
It was my internship and I've end up working on a law company specializing on Australian construction laws they're working on a website that will take care of all the paperworks for the contractors. They have a dev team who's working on it but they don't have a web designer. I was accepted for the job as an intern/web designer/tester. I was so happy that I've got a really cool internship as a designer but that's only for a second.
The hell starts on day one. They've told me that they're using agile workflow and that they need to make the website responsive. It was based on bootstrap and gosh their code was so broken. HTML tags overlay on each other, some are unclosed. I've tried to fix the problems and did a great job at that. Made the front page responsive and all laid out. When I went to the next php file it has a different header.php and footer.php and same problems apply and we're not even touching the worst.
They didn't use any version management and they're cowboying everything. Now that the website is on the staging server they use Cpanel text editor to edit the code! My headache started to pileup.
The Australian client asked me to provide icons and fix the colors of the website. Also the typography looks great already. I've fixed almost all the problems and I'm satisfied with the design when suddenly a new co-worker from a famous and expensive college was absorbed by the company. He worked as the marketing specialist who has no experience at web design at all. He told me to do this and that and the whole website changed. He bullied me for my skills in design (I'm an intern) and just took over the whole design. Everyone even the boss listen to him as if everything he say is right. He's skilled at design but not web design. He made the website look like a freakin movie poster.
All my works are for nothing, I got headache for nothing and I've got hated for nothing.
It was the day when I finished my internship. It was a long 3 months. After a month I've heard from my co-interns that the whole dev team was fired including the marketing specialist. Also the whole website is scrapped and has been rebuilt by a single guy who used WordPress which he did in only a month. -
There are 20 of us in the whole team. Each of us are entitled to 1 month of leave/year. Then here's the manager telling us that there should be no overlapping dates of leave vacations. FU!!2
-
I manage a team of engineers.
Toxic Culture Post #2:
Manager: Everybody on your team needs their own swimlane in Jira. Each person's work should be their own lane. When I have a ticket for <Project A> I want to make sure that <Bob> always gets it, all tickets for <Project B> must go to <James>. You'll need to figure out which team member will handle <New Project C> and create their personal swim lane.
Me: That's not really how SCRUM works. Actually, that's not how teamwork works. You're creating silos and we all need to learn how to do these tasks. We're a cross-functional team, and each team member brings their own unique talents to the whole process.
Manager: So you'll create the swimlanes?
Me: No
Manager (to Bob): You'll be devoted to <Project A> from now own. It's the only work I expect you to do. All work for that project will be yours.
Likewise, my manager also reached out to each team member and assigned them specific tasks, furthering the silos.6 -
Our company maneuvered themselves into a classic technical debt situation with a project of a second team of devs.
They then left, signing a maintenance contract and now barely work on the project for exorbitant amounts of money.
Of course management got the idea to hand off the project to the first team, i.e. our team, even though we are not experts in that field and not familiar with the tech stack.
So after some time they have asked for estimates on when we think we are able to implement new features for the project and whom we need to hire to do so. They estimates returned are in the magnitude of years, even with specialists and reality is currently hitting management hard.
Code is undocumented, there are several databases, several frontends and (sometimes) interfaces between these which are all heavily woven into one another. A build is impossible, because only the previous devs had a working setup on their machines, as over time packages were not updated and they just added local changes to keep going. A lot of shit does not conform to any practices, it's just, "ohh yeah, you have to go into that file and delete that line and then in that other file change that hardcoded credential". A core platform is end of life and can be broken completely by one of the many frameworks it uses. In short, all knowledge is stowed away in the head of those devs and the codebase is a technical-debt-ridden pile of garbage.
Frankly I am not even sure whom I am more mad at. Management has fucked up hard. They let people go until "they reached a critical mass" of crucial employees. Only they were at critical mass when they started making the jobs for team 2 unappealing and did not realize that - because how could they, they are not qualified to judge who is crucial.
However the dev team behaved also like shitbags. They managed the whole project for years now and they a) actively excluded other devs from their project even though it was required by management, b) left the codebase in a catastrophic state and mentioned, "well we were always stuffed with work, there was no time for maintenance and documentation".
Hey assholes. You were the managers on that project. Upper management has no qualification to understand technical debt. They kept asking for features and you kept saying yes and hastily slapped them into the codebase, instead of giving proper time estimates which account for code quality, tests, reviews and documentation.
In the end team #2 was treated badly, so I kinda get their side. But up until the management change, which is relatively recent, they had a fantastic management who absolutely had let them take the time to account for quality when delivering features - and yet the code base looks like a river of diarrhea.
Frankly, fuck those guys.
Our management and our PM remain great and the team is amazing. A couple of days a week we are now looking at this horrible mess of a codebase and try to decide of whom to hire in order to help make it any less broken. At least it seems management accepted this reality, because they now have hired personnel qualified to understand technical details and because we did a technical analysis to provide those details.
Let's see how this whole thing goes.1 -
> ticket comes, new feature is requested
> create the new feature from scratch. Code is neatly splitted in files and methods, each with clear responsibilities
> every method is documented, there are clear service layers for the business logic, which resulted in controller having 10 lines of code, give or take
> commit the whole code, everything works
> check the develop branch today, team leader littered business logic in the controllers because "the codebase is a mess anyway"
15 -
asked the team to give us their API docs, they gave us the whole fuckin source code. in a zip file...
im outa here!! 😕3 -
devRant is awesome, but Disney also manages to light-up my day.
This is how Wall-E became a beloved member of our team, and helped me put a smile on my face throughout a very frustrating project.
It all started in a company, not so far far away from here, where management decided to open up development to a wider audience in the organization. Instead of continuing the good-old ping-pong between Business and IT...
'not meeting my expectations' - 'not stated in project requirements'
'stuff's not working - 'business is constantly misusing'
'why are they so difficult' - 'why don't they know what they really want'
'Ping, pong, plok... (business loses point) ping, pong'
... the company aimed to increase collaboration between the 2 worlds, and make development more agile.
The close collaboration on development projects is a journey of falling and getting back up again. Which can be energy draining, but to be honest there is also a lot of positive exposure to our team now.
The relevant part for this story is that de incentive of business teams throughout these projects was mainly to deliver 'something' that 'worked'. Where our team was also very keen on delivering functionality that is stable, scalable, properly documented etc. etc.
We managed to get the fundamentals in place, but because the whole idea was to be more agile or less strict throughout the process, we could not safeguard all best-practices were adhered to during each phase of a project. The ratio Business/IT was simply out of balance to control everything, and the whole idea was to go for a shorter development lifecycle.
One thing for sure, we went a lot faster from design through development to deployment, high-fives followed and everybody was happy (for some time).
Well almost everybody, because we knew our responsibility would not end after the collection of credits at deployment, but that an ongoing cycle of maintenance would follow. As expected, after the celebrations also complaints, new requirements and support requests on bug fixes were incoming.
Not too enthusiastic about constantly patching these projects, I proposed to halt new development and to initiate a proper cleaning of all these projects. With the image in mind of a small enthusiastic fellow, dedicated to clean a garbage-strewn wasteland for humanity, I deemed "Wall-E" a very suited project name. With Wall-E on board, focus for the next period was on completely restructuring these projects to make sure all could be properly maintained for the future.
I knew I was in for some support, so I fetched some cool wall papers to kick-start each day with a fresh set of Wall-E's on my monitors. Subsequently I created a Project Wall-E status report, included Wall-E in team-meetings and before I knew it Wall-E was the most frequently mentioned member of the team. I could not stop to chuckle when mails started to fly on whether "Wall-E completed project A" or if we could discuss "Wall-E's status next report-out". I am really happy we put in the effort with the whole team to properly deploy all functionality. Not only the project became a success, also the idea of associating frustrating activities with a beloved digital buddy landed well in our company. A colleagues already kickstarted 'project Doraemon', which is triggering a lot of fun content. Hope it may give you some inspiration, or at least motivate you to watch Wall-E!
PS: I have been enjoying the posts, valuable learnings and fun experiences for some time now. Decided to also share a bit from my side, here goes my first rant!
3 -
Another case of "devs too stupid to poop" TM.
We had a funny discussion today.
Topic came up that a project using Lucene was incredibly slow.
Then came the yadda yadda of Java bad, Java sucks, Java bla Java blub in the gossip mill.
Both things irritated me, last thing was just the usual "I want to use new stuff cause I wanna be a cool jackass" trouble.
So. Today meeting. We did quick analysis by pair programming.
If I tell you that a whole team managed to review an PR, give it green light...
Despite the PR using the thread safe Lucene IndexWriter in a non-parallel fashion for large bulk inserts?
The whole problem screamed parallelization.
Yeah. If you ignore that scream and implement it in a sequential fashion, it is slow.
Congrats Jimmy, your retard level is off the charts. -
Whatsapp: "How about you update your browser?"
How about you fire your whole fucking team of genetically engineered super-retards, that is making whatsapp shittier with ever recently rotten braincell you guys claim to have, and just let me use your shitty spyware I need to use for the time being. Fucking hell don't you even dare pulling that bullshit excuse on me when my browser is based on chromium Aka the fucking same browser engine that is powering google chrome. Just for once stop playing along with google, take your update and put it where the sun doesn't shine, you data-whoring deadshits.
9 -
When you +1 one of your colleagues rants on devRant and realise the whole senior Dev team is on here. Hmmmm.3
-
Just joined a new team at the organisation as senior dev.
Team lead keeps singing about how we need unit testing and good standards.
I implement domain pattern on the backend supported by unit tests.
It passes QA and then get an earful about the code not being 'restful'. What does that even mean?
Well, it matters not since team lead changes the whole feature in the release branch and all unit tests obviously fails. Builds start to fail.
The solution? Comment out all unit tests. In the sprint retro, we hear the same old adage 'we need 80% code coverage'
Do as i say, not as I do. FML.6 -
I work for a bank and every production release date it's a chaos... Like, for real, devs running to get their stories approved by the testing team and last minute scope changes that, if not made, would make the whole app fail (real shitty management as you can see).
Longstoryshort, a dev didn't finished one of his stories and create 7 major bugs with another... Today that was my breakfast, took me 4 hours and get it all done and approved... We didn't make the release tho, but I scored some major points with this.
Funny thing, tomorrow I'm telling my PM I'll leave the company for a better job, so that will be their breakfast.6 -
My whole team like to develop the backend of a very complicated platform in python because it is fast to develop. And host the front-end under nginx. And run everything on windows. And without unit test.3
-
Worst dev experience was when I was asked to "take a look at" a propriatery Windows app built by a now non-existent team at the company.
The code base resembled the quality of legacy code where about every hour I felt like I needed to vomit. But that wasn't even the worst part for me.
This was the first time I had to develop on Windows and was sent a separate dedicated laptop for this. Now I started to have a bad feeling about this because as far as I had known every single dev at the company used company Macs for development (including me for other projects). It turned out the Windows laptop was indeed configured for a non-dev team :)
Having liased with IT admins for a day I finally got my environment set up and hit install on the dependencies and in 10 minutes it got to less than 10%. The laptop was pretty powerful so I couldn't belive wtf was going on, fans were ramping. Checked task manager and the company Anti-Malware was hogging the whole CPU.
I was so mad that I managed to get the IT admins to completely disable it and then it was only the pain of working with shitty code on Windows which would have been more than enough from the start. Thankfully it only lasted a week. -
When you are trying to be supportive to a colleague but he sees your act as condescension on your part. BITCH I DON'T GIVE A SHIT ABOUT YOU, BUT UNFORTUNATELY I HAVE TO WORK WITH YOU SO PLEASE KNOW THE BARE MINIMUMS TO DO THE TASK. Also he complained to others that he was offended . He was tryna learn react before knowing es6 and nodejs , doesn't know asynchronous and was strongly suggesting that our whole fucking team move to React and I just suggested some topics to look to. I carried his ass once , and seems like now will have to carry it once more :(
-
Yay. I was yet again asked to make a whole module that is meant to compete with stuff companies have made who have funding of millions - without even a designer to help out. I'm the single frontend guy in the team.
"Let's make our website like that super beautiful website we saw that actually paid a designer, UI/UX guy, interaction designer and graphic guy. But let's not hire any of them. Who needs them anyway? Such a waste of money which their high fees"
I guess I'll just take "inspiration" from Pinterest/dribbble/behance1 -
Me: this App is not working ...
... Few minutes later ...
Me: Can someone help me?
Coworker approaches : Are you trying to modify the bundle.js file?
Me: ...
Coworker tells the whole team and they start laughing at me 🤦♂️9 -
So I am the resident Linux Guru and a contract manager asks me who wrote rm. I guessed and said Dennis Ritchie.
"I thought you were the UNIX Guy" he says. He goes on to claim that Robert Morris wrote it and named it rm after his initials. ... In front of the whole team he did this. Ok.
Did some research and even contacted Robert T Morris at MIT ( his son) and he pointed me to a sight with documentation from the initial UNIX research at Bell Labs where his dad did in fact work with Dennis Ritchie and Ken Thompson. Turns out, I was right.
-
The guy I work with was pissed because I asked him the status of his task during the daily meeting.
He doesn't want me to embarrass him because he hasn't finished this task. He said not to push him further as he will do it soon.
Dude, the point of having a daily meeting is to give updates of all pending tasks. it's been one week, you're procrastinating on this task is delaying the progress of my task.
Mind you, this guy has a PhD but he can't even understand a simple project management like this.
Hehehe this whole team is clown world 🤪🤡8 -
What a shitty day.
3h sleep
Lead very pissed bcuz backend don't know specs
Boring meeting where everything is repeated like 6 times
In a few hours boss wants to talk with the whole team
My co-workers jokingly say they want to fire me.
I should be the "hero that will make things better"
Please just kill me instead...
Edit: started working there 3 weeks ago2 -
So, I'm a Jr. Webdev started one year ago to work on a €200mln. retail platform. Our development team consists out of my Sr. dev who designed the whole platform and it's basically his baby. Now he's leaving and it's expected from me to do new developments, support, meetings with managers from all over Europe, roll-outs in new countries, deal with all the issues SAP has, eat their bullshit when they can't upload a .csv file because they are too stupid to check for missing leading zeros. Listen to important their new functions are that they want because 120% of the salespeople needs it. How stupid can this company be to take the financial risk? I'm done.9
-
My latest post about my mother made me finally realize the whole picture.
Five minutes ago, I send her a long message that describes how I feel. This message will be the very last act of communication that will happen between us.
This felt like a bullet coming one inch away from my head. Like SWAT team rescuing me from a predator's basement where I spent the last ten years. Part of me already realized what happened and is serene, part of me still can't get used to an idea that this was, in fact, the end, and no further harm will be done.
My future is bright. It's so nice to feel that she doesn't know where I live.2 -
I spent two days in a row fixing chairs at work because our whole dev team was waiting for issues (which means helping QA team and playtesters testing the whole game).
Just when everyone left and Im standing up to go as well a playtester comes up with a release breaking bug in the handwriting recognition code...
Since this game is build for a charity which will release it in a country at war we cant push the release date.
Guess who is making overtime trying to fix this bug?3 -
I suggested the other day that devs should not go to every meeting, actually I suggested they should be "sitting with headphones undisturbed" , everyone looked at me like this was absurd.
I wasn't running away from meetings because I suggested I should go to meetings to get requirements and such, instead of the whole team...
Am I missing something?7 -
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
-
At the first company I worked for out of college, the CEO was a bit like a child. Whenever he came up with a new feature he wanted to add to the product, it had to be done asap otherwise we were going to "miss the boat." Every single time.
So rewind to a few years ago. It's a normal day at work and then suddenly my team lead and the CEO call my team into the conference room. The CEO starts telling us about this industry conference (we were in online dating) that was happening and this flashy new company dating company was going to be showing off this awesome search feature.
Naturally, our CEO concocted a Hail Mary plan of how our company was going to upstage this company and get all of the press to write about us instead. Basically, the "plan" was for us to build a brand new search feature of our own, in the week before the conference, and then he stated that the press would "have to write about us because ours will be better."
Everyone on my team knew it was ridiculous but we were pretty young and naive so we busted our asses to get this search feature out the door in the short week. The Friday before we stayed until like 2 AM. It was a little bit fun because the people on my team were cool, but the whole situation was absurd and no one, except the CEO, thought this had any chance of working.
Annnnddd in the end we didn't get an ounce of press, the search feature was pulled from our site, and the "awesome" company that we were so worried about getting all the press is out of business. But hey, we did get it done!1 -
It was the first time I worked on a big project with a big team, I looked at the given code and copied their code style.
I finished very fast and everything was working fine, was really proud of myself. I'd like to add some logging though.
Programm failed it was heavily async and parallel so 2 days of debugging had past the whole team was on board nobody knew what went wrong there.
As I stared into the darkness of my code I suddenly saw what went wrong 😂
As I adopted no curly braces style of the Team for
If (condition)
Justine();
And I added logging above without braces everything broke 😂 it was indented properly so as a heavily python user everything looked fine2 -
After going through the painstaking process of getting automation scripts reviewed by the whole team, edits, commits, reverts and finally loosing sanity
and you see the team is still using the old automation scripts in testing.
(╯°□°)╯︵ ┻━┻4 -
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
-
Please tell me something wrong with me, and whole world is working like that! It can't be right! Or could it, and I'm just one sad fuck who don't know shit?
So... We've got:
1. Jira reporting (agile style with cards and shit)
2. Task timers (via application integrated to Jira in order to count how much time we spent on a task)
3. End of the day email reporting with description of what we have done today (Jira is not enough?)
4. Daily morning meetings with a team leader to report what we're gonna do today
5. Git merge code reviews for each finished component (that lasts for hours)
6. Weekly status meetings
7. Working hours reporting with a fucking fingerprint
And on top of all of that, the developer is the one who just writes the code - team leader decides how this code is gonna look, what will be written first and what last, what libraries will be used and so on...8 -
Fuck you google android IME team and fuck their open source policy..
So recently i had a chance to work with AOSP LatinIME code, basically our Android keyboard was forked from very old code base of LatinIME and my job was to change its base version to latest Version available on AOSP repository. Downloaded latest Android 8 codebase. Did 2 weeks of deep investigation of what improvements we will get from upgraded code base.
And I came to know that those Google fucking cunt sucking dick heads deprecated that project and broke the whole thing to a pice of shit. Half of the code is broken with fucked up todo stuff and motherfucking missing method implementation with not implemented warnings. What those motherfucker did is that they abandoned the open-source project after they released Google GBoard, and fucked the stable code by adding quard gram support and dictionary download with multi account features which was never completed by those motherfuckers..
Those misguiding donkey shit fuckers kept a depreciated project in AOSP build tree which has not received a single fucking commit from shitty ass Google IME team, is said to be reference model of Android IME implementation..
What kind of fucking shit is going with open-source code in name of making competition high with thirt party Android keyboard developers ..
Fucking shit fucking ime team .. fuck you .. wasted my fucking time reading your shitty code base .. Fucking shit1 -
The whole point of having a daily scrum is to let your team know about the progress you've made from last day and what you'd be needing to stick to the sprint plan.
So ideally everyone has 30-60 seconds to give a gist of their activities. And a small scrum team would be productive because everybody is on the same page.
Our scrum meetings usually wait for all of us to assemble with our coffees and donuts, sit down, joke, and then agonizingly go over everybody's existential crisis as a developer because of the task they've been assigned to has too many dependencies. And this happens every single fucking day! These "scrum" meetings tend to go for 1 hour. FML!5 -
PM sends email to development team with the whole management team in cc.
"Guys, the data is not updating correctly! Make sure all the updates are being done! If we can't get this right then we can just forget about this whole thing!"
Me: Yes, because making generalized statements and inflammatory remarks actually help in correcting the problems... -
Okay, I'm interning at a government institution & boy let me just tell you... mmmh... A FUCKING MESS!
So I'm tasked with developing a HR system that the whole company should eventually use. I tell them I'm not familiar with the open source technologies they'd like me to use, they tell me no worries, you can develop a prototype with a tech stack that you're familiar with. Also, they tell me that they don't quite have the requirements from HR so what I can do for my prototype is just develop something "general" that works according to their "idea".
Being the good intern I am, I develop quite a good functioning prototype & present it to the team who then present it to the managers.
Finally we're all called in for a final meeting with the managers & HR, and guess what? The requirements for the system are different. Almost 90% of the features we built into the prototype need to change. Also, the system must use open source technologies. The managers promise to send a detailed requirements specification document, with sample data. I think this is a great idea as there's still a lot I don't understand. I expected this to happen, so I soon start to redesign afresh, this time trying as hard as possible to consider open source technologies within my plans.
But noooo... My team wants me to "finish" the system!
"Finish" what system, I ask? That was a prototype!
"Just tweak the functionality you built to meet the new requirements".
WTF!
We don't even have the actual requirements specification document, so I'll still be coding blindly. Also, the whole system needs to be re-built using open source technology!
Instead of pushing me to develop a system blindly, with no requirements, how about you push HR to tell you exactly what they need and how it should work first!?
I'm honestly exhausted with the false sense of urgency from my team!!8 -
!rant
My love for Clojure is so deep that I have invested the whole company. Over the past months just everyone came up to me and asked me, if I may teach them some Clojure programming. With everyone I mean literally everyone working in this company - fellow programmers, the ladies from HR, the Sales Team and even the CEO.
So today I gave a two hour introduction to the whole team on how to Clojure (in absolute basic terms).
The team has just voted that we will do that every friday starting next week for the rest of the year.
If you have passion, show it.9 -
So apparently the CIO knows all about my team lead sucking it up as a boss, and is letting him do it. He's constantly on the team leads ass about stuff and it's stressing him out.
The CIO wants him to stop being so micro managey and let the team handle things... But instead of telling the team lead that, he'd rather just blast him constantly and stress him out which makes it roll onto us and stress the whole team out.
I wish the CIO would just tell him to square up or just fire him... This stress isn't good for anyone. -
remember when our whole dev team was drunk but we went back to work anyway? turns out, someone rm -rf a whole folder of js scripts!! it took us some time before we could find the back up files which were in the old server (that crashed) because recently we changed servers (so we were transferring files) and we are now using amazon.
our boss got so pissed this morning but oh well, it was his idea to drink and feast in the first place!7 -
When your new team-members don't commit their code end of day Friday and you end up working the whole holiday weekend to fix their shitty work while they're away for the week....
Joys of being a team-lead..1 -
Sometimes it's better to burn a bridge so you don't even think about crossing it in the future.
See, I left a company some years ago because I didn't see my future in it and all management combined had a collective intelligence of a chicken.
However, I got a call from them a couple of months ago asking me if I could return. The salary was double and the working arrangement seemed fine. On paper. WFH. Flexibile hours...
Since I actually liked the project itself for its technical challenge, I accepted the return offer. What a bad idea that was.
Of course, the things that made me leave for the first time had only gotten worse. Bad leadership, idiot developers in team leader positions. Tech debt higher than Mount Everest. Bad infra that makes you want to off yourself every time you work on it. The whole circus.
Seriously, the "senior" team leader will happily merge code that includes assert(true == true), but hold up a well written MR because he has a personal vendetta with the developer.
Personally, I always check him whenever he starts being an ass. But the poor juniors are in hell. They're terrified.
Now I'm leaving again, but this time I've made sure I can't come back.3 -
So we were supposed to have another good build today.
Supposed to.
This one guy on our team gets weird sometimes, and refuses to commit his shit until the last minute. He says "Don't worry, I'll handle all the merging, it'll be fine!"
What he forgets is that much of our code relies on his! His latest commits reworked a couple entry points and a class definition. No backwards compatibility.
He made his commit, and nearly our whole stack shit the bed. Jesus jumping Christ. Weekend? Nope.2 -
Microsoft engineer walks into my room. we need to join your laptop to the domain, as part of the migration and upgrade company policy. so I give the guy my laptop. The guy has an agonizing look on his face! He goes. This is linux! Mind you all this time am nodding and bouncing on my chair. The guy bolts from my room, as if he was going to report direct to Bill Gates. Apparently the dev team was left out in the whole migration plan!5
-
New here, don't know the format, etc
Let me describe my Friday:
8:45 standup
By 9:30 I'm done following up with 3rd party platform vendor's jira, and curiously look into an issue related to app camera not working in development build (we aren't in production), fix it in 5 minutes and talk to the team of two other devs. Tell them I've submitted a fix, and QA is unblocked.
"Senior" software dev starts complaining about how "I've wasted my whole morning" because "I mean, come on" and is generally offended because "I've done their work."
After a real puzzling argument, I worked from home the rest of the day.
Where did I go wrong?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
-
*Outsourcing DevOps Company*
> HR got a call from a customer
> Got my contract terminated immediately
> HR and my boss trying to explain to me about the situation
> The customer is one of BIG GIANT conglomerate in my country and high expectations AF
> My boss wants me in the team
> HR denied due to headcount and limited budget from investors
> CEO pay me for the whole 2 months in salary in compensation including unused vacation under the national labour law right away after signing an acknowledge form
> HR told me if I go to the new company, don't forget to tell them about referring
This all happens under 30 minutes after a normal working friday
What a shock
PS. It's a nice DevOps outsourcing company in both working culture and technical TBH6 -
Since it's 42 & I am fond of the number..
The 'most fun' I had was making a completely useless feature for our customers that we (our team) knew will be useless (&wrong) once finished and we will have to rewrite it. But we had to do it nevertheless till the end of the week, since the customer is the king. It turned out hilarious and fun because everyone was making jokes on the floor about what idiotic stuff we code and implement. Even the boss was like: yes, yes, I know but please do it, you can rewrite it later to not do anything, just leave the button on gui. It was crazy it was fun, a little bit of mindless coding to lighten up the atmosphere and it (coding & jokes) brought closer the whole colective reaponsible for that particular customer. -
Developing a notification API, sends emails to subscribers, email API can take only 100 IDs at once, so partitioned the email list and send mails in blocks of 100.
Forgot to reset the list after every block, so each new partition got appended to the existing list and kept going on.
Ran it against a test DB, which was recently refreshed with near-prod data !!! Thousands of emails went out of the app server in one shot and everybody receiving numerous duplicate emails. Especially the ones in the very first partition.
Got an incident raised by the CEO himself reg the flurry of emails. But, things were out of our hands, quite literally. All emails are queued up in the exchange server.
Called up the exchange server team, purged the queued emails. No other emails were sent/received during this whole episode.
Thanks to Iterables.partition in the present day.3 -
!rant
MASSIVE UPGRADE ROUND 2:
We took it by steps, the DBA did his portion and I did mine, we had waited for the entire thing to be finalized today on Sunday since our users are probably jerking off to their waifus (as they should) and today was my part. MA BOE the DBA was with me the entire time and the whole process took us about 4 hours of both of us getting multiple heart attacks here and there and praying to the elder gods of Asgard for their devine protection as we venture into the calamity of fire and juten ass mfkers that are our fucking servers for this particular process.
Man I really hope for the pandemic to be over and take my dude out for a nice beer, some wings and some relaxation time.
Best DB/Dev team I have ever been with.7 -
Scrum CSM course: it's good to accept that we can't be perfect.
Also CSM course (1): if it's not followed perfectly it's not scrum
Also CSM course (2): scrum won't work in your team unless the whole organization adopts it
CSM course provider after cert: $1k CSM cert isn't enough to practice Scrum responsibly12 -
What is it with inabhorrent arrogance plastered all over IT as a whole?
I get younger, inexperienced people telling me I'm wrong constantly, criticising my work despite them having no clue (visible from their own work standard and TTL of their projects) .
Similar from older generation, who are resistant to change and aren't even part of my team telling me I'm doing my job badly.4 -
I don't know how managers are planning deadlines and counting December as a full working month!
Most companies that I worked with, count either half a month or push the deadline until the end of January when the workforce is back but not here.
Our division manager has promised the customer that the production environment will be ready on the first week of January, without even consulting the team or checking the schedule like WTF!
The person responsible for setting the infrastructure was on vacation for 2 weeks and he didn't hand over the access to production or share the progress done.
Fast forward, the manager went to slack and pinged the whole company with full caps message that the production should be done today.
Fun times :/7 -
I feel really bad for the guy I'm currently working with. I have until roughly the end of August to upskill him in every aspect of 3 different iOS apps because once I move to a new project he will be the entire maintenance team for those apps. Feel like he is getting shafted so badly. The whole process has been poorly managed. The managers don't care how well I train him as long as it doesn't take too many man-days. And they are expecting that they can still pull me back in to help if he gets stuck even after I've moved. Starting to feel like I'm being taken for granted. Can't wait to get off this horrible project.
-
"Yes, the work could have finished way earlier. But it's easy, and I would have probably been bored of it and left earlier"
Finally got the reason why our fucking CTO couldn't create a fucking stable Backend for almost a year while the frontend team got all the slack because certain things are still not functioning well and while the marketing team every fucking time got their face red while showing the demo because the fucking api is not stable. Seriously, we wasted a whole year just because you could write something more interesting and enjoyable. Fuck you. Never been this willing to murder someone.
Context: A simple booking platform. No need for creating a complex distributed system while our userbase may not even be in million even on a peak season.
And he laughily commented maintaining it would be a headache.
I could seriously kill someone right now.2 -
Fire your whole fucking web team Bethesda
* Your design is a classic ipecac. Whatever the fuck you are doing doesn't in frontend doesn't justify the 4Mb of bandwidth I wasted on a single js file. Why the fuck can I see the whole fucking node_modules directory when looking at the sources?
I know this is supposed to be a webpage for a game development studio, but I'm seriously wondering if your budget would even get me a prostitute.
I'm a greedy fuck and want a free game. apparently your servers are only good enough to register me, but login is apparently too much to ask for. Yeah sure. Oh and also thank you for choosing an "incorrect username and password" error message by default, even though your fucking gateway timed out. Please be kind enough and punch me directly into my face next time. Not like I'll ever access that shit ever again3 -
Me and my friend were having a coffee in a coffee shop and then she told me the story of how she got fired.
So back then storing data on cloud was not that convenient and employees in her company used to carry softwares and other stuff in pendrives.
This one day after completing a MAJOR project for a very irritating client, my friend and her team decided to take the day off and celebrate this victory in a pub.
She got drunk and then came the call of her boss saying that they needed to showcase the software right then to the client.
Being always responsible and committed to her work my friend had decided to keep a backup in her pendrive which she kept in her breast pocket of her shirt.
So she goes into the washroom to freshen up, bends down near the toilet to vomit out liquor and lo!
The pendrive slid all the way down from her pocket into the toilet sink.
She didn't notice and flushed and down went the whole project into the sewer.
Moral - life fucks you in ridiculous ways.
Ps. She left her laptop at her home which was very far from her office and the pub. The team had to go to her home first to retain the project and eventually got seriously late. Boss didn't like it as the client was a real pain in the ass and this was a big project too and being the team lead my friend was supposed to deliver as expected.
She got fired.1 -
some genius modafaka thought REPLACING python3.6 by 3.7 in all the dev machines is gonna be fine... the whole team is going nuts... fuck you IT... who gave you the permission5
-
I just found out last Friday that my team collegues (all of them are team leads) are suffering from depression or the so called burn out syndrom. I guess it's my boss' fault. He never gives clear jobs, changes his mind from day to day, we have to manage unclear responsibilities and the baddest thing is that we think that our boss is too stressed out himself.
Do you have any advice for me how we as team could solve that besides changing employer? One thing to mention is, that my boss likes to hear himself talking. That makes it even harder for a guy like myself who is more or less introverted to come up with good arguments which are not overheard or overtalked immediately. What are your feedback strategies to your own boss, how do you bring such stuff on the table?
I fear that when nothing happens, my company will suffer very hard when the whole product engineering departement will fall apart (¼ of the whole company and is responsible for engineering and maintaining of internal services and managed services for our customers).
Well at least it was worth writing about it, maybe my subconcious mind will come up with a brilliant idea itself in the near future in some asynchronous way. But you might be the one with that valuable input, then don't hesitate to share, it will be welcome.4 -
Have you ever argue with a developer who:
+ have the same level as you
+ on the same position in the company
+ in the same team
+ OLDER than you
+ thinks their code is the best
A few years back, a coworker and I argue about how to implement a feature. I proposed an approach. He proposed a different one. I immediately saw some problems and told him. But hell no, he defended his idea so strongly that I just gave up since I will leave the company soon.
2 weeks later, when the sprint was about to end, the whole team had to work overtime to fix the mess because of his terrible approach.7 -
I'M A SENIOR DEVELOPER NOT A BUSINESS ANALYST...
IF YOU GIVE ME SOME CRAPPY LEGACY CODE THAT SOMEONE RANDOMLY DECIDED TO USE, THE ONLY WAY I CAN UNDERSTAND IT IS BY RUNNING IT AND REVERSE ENGINEERING THE "BUSINESS LOGIC".
ADD THAT WITH BAD INPUTS... THE ONLY THING YOUR DOING IS WASTING MY TIME..
JUST BURN THE WHOLE THING AND GIVE ME THE REQUIREMENTS OF WHAT YOU ACTUALLY WANT....
It feels like I've been fucking a pig all week...
Oh and now my team agrees and will look to get the actual requirements from the business...
This feels like a hallow victory.... As that was the first thing I told them to do.... -
Company is celebrating new awards. Whole dev team basically says fuck you we have better things todo and isn’t attending for champagne.
-
The guy thinks I'm her friend but I deeply hate her !
Just because she thinks she knows everything but she is actually an idiot !
Last term I was in her team for the c++ project (she fooled me ! I thought she is advenced !!) And guess what?
I ended up doing the whole project myself ! (Not fair at all but she got the score cuz of me)
I really don't need enemy so I'll just stay away from her :/4 -
As a person from low-paying country, how do I reconcile with the fact that for the same work, and the same 8 hours, I get 1/3 of what a person in Germany does? In my previous team (same company), one of my teammates was from Germany. The same team, the same work, but he happened to earn a lot more.
This bothers me a lot sometimes. I have seen people requesting to be transferred to another country, and being denied, presumably because of the salary difference. Then, the person leaves, and someone in Australia gets hired. So, rather than moving a veteran person of whom you know fits your company culture to a higher-paying country, you let him go and hire a newbie in an equally-expensive country? What the fuckity fuck?
And to my friends from high-paying countries, especially managers: you don't have to feel bad, but have some common decency. If you come to my country, do not say "oh gosh, everything here is so cheap," or "the dinner for the whole team costs less than buying my family of four a dinner back home." That's offensive as fuck. If that's the case, fucking give me a raise you cheap fuck!30 -
Spent 2 days refactoring code written by our "offshore team". I've done refactoring on the same code in the past, probably upto about a week in total of refactoring now. The code looked like it was written by someone who had literally just finished their first "Hello World" app - loads of code blocks copied and pasted instead of declaring reusable functions.
The whole thing should have been done by us in the first place.
And yet our money-conscious company wants to employ more of these developers. Cheaper than us? Sure. Quantity over quality though, but I guess money is all that matters to the big cheese1 -
I joined 3 months into a project that was expected to be done in 6.
As the day passed I learned about the scope a little more, 30 days in I decided to step aside, I slowly learned that they wanted a whole bank built from scratch.
User support ticketing systems, the banking core and an app like "revolut", everything with a team of 4.
To this day I have not seen them launch, and it's been over 5 years. -
my job went from being a programmer ==> technical support girl for the whole company D:
its kinda annoying because its mostly about amazon ec2 instances and i have to chat with the support team from amazon when something goes wrong while following the steps (that the others could have followed instead of going to directly to me to make me do it)
now i have to try and fix all the problems occuring in the servers :((6 -
Worst Hackathon experience:
Taking an API built by a junior dev team with minimal specs and "hacking for two pointless days" to make it work in production...
The whole Hackathon idea was an experiment to see if they could make the dev team stay late if they bought pizza and said "have fun".
We all spent 2 days cursing at the shoddy tools and lamenting that you can't run a Hackathon with a single directive and "production ready goal" yet remove any choice the developers have to actually contribute.1 -
!Rant But this is hilarious 😂
Appraisal interview of Gayle:
Gayle:- Sir, I scored 211 Runs in 118 Balls. I made the team win the crucial match. I should get “A” rating.
Management:- You hit 17 Sixes and 23 Fours. Though, that is good but that is not something new you have done. That is why we hired you. As this is not something new, I will mark it as “Innovation Lacking”.
Gayle:- But sir, I played according to the situation. I took 21 singles as well.
Management:- Exactly, your performance is not consistent. You played 15 Dot Balls as well. This means, you failed to optimize the resources.
Gayle:- But…
Management:- Also, I would like to mention that you are not a team player. The whole team scored 112 and you all alone made 211.
Gayle:- What??
Management:- Yes. So, overall, you are getting a “C” rating for the year. Improve Consistency, Innovation, Utilization and Team Work...1 -
We rewrote the whole thing, except for iFraming some old pages in. We had to, the system was fucking awful and couldn't cope with any of the new mission critical requirements.
Client didn't understand the scope. Our project leader somehow snuck it in and we worked on it for months. We were sure we'd be kicked off the whole project... Somehow things didn't crash and burn. How it didn't blow up defies rational thought and the laws of physics. The new system worked, the client was happy, and boss made a lot of money.
Lead dev worked weekends for what feels like an eternity, it really was his baby and no one else on our company could have done it. It's where I finally learned how to do things the proper way; DDD, unit testing and TDD, architecture, building strong components in front-end, you name it. Before that I had a great nose for code smells and how not to do stuff, but now I got to see a proper system for the first time. It was glorious.
Then lead dev left and the system degraded quite a bit because new team didn't keep to the architectural patterns or general best practices. But we had a good run.1 -
TLDR: There's some days where the Gods of IT are not with you. Just lost a whole day of work.
So this morning, we (me and my team) big performance issues with our web app. Lot's of requests time out, big latency, etc
Try to ssh to VPS, latency of 10 seconds between user input and output.
Usual checks: RAM ok, Proc ok, hard drive ok, reboot server (20 minutes), update/upgrade
We decide to call OVH. After 15 minutes call, we try to reboot in rescue mode. Reboot fails at 60% + everything freezes.
After an hour, OVH opens an incident ticket on +200 vps instances (including mine) everything is down during +1h
Finally everything is okay ! Even had time to migrate my new database schema.
Still, quick heavy on the mind but feels good to go home with everything working out correctly
-
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 -
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
-
Team member knows x better than me?
No fucking way am I gonna ask them to do it. Even if I have to learn the whole damn thingamajig from scratch. Coffee and some Halo OST are all I need, baby!
(In fairness to myself, said teammate is a bit of a hijacker when it comes to helping...)4 -
Am I crazy ?
Right now we have an API which returns a full planning for a week for 300 employees with indicators (Like "late", "may be postponed" etc) in 4 seconds.
I have a pressure, people telling me it's not fast enough.
I honestly think it is fast.
In order of data it'a around 100 MB of JSON. AND you can do actions on the whole set if needed.
Long story short, I think 4 seconds to get all that data is pretty great. Customers think they should have it instantly.
(Never mind the whole filtering system at thier disposal, they literall only lod the full set and then MANUALLY scroll (Yes there is a quick search box)).
What can I do more ????? cache that ? I can. But they also expect that any changed value is reflected.
And we fucking do it. While you are on the page there is a SignalR conenxion created and notified when any of data is changed and updates it on front. Takes around 500 ms.
Apprently "too slow".
I honestly don't see what we can do more with our small 4 dev team.
Give me 56 developpers I can do something, but right now I'm proud of result.14 -
Currently a lower manager (I lead a team but I report to a handful of uppers). In my line of work the holiday season means more work instead of vacation. My team consists of 4 other guys, 2 of which aren't worth their weight in shit, 1 guy who's leaving for the military soon, and 1 guy who's just okay. The first 2 are about to be fired for any number of reasons, and there's no plans to hire anyone else. The lady in charge of hiring is incompetent; should've been hiring anyways for the past several months and hasn't (not due to a lack of applicants either).
I consider myself the hardest worker of the team, and one of the best in the whole place. Well, instead of being rewarded with even so much as a peptalk, my superiors have seen fit to tell me that I'm not doing enough. Like holy shit really? Are they taking credit for my work or are they just retarded? Track record at this place isn't all that great to begin with. I'm not in a position to leave as I need the money to put myself through college, but I'm thinking about hopping on the minimum effort squad at this point.4 -
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 remember a certain prank that amuses me till today....
Just add some devices to monitoring and the notification queue of the build chain / ... ...and wait patiently.
I still cry tears remembering an manager screaming what the hell "the poop train clogged the drain" means and why this is a critical system failure.
(Notice: next time check the mailing aliases of mailing aliases)
Although I can only recommend this if you know your team well. In my case we had a whole lot of fun after I got my head chewed off. XD (got an earful, but in the end he laughed his ass off)1 -
I'm the lead dev on this team. The project is split into multiple separate modules to comply with separation of concerns, and so new devs don't need the whole fucking codebase (risking them running away with everything) to contribute to the project as a whole.
So we don't need a fucking config file to enable and disable features.
So we don't need to upload a 500mb monolith every time we want to test a change.
So we can test old fucking versions of modules without merging it back into the entire codebase.
What did this fucking dev do? He was having one small issue with Maven. One. It wasn't updating his local snapshots to the correct Artifactory version.
He decided, instead of trying to fucking fix it: HEY, LETS IGNORE THE LEAD DEV'S DEMAND TO KEEP THEM SEPARATE. IM GOING TO MERGE THEM INTO ONE MODULE FOR SOME FUCKING REASON.
I refuse to continue working with this dev if he's going to sidestep my demands and undermine my authority. He wants to go it alone? Be my fucking guest. I'm not touching his shitty single-codebase monolithic monstrosity.
If this is going to be a regular fucking occurrence, he can eat a dick and choke on it.2 -
Next weeks rant theme should be worst dev day.
Any how today I fucked up at a whole new level. First ran a script thinking I am deleting my local dev environment.
*An Eternity later*
Fuuuuuuuuuuuuuuckkkkkkk
That dreaded script ran on main dev server and fucked up the server used by a team of 15+ teammates. Dead.2 -
Why do CEOs and higher ups always think development is just some easy quick thing you can spit out in a week? {
"I need a web app that can do X and I want to sell it to make more money!"
} or {
"I want something that can automate this thing here and then I can re-sell it!"
}
Usually, the project is something that already exists and has taken a whole team years to iron out and perfect and to compete with it would be insane or it exists and it's actually FOSS. We're a small MSP, we don't have the resources to make big ticket SELLABLE software.6 -
So today I accidentally updated more than 3000 records in a table and wasn’t using transactions so I couldn’t Rollback, LOL had the whole team freak out this Monday morning and we had to pull a backup6
-
When you're pitching to a whole team of clients at a resteraunt, and you find out a minute in that their WiFi is terrible. Pages that take less than a second to load take 30 seconds. Talk about first impressions. ....2
-
I am surrounded by incompetent fucking idiots, from the team lead that does a half arsed job at coding and then wonders why nothing further down the chain works to whole component teams that seem to be lagging so far behind they don't even know what the current code base looks like.
And who's in the middle of it all running around fixing all the problems these fucktards create, why yes it's me.
I would leave to let it implode and see what they'd do but I already know, they'd leave it till I got back so I could fix it all for them.
Feel like going around with a rolled up news paper and whacking each of them on the back of the head while screaming "no, bad code monkey, bad, fix your own bugs"
I hate being the go to fix it guy sometimes.1 -
[tl;dr at the bottom]
(Project Team Group Chat)
dev: @Desing team, i have a question, there's a required field missing in you design, can i go to your desktop to get an quick answer/explanation about that?
design team:....
dev: hello..?
PM: [writes a huge text to tell me that i can not interrupt them even if its a blocker and that we (dev team) shoul write them down and tell them only once a day in the scrum meeting]
dev: uuumm ok
-next day-
dev: so about that field, why did you...
Client: WHAT? There's a problem with the design!? oh boy, lets re-check every view right now with the whole team!
(it took like 2 hours, the field was missing just because they forgot that feature)
PM: okay, @DesingTeam, answer any questions from developers when they ask you...
tl;dr
we spent almost two hours with the client just because desing team didn't want to answer me a little question -
We are 3-4 days away from deployment to production. We are still bug fixing. But one coworkers decided this is the time to make a fuss about the way everything is set up. He doesn't like the dev database. So he knocks it over.. and while so doing it, he doesn't inform the team. And when I ask if something else is gonna knock over? No answer! (And something broke down too..)
Now we have issues to test our bugfixes. The whole thing took me half a day finding out and made me distracted with frustration, and not just for me. Most bugs could've been done in that half a day!
I so wanna punch the guy xD but no, I gotta save face, pfff!2 -
I spent the whole day documenting a framework I recently built for my team so they would know how to use it.5
-
In january this year i convinced my whole team to switch from Skype to Stride. And now Stride announced that they are teaming up with Slack... I am going to look like complete idiot because we have to switch once again ... 😥5
-
Would I be going too far out of my role as a developer if I write a coding standards/development practices/procedures guideline for the whole team dictating a set of rules everyone needs to follow? Basically telling people how they should be doing everything.
I'm senior developer but not the only one and also the youngest. No one has to follow it but I would plan to present it to my boss and his boss. I feel like I would come across (if not already) like "I'm better/more experienced than all of you, so you should do what I say because the way things are now isn't working and will only get worse".5 -
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 -
Why do game studios force social/multiplayer in single player games?
Single player sandbox? How about we make it a multiplayer co-op?
Just fine 1 on 1 brawl? Hey how about you find a team and tag team? No? Too bad fuck you, no points to you for a whole fucking season.
Ugh.15 -
Optimization issue pops out with one of our queries.
> Team leader: You need to do this and that, it's a thing you know NOTHING about but don't worry, the DBA already performed all the preliminary analysis, it's tested and it should work. Just change these 2 lines of code and we're good to go
> ffwd 2 days, ticket gets sent back, it's not working
> Team leader: YOU WERE SUPPOSED TO TEST IT YOUR CHANGE IS NOT WORKING
> IHateForALiving: try it on our production machine and you'll see the exact same error, it's been there for years
> Team leader: BUT YOU WERE SUPPOSED TO TEST IT
Just so we're clear, when I perform a change in the code, I test the changes I made. I don't know in which universe I should be held accountable for tards breaking features 10 years ago, but you can't seriously expect me to test the whole fucking software from scratch every time I add an index to the db.1 -
I work remotely from the rest of my team and I just came back from a 1 week vacation. Logged in this morning and no one else was online...
My first thought was WTF happened... did something blow up do bad they all gelot fired???
Turns out today is a holiday for them. So now I've a whole day of peace and quiet to figure out what the hell in supposed to be doing again. -
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! -
I want to fuck the whole Skype team until death for blocking my contacts and won't let me to make any call with my father and my family member. FUCK YOU SKYPE.
Happy new year to all devRanters !2 -
So we have this team bonding and feedback session every monday, where everyone in the team needs to say what they appreciate of their team member and what they wish the team member would change... The whole thing takes about 2 hours.
Honestly, feel like a corporate BS, what feedback do you want? Just do your job and I am happy with it... Well I guess that's part of the corporate world, instead of just doing your job, it is about how big your "influence" is in the company and how many people like you4 -
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 -
We had this team project to do in my second year at university. In C btw. My team consisted from 3 members. We had about a month or so to finish it. So of course we started 2 weeks before the submission. Well... I started. Those two didn't give damm about it at first but after I pushed them to do something one of them tried to code this simple function. It was supposed to check if the opptions from command line could be combined. His fuction had around !!200!! lines of code 😲 but he swear it was working. I was skeptic so i tested it. waaaaaait for it... it didn't work... the very first combination I tried that should not be accepted passed his awesome test 😱 I gave him another two chances. Result was the same.
I was furious. I had my part to do with little time to test someone else's code... So I desided to code the whole project on my own. Then I told my "coworkers" that they either pay me for it or they will be without any point for this project. I earned 80 € that day 😀😎
Btw my test function for those opptions had less than 10 lines 😁 -
I always write a Google Doc before I start developing a feature to help me think what and how should I implement it and so I can share it with the team.
It is possibly the most frustrating process of the whole development cycle because Word and Google Docs still manage to make it a fuckin ordeal to insert a simple image without bombing the whole text to hell. How is it that after almost 30 years of history it is still shit to write a document?8 -
So I go on a 10day holiday and when I come back I realise the scrum master commited a whole bunch of messy code straight to develop and didn’t even bother to run lint or build or test or anything. WHYYYYY??? Everything worked before that. Why is a scrum master who doesn’t have experience in front end allowed to touch my code and commit directly to master?
I know why. Because the whole team does it all the time and they just keep breaking and fixing things over one another and all commit directly to master.
Kill me pleaseeeeeee 😭😭😭5 -
My team lead at my summer internship hailed from an MFC background.
I was able to dictate a whole block of jQuery code to her orally while I was in a hurry to go for lunch, and she typed it in. And it ran perfectly in the first time itself.
jQuery isn't a great deal, but it was a confidence booster for a guy who had only worked with JS for a week. -
I swear the God I'm considering getting a rabied dog just to bite your balls off in case I ever see you in the streets..
- guys X are running load tests on env A
- load tests complete
- analysis of test results is being done
- slow response times are obsered
- someone asks whether X guys took a thread dump for further analysis
- a guy from team X (Mr. Xx) replies: "Will take the Thread Dump now."
- 10 minutes later uploads the whole fucking 2GB log file to Slack
- Xx replies: "I do not see anything wrong in the dump"
A fucking retard... Shove that useless dump up your ass and THEN tell me there's nothing wrong with it! Why the FUCK do you think that's the case? Moron1 -
when the client's consultant try to micro manage the project and create panic on the whole team... fml2
-
Today I got paid 75 bucks for the last four weeks of full-time work at an internship but was expecting 1500. Turns out 1500 was an yearly stipend. Haven't been learning much coding in the past 5 weeks so I'm thinking of not turning up from now on. I architected the whole application and was in the middle of leading a team to build the front-end. These skills will be handy later down the track but won't help me get a job...8
-
React's `useEffect()` won't fire if you have someone in your team wrote a hook that maintain a state of an array, mutates the array, empties it, and then set it back to the state.
https://codesandbox.io/s/...
Reported it, ticket closed without asking, told should avoid mutating the object stored in useState.
Isn't it bluntly obvious that if someone spent hours to spot the line in hundreds of lines of code, which actually caused the problem and reduce the whole piece of turds into some understandable minimal reproducible example means they must of course for sure know that by avoiding mutating the array it will fix the bloody issue?
Isn't that bluntly obvious they are trying to say that there is a bigger issue behind those twisted wires?9 -
So related to my very first rant, after two months on the new job, I got the whole team together (including my boss) and taught them how version controlling works!5
-
I really don't understand why my company is so slow when it comes to change. We have a very small engineering team (<100 people), but it takes MONTHS to get anything done. They have spent the last 4-6 months getting FontAwesome Pro into the platform, been taking 8 months to get engineering levels out the door, and we've been lagging on choosing between React or Angular as our upgrade from AngularJS (yes it is the old one) for a year.
Is this normal? I am on the FE and don't know much about our dependencies, but it should not take this long to make a simple decision. The whole migration process will take time, but be decisive for Jesus' sake.2 -
Moved all my configuration to json files from normal JS last night. It took me 10 mins to convert. Everything worked perfectly.
This morning I woke up with angry messages from everyone in the team. No one could run their code anymore. It took me whole day to find out that those jsons were the issue. I still don't know how though. 😥1 -
! RANT
Yesterday I went to pool campus recruitment drive and there were 3 rounds
1. Written aptitude test
2. Group Discussion
3. F2F interview
Cleared first round and got selected for second round out of like 80 students. (15-18 got selected)
Went to group discussion first topic was "Donald Trump Administration is threat to IT for Indian or not" and the all were saying he stopped giving visa to Indians, there is no opportunity for us there because of him and I was like wtf... And they think because of Trump, Indian people from Infosys got kicked out hahahaha wtf is this.
Second was how AI and Digitalization can help in growth of nation.
And again those girls hahahah one girl said by using AI we can make new technology and can explore galaxies. What the fathafucking fuck!!
And YES THEY GOT SELECTED.
(Whole HR team was non technical)5 -
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.
-
I'm in a team of 3 in a small to medium sized company (over 50 engineers). We all work as full stack engineers.. but I think the definition of full stack here is getting super bloated. Let me give u an example. My team hold a few production apps, and we just launched a new one. The whole team (the 3 of us) are fully responsible on it from planning, design, database model, api, frontend (a react page spa), an extra client. Ok, so all this seems normal to a full stack dev.
Now, we also handle provisioning infra in aws using terraform, doing deployments, building a CI/CD pipeline using jenkins, monitoring, writing tests, building an analytics dashboard.
Recently our tech writer also left, so now we are also handling writing feature releases.
Few days ago, we also had a meeting where they sort of discussed that the maintenance of the engineering shared services, e.g. jenkins servers, (and about 2-3 other services) will now be split between teams in a shared board, previously this was handled only be team leads, but now they want to delegate it down.
And ofcourse not to mention supporting the app itself and updating bug tickets with findings.
I feel like my daily responsiblities are becoming the job responsibilities of at least 3 jobs.
Is this what full stack engineering looks like in your company? Do u handle everything from app design, building, cloud, ops, analytics etc..7 -
Fucking fuck! I'm done.
The client IT team decided to change the whole fucking theme of Wordpress and the manager who fucking approved the previous changes left month ago.
Spent whole day trying to integrate all the changes I've done previously on different theme in new theme but this fucking new theme always decides to fuck up whole CSS every time I do some changes in theme option.
FUCKING FUCK!1 -
Not really a fight but another Dev was telling me how I should implement things and to keep the code clean and clear/not spaghetti.
In the back of my mind I'm going yeah... I know what I'm doing... probably better than you.
I'm usually the guy telling other ppl to clean up their shit..or forced to dig thru it when their stuff blows up in production.
Anyway I'm going to add him to code review and maybe email the whole team... and then go, now this is how I want our code to look.11 -
Job review time,
(just a random pick from the a list).
---
"Engineering Lead"
Translation: "Chief Calculator Officer"
"Anyone can design or spec a product, get it manufactured overseas and get it to market. But will it be good? Will people buy it?"
Translation: "We're looking for a miracle"
"Take on a top notch team that is going places in Electronics, R&D and advanced product development."
Translation: "Professional Excel engineer wanted"
"This company is a little-known success story that has been operating for over X years, making mission-critical electronic equipment for use by consumers, professionals, government and industry."
Translation: "Design weapons and tamagotchis."
"Working as part of the Senior Leadership team, you will have charge of the I.P. engine and product development team spinning up new ideas and throwing them out the door."
Translation: "You're success is our success. Your failure is your failure."
"The Role
- Generate New Ideas
- Push for new products
- Drive manufacturing
- Manage a cross disciplinary team that includes Electronics, Software and Mechanical
- Project Manage new projects to completion
- Interact with marketing and sales to drive results"
Translation: "We've never hired one person to be a whole team before but we think it will work."
"On your first day, we expect:
- Strong Leadership experience and skills
- Solid Engineering Fundamentals
- Experience taking new and existing products to market
- Experience with manufacturing high-tech, mission critical equipment
- Commercial Acumen
- Bachelors in Electrical or Electronic Engineering"
Translation: "We expect you know where to hide the drugs already."
"Nice to have:
- Experience with Defense or Medical Systems
- R&D background
- MBA, B. Commerce or similar"
Translation: "By clicking on this job ad your background check is already under way."
"In return:
- A loyal and oustanding team will be there to support you
- Extremely knowledgeable experts to guide you
- Incredibly smart founders to mentor you
- The opportunity to work on a real product
- Extremely generous salary package"
Translation: "Our last dev has removed the Warrant Canary. Can you pleeease put it back?!"2 -
As the head of the Web Operations team of my college, I managed to compose quite a convincing pitch on college mail, as a call for interns for the team during the summer. The basic idea I explained to people was that even if you aren't a pro, you can still try and apply: you have one week to impress me with your CSS/JS/PHP skills(Really basic stuff in the problem statement; I didn't even make all of it compulsory), and encouraged them to start from scratch, cuz that's how I made it last year.
Last year they had around 30 responses in 7 days - I got 42 responses in 7 hours itself. I could shut down the portal cuz of far more than enough responses, but where's the fun in that. ;)
I'm not a good programmer, I'll admit, but I certainly benefitted in this field of being the head of the web ops team with knowledge and experience my non coding friends keep sharing with me. Not having a lot of code buddies didn't turn out to be so bad.
It's not much of an achievement, geez, there's literally everything left to be done for a whole year, but well, good start! -
A whole bunch of new features were added mid-sprint without ever consulting any of the development team. They dogpiled on devs from other projects who had no prior experience with the code base, so naturally I lose traction because I'm tied up answering questions and explaining things.
This sprint I'm not getting any feature work done as I'm stuck fixing bugs and awful half-ass implementations (by well meaning devs that were thrown at unrealistic expectations).
Concerned at the burn down rate, next week they're planning on dogpiling on more guys to play catch up.
I'm so sad -
who's so stressed out right now? me.
why? i need to change the access token in my code because it was changed
why is that stressful? because there is no variable for it, it was hardcoded
who coded that? me.
when? when the whole dev team was drunk asf
fml1 -
What i thought to be a cool company, turned out to be a shitshow.
Our "Team Lead" when assigning tasks keeps saying things like "it's only..." or "It's just..." or "You only need to change one line [there]..." And that's in regard to a terrible product with a pile of tech debt. So when you actually start to develop/fix things, you end up redoing third of the whole application.
How do you deal with this? How do you tell the "leader" that he should look into what we have in a code before making us all look bad for doing "just this one line change"?2 -
Why on earth I am doing docs and sending them to the whole team, if they keep asking me how to do X and why is Y not working
YOU WILL KNOW IF YOU READ THE DOCS
GAAAAAAA2 -
Last day on my first job where I stayed for a year. I really enjoyed it, loved the team, we were always laughing and making jokes, even in the worst moments.
Had a leader who became a friend, I made some good friends in there.
But I was really unmotivated as a dev, we maintained a really old and complex software, with a poor infrastructure for the dev team.
The manager was a great guy, but couldn't handle much pressure, saw him about 3-4 times quarreling with someone when he should be talking with the team to solve the problem.
But as I said, he is a great guy.
Today the whole team will be making a happy hour as my farewell party. I love this guys.
After that, on monday, I'll be joining a new company, working with a whole new stack, studying a lot for this new challenge.3 -
The irony that goes along with smooth migrations on production is this.
If the migration is smooth, no one knows how much effort, careful planning and execution went into the whole process. They just get a for your information mail that everything went smooth. No one, not involved in the process would know the scale of things; or what could've happened if the transition/migration was screwed up.
On the other hand if there are problems during the process and the tech team fights back, they indeed are the heroes. No one notices the silent crusaders.
No wonder then that all superheroes just smash stuff. Its only then that people notice that they worked so hard. Silent superheroes remain dead. -
Be a nice guy and volunteer for a weekend release that's supposed to be fast.
1. Release team person doesn't have permission to deploy our app
2. Dev that raised the change ticket didn't make sure it was fully approved and usable
-My whole morning go bye bye
-ah fuck it, clean up your own shit, I'm out...
Learn and don't do it again next time... Or not5 -
Fuck it. Two big releases plus all the minor shit raining down on our team with only three active devs. A new team member who's unfortunately more of a burden and nuisance while the whole ship burns so beautifully....
And stupid me? I fucking break my arm, is in a cast now for four weeks. So I can mostly watch, while everything sinks.4 -
2 years back when I was onshore, we were in the bad situation due to the size and complexity of handling big webserivces simulators. A single change makes the build red hence the face of other developers too.
These simulators were created using J2EE and VM templates 5 years back. With the time, application and data size grown. We were supposed to maintain consistensy in dummy data accross the applications. But some programmers made a copy of these simulators to finish their applications fast and made the situation worst.
Finally one of the team member dare to use stubby4j to solve this problem. Choosing the stubby4j was a good decision as it was the specialized tool written to create simulators only. But as the stubby4j was not having all the features a simulator need, he customized it's build for our simulators. All the team members were happy.
After few weeks, I picked a story to transform other simulators using stubby4j. The story was previously closed as it was hard to implement in stubby4j. I ingonred the comment and started working on. I spent 2 weeks but couldn't solve the problem. I read the comment in between but It was very late to take the step back. I was not able to give proper status update in the daily standup. Other team members (working from offshore) were thinking that I'm just passing the time. However my manager handled the situation very well and asked if I need some help.
This was friday, I took the leave as it was my wife's birthday. We couldn't go out due to the bad weather. I was thinking about the code all the time. Hence I started to write a new utility to handle all the requirement a webseervice simulator need. I took 2.5 days to complete it. On Tuesday, I demoed it to the whole team. And published it as an opensource application "STUBMATIC". In few weeks I received the good response from other teams as well.
I'm a full time open source developer now. -
at one point in time, i had to work with a really junior backend team, they used javascript and neo4j as the database for an in-house developed community forum because "graph databases made sense" in the eyes of their tech lead
turns out that the team struggled quite a bit with it, and had some "unexpected complexity" problems when i asked them to add filters and sorting on the post endpoints
in the end, the "solution" they gave me was an endpoint that spewed ALL the posts so i could sort it in the front end
had they kept the same relational database they were using for the rest of the whole project, i'm quite sure it wouldn't take much to implement that (and their architecture was really performatic)
as a side project i rebuilt the whole forum in a weekend, but using postgresql as database, and it worked nicely, i even added some unit tests just for fun
gave myself a really big slap in the face after that, though1 -
So our Chief Test Engineer left the company because of overwhelming frustration and stress. We working on new stuffs so we test our partly done product with partly done test tool developed be another of our team. His successor started to drop most of the 3rd party tools and workflows and documentations to trash expect this one unfinished test software.
Now he wants that we add more features to this software so it can replace everything he trashed already: run tests, generate test reports, generate documentations and so on.
On top of that he organized a workshop to read all this software's source code together, understand how it's works so we can rewrite the whole software from scratch.
WHAT?!1 -
Today I basically threatened my whole team that if they weren't going to help me take a backup (somehow don't have access issues to the machines) I would just deploy the thing and if it crashes then just fck it...
I already busted my ass for a whole week on top of other issues and you can't even help me run a few simple commands...1 -
Working with a group on a startup idea. We have weekly Google chat meetings with the full team and sometimes me and the other two founders have side calls. Our group is getting bigger so the weekly is getting longer so the 3 of us were talking about ways to make them more efficient. One was, background distractions like TV, random people talking in bg, kids...
So then yesterday the 3 of us went over a different topic and the guy who had brought up the distraction issue was in the bathroom shaving and trimming nose hairs the whole time. He kept asking questions about the agenda which we all had access to. I shouldn't even care much. I drink through the meetings anyways.2 -
One of the most inefficient practices I've seen done in companies is the company housing 50+ devs having to hire an expensive consultant who is only available on a limited time to figure out mysterious or in-depth problems with the company's main application (for example, JavaScript problems).
Then the whole dev team sits on his shoulders and production can't run smoothly until he fixes things. Even worse, him having the so-called qualifications, being the 'expert', but when asked an in-depth JavaScript question, they don't know the answer.
When I suggest to figure out things in-depth so problems like these can be prevented in the future, I'm met with: "Nah bro, we'll just apply quick fix #2" just because I carry the title 'Junior Developer'. Makes me want to hit my head on the wall on how stupid these people are.
This could all be solved if the dev team would be competent in the first place, knows how to read documentation and isn't lazy, most importantly. I hate teams like that.
Grab, the damn, documentation, read W3C, read MDN, get educated, and stop using band-aid solutions! Gah.
Toxic companies like these are what's wrong with some places in the development world.
I'm a proponent of knowledge.
Fellas, know your stuff. -
For me it has to be dealing with other developers who don’t want to keen with the times.
I don’t mind anyone deciding they don’t want to learn new things, for whatever reason.
But when you’re in a team if you feel that way it’s unreasonable to expect the whole team to stop developing their skills for you.3 -
10K bump but salary is probably still below market for the skills I have... Most likely reason? Trump tax cuts...
I can't showcase my skills in interviews assuming I get any... Not motivated in cramming or studying those useless algorithm questions that have little correlation to actual work.
Whatever.... job pays the bills pretty well... Sorta boring as I'm like the biggest fish on the whole team but that's also the upside I guess... May not be true but I think I'm pretty hard to fire...
So now it's sorta 20% work 80% life... So guess I'm done exploring and just gonna exploit...
P.S I wore this while taking a break from solo karaoking.... (Thursday night)10 -
Had a production issue last night where db hung so today whole team was investigating.
I checked the graphs and noticed a huge spike in inserts during a few hours. Normally it's distributed evenly through the day.
Emailed team with screenshots and also mentioned it to someone but then forgot to follow up... I assumed they were looking into it (I don't work in the same office as them).
Someone just logged in and notice the same thing happening right now... which made me remember.
So I asked him, did you see my email?
Silence....
Also got another guy doing a sort of code review on a util app I wrote that deletes certain records from our db and why I'm not just using SQL. I tools him the most obvious way doesn't work I tried but he won't believe me so let him do try it himself.
Anyway, these few days just feels like "why doesn't anyone listen to me?" ... and just feeling overqualified and sort of not part of the team again....3 -
I think I joined the wrong crowd. After the recent Hackathon, I proposed that the team that I was working with, form a company in which we continue building apps, launch and try to profit. Y'know, the whole build fast and die slow kind of thing. Granted, I proposed it late November and we're all gearing up for the holidays. Now its January and everyone has this mindset of "if we don't meet, we don't get anything done" or "discuss face to face only". Guess they don't like the idea of working remotely.
I think I might just quit this venture after a couple of meetings with them before I lose my mind.4 -
A teammate wants to transition from our current team to another team while there was an ongoing project.
Ended up leaving the whole project to me. FML2 -
Not a rant.
But, who loves to run gource on your project's directory and gets excited staring at the awesome animation created based on the git logs.
+1 If the whole team stares at it and yell "Look, thats me adding the .... component" -
Very useful!
It's not just about code but the whole package.
Watching great programmers fail miserably at project management, research, documentation, team leading and acting professional is just embarrassing, especially when they slate those who went out to educate themselves.
🎙️ Mic drop, I'm out!2 -
!Rant
Tldr: great spike to solve deployment problem may be a wasted effort.
Deployments of an ancient electron application need to be done in CodeDeploy to deploy the latest build. Customer hour restrictions cause this to be done only after midnight, and manually checked.
The whole team knows this is the wrong method of deployment and that there are many other operational problems with the project.
A few other senior team members get together and decide to spike out a way to use electron auto-deployment to accomplish this without using code-deploy at all.
After a shallow dive into this subject, we all get pulled aside to handle a change in another part of the software ecosystem. It happens. We leave the spike behind.
A junior-intermediate developer on the team pics the project up and gets a good spike going in a day and a half! We are all high fives and beers. This is Friday.
By Monday there is a pull request in for code review and it looks solid. Seems like it will make deployments a lot better.
Preparing the last deployment (hopefully) with CodeDeploy ever...
Marketing team members inform us that they are running an add system on the customer devices and to do it they are using Linux.
The current application being deployed is using Windows 10 (yeah, another problem).
They say they have made plans to move our application over to Linux. This means we may not be able to launch the junior devs great spike and the old deployment method may stay for the time being.
Meetings soon to find out how all of this will hash out.
End of rant. I hope I'm doing this right -
I was just copied on an email that had far to many managers included that basically says 90% of the problems come from an original group that just didn't follow directions.
Now we wait to see if upper management cans the whole team.1 -
!rant
In my team, I am not allowed to use ANY comments except for the really lengthy classes in the backend.
Thus, the code of the whole project (a complex webapp, consisting of 20-something Django projects and various services) is basically undocumented.
The slogan sounds "good code doesn't need commenting".
Seriously, fuck this and all of the times I scratched my head wondering "what the fuck is this spaghetti about".
Have any of you encountered something like this? Usually people don't want to comment, I would do it gladly but can't even make a small inline about what complex method is exactly doing :P3 -
The whole episode of me managing an outsourced team for about 6 months. I thought because I’ve managed other teams doing non dev things, it would be like that.
I’ve never been so wrong and NEVER AGAIN! I had to own everything and they’re code is so repetitive and confusing. It misses basic structure because I didn’t outline some things like knowing when a operation is complete and that if the same button appears in two pages it should do the same thing! Or that is you break up a SPA you shouldn’t just duplicate the whole files and then confusingly use randomly parts to so random jobs across all layers of the app. Ffs. Never want to work with a team that doesn’t have a plan to maintain the code they write. I felt like a failure but for me to make them successful I would have had to pretty much write the code.
Now I have to explain this embarrassing pile of curry spaghetti to my colleagues who need to do some other work on it. Fuck. I want to throw it out and start over so badly.
I should have told my boss a hard no on that one and let him know outsourcing would slow things down not speed them up. He just needs to stop trying to get software developed and deployed at the same time. Fuckers.3 -
I'm currently the only dev that works with a client's dev team. That's not really how we usually work, usually it's a whole team of ours.
Three aspects why this sucks:
1) the client's dev team is made up of juniors and junior to intermediate devs. All of them are new to scrum. I therefore have to constantly support (dev & agile workflow), check all the PRs and have to think of everything in Refinement meetings.
2) the client's based in another timezone and the PO is super busy because we're the only agile team in their company. Therefore this is going to be the third Friday in a row where I have meetings until 6pm.
3) I also have a specific time frame I have to start working for my company, so I constantly work extra hours due to the time difference.
I'm just tired.4 -
My class team picks me for a competition.
My team tells me to do everything and doesn't give me an outline of what they want for the code or design.
They have 7 members. + me, 8.
I have to design and code the whole app on android.
Furthermore it was my first time with library stuff.
I had to develop from 10pm to 6 am with short rests in between. Almost no sleep.
It's impossible sht. I continue with it.
When it was time for school, I just went to school as per usual.
When it was the interview someone just had to roast the judges.
Our idea was very sophisticated; was to help track down elderly or child with a gps tracker and the app.
Didnt got in the qualifiers because of the leader being an asshole to the interviewers. -
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 -
Look, extra remote team member. If I hired you with the express requirement that you work and/or live in sync with my time zone, and you claim to live and work in my time zone for a few weeks but you're lying to me and you were actually just on vacation here and have moved back overseas, you SUCK. And now we're firmly entrenched with the project and it's near impossible to fire you at this point if I don't want to deal with a whole new developer and learning curve!!!
-
yay!!! Another PROD issue on something that we've had PROD issue on and well should be an easy fix... Cuz the root cause is prolly bc the idiot that implemented the logger had no idea what the fuck they were doing... And well the whole team didn't bother to ask me (and never listen to me anyway).... WHO WOULD PROBABLY SHOW THEM HOW THEY FCKED UP...
BUT ....
¯\_(ツ)_/¯1 -
Your time is better used somewhere else, let the intern write the documentation. While the project was transitioning to a whole new team with no one from the old one.1
-
Some advice please: In our last sprint meeting my manager told the whole team that I broke something. What he didn't say was that he was also responsible for that. He generally has the habit of accusing others to cover up for his own faults. I don't care, I own up to my mistakes. Any witty but nice responses if he tries that again? I'd like to answer "Man, I don't even feel bad" but that would be too sarcastic.3
-
Follow up to this:
https://devrant.com/rants/6403741/
So we had today a meeting....
To restart the project, as the current state is garbage.
Turns out the whole team has after two weeks of being left alone with it - kinda like the rant says - zero clue how lucene works, what it does, what its for.
In case anyone of you wonders why some managers are micromanaging biatches, there you have it.
The whole meeting had more "oooh"... "ehm".... "eh"... and other fillwords just to cover the shame of not having any clue at all.
I'm really disappointed that a team of up to 5 people really thought they could pull a stunt of "fake it till you make it". Collectively. Really noone had a real clue.
Now to an interesting discussion: How would you devs reprimand them?
:)
Just curious. Firing is out of option, for several reasons, e.g. law.
Serious answers, I would be really curious. :)
I'm feeling sad for the socks metaphoric in the last rant btw.
Even a cum socket deserves more dignity than them imho.6 -
How can you avoid becoming a knowledge silo if everyone you train and upskill ends up leaving for another job? 😩 So frustrated that over the last 5 years I have tried my best to ensure the whole team is skilled in my specialist area so, that they can manage it on their own.... Yet... here I am... a silo again.4
-
The time that I felt most like a Dev badass was when I had introduced an E2E test framework and added a bunch of helper classes to it so that our QA team could pick it up and write automated tests for the manual tests they had been doing for years.
Sure, the whole department got laid off after that because we had gotten a new CTO and all of my work was essentially for naught, but it made a lot of people enjoy showing up to work for the first time in a long time, and that was what mattered most to me -
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 -
IBMs Rational Team Concert.
Whole the VCS is okay for a semi-centralized one, the client was based on eclipse.
Who in a bright mind could possibly think that writing the client as an eclipse plugin is a good idea?2 -
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 -
People who use automatic code beautifiers and standards fixing scripts. 😠
Agreeing on a coding style with your team is important. But I really don't feel like reviewing the new guy's PRs if it's a thousand style adjustments and a tiny bugfix.
If you disagree with the current style, communicate about it so everyone can discuss and adopt new rules, and fucking fix the whole codebase in a separate PR.1 -
A long time ago in a decision poorly made:
Past me: hmm we're having trouble getting IT to give us a new build machine with the new compilers.
Past me: I know we'll just use one of the PCs that belongs to a member of the team to tide us over.
[2 months pass]
Present me: that's odd, Jenkins is really slow today.
[Several minutes pass]
Present me: holly shit fuck; it's building the whole weekends worth of builds at 9am on a workday and eating licenses like a cast away that suddenly teleported to an all you can eat buffet.
Present me: [abort, abort, for the love of fuck abort]
Present me: contacts IT, they can't find any problems, wtf happened.
Present me: discovers team member turned off his machine on Friday and builds had been stacking up all weekend.
Lessons learnt: disable power button on team members pc and hire a tazer guy to shoot whenever someone goes near the wall socket.
1 hour lost and no build results for the last 3 days.
It's looking like a bad morning
-
Technical question that I just cant find the answer to anywhere.
I have a load balancer and want it to pass the IP of the original caller to the server. Usually it is done by modifying the header? of the Request HTTP packet? and adding X-Forwarded-For: ....
The LB team though says it needs to modify X-Originating-IP and somehow causes a noticeable impact of the speed of all requests.
I don't know the details but it should only modify the first Packet that has the HTTP headers and should be appending X-Forwarded-For. If only need to modify the Header packet, how can it slow down the whole interaction so much:
-Adds 100ms to a 200ms request
-Increases a 10 minute download to like 20-30 minutes6 -
So Thursday our first beta client is supposed to go live. Tomorrow there is a team meeting to discuss the status. Team lead wasn't in at work last Thursday and Friday and gave me his work to finish, which I need to proceed with mine. I hardly made progress on it. So now I have to tell him about that tomorrow. And I'm dreading it so hard. More so because for some reason HR/support sits in on our meetings and will be on my ass again I'm not meeting deadlines. I did say last week it looked like it wouldn't be done in time but I was told it just needs to happen because the release date was already announced. So yeah the coming week is going to suck. And I'm on leave myself this coming Friday so I expect people to explode. I know I should just stop caring and get on with job searching but the whole injustice of being set up for failure by others and then being blamed really makes me mad.3
-
got back from a week long (mountain/snowboard) trip, disconnected from anything that means work, just to found out the team decided to do a huge refactor of the whole app! now i have to 2x work to catch up. i need another vacation 😩!
ps: at least they were nice enough to not break me the news while i was gone and enjoy my time 😅1 -
So, I realised that I know my manager personally. He has left the team. The thing is, I thought I was crushing on him instead it's just knowing him. I never had any personal conversations. Now, there is nothing I can do to interact. I do not want to seem as someone who likes him as that looks desperate. I know it's not a platform of this kind of posts but any advice? During the whole 1 year lockdown I haven't interacted much with anyone except him and someone from my team. I really see his insta profile 3 times a day. Think about him a lot. Again, do not have a crush, just want to know him more so I get to know if he is nice person to have in my life. Any advice?9
-
This is more of an advice seeking rant. I've recently been promoted to Team Leader of my team but mostly because of circumstances. The previous team leader left for a start-up and I've been somehow the acting Scrum Master of the team for the past months (although our company sucks at Scrum generally speaking) and also having the most time in the company. However I'm still the youngest I'm my team so managing the actual team feels a bit weird and also I do not consider myself experienced enough to be a Technical lead but we don't have a different position for that.
Below actions happen in the course of 2-3 months.
With all the things above considered I find myself in a dire situation, a couple of months ago there were several Blocker bugs opened from the Clients side / production env related to one feature, however after spending about a month or so on trying to investigate the issues we've come to the conclusion that it needs to be refactorised as it's way too bad and it can't be solved (as a side note this issue has also been raised by a former dev who left the company). Although it was not part of the initial upcoming version release it was "forcefully" introduced in the plan and we took out of the scope other things but was still flagged as a potential risk. But wait..there's more, this feature was part of a Java microservice (the whole microservice basically) and our team is mostly made of JS, just one guy who actually works as a Java dev (I've only done one Java course during uni but never felt attracted to it). I've not been involved in the initial planning of this EPIC, my former TL was an the Java guy. Now during this the company decides that me and my TL were needed for a side project, so both of us got "pulled out" of the team and move there but we've also had to "manage" the team at the same time. In the end it's decided that since my TL will leave and I will take leadership of the team, I get "released" from the side project to manage the team. I'm left with about 3 weeks to slam dunk the feature.. but, I'm not a great leader for my team nor do I have the knowledge to help me teammate into fixing this Java MS, I do go about the normal schedule about asking him in the daily what is he working on and if he needs any help, but I don't really get into much details as I'm neither too much in sync with the feature nor with the technical part of Java. And here we are now in the last week, I've had several calls with PSO from the clients trying to push me into giving them a deadline on when will it be fixed that it's very important for the client to get this working in the next release and so on, however I do not hold an answer to that. I've been trying to explain to them that this was flagged as a risk and I can't guarantee them anything but that didn't seem to make them any happier. On the other side I feel like this team member has been slacking it a lot, his work this week would barely sum up a couple of hours from my point of view as I've asked him to push the branch he's been working on and checked his code changes. I'm a bit anxious to confront him however as I feel I haven't been on top of his situation either, not saying I was uninvolved but I definetly could have been a better manager for him and go into more details about his daily work and so on.
All in all there has been mistakes on all levels(maybe not on PSO as they can't really be held accountable for R&D inability to deliver stuff, but they should be a little more understandable at the very least) and it got us into a shitty situation which stresses me out and makes me feel like I've started my new position with a wrong step.
I'm just wondering if anyone has been in similar situations and has any tips or words of wisdom to share. Or how do you guys feel about the whole situation, am I just over stressing it? Did I get a good analysis, was there anything I could have done better? I'm open for any kind of feedback.2 -
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 -
The whole company (including the rest of the team) is an uproar because our biggest client is going live and I'm sitting eating out of my nose because I've done all my shit on time...
1 -
I don’t see my myself ever becoming a team lead or PM because I fucking hate meetings. Imagine spending the whole working hours attending meetings! Jesus Fucking Christ!4
-
How to View Writing Documentation as a Developer
You finally have the time to sit back and tell the world (or your team) the amazing system you built over the last month and how use it to save everyone's asses a whole lot of time.
... While watching everyone else running around like headless chickens.
... But then again you've been heads down coding for the last month... -
Was told by my boss to fix an already written file and I have been doing that for the past whole week and today the architect of our team comes and tells me to write the whole file from scratch cuz it's too messy...FML..
-
Automating installation and configuration of an automation tool would actually save some time, which itself is supposed to save time. Puppeteering 2000 nodes of F5 loadbalancer and BIG-IP configuration spiderweb is actually fucking with me, oh well btw, that is the smallest task of whole project and none in my team are able enough to write a decent puppet class.
Deadline today, hoping to finish it up soon, getting back to you soon when I am done with it, cheerio devRanters! -
We have about 12 standing desks at the office for people who say they /need/ them.
I only ever see two people standing.
One guy is standing every month for a few days, and sometimes for the whole month.
The other one, where a whole team moved for so he can have his standing desk, has his desk up high every day but is sitting on a high stool in an unergonomic way, slouching forward.
All the other people just don't use it ever.
Plenty of people who want to actually use it don't get the opportunity.6 -
Fuck me! Fuck VSCode!
Wasted nearly a whole day of entire team by breaking a core functionalty.
Don't know if others also hate it so much when you want to add a bracket and VSCode detecting a closing bracket or whatever nullifies your attempt leaving the number of brackets constant.
Not exactly sure today's defect was caused by this, but I strongly suspect it because it was caused by just a misplaced bracket.5 -
Ok I don't know what ticks managers off about working from home.
I live an hour away from the office and my team (i.e. The whole company) consists of 3 people, INCLUDING ME. And we all work on different projects. So what's the point of even going to the small room with cubicles AKA the office? No, there aren't really any "learning from my colleagues" crap; we work on different stacks. Plus we're all juniors. Oh yeah, haven't I mentioned that? WE HAVE NO TEAM LEAD OR EVEN SENIORS. The CEO has a tech background and he communicates with us directly and discuss the requirements etc. BUT HE LIVES IN ANOTHER FUCKING CONTINENT. So, again, what's so bad about working from home in my case? My manager doesn't like it for some reason. -
Director walked in asking about the new homepage which we’re currently running an A/B test for. This page has been made and discussed by her direct colleague, the general director.
While walking though the page together with my colleage the designer the encounter a broken link.
Easy to fix ofcourse, and so we did, but shortly after he went back to hos room my colleage got an email asking who was responsible for this mistake.
It’s not one person. In first instance it’s our 6 headed web team. But after we deliver it multiple people test the page, and also the company who creates the A/B test sees tests and confirms.
This all happened during my holidays, but still i feel also responsible.
Couple of tiny mistakes, and still nobody in this whole process notices.
(At least 10 persons)
HOW THE HELL is that possible?!3 -
Getting too attached with the code you wrote and later realising that you have to erase the whole thing and write again just because your team lead didn't like it! 😒
#FeelingSick2 -
I have been using an app through Slack for months that helps me to get specific emails related to users needing help into a Slack channel for the whole team to easily see, manage, and talk about. Just found out that they updated their app to version 2.0, and with this, the free service, has now become a paid monthly service (along with a lot of other things I will never use.)
So now I have a workflow that no longer works, and have to put a pause on everything else I was doing to find something else that can work, or code something from scratch. There goes my day. -
Voice call with the whole dev team
Former team leader: Yeah, basically we stopped using RxJS because it ended up being too complicated, every minor problem required so much code to solve :(
IHateForALiving, extremely loudly: WELL WELL WELL, GOOD FUCKING MORNING, SUNSHINE3 -
Worked as frontend on a company that also had backend devs making frontend work. One day we've received a task of redesigning those screens, since their work were poor. Past half of the work is done, the whole team came onto us saying to pause the task since there would be multiple changes into the informations on the screens. That day we lost something like 4 hours of work. Didn't punched anybody though.2
-
Actually, it was probably my whole first two weeks in my first dev job. I got hired while still attending community college for my associates, and was woefully under-qualified (I didn't embellish, they hired me anyway), and my boss went on a three week vacation three days after I started. I had no idea what to do, didn't get much help from others on the team either. First couple of weeks were rough.
-
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
-
When I was doing my onboarding training for work, we had to do a group exercise. We had to build a small app using Spring MVC connecting to a MySQL database.
We had a team of 4 people, and I think I was the only person who wrote a single line of Java the whole day.
One person decided that she would build the DB schema, so I thought ok fair enough I will make a start on hooking up Spring. But the other 2 decided that they would “focus on making it look pretty”.
Several hours later what they had basically managed to do was import Bootstrap.
We ended up with only one screen to demo while other groups had 3-4.
Thats not the only story I have where Im in a group project and basically end up writing all the code. I’ll post the other one later. -
So I applied for this company that was a perfect fit for me, I cleared the take home assignment and did the round with CEO and CTO.
When it came to CTO round, he handn't even gone through the take home assignment task that I submitted, instead he asked me about hackathon experiences . Now I have 6 years of experience and during the technical round, he was out not even on the call for most of the interview.
It makes me more angry than sad . Hopefully I can channel this anger into motivation for a better company
Today I got the rejection email and it makes me so angry , how can you go through multiple rounds until the end and reject without giving any reason ?
Their whole tech team consist of people during internships and just out of college.4 -
When you spend the whole fucking day waiting for a colleague to finish something that is blocking the whole team.
He finally finishes at 5:30pm and goes to home.
I just left work at 9pm.
He's a nice guy but gosh he can be slow sometimes.5 -
When you boss makes a product decision in a meeting and never tells the team or me the lead dev. Then when it comes to an overview day he gets angry that I didn't know about these changes cause he never told us or put it in the sprint. So I have to spend my weekend refactoring the whole website so make it work the way he wants.....5
-
When the whole team started to work on the same project for the first time.
You could know that the code was written by more than one person.
The test suit took about an hour to finish.
Glorious days they were.1 -
!rant
My employer is a subcontractor on a big and rather complex project, that already is way behind schedule and over budget (as these monsters tend to be). To get back some confidence from the client our principal moved an important milestone up two weeks. Which we protested against vehemently because the projected workload was already a very tight fit for the original timeline, without any reserve to speak of left. They wouldn't listen though...
The result? The whole team has to work the next weekends to have even the slightest chance of making the earlier timeline. Which is exactly what we told them would happen when they moved the milestone.
The worst? This isn't the first time this has happened while I worked on the project 😑5 -
Every dev team has this chatterbox guy, who works as a support, does sometimes whole work in a hour, watches anime for following 7 hours and wants to fix the whole world with JQuery. Still can't imagine working and hanging out without him.
-
Couple months ago I mentioned that the product group needed to involve engineering when making promises to the business. Otherwise they were going to write checks our asses can't cash.
Welp, now the situation has happened and I pointed out that a lot of things have been promised for delivery that we haven't planned for or even seen in engineering. And things that I have been harping on haven't even been accounted for and, unlike business promises, these are legal requirements. Now I'm the asshole because I pointed this shit out in front of the whole team.1 -
I get a call asking how I would handle a problem using the system from one of the Project Managers.
I told him that with very little information, the system is designed to do 80% of what he wanted automatically and walk you through the steps to make sure him and his whole team know what's going on during the process.
He says back, honestly I don't want to learn that, I'm just gonna use excel and here's why
**hang up phone**
It's a walk through that does 80% of the work automatically that will take you days... What is there to learn? -
Working on a multi-year college project, going through tests from previous team.
Every test is not working quite right. They're almost all intermittent failures.
The reason? Every single test class extends some test class, which usually extends from some primary test class.
That primary test class opens up their whole UI, and outside of their UI test package, the only thing that gets used is a variable named session (a string), which isn't even specific.
WHY THE FUCK WOULDN'T YOU JUST MAKE THE SESSION NAME STRING A VARIABLE IN THE TEST FILES YOU DUMB FUCKS
THE ARGUMENT VALIDATION TESTS DO NOT NEED TO OPEN THE UI, LET ALONE CREATE THE WHOLE FUCKING DATABASE JUST TO VALIDATE ARGUMENTS, WHICH YOU DO APPLICATION SIDE
(Also they made it so every session has their own tables as opposed to having session IDs. E.g., "person_sessionID1" and "person_sessionID2" exist.) -
My client recently asked for help with a product idea he has. He already got his lead developer to hack a proof of concept together.
My client knows I have more time and would start progressing the whole project. He says that he is fed up of all of these huge plans for some huge product...
I said ok, let's start getting the next few features on and using the product with the team.
He then said he wanted a big plan for the whole thing... so I said the whole point was to just get on with it and see how we get on as there are so many unknowns.
Somehow, due to a lack of other work, I have decided to help make a proposal that is far too long for this project. Would have just been better to get on for a few days and make a MVP of the product that works.
Instead I am waiting to see if this latest proposal will actually land me this work...
I'm pretty sure all of this back and forth is proof I don't want to work for this client! -
Fellow ranters, I need some advice.
Work at an early stage startup to build their initial product(let's call it X) or work at slightly established startup with funding(let's call it Y)?
Both have their own benefits.
Working at X:
- I have equity (and a co founder position) thus chances of high rewards if the startup is successful.
- I get to build the whole product from scratch (great learning experience).
Working at Y:
- Don't know much about the company but I get a decent stable income.
- Work with a team (although a small one).
- Job security.
I'm currently in my final year and have given up on campus placements. Moreover, I'm not interested in wasting my time in pointless interview preparations. So I figured that startup is the way to go.7 -
I'm gonna soon start on a gaming project with my team, it's not gonna be something we want to push but it's gonna be an on going project to slowly grow some skills within the whole learning and understanding game machenics. Any advice from any fellow veterans :3 ?2
-
About a year ago I had the great idea to enforce ago I had the great idea of proposing that we all lint our legacy code base using eslint to increase the overall quality of our JS.
I distributed the task of initially fixing all the errors eslint would find to the whole Frontend team (Luckily we only use JS there). I've finished my part in a couple of weeks and came across this piece of spaghetti.
One of the guys who has been with the company for over 10 years said, that the guy who wrote this monster was very proud of it...
In case you cannot understand what this does: It calculates the distance between 2 points on earth.
9 -
A parade of planning meetings every Monday where the whole executive team (including the CEO) sits in. Each meeting was an hour long and it took up their whole day.
It was ridiculous how unproductive that was. Continues to this day AFAIK! -
VS2022 is an abomination......
I was forced to put the whole team on 2019 ansd remove all .net 6....
VS2022 is NOT USABLE AT ALL !
It's like vs2010 which we all skipped.
I'll wait for VS 2024 at this point...
can't work. "Changed a file" ? Oh wait i'll just recompile whole solution for 3 minmutes at EACH FUCKING FILE CHANGE.
VS2019 9Same project) : 0.2 seconds.8 -
Wow why is TFS (with default settings) locking files and the whole solution for the whole team just when i change the code formating for better reading? I cant wait when we move to git or even svn1
-
I joined a startup and suddenly all I thought I know was disappearing and a very complex creature fell into my laps asking me to code it. Then there’s these trello cards asking me to pick them up and start solving.
Well, first, no idea how the whole app is structured.
Good thing, have a supportive team for sure. -
I wish devRant was also a little fluid to browse, I personally enjoy Twitter a lot, cause the transitions are really smooth and things load pretty quick.
I can understand that this platform is built by a very small team, but I think making this platform open source can help things change quite a lot.
Not only it would help people learn open source contributions, but it would also help improve the platform as a whole.
A community of developers building a community 'for' developers would go a long way in the future.1 -
So in the next term we're going to learn web dev(bootstrap and some javascript, no backend :( for now), the previous term was about c#. We'll have to build a website as a team (4-5 people) and everyone has a specific task and have to do the research on their own,but at the same time we can help each other out. OMG if the whole school was just like this I would be happy to come here every day lol! I also hope to improve on my social anxiety, but this could easily backfire depending on my future teammates, coz you know, in every highschool there have to be some badass kid whose intelligent equals with two rats...
So yeah, right now I feel 50-50% about this whole thing.1 -
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 -
I am an intern and was put into a fresh project to do node back end. They didn't really give me any supervisor because the company lacks employees and has too many projects, and they were afraid I won't do myself. I was assigned to a front end oriented colleague to make a team, and cooperation with him is really demanding. After a month, a company that outsourced for us did a complex code review and said we wrote some darn good code, and they were said we are both mids (while colleague is a fresh Junior with an intern by his side). Damn it felt good :)
And also our pair is said to be the only Dev team in the whole company that can call client for itself, without PM or any host of the call, as others, with a lot of experience, need to be guided through each call :D -
Colleague is programming/scripting for over 5 years now (that I know of), even attended Udacity programming nano-degree.
Yet, he still writes code/scripts without a single function. How the hell can we start any programming best practices, clean code, or making steps towards TDD with this sort of mentality.
And it's not just him, it feels like a death by thousands cuts as the small things add up. I know we're Ops and not Devs and some other colleagues are trying really hard to get their work on the next level but I see no hope for the team as the whole.4 -
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. -
I was away sick for a week. Come back to a chat log with messages about how the other dev team is trying to figure out a solution to a bug that they only show three services listed in the system.
Me couple of weeks ago on my second day in the project figured it out relating to a task I was doing. It's not a bug, it's a feature. It's a constant defined in the constants-file.
And the best thing: my team mate quoted me and said "Lankku figured it out last week". And it was passed down back to the team who had actually developed the whole feature and couldn't figure out why it was working so now. xD -
so a good thing happened. after struggling with our current TL for whole last year, one SSE was promoted to TL and the team got split into 2. now our team has the new TL which is strict but a much more responsible lead and a good friend.
and in a striking change of culture, she has askedus to define our own KPIs rather than using the pre default KPIs. our predefined KPIs were weird :
- number of sprint spillovers >> to minimise
- number of POCs , learning sessions done >> min 2 in year
- number of prod bugs caused >> to minimise
-instancee of coding standards miss >> to minimise
i kind of excelled in all , yet got an 86/100 rating. previous TL was an asshole , so that also contributed to a lower rating without reasoning.
but since now i have the opportunity, what do you suggest should be ideal KPIs for a software engineer 1?1 -
Everyday life: Colleague offers me a stress ball after hearing about deadline shifted forward (again).
We are ending up playing basketball in office with the whole team... -
Currently still working on this one. Interning at the sugardaddy for dutch students. Have a great team there, but the whole research thing that my university demands me to do is on my mind so damn much that it takes all my joy from the internship. It feels like it prevents me from learning things that truly matter to me, like my extreme anxiety of even doing any form of coding. I just want to be an IT teacher/lecturer ;¬;
-
Appraisals are pretty insightful times. I wanted to check how much work I do as compared to others in the team. So, I tried to pull up number of pull requests created by me and others in the team. And to my surprise, I create 4x(I created about 850 pull requests) more pull requests than the next contributor(200 pull requests). I knew in general I was doing more work and much faster, but this is just too much.
I know number of pull requests is not an indicator for the amount of work done by anybody, but I had this feeling as well that I was doing more than others. I often see other members of the team not putting that much effort, and rather have a relaxed approach to getting work done. They pick one ticket and take the whole week to complete it slowly. While I hustle to get as much done as possible.
As far as the appraisals go, I am kind of laid back in terms of contributing towards overall organization which is now getting more weighted for my appraisal. So, despite me doing quite a lot of work, I am getting the appraisal at par with others in the team.
So, its kind of feels a little bit uncomfortable.3 -
The community has multiple fixes to 3.0, but it looks like the whole team has been allocated elsewhere in Apollo, this is not the first time.
Good job, Peggy. Keep poaching for community hype and let us down, it will backfire.2 -
When you discussed something with the whole team, let someone implement it and see almost opposite solution as the result
-
I was hired about 6 weeks ago to help the company take ownership of a piece of software written by an external team. The whole thing was MEAN stack. I had never done anything extensive in nodeJS, but I am quite comfortable in JavaScript and so there weren't any problems. I even ordered myself a JS DevDuck for my new desk.
Just about 2 weeks after my new DevDuck came in, my boss told me that everything the external team wrote is shit and is going to be thrown out. Instead, we're going to rewrite the whole thing inside the existing middleware in Java. Luckily for me, I am also pretty comfortable with Java, though it has been about 5 years, and I know a bunch has changed. But I'm confident I can do the work.
I guess I need a new cape for my duck. Or maybe I'll just start a duck family.1 -
Hola community!! Everyone going over this, please read this once and honestly answer my query.
I am on a probation at a startup. When i will be full-time, then the startup has promised me to provide CTC of 7,50,000(inr) i.e 10,000$ (usd).
Now I want to switch this startup company. Here are my reasons -
1. Less people, more work. - Well, that's what we call a startup. The tech team consists of 3-4 members only and we ourselves have to do the whole thing from end to end. This consists of designing the architecture, PR reviews, qa testing and coding ofcourse.
2. I see myself that I am capable enough to earn 1.5 times more than the above CTC. Also, all my friends are earning 2x the above ctc.
3. Also, there is no senior in the team except founder himself. This really seems awful as can't learn from anybody.
4. Also, i have plans of higher studying due to which i have to entrance exams. So i need to prepare them too. Switching to an established company can mean more money and less work.
Now, can anyone suggest me whether my reasons to switch are legit or vague??1 -
Our HR in the company did not send any newcomers to our Team and we are waiting for a whole year...
The work was not overloaded but the development progress are slowing down
Even I have been relocated from Team A to Team B after 6 months in Team A... They never came for both -
Trying not to end it all at the thought of a whole game dev team working through perforce. Incoming "oops I checked out the whole thing"
Top Tags
Weekly Rant
View