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 - "teamwork"
A group of ten top software engineers is sent to a class for aspiring managers. The teacher walks in and asks this question:
"You work for a software company which develops avionics (software that controls the instruments of an airplane). One day you are taking a business trip. As you get on the plane you see a plaque that says this plane is using a beta of the software your team developed. Who would get off?"
Nine developers raised their hands. The teacher looked at the tenth and asked, "Why would you stay on?"
The tenth said, "if my team wrote the software, the plane would not get off the ground, much less crash.4
Client: Our meeting is going to be on March 27th at 9am. Clear your schedules and add it to your calendar.
Me: I'm not sure why this wasn't cleared with me, but I'm 3 hours behind you guys and that will be 6am for me. If you want to have a meeting at that time, I'll be sleeping.
Client: We start our days early, so we need you to make yourself available at that time. We have other stuff on our agenda so this is the time it will be taking place.
Me: I will not, repeat will not be available at that time. I have the 29th and 30th available at that time, but any day before that will have to be scheduled at 1pm or later. Mondays however are a no go. We have standing appointments on Mondays that we cannot reschedule.
Client: Monday, April 2nd at 9am is the new time. Please clear that time.
Our Company owner: we just said Mondays are a no go.
Client: we're getting frustrated that you are not being flexible with your schedule. Here is what you are going to do. Give us a calendar with every day and time you have available and we'll tell you what works.
Owner: We just gave you a bunch of dates. We're the ones trying to be flexible while you've been dictating what time's we've been available. That's not how this works. Mondays aren't happening. The 27th isn't happening because I'm not going to expect my developer to get up at 6am because it's convenient for you. This is a not a one way street. Let us know when you're ready to find a date and time that works for all of us.
This is the same guy I argue with on a daily basis and tell to fuck off when he's being a douche, but when it matters, he's pretty badass dude.8
So, I'm programming a control system for a prototype aerospace vehicle. You know, the stuff that needs to work to prevent falling out of the sky.
Anyway, test day was today (was -- not anymore). Wiring all the electronics, everything is actuating and works well. Except for one part, a little thruster for stability.
I spent hours - literally, fucking hours - trying to fix the problem. Wrong address? Wrong syntax? I had absolutely no clue what was wrong. Queue the hardware guy, $stupid:
$stupid: "How have you not got it working yet?!"
$me: "I don't know, everything I'm trying isn't working. I've spent hours digging through this code and nothing is fucking working."
$stupid: "Well have you set it up for the new thruster?"
$me: "What...What new thruster?"
$stupid: "Oh, the one we installed this morning, did noone tell you?"
WHY WOULDN'T YOU TELL ME THIS?! COMMUNICATION 101!6
Variable naming at its best...
Took only 2 hours to notice the difference between leftToRight and lefttoRight11
Mountain climbing. Increases social skills, teamwork and trust.
Building a house. Increases spatial visualization and planning skills.
Electronics. Increases mathematical and problem solving skills.
Chemistry. Increases precision and analytical reasoning skills.
Psychedelic drugs. Increases imagination, inspiration and abstraction skills.24
A repo on GitHub I'm maintaining has grown with 200k downloads / month since I started working on it a year ago. My recipe? I added an npm badge in the readme showing downloads / month and I responded to every issue and reviewed every PR. Now there's so much issues and PRs coming in that we had to add an extra maintainer, feels great! Teamwork, fuck yeah!
Not every PR got merged of course, but every single one of them got reviewed. Just being a good and friendly developer, giving back to the community that has given me so much. Some tips for you maintainers out there. If you have a popular project and no time there's always someone else who's willing to spend time on it, ask around and you will surely find someone else.7
I didn't know any one of them, we just meet at the TADHack last week end. Because my team members apologies at the last moment, I joined one of them who forgot his laptop. The third came after five minutes asking "can I join"?
We established a team from three different backgrounds, and started the work. Each one built what he know, and we integrated all of it together.
Luckily, we won.... I enjoyed these weekend...5
My colleague: *merges my pull request and his like an idiot and removes my changes*
Me: you merged incorrectly. *Shows code*
Him: .... Yeah try to avoid adding comments because clean code best practice is to not have them.
Me (to myself): how about you merge correctly instead of putting blame on something else.
For gods sake, it was a comment explaining why the code exists and not what it does.
He somehow was selected as tech lead because there were no free resources at the time. Hate it when these kinds of devs who can't code try to save their non existent prestige.
The guy can't even make proper rest apis. Give a wrong param value and it returns the whole json with null values. How the fuck do you still think you can talk about best practices when you can't implement them yourselves.
This is the same as the colleague in my previous rant who can't use git correctly and has everyone save their work so the guy can push cuz who pulls stuff, and then proceed on sharing posts about *teamwork* on LinkedIn.10
When two different clients, on the same day, congrats and thanks us for the work made by me and my team.
This was today.
The best part, they pay the bills XD
Wrote 2000 lines of working code last night. All of a sudden teammate who didn't do shit says in group chat:
"You're slow man"
Group projects in computer science usually go like this for me:
Me: Want to be in a Group?
Group member: sure
Me: okay, we can discuss the project and start coding some stuff tomorrow
Group member: I don't have a laptop, won't get one till two weeks
Also me: fuck off
"when i die i want my group project members to lower me into my grave so they can let me down one last time"
Last year in College, I had two simultaneous projects. Both were semester long projects. One was for a database class an another was for a software engineering class.
As you can guess, the focus of the projects was very different. Databases we made some desktop networked chat application with a user login system and what not in Java. SE we made an app store with an approval system and admin panels and ratings and reviews and all that jazz in Meteor.js.
The DB project we had 4 total people and one of them was someone we'll call Frank. Frank was also in my SE project group. Frank disappeared for several weeks. Not in class, didn't contact us, and at one point the professors didn't know much either. As soon as we noticed it would be an issue, we talked to the professors. Just keeping them in the loop will save you a lot of trouble down the road. I'm assuming there was some medical or family emergency because the professors were very understanding with him once he started coming back to class and they had a chance to talk.
Lesson 1: If you have that guy that doesn't show up or communicate, don't be a jerk to them and communicate with your professor. Also, don't stop trying to contact the rogue partner. Maybe they'll come around sometime.
It sucked to lose 25% of our team for a project, but Frank appreciated that we didn't totally ignore him and throw him under the bus to the point that the last day of class he came up to me and said, "hey, open your book bag and bring it next to mine." He then threw a LARGE bottle of booze in there as a thank you.
Lesson 2: Treat humans as humans. Things go wrong and understanding that will get you a lot farther with people than trying to make them feel terrible about something that may have been out of their control.
Our DB project went really well. We got an A, we demoed, it worked, it was cool. The biggest problem is I was the only person that had taken a networking class so I ended up doing a large portion of the work. I wish I had taken other people's skills into account when we were deciding on a project. Especially because the only requirement was that it needed to have a minimum of 5 tables and we had to use some SQL language (aka, we couldn't use no-SQL).
The SE project had Frank and a music major who wanted to minor in CS (and then 3 other regular CS students aside from me). This assignment was make an app store using any technology you want. But, you had to use agile sprints. So we had weekly meetings with the "customer" (the TA), who would change requirements on us to keep us on our toes and tell us what they wanted done as a priority for the next meeting. Seriously, just like real life. It was so much fun trying to stay ahead of that.
So we met up and tried to decided what to use. One kid said Java because we all had it for school. The big issue is trying to make a Java web app is a pain in the ass. Seriously, there are so many better things to use. Other teams decided to use Django because they all wanted to learn Python. I suggested why not use something with a nice package system to minimize duplicating work that had already been done and tested by someone. Kid 1 didn't like that because he said in the real world you have to make your own software and not use packages. Little did he know that I had worked in SE for a few years already and knew damn well that every good project has code from somewhere else that has already solved a problem you're facing. We went with Java the first week. It failed miserably. Nobody could get the server set up on their computers. Using VCS with it required you to keep the repo outside of the where you wrote code and copy and paste changes in there. It was just a huge flop so everyone else voted to change.
Lesson 3: Be flexible. Be open to learning new things. Don't be afraid to try something new. It'll make you a better developer in the long run.
We sat down one day and worked for 4 straight hours. We finished the whole project in that time. While other teams were figuring out how to layout their homepage, we had a working user system and admin page and everything. Our TA was trying to throw us for loops by asking for crazy things and we still came through. We had tests that ran along side the application as you used it. It was friggin cool.
Lesson 4: If possible, pick the right tool for the job. Not the tool you know. Everything in CS has a purpose. If you use it for its purpose, you will save days off of a project.1
whenever my team starts on a new project we're all like "okay we're gonna have MEANINGFUL commit messages this time guys"
*5 hours later*
$ git commit -m "go fuck yourself"
[master a7b9de] go fuck yourself
1 file changed, 1 insertion(+), 0 deletions(-)5
Best advice for dev job hunting is work on your soft skills. Don't be a fucking hero, prove your teamwork ability.
Remember all the rules of all religions and social communities can be summed up in one line: "Don't be a dick!"2
When my partner in a project has a sudden change of heart and confesses to the the professor that he cheated and we both get a negative mark(-8 marks) even though i didn't know or participate in cheating 😡5
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.5
Boss: Hey, want a job?
Me: No, i don't feel qualified or comfortable to do your job, it's best for you to hire someone else.
Boss: It's fine you'll have time to learn!
Me: Fine, i guess it's a good opportunity.
Boss: Very well, would you work with this database that is what holds our company together and also work with other people's credit card information, oh by yourself of course.
Me: I don't feel comfortable working with that, but i can link your site to your database, since it's something you wanted.
Boss: Well that's ok, you start next week.
~Middle of next week, had a reunion to talk about making the site from the start, using none of the old site (which runs with Joomla!).
me: I can use a ready HTML template to speed things up (i'm a beginner, and i have experience only with backend), and editing it is easy ~showed them the models i've made.
random employee: I have the design of the site all ready, you'll only need to code.
me: Ok, in which format it is? Did you use a IDE or something?
ramdom employee: It's on .psd, i made it on Photoshop.
me: ok... so i'll have to write down all the frontend?
random employee: yes you'll only have to code.
me: Ok, so we'll need to write down our priorities.
Boss comes up with never once discussed feature, and asks me to take care both of their database system (which, as stated by him: "If that systems fail our whole business is gone") and the site, all by myself, and asks how much time for the site to be ready.
me: If i get it online with only a few features and updates it as times goes by... i say maybe 2 months.
Boss: What, all that time?
EXCUSE MOI WHAT THE FUCK
I know how important a first job is, but they're going to pay me R$5.4/hour (1.4U$/H), and i have NO TEAM! How would that even count as experience, without teamwork? or git? and for god's sake they want me to do and take care of everything! They didn't even let me start working at all, since even the reunions is just me explaining how everything works.
I'm sick of it already, but i keep telling myself i can't lose the opportunity. I'M GOING TO BLOW UP!20
Today’s achievement: my phone didn’t autocorrect ‘fucking’ to ‘ducking’.
Clearly it’s as pissed off as I am about receiving shitty emails from the other team manager in my dept giving me and my team work to do and throwing us under the bus when he does jack shit all day except read BBC news and go on Facebook. On the odd occasion he does actually do work, it’s not good work, it’s riddled with bugs because he’s ‘too senior to need a code peer review’. Such a fucktard...
Oh, and the work he’s asked us to do technically sits in his team so I’ll be firing that straight back at him 😁
I’m all for being a team player and helping each other but I’m going to protect my team over helping someone. The gloves are about to come off....3
You know you've grown up when you realise teamwork is nothing but dealing with people's attitude.
Fortunately I'm working with a lovely team1
After 'Dev' deployed a service using Azure ServiceBus, a particular queue/client was receiving errors.
Dev: "Looking at the logs, client is getting faulted."
Me: 'What is the error being logged?'
Dev: 'Client is faulted'
Me: 'No, that is our error when the client is either unable to connect or there is an exception in the middle of sending a message. What is the exception from Azure?'
Dev: 'Client is faulted. That's it. I'm going to have to re-engineer the code to implement a retry policy.'
<OK, I smell someone cooking up some solution finding, so I dig into the logs a little further>
Me: "Looks like an invalid connection string. The actual exception being thrown and logged is from the Azure client connection string builder. The value cannot be null."
Dev: "No, I'm looking right at the connection string in the config. Looks fine."
Me: "Looks correct on your machine, but what is actually being deployed to the server?"
<I could tell he was getting agitated>
<Dev clicks around, about 10 min. later>
Dev: "Aha!..I found it. The connection string in the config on the main branch is wrong, in fact, the entry is missing."
<dev fixes, re-deploys, life is good, I document the error and the root cause>
Boss: "Great job Dev."
*sigh* ..go teamwork?3
TLDR someone in my team took credit for work he didnt do;
I know teamwork is a good thing and when everyone does their share of the work, it is.
I submitted a computer science project to an event in the UK called the Big Bang fair, I was in a group of 3. We had been meeting every week after for the past 10 months. During these sessions me and uke have been meeting for 1h 30m where as oon could only meet for 1h because "he had stuff to do" and he never saw the point in staying longer. Oon had also been a massive distraction whilst the time he was there as he did no work and messed around on cookie clicker.
Anyway we found out last week that the Big Bang fair was coming very soon and we had not written a write up or done any preparation for the presentation we had to do. Me and uke set up a google doc and started adding stuff to it (as we only had a few days left at this point). Whereas oon did nothing.
I ended up staying up till 3am in the morning finalising the write up over the weekend with uke helping. We asked oon to help but he said he didnt want to stay up late so didnt help.
Then the most stressful 2 days come round. I devoted all of my free time towards the project, uke devoted most of his time and oon devoted 1 hour after school on one day. He said that he couldn't do one lunchtime but I found him in the ICT room playing games :/.
This didn't matter THAT much but what pissed me off is that he started boasting to all his friends about all the work I did and credited it as his own. At the actual event he said nothing during the presentation because he knew nothing about the project. HE DIDNT EITHER BOTHER TO READ THE WRITE UP HE WAS BOASTING ABOUT. What do people get out of taking credit for work other people did.
We didn't win anything and I wonder why
wow thanks for reading all this you deserve a sticker1
Debugging a system error with a good team of fellow developers/devops people is fun.
We had an issue on Friday where we were getting a pretty cryptic error in our error reporting system. A couple of developers and I got together with a couple of devops people and we worked it out well as a team and figured out a pretty complex issue in a reasonable amount of time with everyone playing a solid role.
Nobody tried to steal the show and everyone listened to each other's ideas on what the problem might be. Through and through a great debugging session and made me think about bad ones and good ones I've had in the past.4
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..
When you have been anonymously voted for the team leader and you know only two names from your 80 people class.2
When new developers join in your team, please make a time and help them to get confidence with the project they will work on. Besides the project's documentation there is a human factor that can make the difference between a just another dev team and a great one.2
!rant && !!rant
☝️ What does that give you?
Today will be the last day we gonna work at this fucking hellhole of an office. Since I had so many shits to remember from this office, let me share my favorite.
1) Ground floor. Got flooded last July. Half our equipments got soaked. Oh equipments as in computers, cables, reports documents, etc etc.
2) I am gonna miss those connection down days.
3) I will also miss those black out days where we couldn't work for hours so had to play teamwork games to keep the morale of the team and you know to stay awake.
4) I will also miss that fucking mouse or rat. You are small and cute but fuck you for chewing my potato chips and peanuts. A-hole.
5) No windows so with no air-conditioning, it is a literal hell hole.
Gotta stop. I might cry.17
Two years ago, I developed an security app for Android as a school project. I didn't like teamwork at school (you know, you do all the work and everyone else is getting the same grade you receive, specially if you are the nerd of the class), actually I hated it, so I made it alone.
Its name was "Alex" and was a simple "panic button". You can configure two emergency emails and phone numbers (contacts only, not police) and, if you're in danger, you just have to press the button and the app is gonna send two messages/emails to your contacts: the first one, to tell where are you (GPS, only the name of the place) and that you're in problems. The second one with an audio/photo file of the situation.
Sounds like a great app, and I tested it few times. The reason I didn't continue with this is that I got my first job and I had not time, and that, tree or four months later, the government (of the city) launched a similar app. Less sophisticated, but I think it's still useful: "No estoy sola"(I'm not alone). I haven't tested it cause I don't trust on the authorities, I'd preffer to send my location to a friend through messenger app instead.
I don't know if I should re-work this app (I didn't released it, I just have the beta) or work on something else. I'm afraid that, if I release it, someone could die or get kidnapped because of a bug or something going wrong with the app :c What do you think?5
In the past, we used skype, hipchat, slack and now ... Microsoft Teams. What a tool.
Yes Teams, it makes total sense to tell me that my message is too long. I totally get it that you want me to rewrite my message and yes Teams, I should have rather attached it as a file to my message to begin with. Yes Teams, I wait for you to finish uploading those files before I can send the message. I'm sure there would be disastrous consequences if you send the message with my attached files as soon as you finished uploading. I don't even want to be productive. Thanks for helping me out.6
2 days until I leave my job and I am assigned a large, legal requirement task to complete, with no time to plan or opportunity to hand over the work. No way it will be done in time, and no teamwork, so no one else will be up to speed on it when I leave, and I daresay I'll be blamed for it not working to their 2 sentence specification! Yup, that's why I'm leaving folks!2
Note to self : stop trusting everyone in group assignments.
It always becomes a catastrophe right before the deadline 😥5
> Worst work culture you've experienced?
It's a tie between my first to employers.
First: A career's dead end.
Bosses hardly ever said the truth, suger-coated everything and told you just about anything to get what they wanted. E.g. a coworker of mine was sent on a business trip to another company. They had told him this is his big chance! He'd attend a project kick-off meeting, maybe become its lead permanently. When he got there, the other company was like "So you're the temporary first-level supporter? Great! Here's your headset".
And well, devs were worth nothing anyway. For every dev there were 2-3 "consultants" that wrote detailed specifications, including SQL statements and pseudocode. The dev's job was just to translate that to working code. Except for the two highest senior devs, who had perfect job security. They had cooked up a custom Ant-based build system, had forked several high-profile Java projects (e.g. Hibernate) and their code was purposely cryptic and convoluted.
You had no chance to make changes to their projects without involuntarily breaking half of it. And then you'd have to beg for a bit of their time. And doing something they didn't like? Forget it. After I suggested to introduce automated testing I was treated like a heretic. Well of course, that would have threatened their job security. Even managers had no power against them. If these two would quit half a dozen projects would simply be dead.
And finally, the pecking order. Juniors, like me back then, didn't get taught shit. We were just there for the work the seniors didn't want to do. When one of the senior devs had implemented a patch on the master branch, it was the junior's job to apply it to the other branches.
Second: A massive sweatshop, almost like a real-life caricature.
It was a big corporation. Managers acted like kings, always taking the best for themselves while leaving crumbs for the plebs (=devs, operators, etc). They had the spacious single offices, we had the open plan (so awesome for communication and teamwork! synergy effects!). When they got bored, they left meetings just like that. We... well don't even think about being late.
And of course most managers followed the "kiss up, kick down" principle. Boy, was I getting kicked because I dared to question a decision of my boss. He made my life so hard I got sick for a month, being close to burnout. The best part? I gave notice a month later, and _he_still_was_surprised_!
Plebs weren't allowed anything below perfection, bosses on the other hand... so, I got yelled at by some manager. Twice. For essentially nothing, things just bruised his fragile ego. My bosses response? "Oh he's just human". No, the plebs was expected to obey the powers that be. Something you didn't like? That just means your attitude needs adjustment. Like with the open plan offices: I criticized the noise and distraction. Well that's just my _opinion_, right? Anyone else is happily enjoying it! Why can't I just be like the others? And most people really had given up, working like on a production line.
The company itself, while big, was a big ball of small, isolated groups, sticking together by office politics. In your software you'd need to call a service made by a different team, sooner or later. Not documented, noone was ever willing to help. To actually get help, you needed to get your boss to talk to their boss. Then you'd have a chance at all.
Oh, and the red tape. Say you needed a simple cable. You know, like those for $2 on Amazon. You'd open a support ticket and a week later everyone involved had signed it off. Probably. Like your boss, the support's boss, the internal IT services' boss, and maybe some other poor sap who felt important. Or maybe not, because the justification for needing that cable wasn't specific enough. I mean, just imagine the potential damage if our employees owned a cable they shouldn't!
You know, after these two employers I actually needed therapy. Looking back now, hooooly shit... that's why I can't repeat often enough that we devs put up with way too much bullshit.3
When you're working on the same project and git branch with another intern and he decides to make copies of the files and rename them to avoid having to merge his code with yours. ._.4
First time rant here, and I'm just gonna let fucking loose because this seems to be a good place for it.
My uni can't teach programming for shit. It's the reason people sign up for the course. They want to know how to program. I'm self-taught and unhappy in college as it is.
I joined CS because I thought they'd assimilate work in the real world, which is experience I need. I realized early on that programming is like art, and I love the rush I get of something finally working right.
That said, they sucked the fun out of it. It's too structured. Everyone trying to get the same goddamn result. In the real world, we'd be working on a larger project that involved planning, design, communication, teamwork, and the ability to complete each of our own pieces of the puzzle and subsequently put them together in a project that works for the end user.
I'm paying to be a fucking sheep, people. Why do employers give a shit about a degree instead of talent? Welp, fuck society for this. You can tell me I can drop it and still get a good job, it'll just be harder. That's the fucking problem. I can't get a job if these incompetent fucking bastards will throw out my resumé the moment they see "self-taught."
If we could hire based on GitHub contributions, I think many of us here would be relatively better off. Programmers program, not socialize. We do socialize, but in our own little groups. We team up as needed. The moment the jackass in HR realizes that, the better off we'll be.
Sorry, just the way I'm seeing shit right now. I'm going through some OCD-induced depression and this might be a result of that, but I'm passed the point of giving a fuck.15
Well there were quite some teamwork fails concerning Git and build environments. I covered a few in my previous rants.
Basically I become a tiny bit of FUCKING ANGRY when I have to work with lobotomized pricks who get a segfault at address 0x00000000 in their brain_x68.exe when it comes to handle Git in the simplest ways possible.
Horrible commit messages, unfinished/buggy stuff pushed to master, force-push with fucking 6 months old code +1 change, pushing "resolved" mergeconflicts without resolving, 1 year old issues which are not closed or marked in any commit message, copying repofiles into a backup folder and committing it, not commiting files and change it directly on the FTP...
I HAVE SEEN IT ALL.
If I was not a calm and thoughtful guy I have had exploded and quit a long time ago!
I only help them so they can improve their dev style and workflows.1
We just had a big drama because our team leader discovered 2 of our projects use 79 character line limit. He changed it to 80 and reformatted all the code.
What is wrong with this world?11
*Client calls and asks for a restful api in php*
Me: So the client called and asked for a restful service specifically in php
Co-worker: I'm gonna write it in python.
Me: *disowns co-worker*
The best kind of team work.3
Our team spent 2 continues weeks working on deadline, without going home, doing all our activities in the company, learning from each other, nd developing great apps. Once upon a time.3
A colleague of mine worked 1,5 day solving a programming challenge in our project. Today I thought of another possibility, wrote it in half an hour, and showed it.
I got a speech about teamwork and that I should learn it. I feel bad about it, but should I?3
IF YOU UPDATE AN ADM PLATTFORM FOR FUCKS SAKE DON'T DO THE FOLLOWING THINGS:
1. ONLY DOCUMENTATE IT IN A POWERPOINT
2. WRITE DOWN IPs AND PORTS ONLY ON A WHITE-BORD
3. MOVE TOOLS TO OTHER SUBNETS OR DOMAINS WITHOUT PROPERLY KNOWING THE WAYS OF COMMUNICATION BETWEEN THEM
4. USE YOUR PERSONAL EMAIL ADDRESS AS RESET OPTION FOR LICENCE-MANAGEMENT ACCESS IF NO ONE KNOWS THE PW
5. LEAVE THE COMPANY THE DAY AFTER THE UPGRADE IS DONE
Because the guy who has to take care of the upcoming problems is not going to like you!
BUT having to deal with all of this at once would not be a problem if your, so called team (30 People who work with those applications e.g. as test-engineers) would actually work together instead of having that "not my daily business, I am going to drink coffee" attitude.
Apparently I am the only one who has enough balls to see, admit, and report a problem to our leadership.
This always leads to Me fixing the issue...
....that's alright I am learning a lot...
...BUT IF A TEAM-MATE, WHO HAS THE SAME DEGREE AS I AM GOING TO GET, LEAVES EARY BECAUSE: "HE DOES NOT KNOW WHATS WRONG", IT TRIGGERS ME!!!
- The apprenticeship guy
PS Needless to say hundreds of clients have access to those systems and I worked through a shittload of official tool docs just to get to know the tools first...6
"How long it takes to complete a task"
A slightly exaggerated illustration of why I enjoy coding alone ^^2
TEAM PROJECTS IN UNIVERSITY BE LIKE:
You will need to write a paragraph of text, approximately 100 words long.
In order to manage your work more effectively, you must split the paragraph into sentences and each one of you should write one.
Make sure you don't clash with each other, the text is meaningful and it flows nicely.
You have one month: you should meet at least twice a week to discuss how to go about the tasks, review your work and plan ahead.
We will be checking on your progress on a weekly basis.
Most importantly, do not just wait until the last minute and have one person do all the work: that's just silly.7
Mentors, take note. This is a best practice over here.
I've spent two days digging through obscure documentation trying to accomplish one of those tasks that is simple in word and complex in deed. Namely, I wanted to concatenate (not delete) near-duplicate values in Pandas before rendering the data into a graph. Two days beating my head against the wall.
One of my mentors (I'm an intern) heard about the issue, wrote in the proper line (a very specifically and archaically formatted command), and pushed it to repo without even asking for thanks. Works like a charm and he saved my rear end. What a guy.
Please, mentors, don't leave your interns hanging on problems where the only solution is shrouded in dubious documentation and magic syntax. Especially when there's a deadline involved. Let them struggle on logic flow and writing good code.
Be like this guy. You'll build the importance of teamwork and your intern will think you're a wizard.2
Teammember left. I did his three tickets yesterday. Before that I created and applied new rescue procedure for broken deploys on production and deployed the app manually. Took me about 6 hours to do this right, find the cause, and solve it, and document what I did. After that my teamleader bought me a launch :)
It wasn't his, my former teammate responsibility to bring back prd to life, it was me being good and engaged employee. His tickets, on the other hand, were his duties. Took me one hour to code them. He was working on them for two weeks. I can't wait for the performance review, im definitely going to ask for a nice rise :)1
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
Been in a creative company for more than a year working as front-end, mostly CSS3 Animations and jQuery.
Today got a Job Offer in a startup about building an ERP for Albanian Market, mostly in Laravel and Vue.js
I was so excited for the first 30 minutes and then I remembered that I don't know so much Laravel and Vue, also I must work with an other guy which has lesser experience than me.
Totally scared about this new exp but ready to go for it :D
Any suggestions is really appreciated!!!!!2
Biggest teamwork fail? This is the general way we do business where I work right now:
My boss didn’t want to be the kind who hovers, always micromanaging. He also hates the idea of taking programmers away from their work for meetings. Sounds great, right? This has resulted in:
• All non-lead devs being excluded from all meetings other than scrum (including sprint planning and review meetings). Nobody ever knows what the hell is going on. They don’t think we “need to know.” This means most of our day is spent trying to figure out what needs to be done, rather than getting anything done.
• Our remote boss making dozens of important decisions about our platform, never telling us, and blaming us for not forcing our lead to be more communicative.
• Pull requests staying open for weeks, sometimes months, because nobody has definitively decided what version we’re actually supposed to be working on. This means our base branch could be any of them, and it means PRs that have been opened too long need to be closed, updated, and re-opened on the false promise of someone actually looking at it.
Just ranting here... but I think our biggest teamwork fail is happening right now, with all of those things ^4
When I got in this job:
No test, 0% coverage
No documentation (front and backend)
Senior doesnt want to talk
We have test prolly 10% coverage
Still no team work
Senior doesn’t want to talk
Ps: tried doing documentation but I cant unless my senior will help me because I dont know the ins and outs of the codebase.
I say crap.12
I feel like if I ever get a professional programming job my biggest problem will be I can't work on projects with other people when it comes to programming I really don't know how to split up the work any tips?5
We need more positivity:
Reason why you like coding? / Reason why you chose it as your career? / Why wouldn't you want to do something different?
Best feeling when coding
Nicest colleague/Best teamwork experience/Best boss/easiest client
What do you like about your position/job/company
Besides coding, what makes you happy
Your favorite stack/language/working environment3
Feels so fucking good to see that your effort and talent finally paid off. I FUCKING LOVE THE FEELING! 🙋🙋🙋
Okay, I knew one of my colleagues was actually a work freak, but to this point...
He's been working for most of the day yesterday on a school project, and so was I. Satisfied with my progress, I push the code with TODOs on things we had to agree on tomorrow as well as mentioning it in the issue associated with it on Git, with my last commit a bit before 11PM.
I wake up, with a ping on Discord asking me what was that "bug" I just pushed, wondering what editor I use and asking me if I even use the console debugger. Said "bug" was the point of discussion I said we wanted to talk about tomorrow, I replied in the morning. But he decided of the fix on his own and committed it, as well as other things until... 3AM...
Honestly, I don't blame him for choosing at our stead, he's the leader of our branch and the Gitmaster on top of that. I just reproach him to call it a bug, not see the issue, and all that while he could, you know, sleep. And get some rest overall.
This dude has been working himself madly these last weeks, where he did about 80% of what each of the team member was supposed to do in a whole semester (which amounts to 150 hours of work) for this project (we're nine folks on it).
Now I'm pretty sure it's how he works and that he still gets a decent amount of sleep (like I dunno, until 9AM or so), so I don't expect a response beforehand.
And indeed, as he woke up, he replied to me.
We had to implement our own sorting algorithm for a Linkedlist. My teammate was in charge of implementing this. I took a look at his algorithm when he pushed his changes. He was transforming the Linkedlist into an array, sorting it, then re-creating the linkedlist from the array.1
@Owenvii made a post over at (https://devrant.com/rants/2359774/...) and I want to write a proper response.
The biggest thing you have to look out for as a new dev is the jobs which you accept to begin with.
This isn't minimum wage no more, this is "big league", well, maybe not apple or google big league, but it's not $9.25 an hour either.
Basically you don't want to work anywhere where 1. your labor will be treated as a highly disposable commodity. 2. where the hiring manager doesn't know how to do the job themselves.
The best thing you can do is, if you're new, and just breaking through (and even if you're not), is ask them common questions and problems/solutions that crop up doing the work. If they can answer intelligently that tells you the company values competence (maybe), enough to put someone in place who will know ability from bullshit, merit from mediocrity, and who understands the process of progressing from junior dev to a more involved role.
It also means they are incentivized to hire people who know what they're doing because the training cost of new hires is lowered when they hire people who are actually competent or capable of learning.
Remember, an interview isn't just them learning about you, it's your opportunity to interview *them* and boy, you'll be making a BIG mistake if you don't.
Ideally you want them to ask you to pair program a problem. If your solution is better than theirs then they aren't sending their best to do interviews, and it tells you the company doesn't fire incompetents. The interviewers response can tell you a lot too, if they critique your work, or suggest improvements, and especially if they explain their thinking, that is an amazing response to look for, it says the company values mentorship and *actual* teamwork (not the corporate lingo-bingo 'teamwork' that we sometimes see idolized on posters like so much common dogma).
Most importantly, get them to talk about their work and their team. If they're a professional, it'll be really difficult to pry anything negative about their co-workers out of them, but if they're loose-lipped and gossipy thats a VERY bad sign, regardless of what they have to say.
Ask to take a tour and do a meet n' greet of who you will be working with. If they say no, then it's no thank you to a job offer. You want to take every opportunity to get to know everyone there, everyone you'll be working with, as much as possible--because you'll be spending a LOT of time with these people and you want to rule out any place that employs 'unfireable' toxic assholes, sociopath executives, manipulative ladder climbing narcissists, and vicious misery-loving psychopathic coworkers as quick as possible. This isn't just one warning flag to look out for, it's the essential one. You're looking for the proper *workplace culture*, not the cheesy startup phrase of "workplace culture", but the actual attitudes of the team and the interpersonal dynamics.
Life is really short, and a heart attack at 25 from dipshit coworkers and workplace grief can and will destroy your health, if not your sanity, the older you get.
Trust and believe me when I say no paycheck is too grand to deal with some useless, smarmy, manipulative, or borderline motherfuckers at work constantly. You'll regret it if you do. Don't do it. Do you fucking do it. Just don't.
Take my words to heart and be weary of easy job offers. I'm not saying don't take a good offer that lands in your lap, I AM saying do some investigating and due diligence or the consequences are on you.1
When the only other person on your dev team is an arrogant, miserable piece of shit that you despise but have to pretend to get along with so you can get a paycheck3
my freaking team-mates refuse to use gitHub for our group project, THEN they tell me to hurry up and send them files in a freaking facebook chat.
I zipped more folders in a day than I did pants in my entire life.
Oh yeah, did I talk about having to manually *FIND EVERY FREAKING CHANGE* to the code to merge manually! what a joy banging my head to the wall figuring out where did he change those methods...4
Oh where to start.
TLDR, *actually* prepare students for the *real world*.
- TEACH GIT.
- Stop with the useless projects with esoteric restrictions that absolutely do not exist in the software work field
- ENCOURAGE collaboration rather than make it academic dishonesty with high punishment consequences. Devs need to learn Teamwork!!
- Don't start 101 with Python then go straight to C++ in 102
good lord, the easier question is what DOESN'T need to change in CS undergrad programs.
My collaborator was always telling me what a great team we are, until it got serious.
Getting stabbed back in the butt and fired from your job. HAHA what great Teamwork...
After that steal all my ideas and projects and sell them as there own.
I hope that guys Flip-Flops will burn someday1
My GOTOs are:
- Check if focus on teamwork is emphasized. Does the company state themselves? Spend a day with the team if possible, see how they work together.
- What tools do they use? Sometimes this will hint you towards whether or not you will encounter a good environment or a jumbled mess.
- Is there organized communication? I know, sometimes there are too many meetings, but that is better than too vew. How often does the team meet, even if just for 10mins? How does management communicate with the team? What ways are provided to give feedback? Are suggestions to improve practices welcome?
I left my last company and joined my current one, where these things work out the way they should. While I liked both projects with respect to development, my mental state has improved dramatically in the new environment. Stress is down, productivity is up. I love my job.
Why are the people who give shitty design suggestions always in majority in my team 😓.
Fuck this world!!!1
Oh boy, converting the whole codebase from vb.net to c#
Pain point 1: CType all over the place (Convert.To*)
Pain point 2: almost everything is static!
Pain point 3: "I learned about DI just 3 months ago..."
Paint point 4: deployments ever happened by hand!
But I'm happy to be there because the guy who's running the thing is a very nice one and he's absolutely grateful for every bit of learning lesson I give him.5
Almost 2 years working at this small IT company that has 7 developers and I just had my first small-talk conversation with the lead senior developer that was not related to work.
Maybe I'm in the minority, but I like to be able to chat to my colleagues instead of just saying "Good morning" and "See you tomorrow" and discussing my tasks. In any case, I'll go get a coffee and get back to coding.1
Alright, server got hacked a week ago. Bad enough on its own but okay, perfect time to change the server infrastucture completely instead of doing it later this year. Since Saturday we are working on setting everything up (game server, apache, etc.pp.) while making sure to configure everything correctly to be safer this time.
We are finally at the point where we could go back online. And what happens? One team member _now_ (6 days after the hack) suggests that it might be a good idea to format the hacked server and configure just what we need to patch the clients with it.
Great fucking idea, why didn't you have that idea 5 days earlier?! There was more than enough time already to format the old server and configure it. Another day delay, yay. X_X
Aaah, ranting really helps in those situations. Oh and Hi, I'm new here. Nice place, I like it. ^_^2
Wouldn't say our teamwork failed we just sucked that day.
I had a ticket to fix a SQL sp and then correct some data afterwards. As this was the typical "urgent fix need now" we went through a different process for fixing it.
Me: Just sent you some scripts can you check them over before we apply it to uat?
Boss: let's go through it together.
5 mins later
Boss: looks fine I'll apply the scripts.
2 minutes later
Me: did you apply the scripts to uat?
Boss: No I applied them to live.
Me: oh ... oh no.
At this point I realized I was missing a critical where clause so yup my update was applied against all of the data.
Yup he just spotted my error.
Helpdesk phones start ringing
Boss: you pick it up it's your code
Me: hey you applied its your problem now.
One db restore and several incident meetings later we fixed it. Twas a fun day.1
"Could you help on project X and implement that straight forward feature?"
So I clone the repo. Run the tests in the main branch. 20 tests fail.
Yes, this will be fun and very simple ...2
So I work for an IT consulting firm (web development) and was hired by a customer 7 months ago for coaching Git, implementation of VueJS on the front-end and fostering teamwork with devs who'd been in their solo comfort zone for the last 15 years.
I asked for confirmation multiple times on whether they were sure they wanted to go through with a bigger investment in front-end. Confirm they did, multiple times.
After half the team's initial enthusiasm faded (after 1 month), the 'senior' of them who's worked there for 18 years on a single -in the end, failed- project got a burn-out after half a week of showing up (without doing actual work) from the stress, and started whining about it with management that has no technical clue whatsoever. This and other petty office politics lead to the dumbest organizational and technical decisions I've seen in my short 5-year career (splitting a Laravel app that uses the same database in two, replacing docker container deployment with manual ssh'ing and symlinking, duplicating all the models, controllers, splitting a team in two, decreasing productivity, replacing project management dashboards with ad-hoc mail instructions and direct requests).
Out of curiosity I did a git log --author --no-merges with the senior's name on the 2 projects he was supposed to help on, and that turned up... ZERO commits. Now the dept. hired 3 new developers with no prior experience, and it's sad to see the seniors teach them "copy paste" as the developer's main reflex.
Through these 7 months I had to endure increasingly vicious sneers from the IT architect -in name only- who gets offended and hysterical at every person who dares offer suggestions. Her not-so-implicit insinuation is that it's all my fault because I implemented Vue front-end (as they requested), she has been doing this for months, every meeting at least once (and she makes sure other attendees notice). Extra background: She's already had 2 official complaints for verbal abuse in the past, and she just stressed another good developer into smoking again.
Now I present her my timesheet for January, she abuses her power by refusing to sign it unless I remove a day of work.
Earlier this week I asked her politely to please stop her unjust guilt-tripping to which she shouted "You'll just have to cope with that!", and I walked out of the room calmly (in order to avoid losing my nerves). She does this purely as a statement, and I know she does it out of bad faith (she doesn't actually care, as she doesn't manage the budgets). She knows she wields more power over me than the internal devs (I am consultant, so negative reviews for me could delay further salary raises).
I just don't know how to handle this person: I can't get a word in with her, or she starts shouting, and it's impossible to change her (completely inaccurate technological) perception.3
TeamWork 1 week before release de projet
Guys i dont know why but all the projet is fuckup in Git ...
Me: where is your firts commit of all these shit ?
He: just there
Me : git reset eb23ae --hard && git push origin HEAD --force
Me: now you sit there and you play with your pencil ! 😡😠
I have to finish team project within 13 weeks. Since most of my team mates are quite new to programming, I took first steps along with leader to make tasks as simple as possible for them. 2 weeks into the project and one of the members complains that she doesn't understand her task. So both me and leader tried to explain task to her. I guess we couldn't make it simpler. However she insisted that she will have to see our teacher. Ok, why not? So we are waiting for her magnificence to show so she can be officially dropped from the team and give her place to someone more competent.
WHY SHE EXPECT TO DO HER PART (OF LITERALLY CONSTRUCTING ONE FUCKING CLASS) FOR HER. AND SHE CALLS HERSELF A DEVELOPER!
Well, at least I did my part today to make a world better place :)
What about your experiences with working in teams?
If you are a developer and you are proud of the work you contribute whilst remaining open minded, I applaud you. If you are a developer and you are overly proud of what you do, and you believe the work you contribute to a software project caries more value than the work another developer contributes, then go fuck yourself.
I am sick and tired of working on teams with people who are self-righteous. What you bring to the table is important, but it isn't the only thing brought to the table, so stop acting like what you brought to the table is the best thing on the fucking table.
What makes it worse is when someone disagrees with your work and you aren't willing to take any of it. You deny their opinion as if yours is vastly superior. YOU need to improve your teamwork skills, YOU need to stop being so arrogant and self-righteous, YOU are the problem.2
Question; if you've got a team member who's been phoning it in during the last few sprints and their inattention causes extra work for others, what do you do?
- Have a private word directly one to one.
- Say nothing but bitch amongst yourselves
- Complain to the team lead
- Call them out during a daily standup and tell them they're producing shit.
Working on a project to create a space Invaders clone using Android studio/java. Point is to prove teamwork and our ability to optimise for a phone.
Leader makes the engine
Passes code to me who is doing gameplay.
Creating classes, testing them with a temporary activity class to get them on screen.
Okay, time to get it going properly.
Starts creating the game by placing aliens to the screen via the new alien manager, created in the true starting place.
Nothing appears on screen, sounds still play.
Odd. Repeatedly try to fix, but objects will not appear on the screen if created outside of temporary activity.
Show problem to leader as I haven't been able to figure out.
Gets lectured to no end about how I can't just ask him for help (first fucking time) if I get stuck!!!
Turns out, the value for frame time is way off for the first frame, and their positions get going way off the screens range when being placed. Temp activity works as it skips first frame.
Why did this happen? Genius leader didn't properly initialise it, so first frame time was equal to the First Date Object time ever locked - current time 🤔🤔🤔
We figured it out together.
Sometimes we woulg get a request which involves adding something or changing something to a rather large and poorly made codebase which me and my lead have not had the time to change.
This b how shit goes:
* the lead gets a call after an email was sent with apparently only 5 secs of response time( inpatient fucks)
* lead calls me in next to his station to listen to the call
* i b listening and shit, not even taking notes and shit, looking all secret weapon and shit.
Texas as fuck.
* lead puts shit on hold and looks at me
Lead: "Allright. You know the codebase as well as I do, what you think?"
Me: pffft gimme 30 mins and Ill whip out yo solution
Lead: we positive on the estimate?
Me: as positive as the Texas Rangers sucking ass but we still love em, fuck the Astros
Lead: there is only room for one team
Me: only one
* goes back to the call:
Lead: yeah its gonna take 2 days at most.
Aaaaaaaaaaaaaaand we do finish them in 30 mins. The trick is in doing it extra fast so we have enough time to fuck around or do some other shit and to make it seem like we do some hard shit. After maybe 6 hours we tell them that we managed to fix it before time.
Btw me and the lead tall about whatever while we code the stuff, most of the time I do it since my boy has heavy eye problems and I want him to relax. He has been training me a lot in regards to knowing the codebase, before I got here it was only him for two fucking campuses and the man did an outstanding job. My boy got my ass and I got his.
Teamwork, the southern gentleman's way.
P.d while coding it he said the one of the file sizes was too big to handle, i said "das what she said" and our female manager said "i heard that".......i could have sworn that she gave me a lil wink. Well damn.8
When you find a fix that is consistent and covers all edge cases, then your teammate writes two different work arounds .
My colleagues: "We should fail for scalastyle issues! Warnings will get ignored! Nobody fixes them! We should enforce a clean code style!"
Also my colleagues: Create PR with loads of `// scalastyle:off` flags comments.
Starting programming project at the collage with 6 month running time.
In team we agree every day to start "soon"...
1 month left.. everybody gets hectic..
..Until then i had finished the project alone..
TEAMWORK ;) :''''''D
"If you think you're the smartest person in the room, you're probably not*."
*You probably are a fucking idiot though.3
Brains. Mostly the brains of everyone else because just about every issue I'm ever going to run into has already been solved by someone. But sometimes my brain can be helpful as well.
Honestly, communication is probably the most important skill you need for programming. Putting heads together produces the most amazing results.1
Not having a team that wants to work together. Everyone does their own thing, occasionally people talk whilst making drinks, but no real communication. Worst teamwork fail.2
I find IT to be an amazing field. There are so many parts to it that take tremendous dedication to fully understand, yet, each part works together.
Teams of people dedicated their entire life to software development, which would be impossible if teams of people did not dedicated their entire life to the development of operating systems. That would be impossible if teams of people did not dedicated their entire life to integrating hardware and software. That again would be impossible if teams of people did not dedicated their entire life to electrical engineering.
I know I missed tons of subfields that link everything together, but just the massive amount of dedication and teamwork to make something as simple as a console application work properly is amazing. I wish I could understand it all and I hope everything will always be as easily accessible my entire life as it is now.2
What's worse than no comments? Outdated comments.
If you won't maintain your comments, I'd rather you don't comment at all. We are all better off for it.
The sheer amount of information to be gained in this field, and in my case specifically at my job, is mind boggling. Maybe it's just the week of fatigue talking here but I feel I'm way in over my head. Learning business, teamwork, development strategies, progress tracking, the code base itself, how different teams work together, how different sectors work together, overarching goals, individual goals, and then going home and having a social life, good nights rest, and somehow exercise in there?
It's certainly overwhelming. I know being new makes it seem worse than it likely is but I don't see how people even manage to amass so much knowledge in such a short amount of time. It's honestly so exhausting to keep track of everything and try not to make mistakes that it's nauseating. I'm still gonna try but good lord does it feel impossible.
The double-edged sword of teamwork. I'm an indie Game dev, so I have no choice but to work with others of completely different fields. I enjoy it and I get a lot of motivation seeing things done and learning many new disciplines, but team projects have so many downsides when you have to handle everything from programming to cinematography that someone else was meant to do.
My final team uni project I even had to do our music composing cause our sound effects guy did almost nothing in 6 months (he wrote 6 midi notes in 2 weeks at one point).
A guy while in college, he did the work I hated and left me to do the design and coding. Straight A projects every time due to our excellent teamwork.
Hello, today was my First day, internship at Microsoft innovation center BE, a great day with amazing people, my project is called tech Office, we need to process data from sensors in the office, create and use Microsoft AI to optimize and help the office become smarter and more efficient. Make the life better and the environment more productive. I don't really know where to start but I'm happy to be given such an opportunity and will do everything to make this work !
How many devs does it take to change a water cooler bottle?
Two (I saw them), and one DevOps to unfuck the cooler...
How does this even? There were even instructions with pictures on the wall... This explains so much.2
When your senior says he may as well stops working as I'm always refactoring his code...
Same sentence says I copy what you've done in other places so I don't see why it isn't good enough. By copy he leaves redundant code in there too.
Am I a being a douche is he just being over the top?
- He writes code and expects it to live for a long time.
- I write code and will go home and refactor my own code.2
Honestly? In a way. The degree itself did not bring me anything more that I already had. The process, on the other hand, was very useful. Both medicine and SW engg. courses taught me a lot: patience, manipulation, listen carefuly to what is asked/told [rather than assuming I know it all], dealing with consequences of my decisions, teamwork, "I must", "I mustn't", "I will", etc.
As for tech skills - nay, I didn't get anything new from IT course [although I've learned a freaking lot in med].
I give a draft version of my report to my colleagues so they can review it with things to add or correct while I eat. One of them:
"This report is really well structured. I think there's nothing more to add. Good job!"
I think the finishing touch consisting of "[...]" here and there had him fall in love with it.
So I’m in a bit of a pickle.
I’ve become involved with a pretty fast paced group project. We’ve got 9 weeks to write up a mock PDR and all of the communication is done through Discord and teleconferences. As of last week an issue came up where one of the teammates (Black) felt accused by Red of being called authoritative and feels disrespected by the following message: “I don't know if I'm picking up on it correctly, but it feels like you want to control every situation. I feel like you're trying to take on a part of everyone's role so that you also need more people a part of each sub category. I think whatever happened is done whether we did turn it in late or not, I don't think we need to pressure others to do more that is needed. Also, Project Manager's dad passed. Not to make it an excuse, but I think it should be taken into consideration. Also, we didn't even verify all the positions til the meeting we had. So even still, we would have had to turn it in late since there were so many arrangements
If you don't trust your other members to do their job without having to be supervised, it can be counterintuitive to the whole teamwork aspect.” This message was sent after we missed a deadline to submit a team organization chart and Black team member insisted on becoming a third Assistant Project manager while making it seem as the other 2 APM’s were incompetent at their job.
Although I agree that it is difficult to communicate all of your emotions through written messages, I still think that taking your tone into consideration is crucial when working remotely. Am I wrong? Is there a better way to work with this team member? It’s still very early on in the project and this is the first time I’m working on a project with others with very little face to face communication. Typically when similar issues became present in other group projects, we would all sit down and discuss it and try to reach an agreement (or at least an understanding of where everyone is come from). Any advice is seriously appreciated.13
So, myself an a friend are working on a project together. I leave for a weekend trip, I come back and find out the changelog is out of date like... six versions. I’m the type of person that likes to keep things like this. I had to manually go to the commit history and check when the package.json version was bumbed.
Yesterday, he updated it twice and pushed the versions to server, without updating the changelog. Turns out we accidentally skipped a version and decided to combine the two.
Now I have to find the dates each version was published since I like to do that too. Great fun.
Today's task: create a wireframe for the website.
Teamlead doesn't give a fucc about me, k I'm chilling then. I looked at their work and I saw a picture where a stickman types the domain in the browser and then the site appears (as a printscreen of the existing site I've done so far)
It's a challenge working with people that aren't as competent as yourself. Having another programmer misunderstand some system's design and throw copypasta around; or an artist who wants to chime in on low-level system design. It's hard to communicate not only how things work, but that a person should stick to their designated role and competency - without bruising egos.3
Went on a Hackathon with two friends. They didn't do shit. This week, they told me that they only knew c#, so we should switch to that. (I use Linux so I shouldn't have accepted that) Just learned that they are going to a maths camp this week and the deadline is next Sunday. Dotnet core CANNOT PARSE FUCKING JSON. I'll rewrite it in node.js, and hope that I can type fast enough to finish in time. Fuck me, fuck my lazy friends and especially fuck Microsoft for saying that they support Linux while providing a dotnet for Linux published in 200-fucking-56
It is ok to fail and commit mistakes, that's part of the game, specially for beginner devs. Just avoid failing alone, the most you can!
- Ask people to review your code before pushing to the source repository.
- If you are not sure how to do, ask.
- Never work in production environments without supervision. Pair with someone.
- Have a desk mate for rubberducking (https://en.wikipedia.org/wiki/...) and blame it in case you need
That moment you need a messaging bus for a part of your application and there is always 1 cheeky dev who will shouts for building it oursevles instead of using of the shelve libraries.... STFU and GTFO
Why do some developers seems to be fine if you copy paste some simple code but are losing it when it comes to using new libraries/services which are designed for exactly your problem?1
I went to a vacation leaving my colleague a working code that she was supposed to use and commit as is. Coming back a week later the code is unrecognizable, not committed and doesn't work. Now I need to fix it again while she went home. Plus I hate it that we're forced to use svn, the change is 40 files strong already.1
I think it was very useful for developing soft skills like time management, teamwork, dealing with failures, the willingness to learn and how to approach a problem, etc.
It's not about learning a technology or programming language super good and be the C++ or Web expert after finishing your degree. It's about self organization and problem solving IMO.
My teammate doesn't understand that the quantity of lines/method that he does in one commit nor the number of commits he does in one day translate directly into the quality of his commits.2
As a company we have reduced the number of emails we send each other. We use slack and for the most part it is very good.
It's also very resource intensive and some computers we have tend to choke after a little while.
Does anyone know of any open source alternatives we could look at.
(slack is a little expensive too. We're a startup)4
Chronicles of UX struggles vol. 2
I ask the design team to do some sketches so I could see how they want the pages (2 pages), UX guy says he'll do the sketch for the page, and I ask to which one, the first one or the second one?
He answered me "Yes"...
Edit: he took over 3 hours to send me a new message after I tried to understand what he was indeed going to do...
Lead dev asks me to take on the restful api aspect to a new internal tool UI I have been building. Happy for the challenge, I spend the 4 days (half of that in my own time), writing out 1k lines of C# that I endeavoured to keep clean, thoroughly decoupled and something I can be proud of.
I give regular updates.
This morning he responds to my last update “we already have most of that code in place”.
This stuff happens a lot. Back of a fagpacket planning and then cries all around when it INVARIABLY goes wrong.
Does this kind of bullshit happen in a properly organised, Agile team? We are about to take on a huge project and frankly I want to save myself the ballache and go find a well oiled team if what I am witnessing isnt just how things are in software land, but as I rather suspect a product of lack of communication and organisation.1
Dunno if it count as teamwork fail, but a few years ago, when I was beginning with webdev while working remotely with another person, I was coding a project for a client that had a very peculiar list of things he wanted (a.k.a. things-I-can-do-in-photoshop-excel-or-word-that-you-MUST-implement-no-matter-how-ridiculous-or-hard-it-looks-to-you).
The problem is that with each exchange of e-mails, the list either increased or changed for worse. I was so fed up with implementing so many ridiculous features (like soda bubbles popping up in the background with the word "SUCCESS!" in different languages inside) that every mail I exchanged with the other dev I wrote sometihng not-so-nice.
One day, it was late at night, I accidentally clicked on the "Reply to All" and sent this message to the dev AND client without paying attention:
"Here, one shit down, 2 more to go, then we're free of this piece of crap. Test it in your environment and see if it works. I'm tired of this, for real."
You can guess why it was one of the last e-mails I've exchanged with them. :P2
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
In our class we have one subject where we take notes on one shared Google docs document. To be honest, this may be the worst "teamwork" that I every had to deal with.
• Simply copying the stuff from the blackboard:
• Missing context
• document consists of keywords and occasional sentences
• These fucking deep nested lists
• No quality control whatsoever
--> nobody fucking cares
• What, nobody made notes for this point?
• Any attempt to speak up result in me being scolded
• Be me, the only one not shopping on amazon instead of taking notes
• Wtf does this mean, where's the context
• one line of code without needed context code
No quality, no Motivation, no better alternatives, no fun.
Who want to make programming team?
Who want to form a programming team. Anyone can anywhere in the world5
Yay! We completed this project in 8 weeks.
Collaborate with unlimited users to share your ideas and take your teamwork to the Next Level. Work together anywhere, anytime!
Check out the demo here: https://youtu.be/1lMAnxmsgKw
Check out the web app here: https://doodlelive.herokuapp.com
Please don't ignore it, let me know your feedbacks either good or bad and I would surely work to improve on it.
Thanks a lot in advance!4
So this post is going to target an irritating aspect of a specific culture based on observational evidence over the last 20 years, and has reared its hideous face yet again. If you're triggered by that, stop reading here.
I'm flatly fed up with two-faced onshore Desi coworkers. They make up 95% of my colleagues and the following sequence of events has played out repeatedly over the course of my career, consistently, though it's slightly more pronounced in other women for whatever reason :
1. Work with them for years, good relationship, teach them all sorts of skills (which I will do freely for anyone, for any reasons as I view it to be a moral imperative), general lifting up and solid teamwork.
2. They move up in the hierarchy, generally to management, usually project
3. The second they view themselves as higher in the pecking order they start treating me like shit as if we have no history. Rude, commanding, unwilling to share details, obligatory exasperated thank yous if any at all, not interested in anything I have to say even if I'm the noted expert on the subject.
I understand a lot of their etiquette culture, specifically the level of "directness" or politeness they employ is based on the estimated risk of loss in the interaction. I find that disgusting, but I understand that academically. I just can't get my mind around how universal this shiftiness is, as it happens over and over again. It's like human decency and respect go out the window the second they don't feel like they have anything to gain from you. In *my* culture that is the lowest form of behavior a human can exhibit, and it causes me to rage because I can't imagine being so utterly devoid of altruism.
Fuck. It's just so sickening. It's fucking debased, and selfish and greedy and fuck. I can't even, this is one of those things that so irrational my mind can't accept it and I just go around and around on it.
Tl;dr you want to get throat punched? Because that's how you get throat punched. It's definitely getting this person doxxed to USCIS5
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.3
My current employer...
In 3000 coworkers they have many things, but a team is not one of them... Fuuck
Let's do a story mapping session! Ok cool. PO asks the team: so guys what do you think? *silence*... *more silence*.... PO: come on guys, please respond. *silence*.... Then someone finally responds.
I'm starting to hate this big time. It's almost always like that, no matter the type of session (story mapping, refinement) And there's someone in the team that thinks he always knows best, so if ever someone speaks up, it will always be challenged and lead to useless discussions. He always wants the perfect solution. A good solution is good enough, it doesn't have to be perfect. PO is happy with a good solution (good = maintainable, scoring at least x on our code quality tooling), so why the fuck would you want to go for the 'perfect' solution, which may score just slightly higher in regard to quality, cost much more to develop and people have a hard time maintaining it due to the high level of abstraction? He's always refactoring stuff because it's not future proof. Well, why completely reimplement parts that have been working properly for 2 years and have a very very small chance of needing a change, which then still only needs to be done in just 1 place?
And you know what? All these fancy structures, patterns etc are in there but will their flexibility ever really be used? In my 20 years experience haven't seen such flexibility being really used. Some exceptions of course.
Once it's built, it will keep running, yes, changes will need to be made, but in most cases they never touch all these expensive fancy structured components. Just because most changes are in content or small changes in functionality.1
So happy, a former colleague, now friend, of mine decided to join my project, he has a lot of experience and helped me out a ton in my first professional years to gain knowledge about optimization, performance, architecture and countless more stuff.(--> wk73 best dev teacher I had)
The only downside, in this case very minor downside, is that I now have to go back to something I despise: project management... I need to properly format and transfer all my scribblings and thoughts into a roadmap and a rough specification, so he has a good start into the project.
Overall though I am really looking forward to this collab, since I love to work in a team, especially with such great support.
So yeah, right now I feel 50-50% about this whole thing.3
To those who have worked in mad RAD solo environments, with next to no testing...
...and those who have worked full Agile, with high code coverage, code review amongst hoards of T-shaped developers...
...how much difference does it make to wellbeing and upskilling in the two?
Bonus points if you have done both and can compare in an n=1 way.4
Worst part of being a dev?
When you need to work together with people that are too stubborn. Recently I needed to work together with 2 guys and when they started ranting on me for literally nothing, I realized not everyone is able to work in a team.
Now im ranting back on them.
What are your experiences with people like this and what do you do to make teamwork more enjoyable?
When your teammate is thinking more about his vacations and when he leaves, you find that he calls a variable "cruise" on a project that has nothing related to it3
What non-technical qualities does a software engineer need to be successful?... Attitude? Communication skills? Vision? Teamwork? Passion?... What do you think? And why?7
My dream was to have collegues that teaches me different approach on developing and will never be selfish, and now i have that! teamwork at its best! sometimes we have discussions when our logic doesn't match and in the end, we'll come up on better ideas.. :)
When you go after a 2 day leave and take an update and spend half of your day merging YOUR module properly. I wonder why its MY module anymore. :-/
I have this workmate who whenever we are given a project to work together as a team always makes me feel like isht. I always come up with cool features but he will never appreciate my effort. But when he implements his idea and I oppose it, I can see the anger and hatred in his eyes. Is it only me who experiences that? I hate the guy.1
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 need some advice, you guys.
I'm weeks away from graduating from my code school and working on a capstone project with a group and there are several people who I'm having a hard time following their code.
No comments, no documentation, just "30 hour sessions" and opinionated, undocumented code that doesn't mesh with the project plan 100%. It works, it get's the job done, but it's over complicated, undocumented and hard to follow.
Starting to feel like the 3rd wheel in a 4 person group because I'm the only one that is having a problem and I'm not sure how to get them to document their code for me. They try to explain it and just end up literally reading their code, which doesn't really help.
I feel like I'm working in a group of individuals who don't really want to work together and I'm worried it's going to be a problem.1
I am in a team where almost everyone is an apt critique. everyday new challenges and people seem to be so competitive that they don't share any information across, thus making everyone isolated and whack the motto "collaboration is key" teamwork rarely comes into play and it is most if the times one man show. thriving in such an environment is a challenge thanks team 😃
I am currently taking a cures in leadership and teamwork as part of my computer engineering education. One assignment is to write a text about how formal and informal leaders in a team creates problems. I am sure that some of you have been in a team where the leadership have created problems and I would love to have some stories from real teams to use in my text.1
Always fun to watch if you know it, inspirational if you don't.
And if your boss is De Niro, meditate - and better be part of the team.