Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "teammates"
I'm the git master in my group for a uni project as I am the only one with some experience.
This is what I have to deal with21
Team: *furiously discussing something outside of my expertise*
Team: *finally acknowledging my existance* "Yeah, dude. We are going to delete te project and start over because we can't fix this issue [which we have never ever discussed with you]."
Me: "What, that's stupid."
Team: "Well, do you have any bright ideas to fix it?"
Me: "Gimme until tomorrow."
Team: *doing absolutly nothing*
Me: "I fixed it!"
Team: "Why didn't you do that a week ago?"
Me: "You didn't ask..."
And so goes te story of how i was almost killed by an angry mob.15
TL;DR: One of my coworkers is a genius engineer and doesn't get as much recognition as he deserves, whereas another extremely mediocre engineer on the team gets praised for his crappy applications.
We have one engineer on our team (let's call him Hank) who started with me at the company when we were interns, and man is he a freaking genius. I swear, you could give this guy any language/library/framework, and he'll be fluent in it in less than a week. He's singlehandedly written two of our most complex applications by himself, and has a great sense of UX as well. All of his apps look fantastic.
The problem is, I feel like he doesn't get anywhere near as much recognition as he should. I try to talk him up to our manager, and our manager knows that Hank is smart, but he also overlooks him for promotions and praise because he's a little spacey (he's got quite the case of ADD) and doesn't speak up very often. He's got trouble focusing sometimes, but when he's in the zone, he can write an exponentially better and more complex application in 2 days than some of our other engineers can do in 4 months.
For example, we have another engineer on our team (let's call him Phil,) and the entire team has their heads so far up Phil's butt that I'm surprised they haven't suffocated yet. Don't get me wrong, he's a smart guy. He's great with the more basic aspects of our job, but when it comes to writing an application, he has no idea what he's doing, and he takes months to write something that should have taken him days. Then when he finally releases it, it's riddled with bugs. But everybody praises and bows down to him for it. "Oh Phil, this app is amazing. You're a genius, you deserve to be a Lead." Then we have Hank sitting quietly at his desk, banging out his 3rd big application of the month, and people say "Eh, nobody's going to use those apps anyway. He's wasting time." And I'm standing there thinking, "You asshats, we already have a solution for the app that Phil wrote, and the entire company is already using it. It's exponentially better, why did you let him waste time writing this when there's already an existing solution?!"
Oh well, I hope Hank gets some recognition soon. He certainly deserves it.18
I asked my teammates if it would be ok if I made multithreading code for the collisions of our game engine and they just sent me this, I'm going to try anyway. Yolo.4
My teammates are working on a legacy codebase so shitty awful, so poorly written, so full of pitfalls, hidden information and intricate relationships, they gave a name to their development style:
Indiana Jones programming.6
I live in the terminal. I write lots of scripts (Shell, Python, node js) to automate tasks that would take hours to do by my teammates. Recently, I started automating everything that I put my hands on using Ansile: from pointing DNS server to continuons deployment, provisionning a fully customized infrastructure on the cloud using just a single command!
This is because automation gives you super power, the feeling that what you do help tl increase the productivity, reduce bugs etc.. Simply, once mastered, automation is ausome!13
2 years into polytechnic I got my 1st big project as a subcontractor doing Symbian. No need to tell the company I presume.
Anyways, I was brought into the project just couple weeks before holiday season started. My Symbian programming experience was just the basics from school. 1st day I was crapping my pants out of anxiety. I pretty much didn't understand anything what my project manager or teammates were telling, so I just wrote EVERYTHING down on paper and recorded all the meetings to my laptop.
My job was to implement a very big end to end SDK feature. Basically from API through Symbian OS through HAL to other OS and into its subsystem. Nice job for a beginner :/
As the holidays were starting we had just drafted out the specification (I don't know how, because I didn't understand much of what was going on) and I got a clear mission from team lead. Make a working prototype of the feature during the time everybody else was on vacation.
"No problemos, I can do it" I BS'd myself and the team lead.
First 2 weeks I just read documentation, my notes and internal coding tutorials over and over again. I produced maybe couple of lines of usable code. I stayed at the office as late as I dared without seeming to obvious that I had no clue what I was doing. After the two weeks of staying late and seeing nightmares every night I had a sudden heureka moment. Code that I was reading started to make sense. Okay, still 2 weeks more until my teammates come back.
Next 2 weeks were furious coding and I got better every day. I even had time to refactor some of my earlier code so that quality was consistent.
Soooo, holidays are over and my team leader and collagues are very interested with my progress. "You did very well. Much better than expected. Prototype is working with main use case implemeted. You must have quite high competence to do this so well..."
"Well...I did have to refactor some stuff, so not 10/10"
I didn't say a word of my super late nights, anxiety and total n00biness.
Pretty much finished "like a boss". After that I was on the managers wanted list and they called me to ask if I had the time work on their projects.
Fake it, crap your pants, eat your crap and turn into diamonds and then you make it.
PS. After Symbian normal C++ and almost any other language has been a breeze to learn.3
I once reviewed a Pull Request made by a fairly junior developer. They had joined recently, and this was one of the first times they had to touch a bigger part of the code.
Due to a mix of inexperience, new (to them) coding standards and lack of git knowledge, they ended up with a mess of a PR, with a few thousand lines changed, and no way to split it off.
I ended up spending the best part of a day reviewing the whole thing and requesting changes.
Even with the long list of improvements, however, I wasn't sure they would get the magnitude of their fuckup.
So I decided to use a real-world, palpable way to show them what they had done: I went and printed the github diff for that PR. It rendered the glorious amount of 73 pages.
I'll never forget their face, and those of their teammates, when I barged into the room with a thick wad of paper and deposited them on their desk.
At least it worked. I never saw another big, ill-thought pull request from them again.3
Yesterday I had my performance review discussion with my manager after about 6 months into the job, which is my first dev job. Before this, I had spent about 2 years in a support role after graduation, but always yearned to build something cool and be a full time developer. Hence I had made the lunge in spite of a pay cut into a development role.
For the past 6 months I was asked to develop a bunch of features on top of legacy code which is ~15 years old. I did my best and brought in the best ideas and practices onto the table and delivered on time. The features turned out great. I enjoyed working with the team and the team loved me back!
But at the back of my mind, I was hoping that I would get to work on something new and relevant. To quench this thirst, I used to spend my personal time on side projects.
The managers and the leads who have been observing me all along, told me yesterday that my manager got AMAZINGLY positive feedback from the leads and my teammates (who are like 10 years senior to me). Going forward, I get to work on any CRAZY idea and pick up any technology I like with the goal of revamping our product. Essentially I get to work on my side projects full time as long as it adds value to the company.
Wish me luck. 😎1
So, as some of you know, I've been on a team with a real asshole. Yesterday, we were supposed to present.
So, my teammate as of Thursday started barking out orders about this project. Mind you, we've had five weeks to work on it. He complained that he needed access to the repository. I discovered he hadn't even used the github invitation I sent him...five weeks earlier.
As some of you know, this isnt even out of character for this guy. He's a skilled manipulator and asshole. So, like I said, as of Thursday he was frantically barking out orders, trying to get it finished. Needless to say, the response of myself and the rest of the team was to spam him with sarcastic gifs. (Love how Giphy is so well integrated with Slack.)
I considered tying 3 or 4 gifs to his account, so everytime he talked, it could just spam the shit out of him. Didn't do it, because I didn't want to make a mess my teachers would need to clean up. Like I've said, they've done a great job.
So, this fucking dickhead who hasn't even looked at the repo is freaking out, trying to manage the project, nine o clock the night before it was due. Honestly, it was hilarious.
So, we get to class the next day, and this fucker, serriptiously wasn't there. Now, I could have sworn he'd show up because dude is a skilled sociopath, he knows how to appear busy.
Anyway, first thing, our teacher apologizes for that teammates performance. He says that now, that teammember must essentially finish this project by himself by next week. Remember the scope is five weeks long.
It gets better, they didn't read his name as a graduate. They read the names of people who hadn't been there in a month, but not his. I'm pretty sure in order to graduate he must finish that project in time.
Thats several thousand dollars he likely flushed down the drain. Well deserved for a scummy manipulator like him.
Moral of the story: don't get mad, get even. It came out over time how little work he had done. It didn't require any of specifically telling on him, the teachers asked and we answered honestly. Never stand up for someone who is trying to take advantage of you. Don't worry about planning some Edgar Allen Poe kind of revenge. Make that motherfucker reveal themselves, expose their bullshit, because the truth is far and away the worst punishment for a liar. :)4
*Programers can't spell*
In a previous job, I once spelled inquiries as enquiries. It was a service and it was used in many places throughout the app. Somehow, it made it through peer review and even my teammates started using the misspelled word.
I didn't realize my mistake till months later and by that time I thought it was too much work to fix it (or I was too lazy).
I'm pretty sure we even misspelled it for the on-screen texts.
Moral of the Story: know how to spell shit7
Since I started reading devRant the productivity of our team dropped a 20%(we are 3 people). Yesterday one of my teammates asked me what was going on and I showed him devRant.
I don’t think we will survive next split.1
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!
New semester, new problems....
Just started my 6th semester at uni and my teammates are already proving to be serious dumbfucks..
They want to keep all files neat and organized, sure, fine, good idea.
They want to use Dropbox to store code and our LaTeX report, no, never! Somehow managed to get them to switch to GitHub, yay!
They want to have everything in one fucking repo! Why? Oh god, why? And I can't change their mind on this!
And they still want to use Dropbox to have a backup and sync between their machines...
So during this semester, we will store our LaTeX report and the, at minimum, 3 code projects, in the same repo organized by folder!
Why not one project, one repo? Then I won't have to pull all the shit code that I don't have to work with!
Expect more rants in the coming months...2
Fucking teammate who did not know how to read/write a simple class diagram.
We warned him that he have to study or we just kick his fucking ass out of the team.
He just did nothing. When we had meetings he just stayed at home pretending to have an heart issue needing surgery.
After just 2-3 days he was tagged on FB in a photo shooted a few days earlier where he was riding a bike for a competition.
He skipped another scheduled-a-fucking-week-before meeting saying that he was on a surprise trip, when I called him 5 minutes before meeting start.
In the end we just kick him out because he did nothing. He went to professor talking about some relationship problem in the team and asked him if he could continue the project by himself just forking the ours.
Professor said HELL NO SON OF A BITCH.
But our team learned a precious lesson : choose your team carefully.6
Calls between Saturday morning at 6 am and Tuesday night at 5.
*does not include calls my teammates worked*22
One of my teammates was pulled to help on another small project... He started to get overwhelmed with being on two projects at once, so I volunteered to help with this project as well. Expecting to just help with his load, he is being transitioned off this project and I'm taking his load...
Lesson: Do not help others.1
Tl;dr younger people on here, especially passionate ones, don't worry about comparing yourself to people who appear to have tremendous laurels, those people are probably completely full of shit.
I say kids because you may be like me and more likely to underestimate your ability or more likely to be modest about your accomplishments, and you're too young to know you're doing that.
Either way. I've been doing a web development boot camp the last six months. It's been quite good with the teachers, and some of the classmates. Hell career services is now run by this woman who really actually seems like she knows what she's doing. It's pretty awesome.
That said, my teammates on the group projects have been a different story. I've primarily stuck with some of them out of loyalty and friendship. But one guy in particular has pissed me off to no end. He said he was a computer scientist going for masters. I thought I could learn from this guy. Now I wonder if he's a pathological liar.
Our first project he made one commit. Ripped straight from the homework. It was a simple api mash-up so alright. Fair enough. Next project was when he really started to piss me off.
He didn't do shit the first week and a half. No PM, no design, no programming. Nothing. Comes in two days before project is due, and me one other guy are fucking scrambling. Because of course no one else is there.
I live significantly further than my teammates mind you. We're busting ass. This fucking guy, this dumbass pick who is convinced he's a genius that will work in higher academia clobbers our whole fucking repo.
Why you ask? To put in an unrelated commit that replicated homework from the week before. Why you ask, again? Because this person is a borderline sociopath trying to appear busy in the commit logs.
We're onto the third project now. I spend days designing something original. Side note: I fucking hate design.
So I design my heart out come up with something awesome. This fuck ass, disappears. And another group member. This was the end of November, I hear from this prick last week about refactoring to ES6. But here's the kicker-fucker, our shit ALREADY WAS IN ES6!
I go in Saturday, slack a message I'll be late. I see this fucking "genius dedicated computer scientist" leaving the fucking university shadily checking to see who was watching. He saw me see him. Coward tried to shrug it off.
Here we are, end of semester. He gets the same certification as I do. The difference? I actually know what I'm taking about, I haven't paid in full to fail.
So never, ever fucking ever take what someone says on their resume or LinkedIn as truth. The better it sounds, the more full of shit they may very well be.
And as for our presentation on Saturday? I plan on handling that but letting him do all of the talking. Let's even see if he knows what the project is about :).6
One thing I learnt after over two years of working as a programmer is that sometimes making your code DRY is less important than making your code readable, ESPECIALLY if you're working on a shared codebase. All those abstractions and metaprogramming may look good in your eyes, but might cause your teammates their coding time because they need to parse your mini-framework. So code wisely and choose the best approach that works FOR YOUR TEAM.9
Resumes don't mean jack shit!!
I just got off an interview call with a candidate for a hardware role. On paper this guy is absolute gold, having worked for some of the best robotics companies and research groups(in India at least) It took me an hour to realize that the was just spitting out buzz words. So I started asking him some very fundamental questions, like ohms law and such.. high school stuff. But, phrased in real world terms. And it took me another half an hour to realize that the guy is dumber than a sack of peanuts!
I can't believe how easy it is for people to coast by on paths paved by seniors and teammates. By any objective assessment this guy would be lucky to get a job as an electrician and instead I'm wasting my time interviewing him for a six figure salary (well, the Indian equivalent). Gaaah!!6
Actual conversation today with one of my remote developer teammates in Ukraine
Me: "next up I'd like to discuss the 'bigger picture' so you have context for the next tasks..."
Dev (after an hour or so and some chat in between...): "Yes, could you please send more details about a large images issue?"
Me (somewhat perplexed): "what are you... oh! Haha"
My former teammates used to store multiple local copies on their computers, as a form of version control, and pass bits of code on USBs to share their work.
I gave them a fair warning about the importance of working with git, and then one night, I just stole all of their HDDs, leaving them codeless.5
But towards the end of the deadline we were sitting and refactoring each others code since we had not decided on the coding standards and practises and random code had been written left right and center.. It once happened that the same piece of code was refactored multiple times by only 2 people..
And it is obvious that we couldnt make it to the deadline and that code is sitting there like a mixture of weird things..
Before I became a Computer Engineer, (actually, this job is where I learned I loved programming) our manager would pull us into a team motivational meeting.
Except she was a bit of an airhead, so her idea of motivation was having a sing-song and listing our favorite movie quotes.
It was even funnier because there was lots of drama surrounding "how she became our manager," and one of our teammates felt as though she should have gotten the job.
Anyway, none of those were the most ridiculous meeting.
The most ridiculous meeting was when the VP of marketing came to town from Florida to address the brewing drama.
In this meeting, all of my teammates suddenly had the delusion that we were in a union and thought they were protected from getting fired. They threw our manager under the bus. I was the only one who could see that he was there to see if our department was worth saving. They thought they were going to get rid of our manager by shitting on her, but they were just confirming his suspicion that there was a bunch of bullshit going on all around.
So I approached the VP after the meeting, and long story short, I was the only one who got through layoffs with a job offer in Florida a couple weeks later.
I didn't take it, because by that time I decided I wanted to go to school for Computer Engineering.2
My first post here, be merciful please.
So, I participate in game jams now and then. About two years ago, I was participating in one, and we where near the deadline. Our game was pretty much done, so we where posted a "alpha" version waiting for feedback.
Just half an hour before the deadline, we got a comment on our alpha alerting us of a rather important typo: The instruction screen said "Press X to shoot" while X did nothing and Z was the correct key. "Good thing we caught that in time, thankfully a easy fix" I thought.
This project was written in python, and built using py2exe. If you know py2exe, the least error-prone method outputs a folder containing the .exe, plus ginormous amounts of dll's, pyc files, and various other crap. We would put the entire folder together with graphics and other resources into a .zip and tell the judges to look for the .exe.
Anyway, on this occasion I committed to source control ran the build, it seemed to work on my quick test. I uploaded the zip, right before the deadline and sat back waiting for the results.
I had forgotten one final step.
I had not copied my updated files to the zip, which still contained the old version.
Anyway, I ended up losing a lot of points in "user friendliness" since the judges had trouble figuring out how to shoot. After I figured out why and how it happened, I had a embarrassing story to tell my teammates.3
So I recently had a university project which focuses video game audio. We had to work in groups of 3 students and the task was to create a video game which uses audio as a gameplay mechanic.
Our idea was to create a game where you collect different audio samples which get looped as background music, and you have to select the correct ones to have a nice tune. To make it a bit more challenging we had enemies, guns and grenades plus doors which only open if the correct music is playing.
The guns fire on-beat, and the grenades always explode on the first beat of the next bar.
It was quite challenging to get things synced since even small offsets are noticable.
I wrote some nice code and theoretically it should have worked but for some reason the gun shots and the grenades didn't quite hit the beat of the music.
I tweaked stuff, created workarounds, optimized lot's of code to get execution times down but it still only worked sometimes.
I tweaked more and more only to realize that the timing drifted over time.
At that time I worked 20-30 hours on tweaking and trying to get it perfectly timed.
After recalculating some numbers I realized that all the audio samples are recorded at 135 bpm, but the guys who did the recordings said it was 130bpm.
I asked them if it could be the case that the samples are 135bpm and they said:
"yes, they are at 135 bpm as we told you"
I scrolled back in the telegram conversation only to see that they said 130.
Changing the number to 135 resolved all the problems and all of my workarounds and tweaks weren't needed.
So I worked for nearly 30 hours just because they didn't notice their fault and even when they realized that the timing is off sometimes (which took forever because they never played the game), they didn't even consider that they might have given me the wrong numbers.
This all wouldn't be that bad if both of my teammates had worked for more than 15 hours but they didn't. I did all the hard work and the only single thing they did fucked up my workflow. It fucked up the system I created and it fucked up the gameplay as things got unpredictable. Because of their fucking fault I worked as much as both of them combined IN ADDITION to all the other work I did (built 3 maps, coded everything, created animations, ...)
I love working in teams, but only if the whole team is motivated. Those two fuckers were the exact opposite.
Luckily i found the error so I could fix it, but guess with whom I'll never ever work together again?12
!rant but emotional
Work is significantly less terrible than it could be because I have the best teammates and i can come rant here and be understood. My non tech friends just ask why I don't quit if I "complain" so much. My dev and tech friends are all together at another company and have releases every week they're working on. I appreciate you all and am happy I found this community. 💚1
We all know that being distracted while coding is frustrating. That's why me and my teammates (we are 3) we "protect" each other while on "full dev mode" - meaning anyone coming to disturb one of us while in that state, the other push him/her away.
The most productive 2 weeks of my life 😂😂1
What do you do when another dev overwrites/changes your working code without telling you, only because s/he cannot understand how your code works?
And your code was working fine, mind you, no bugs or anything, and is following recommended guidelines/standards. It's just that this other dev has a different coding style and prefers to rewrite everything his/her way even if it means breaking up otherwise sound logic.7
In pull requests, I point out every spelling mistake, unnecessary whitespace and formatting issue.
It's not really a bad practice, but my teammates don't like it.2
This is what u get when u trust your teammates on a group project.
Not my fav function, but I was rofl when I saw it 😂
That is, until the frustration of working in a group kicked in11
I missed a week of school while I was sick, and in that week my teammates made a deal with the client to have a prototype for him in 3 weeks, AFTER asking me (teamleader) how long it would take (4 weeks min.). Why don't they FUCKING listen to their teamleader!! They're gonna have a bad time in the future...
And now I have to spend my whole night writing a prototype because THEY told a wrong estimate...3
I have a colleague, let's call him Zigo.
Each time we have a technical discussion inside the team Zigo wants to always impose his opinion. Even if it's the dumbest thing ever.
Zigo thinks he's always right.
Zigo never accepts other's arguments.
Zigo thinks he's smarter than everyone...
Hey Zigo... f**k off and learn to respect your teammates.
I'm sure all of you have (or had) a Zigo in your team.
PS : I've known people that were like Zigo, but they have the technical background & knowledge that "allows" them to be like that. The only problem is that our Zigo doesn't have all these qualities...
PPS : sorry for my English - it is not my strong suit.1
It's been a while I haven't check devRant. Been very busy and spending a lot of time with my teammates; knowing each other since we transferred in one room and can't avoid joining the small dirty talks with my colleagues since I'm the only rose among the thorns. :/
So anyways, I missed being in here. I missed ranting about my boss and coworkers, swearing a lot and following your rants. Got to randomly check my notif and catch up with you, guys! ;)5
50 hours straight.
Attended a hackathon for 3 days and sadly when it was time to sleep the "sleeping arrangements" were already taken by some other teammates and there was no place for the rest. So me and 4 other teammates decided to work through the night and day to finish everything so we can go home and sleep.
Finish 3rd in the hackathon tho, not bad for a first time.😁3
So I'm on vacation right now to visit family. I received an email from the head of department that, due to our department getting 7 new hires in one day, the seating arrangement has been changed.
My new seat is next to this one developer who's old enough to be my dad. He's a very nice guy and all, but the problem is he burps ALL. THE. TIME. I've never met anybody more gassy. His burps don't stink, thank God, but they're loud enough that it's seriously jarring.
You know how us devs can be completely in the zone until some marketing dickbag taps you on the shoulder and asks you to check your email or help with something that is absolutely not your job and you completely lose all focus and have to start over? Its exactly like that, except it happens every 10 minutes.
Another thing is, my back is now facing away from the wall, towards the rest of the office. The nearest section to mine is management. That means that anybody, including the CEO, can walk up right behind me and see what I'm doing at all times.
I really hate that. Id much rather be next to the wall to have some sort of privacy. Somehow sitting next to burpy guy is still the thing I'm most annoyed about though.
I tried to ask for a different seat, but my manager effectively said that I have no choice but to sit there because that guy is part of my team, and teammates should sit together. He forgot about the fact that, while the work him and I do is indeed related, I've been working on a solo project for the past few months and I don't need to be next to anybody in particular because I'm the only one working on this thing. Theoretically, I could sit in the toilet with my laptop and get my work done just fine. Maybe when I talk to him face to face in the office I can convince him to have some mercy on me.
The bright side is I'm very excited about meeting those 7 new hires I mentioned. They seem to be smart, capable people so I look forward to working with them and learning from them. Every cloud has a silver lining. 😊7
My biggest obstacle? Stupidity, laziness, willfull ignorance, procrastination.
Sometimes my teammates are the ones guilty of these things too. That, and impossible timetables, but that's par for the course for pretty much all of us.4
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
Spent half an hour arguing with my teammate about where a method should be.
Then we discovered that both ways were wrong..
On a company event. Supposed to do some water skiing.
I'm no fucking Jesus, I can't walk on water! Leave me alone!
Also, I am NOT interested in seeing my teammates in swimsuits. Yikes!3
Hey everyone, I want to start an IT company that focuses on web and Android applications development. I along with my teammates have planned to take freelancing projects from various websites in the beginning, I was thinking if you guys could guide me or give me some tips to jumpstart my career and the tips may help me in the long run.
Thanks in advance.
PS my team is fairly experienced since we've been working on local projects since 2014.15
My lead loves to over engineer crap and waste weeks building complicated solutions.
And then during retro when a team member has the stones to say we should've thought about it a little more or used the input of some other teammates, he shuts them down by saying that more input would've been bad for the design. I can see where he's coming from, but he always seems to have an excuse for us. Why can't he just be more transparent and clear with us? If he has a problem, just say it. That's what retros are for.
Oh and then he takes a shot at me saying that we shouldn't have built a UI in tandem with it. I didn't even recommend a UI for the thing. All I said was that if we ever have a UI, we should consider a database setup that assists both the server and UI. But nooo, he's stuck with this "server design" approach. Everything has to be built to make it easier for the server.
I still don't understand why anyone would have their server logic influence the design. Especially the database. I just seems too targeted. It just creates these nasty denormalized tables.
Ugh... Our team is getting dragged around by this arrogant and silly man.
My first project it’s an emotional roller coaster. I was a little trainee/ junior dev at my job with a little more than a month learning RoR and one day my tech lead receives an email from the big boss saying: “We got a big client who wants a total redesign of his web and we said yes we can do it in a month, so please check if anything it’s reusable”, after reading my tech lead said to me “Do you want to help me with this ?” And well, we spend like 2-3 hours checking all the controllers, views, assets, etc. We conclude that the project was mostly front end changes and the back end will stay the same, so yeah it can be done in a month. The next day in a meeting with all the team I was nominee to be the person in charge of that project, because it was an easy project and all my teammates hate to do front end stuff, so I take the challenge. After that I met the Project Manager, another guy who recently start as PM about a month, so yeah we were two new guys who need to handle the project of a big client, nothing can go wrong. We did the planing, I give an estimation ( first one in my life ) for the tasks and added like 4 hours in case anything goes wrong. Then the first sprint came by, and I couldn’t finish it because the time given to some features was to low and the “design” was a mockup made by the PM, ok, no problems, we add more time to the tasks and we ask for a real design. At the half of the sprint the client start adding more and more stuff, the PM doesn’t talk back, just say yes yes yes. Then in a blink of an eye the easy project became a three months projects with no design at all, two devs ( a new guy who recently begin as dev enter the project ), just mockups and good hopes. But somehow we did it, we finish it! Nope. The early Monday of the next week I received an email of the PM saying we would have a second version and the estimation of the tech lead was a minimum of six months ( that became 8 months). This time was hell, because the client doesn’t decide what the hell he wants so a task would take a couple of days more or so, the PM became the personal bitch of the client, but it wasn’t his fault, because we later knew that the company became partner with this client and because of that the PM didn’t have too much choice :/, the designs were cool, but they weren’t on time ever, our only design guy had to do designs to our project and another 5 projects of the company, so yeah, we weren’t the only ones suffering. At the end we survive, the project was done and the client somehow was happy. Of course the project didn’t end and it was terminated half a year later, but I’ll always remember it because thanks to this project I was given the opportunity to work as a Front end dev and I’m happy still working as one.
Imma be real with youse, i havent been posting shit cause i have a great job with great teammates and great management. Like it a rant that i cant rant but thats a good thig i guess. But ion wanna see devrant community goin down the gutter cause old members r leavin so imma stick around and post stupid shit in the comments as usual. So youse can stop bothering me bout bein inactive hmmm3
You ever have to work with people that are worse than you? and yet everyone in the group sees them as more competent? So much so that they get to be involved more with the projects than you are?
I hate this feeling, I'm just as good.
My worst collab/group project experience definitely has to be my final semester project during my undergrad.
We were a team of 4 including myself and would meet every day to work and every day:
1. My teammates would show up late
2. One of my teammates’ girlfriend lived in my apartment and shed just show up every day and waste our time and make him never contribute (He LITERALLY never did any work and got by with no effort)
3. The other 2 on the team didn’t know anything and never made efforts to learn
I literally did the entire project on my own (Code the full project, make presentations for all the reviews, and teach the other 3 every step of the way).
TLDR: I topped my batch and got 199/200 whereas everyone else were 190 or below, and I went on to publish that project in a Science Journal (Again, with no efforts from the team)1
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
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*
That dreaded script ran on main dev server and fucked up the server used by a team of 15+ teammates. Dead.2
In "Sprint Planning", the team is supposed to come up with stories, break those down into tasks, estimate those tasks as a team, then let devs choose what tasks they want to work on based on the stories pulled into that particular sprint.
Instead, our manager creates the stories. He assigns the stories to each developer and then has that developer announce his theoretical tasks (without any research on feature's or project's requirements!) in front of the entire team. So, when I say, "I think it will take me 6 hours to implement this feature", he says, "6 hours? I think it will take 3." and then types the estimate as 3. I have so much rage when that happens. Then we continue to sit in the room for 2.5 hours where we go through this long data entry mess of him typing out tasks and second guessing estimates. There is no team deliberation or collaboration, its whatever the manager says.
While there are many issues I take with this approach, my pet peeve would be the second guessing of the estimates. It would make sense for teams members to second guess estimates as long as they are the same teammates who have the ability and possibility to take on the tasks themselves.
But I disagree with a manager seconding guessing an implementation feature that "I" definitely have to do alone, and they do not possess the immediate knowledge to implement it themselves.5
Just came back from vaccation yesterday. During sprint retrospective today I hear my team was having trouble dealing with the API layer (which was mostly written by me). Suggestion was a session where I sit and explain the application to the team ,which I have no problem with.
One of my teammates asserts that it's written in such a way that "only the person who wrote it can modify it".
Agree to disagree but whatever. This thing goes through code review everytime I push changes to it. If there was a problem I don't know why he's just discovering it 6 months into the project. I assure you there's no rocket surgery going on. The problem is that I have been doing everything on that side of the project and nobody was curious enough to give it a read sometime. In fact I dont think anything needed to change while I was on vacation, they just didn't have me to troubleshoot every problem for them like usual 😤
Update to my last rant:
The best teammates are those who don't give a fuck about the project until one week before the deadline and then have the fucking audacity to tell you what to do.
Some people really need to read their error messages.
Just now I got this teammate asking me how he should handle the error git returned. The error message stated: "Please commit your changes or stash them before you merge." He asked me what he should do to fix the error... I was astonished by his stupidity that he did not read the fucking error message.
Almost every fucking time a teammate comes to me with the question how to fix an error, there is a message that says how to fix the error. Why don't they read them?!?! I told you so many times to read your fucking error messages!!!
I'm really glad the project is over in a couple of weeks and I get a new team..2
So another story about college and stupid team assignments that I have to be responsible for dealing with.
So we had an assignment in operating systems 1 course, it was about memory management and we are a team of 3. Then came the time when we should discuss this assignment with the TA and that day I had to stay all night finishing a project in software engineering (literally giving us a description of a big project because that's what the course teaches And I had to finish it in one all nighter alone because my teammates just gave up).
When the discussion time came I was really tired and then the TA asks me something really simple and I say it but then she tells me that I'm wrong so I wondered a bit and then said no what I said was right! She then asks my teammate (who we are supposed to be good friends) "did he say the right thing?" And his answer is a definitive "NO he's wrong" and then he starts to say the right answer which I swear I said the same but in a different way so I start to say again that I was right and say that I said that just a different way and she took that as an insult and said that I'm shouting at her and being disrespectful to her.
When we finished I asked my friend if he heard me say it wrong and he said "I'm sorry but I didn't even hear what you said and I was afraid" WHAT THE FUCK, he just said that I was wrong to please her and make her feel like she is right and I had to be the wrong one even though I said it right but NOoo her pride is more important
All this was last semester and the second semester just started today and I go into operating system 2 and guess what? The TA got her doctorate and is now the professor for OS 2 when she doesn't even understand anything.
Really FUCK the academic system it feels like it is a grind more than actually gaining mastery of a subject.2
I work on a team project for a test and maintenance course in University. We agreed as a team to adopt a git infrastructure that would prioritize the stability of the master branch at all cost by only updating commits up to the next stable point and tagging every single release. We have a long polling development branch to prepare our releases and we create feature branches for the tickets we need to resolve. I even wrote documentation to make sure that we don't forget and protected the master branch on gitlab from direct modifications.
Can someone fucking tell me how one of my teammates managed to fuck over all of this and work on an unfinished feature straight on master?
N.b. I know that he probably edited straight from gitlab's online text editor because they have a big where they don't restrict modifications on protected branches.1
Debating on whether to quit my job.
Part of the reason it's hard for me to make a decision is there are a lot of good things about my job:
- almost all the projects we work on are blue sky; no technical debt anywhere
- great teammates; people help each other out and generally there's a good vibe
- reasonable boss; he's totally fine with me managing my own schedule, and since I get my work done, he basically never questions when and where I work
- about 1 hour of corporate meetings each week
- best healthcare I've ever had; basically everything is paid for
- 3 weeks PTO & all major US holidays
- free food; generally healthy office snacks and such
So why would I want to quit this environment?
- I hardly get to code anymore. About 2 years ago, I got asked if I would mind helping spec out projects. Since then, I've moved from writing code related to projects to helping my teammates understand the business situation so they can build the right thing.
- I'm in lots of meetings. So we have very few meetings for the company itself. We have a bunch of customer meetings, though. And progressively, I've getting pulled into meetings where there's really no reason for me to be there, aside from "we should have a technical person present."
- The sales people are getting tired of turning down clients that our product isn't targeted for. So they're progressively pushing to make products in those areas. Unfortunately, I'm the only one on the engineering team has any experience in that other tech stack. Also, the team really, really don't want to learn it because it's old tech that's on its way out.
- The PM group is continuously in shambles. Turnover there has averaged 100% annually for about 5 years. Honestly, IMO, it's because they're understaffed. However, there has been 0 real motion to fix this other than talk. This constant turnover has made it so that the engineering team has had to become the knowledge base for all clients.
- My manager has put me on the management track, but has been very slow to hand off anything. I'm the team supervisor, and I have been since the beginning of the year formally. When the supervisor quit last year, it basically became obvious to me that I was considered the informal supervisor after that. However, I can't hire or fire; I can't give a review; I don't have any budget; I can't authorize time off. So what do I do now? Oh, I'm the person that my boss comes to ask about my co-workers performance for the purpose of informing promotion/termination/pay increases. That's it. I'm a spy.4
Heard a story about an interview taken by one of my teammates..
The guy had approx. 9 years of experience of full stack development having current exp in JS based work.
He was stubborn on the condition that he'll work only on JS for the rest of his career and nothing else.
I can't understand people having a raging boner on one language...
P. S : I am a JS developer too!2
I'm the youngest person on my team, and I mean significantly younger, most of my teammates have kids older then I am. So should I be bothered when one of them calls me "kiddo"?9
Design team constantly needs help fixing bad commits and merges. (can't use git after using it for 3 years...) And boss wants to know why the ticket is falling behind.
After explaining I'm pretty much told that assisting other teammates is part of the job but I'm being paid to write code and need to stay late.... this is while I'm hitting a 10 hour workday already (skipping lunch). And btw, we aren't doing reviews this year because the business made some bad decisions recently and raises aren't in the budget.7
The best teammates are those those who don't care about the project for 3 months and then one week before the deadline ask: "Is there anything left to do?"4
Jenga driven programming:
Stack pieces of code on top of each other until everything falls down and you have to restart shit.3
So I've forgot to share with all of ya our first !!!SUCCESSFUL!!! GGJ Game!
Its called "Communism Overload" and its super hardcore.
Things you should know:
1. Its 2 players ONLY(You wont win alone)
2. You will break your keyboard
3. Only handful of ppl have successfully finished it.
4. There was one guy that managed to finish it alone and it took him a lot of time to master the skill of sync keyboard breaking!
5. Some ppl say that the instructions are unclear and they manage to stick their heads in toilets, so I'm attaching a small GIF of explanation.
6. This game gave us a new meaning in life, so its surely, not the last one.
7. Everything in this game, except for the music is my teams hard work. Every image\animation\line of code.
8. Me and my teammates would be freaking glad to hear you thoughts on this game (MADE IN JUST 48 HOURS)3
I need help.. I want to make a web app where me and my teammates can upload save files / project files. And then I want it to organize them by date, name, and file extension. Can someone suggest a place to store the files, host the app, and host/run the backend code.4
First rant here
Well thing is that my CS school did have teachers and half the grade was from a product presentation and half on teammates reviews.
My teammates mostly didn't have any idea what SOAP was. That was the theme of the project and we had to make a Webservice which they didn't even understood what it meant.
I spent one day from 8am to 1am trying to explain, in despair I ended up not sleeping, not eating, working 24/7 all the week and collapsing of exhaustion.
I was taken to the hospital, got back home but have lost time and had only implemented 3/4 of the functionalities.
The others (6) only did managed to make a basic GUI I would have to link myself. One of them, the project manager had done testing and lots of good stuff, made a 80pages report but the other 5 were shitty.
They all gave me the worst peer review grade but the manager, they got A I got C (ABCD scale).4
I am on my way home from an 8.5 hour non-stop call with one of our software suppliers...
How to you guys handle situations like that?
Consentrating became very difficult at the end to be honest.
And if it my teammates would not have been there (they gave me food, sth to drink and filled my coffee cup) I would have snapt after 4 hours...
The only thing I feel capable of doing for now is to listen to extremly loud music9
I'm in a senior level game design course, where me and two others have to create an actual game. I picked my teammates out bc I thought they've already taken classes in the subject(as they are both seniors and I'm a sophomore taking this as a final class for my minor). Turns out, they haven't taken any courses in game design and know nothing about the basics of making a game... FML, good thing they can code I guess lol.😅😓2
Everyday at our standup with my team we chant "Aaaand Break" at the end, Today my manager gave me a new task to come up with a new routine chant for our team standup tomorrow, I have no idea about what to come up with- Any thoughts ?
I just have "go team" in mind, does anyone here do anything similar, want to hear your team disperse chant.?10
Best experience: web development boot camp with serious and knowledgeable teachers who work hard. Classmates that are skilled professionals looking to succeed.
Worst experience: web development boot camp where the administration are jackasses. The career services are useless. And my project teammates are mostly lazy morons.
8 hours straight for school project! I wanted to wrap things up... Deadline was approaching...my teammates no where to found..(fuck them btw)..but hey I learned a lot!😊😎1
Does every project have that guy who likes everything organized and strives for it, but at the same time there is nothing to organize because he doesn't do a thing?1
!Rant, rather a small question.
Few weeks back I have provided Python lectures to my teammates and they were so happy that my manager raised my name for one of the major python resource (though my core work is CMDB, just to ease my work I have learnt Python).
Today I came to know I have been SPOC from offshore liable for entire integration team in JAVA. I don't have much knowledge in JAVA and without asking me they gave me. I'm confused what to do? (Write a mail and say No or simply accept this new challenge) :(16
Two (2) senior developers and one (1) senior tester left our team and I am left with two (2) Java legacy applications that are hard to maintain. Here is a list of things I hate about these old webapps (let's call them app A and B):
1. App A depends on 80% web services. If one web service for a product or warehouse goes down, work flow is impeded while prod support team checks with the core services team for repair
2. App B is a maven project with multiple modules dependent on libraries that are dependent on company's internal libraries. So if we want to upgrade to OpenJdk 9 and up, the project will definitely produce a lot of errors due to deprecated/unsupported codes
3. App A is dependent on Tibco and I have no experience on that
4. App B's continuous integration build tool is Jenkins and the jobs that build it has a shell script that wasn't updated during the tech upgrade enhancement. The previous developer who did the knowledge transfer to me didn't tell me about this (it should be considered a defect on her part but she already resigned)
5. App A when loaded in eclipse IDE is a pain to work with since it is only allowed to build a war file using ant. I have to lookup in quick search instead of calling shortcuts (call hierarchy) because the project wasn't compiled via eclipse.
6. It's impossible to debug app A because of #5
7. Both applications have high priority and complex enhancements and I have no other teammates to help me
8. You never know what else can go wrong anytime1
Sitting in a bar with a senior colleague (Me - Student part timer, Him - 15+ Years of experience).
We started talking about our projects and he mentioned that after this, he'd get to spend his evening fixing a git merge, which went wrong because one of his teammates used cherry pick and thus messed up the history a bit (oversimplified).
So he tells me he'd be spending hours to get an overview of his colleagues codes (multiple devs and only team leader knows who does what exactly).
So I suggested he revert these cherry picked commits and so could maybe solve the problem in less time.
He thought about it... Told me HE didn't think of that and thanked me for my help.
Long story short: Today was a good day :31
ima sound cocky but
my new team may have ppl who know more in general than me - and that's a great feeling1
So I'm at this gaming event to enter in a small game I have been working on with fellow teammates. As an OOP, does anyone find the following conversation hmmm, odd?
Guy: I program for Microsoft!
Me: That's great! What's your favorite syntax?
Guy: I don't want to get into that? Me(inMyHead): 🙄😂😂😂👍🏾4
It was the worst local Hackathon. It's not even a Hackathon either, where the whole event spanned over 2 months.
It was a group entry with me and 4 teammates. Each of them did contribute:
Guy A: criticizes what is built and designed
Guy B: offered financial tips on how to make this thing feasible
Guy C: did UI but in graphics. No CSS file, just bits of graphical elements.
Guy D: family commitments
And then there's me, writing documentation, built the entire project, wiki, drove the project, prepared the presentation slides, tests the framework, unit tests, stuck with stupid problems like SSL, localhost, Google Maps Key and the likes.
And we didn't even win, let alone launch this thing, whatever it is, to anywhere. Never doing group projects again.
I'm flying solo for now
*Writes CloudFormation Template.*
"The cycle repeated
As explosions broke in the sky
All that I needed
Was the one (JSON Invalid Format :| ) thing I couldn't find
And you (Teammates) were there at the turn
Waiting to let me know
We're building it up
To break it back down
We're building it up
To burn it down
We can't wait
To burn it to the ground
Me: "FML :| "1
My Teamleader is such a dick, he has mental and isn't able to act as a normal human being. The year started with his disappointment that we didn't worked for the company during the holidays! Sorry, but my family has higher priority than the company, especially during the jolly days, you lonely nerd without any interest beside sitting in front of your computer all day long.
He managed to get me thinking about moving to another company. I need the harmony in the team and won't fight every single fucking day. I noticed that I get very nervous when he enters the room. Everyone in the team is hating to discuss things with him because he knows it better.
The problem is that we're a small team with big responsibilities for each developer. Loosing one team member is quite hard to compensate.
Should I still try move? I guess the harmony with all your teammates is evenly important as it's in a good relationship, right?4
Let's see: Right now I am in two recruitment process of two enterprise.
One enterprise (Genexus, a big enterprise) I would join the I+D team, good salary, EXCELLENT work place, and 2hs of travel from home.
The other enterprise (InnovaAge, a little but powerful enterprise in grow) I would join as trainee / junior developer who helps in the development team and I would constantly learn to become like my teammates, same salary than Genexus, good work place, and 1.5he of travel from home.
Same working hours amount and same salary but InnovaAge have the GREAT advantage of be near from my University, Genexus is TOO far from there.
So, I ask you: if both enterprises would want to recruit me ... What offer should I accept?
I ask to you because you have more knowledge and exp. You are lvl 20-40 xD2
This was a project for school, we had to simulate an app that traced bus routes over a map.
All the teams but mine do it in Java (desktop app), we took another approach and did it on Android with the Maps API.
I had fun coding a parser, this parser job was to read a file and load the bus routes and draw them on the map.
It was structured like:
The fun part was coding and telling my teammates "chill out, it will work", so we finished, built and run and... done! First code working smooth AF.
I know it's a simple parser and a simple app, but it was a nice feeling not having to debug the app.1
Playing Battle Royal with friends, had to leave 2 of 4 teammates behind as the play area was shrinking and they couldn't be rescued. The 4th player ran me over with a game car just to get revenge for our other team mates.
With me alive we actually had a fighting chance to win the round. (8 kill streak and lots of ammo with a decent tactical position) ....but NOoo the fucker thought it more sweet to kill me rather than help me win the round!
Fuck this shit, I'm out!1
First job while in college... Was working for web dev team lamp set up before lamp was lamp (year was 2000).
Had deadline one week after summer vacation. Worked non stop a couple of days to get shit done and didn't make it. Got in a conflict with my manager in front of the team and I blew my steam off. Quit on the spot.
1. Don't be a fucking idiot when estimating work.
2. Be cool with other teammates, nobody cares about drama and nobody has to feel sorry for you.
3. Uhm, plan? Had entire fucking vacation to get work done. I was a fucking moron.
4. Burning out is stupid and unproductive.
5. Your manager can be as poor in management as you are. Your job is to try to make them better at it, as they have less visibility in the details.
Next job in grad school. Worked for a security company. Direct manager had the bright idea to make execs sign the change requests. WTF. Code was in Perl/php, a mess. Team rewrote back end DB access , taking over six months, or more, failing twice the deadline. After a final 48 hour burn out, we ship and get laid off the week after.
1. Don't work for dicks.
2. Don't be a dick yourself.
3. Don't work for dicks.
Third job was in silicon valley. It was a great company, and I stayed there for five years.
Pro TIP :
If you have a lot of work and SOMEONE from your team is disturbing you every hour,
Move away (alone) to a meeting room, away from your stupid teammates for one day. For High productivity work.1
Doing overtime during my notice period. Don't like the company but love my teammates. One for the team. Fuck my life though.1
Today is just another one of those days. Having to take (paid) time off from work and play golf at Topgolf for the after noon, with free food and drink,with all my teammates. I love this company!
When you tell one of your teammates this would be a perfect feature to develop using TDD. They agree, and after a couple of days they send you a code review with 0 unit tests and a message saying "I will start working on the tests while you review this."
When you work for a multinational organization that's adopting scrum. We don't swarm, our PO isn't even in the same building, and one of your teammates hates git (loves TFS).
Fake it till you make it I guess?3
I posted a rant a while back about a contract I was working that was making me particularly unhappy.
I didn't notice at the time but my studies had taken a turn for the worse, my concentration had begun to wane and I started struggling to finish work.
I was miserable and the client had figured and pulled me up on it, I turned the working relationship around and the client was happy.
That was two weeks ago, Monday I was called into a room with the managers, manager straight to the point "contract is being cut short" (I was contracted to the end of the year but was seriously considering handing my notice in that day anyway).
They made the decision for me, awesome!
Also I was given the two weeks notice as paid but asked not to come to the office again and had to hand in all my equipment that day.
Could I have been that much of an arsehole to deal with that they thought it would be better for all concerned that I have no further dealing with any of them?
Talking to teammates it does appear that I was getting special treatment from management, I think if it is me I need to address this before moving on to the next contract so I don't get myself in the same predicament.
Although two weeks paid leave was a quite nice bonus 👍
I was asked to revisit some code yesterday - code that I had written at a much better time in my life. I was productive, I was on top of my project and we were delivering value to the organization.
I'm at a point now where I haven't written any code for months. I've been documenting and designing and arguing with teammates over inane shit. It's been an absolute slog, and I've started looking at what it would take for me to actually quit since I've got a kid on the way, and I've been bringing the stress and anxiety home from work. I've got so much money in options and salary, it's basically impossible for me to leave for better work.
I'd consider this the lowest point in my professional career. Four years of college - where I beat alcoholism and depression (mostly) only to end up at a place that I fucking hate, but cannot leave. It's affecting my family. I've drank more in the past 6 months than I have in my entire life.
And now I have to start repurposing old code to work on a new project that is fucked up 5 ways from Sunday. I honestly don't know how much further I can stretch my professional ethics to keep this shitload of cash flowing into my savings.2
In every team there would be a "git spammer", who always commits on top of other's commit just to increase the number of commits.
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!!
Really WTF ... am I the bad guy for caring about my team??3
Every other engineer in my team: "I just pinged Avellable[me] on hipchat 5 seconds ago. He hasn't replied. Maybe I should go to his desk and poke him."1
First of all I am an applied computer science student in the second semester.
We've got a few assignments and the first set went fine but this last week boy ohh boy - first of all today I got noticed by one of my two teammates that the other one won't get stuff done in this assignment (he also did next to nothing in the first)
Also the the assignment is unclear and the given methods and parameters don't care about naming conventions (for one method I don't even know what it should do). Also we have to use new liberies (java.io etc.) and learn them on our own so far it would be okay, the time limit is two weeks, also doable
BUT the same chair also made one assignment for web development with the same deadline and also no explanation how to do stuff.
I don't say I am perfect but the expectations are too high, while also studying for other modules2
when you're already at the verge of getting the right code when suddenly your teammate asks you what you want to eat for lunch...
I'd like the ability to convince my teammates to gradually work on a project rather than working obsessively on it the day before it's due. I don't like waiting for the last minute to get things done, I like finishing things early so I'm not stressing myself out.
I'm helping my teammates with the problems that they face in debugging an issue or fixing a Dev environment.
Sometimes ppl go too flexible and ask for my Dev VM. The help I have to offer is tell them cause of an issue and tell them the fix that they have to give. What the fu*k they do? What did they gain as experience all these years.
Ppl don't know how to make draft commits. They can't fix but failures. They don't know anything.
They just sit at office and age as it is their only job.
Seniors take so much salary. Why don't they feel bad that they are not doing justice to their work.
I always ask my teammates to git by saying
"git commit repeat"
I need a more catchy line to using which I can ask them to git.
Can you suggest?4
How does one get experience on working in teams if every project I've built has been solo because of a lack of developers from where I am from?4
Intelligent Development class (yeah, that's how it's titled), teacher leaves us as first task to develop our own Database, because later we will make it a fuzzy database.
She gave us three days. Three (counting me) in the team. I began working on Interfaces (Java development) and so on, using GitHub for VCS and documenting each method.
This assholes didn't even ask what was missing or what should they do. One day before date, I told them "Hey, I think I can nail the underlying file management tonight, so, work on the language parser, please"
Stood awake until 1 A.M., waiting for their reply, but there wasn't any.
Next day, I'm the only one of the team and I tried to decline the presentation of my work, but a friend encouraged me, because it was my work and I worked hard.
Presentation went better than expected.
After the class, I have another with one of my team members, he asks "How did you do?", "Us? You meant me, because the other prick didn't go".
And that's all, not another single question nor explaining why did he didn't answered the DM's I sent.
Fuck those guys, fucking team of shit, I hate it when you can't pick your team, but I guess that's just a common place for all of us here, isn't it?3
I'm want to hear other Dev's opinions on this week's weekly group rant! Do you find that the "worst projects" are caused the most by:
A) Poor solution design and/or terrible-idea-to-start-with
B) Poor process and/or terrible project management
C) Working with terrible teammates/customers6
The bugs that make you think are the best/worst.
Had a ghost foreign key constraint from a dropped table. Cant drop it from a non existant table.
Turns out the dev copied a file for the new table and since you can technically name those foreign keys anything you want, there were no errors when he ran it.
Also sloppy/overworked dev teammates are the worst...
Also I'm pretty sure rule 2 of programming is "Never Copy and Paste"
It's frustrating when you tell your teammate after code review that they have to rework their code a bit to capture certain scenarios they've missed and they just scowl at you.
I'm just trying to make it easier for us in the long run!
One of my teammates signed up for a day-long session on Angular 2, since he's been doing a lot with Angular 1 and wants to transition to the new version.
The instructor spent the first half of the day going through the w3schools tutorial on Angular 1, because "understanding the basics of Angular 1 will help understand Angular 2".
Btw, this was a paid workshop session.
I'm on a project that has been off the rails for a few weeks. We're no longer working off tickets/the scrum board. Clients are asking for production servers yesterday.
Things are behind. Some people are working nights and weekends. I'm one of the people who are vary vocal about not working over time and I haven't worked a single night or weekend yet (we're salary exempt too; no extra pay).
I even bought up in a meeting how I was not happy about people being guilt tripped for not working over (our PO messaged me out of band a few weeks back telling me my teammates would appreciate me putting in more effort).
I agreed to work this Sunday and already regret it, even though they said there'd be compensation (without mentioning what that compensation is). I was also told everyone is doing it and that's not true either.
In my 18 years in IT, I've worked at ~ 13 companies. This one is in the bottom 3 for sure.2
I wanted to refer devrant to my teammates but then I realized I wouldn't be able to rant about them if ever. Better that they discover this themselves instead lol 😂2
It was quite a rough begining of 2016... having to give the context of a 7 team members project to 5 new team members, that replaced 5 teammates that left the company...2
About 6 months ago our teacher made us do programming projects in groups of three in order to learn project management. Together we planned who had to do what and until when. Now guess who did all the work - Me.
They did absolutely nothing and because I could only do my part if they did theirs in a correct manner I also had to do theirs too.
I always asked them how far they were and they told me they are almost done, but just before the deadline they copied some code from the internet that didn’t even work and claimed they wrote it. That way I couldn’t even report them to the teacher because “they did something for the project“.
It sucks to be the only one in a project that really cares.3
I believe that I have found the worst feeling in the world.
Not when a push to production on Friday fails. But when a few of your teammates don't want to do JACK FUCKING SHIT. The worst ones are where they think you fabricated projected expenses for raspberry pies, and thus believe that you are apart of some communist conspiracy.
They also believe that cheap AWS ec2 instances are crappy for teaching some basic fucking command line and git to high schoolers!!
I feel like a need a brick handy at all times just to chuck it at a wall.
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!
It is when I'm doing my fyp during my college studies. I in-charge on the front end part, but i do a lot of debugging for back end part because my teammates aren't very good at it.
full of coding day and night, i found it is enjoyable 😁😁😁
from then i consider my career to be a web developer. and here i am 🤓
When it's holiday season and your teammates are on leave, so you have to open a pull request and approve it on your own.
When people around u talk about Hackathons, winning them and all you do is submitting ur assignments and frustration of not enough getting teammates to participate is fucking irritating and demotivating!2
Anyone have tips/tricks for encouraging teammates to comment on an RFC? It's work enough to write them, would be handy not to have to track people down for something more in depth than an "LGTM".
I'm so proud I have you. You're the incredible professionals. Your efforts and your desire keep us on the track even at the toughest moments.
It's a honor to be this team's leader.
I bagging you. Do not ever fucking think you are able to make design decisions on your own!
I'm tired to toes of that shit you submit for code review every fucking day!!!
Best: Completing the first year of my professional career doing what I like and learning from my team mates, which have been awesome. Wrote a couple of blog posts, they were my first, that helped me learn more and improve my communication.
Worst: On the last months of the year some work just got too repetitive which I think will lead me to some stagnation.
Would you consider a technical leader to be as some kind of teacher ? I mean should he/she be teaching stuff teammates should already know ?1
That moment when you can actually squeeze your programming language into any conversation with your teammates