Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "wk12"
-
Me: I'm building for 32 bit.
Me: But I feel like I should be building for 64 bit.
Me: But not everyone has a 64 bit OS.
Me: But who the fuck doesn't?
Jerry: The people who can't run our game.1 -
The moment I dared ask a colleague about unit testing, and instead of giving me a book or a look, he stashed his work, pulled over a second chair and we coded some, for an hour.3
-
I can't name one specific time that was the best memory per say. My team is super close - we get lunch almost every day, have (inappropriate) inside jokes and just act dumb together. Not one person on my team who doesn't fit in. Even our boss is cool. :) #LoveMyTeam4
-
In a weekend release chatroom, the lead- working from WiFi in a bar- asks "What's the issue count?" But forgot the "o".4
-
A while back our whole team was really frustrated with the marketing department.
In retaliation we made a new branch for our project called marketing-bs, which was used for all of marketing feature requests.
It's the little wins that keep us going.1 -
My teammate push 2gbs worth of CSV files into our repo.
He also merged all the other branches so, it's kinda hard to revert back without reworking a lot of stuff.3 -
it was 12am when we are ready to launch our new web design which requires a lot of hardwork and routing processes. my team lead was the one who pushes the button to production using "cap production deploy" command. everyone in the room (including PM) was like counting down like launching a rocket to space. the feeling is great knowing that everyone was sleepy at that time. im glad it went smooth and everyone congratulates each other.3
-
Staying at friend's place bcz he had corei5 and I had p4 for uni project. We were making arch linux and package installation took whole night on slow net. Made bash script of possible sequence of commands and we slept.
In morning when we woke, it was perfect!1 -
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
-
I'm actually a Dev, mostly just a shell scripter who needs to support 500 servers which run our applications. I install the new versions and check whatever is wrong if there are customer issues.
One release weekend everything went wrong, Development had to make new builds on the fly with hardly any time for testing.
It took 18 hours with no break.
It was extremely hard to concentrate, but being in the Skype group with everyone and finally getting everything fixed was quite rewarding.
Everyone just opened a beer and we stayed on the call for about 30 more minutes just to relax.
I like our Dev team way better than I like my actual colleagues, who merely mess things up and call me for the smallest thing without even thinking.4 -
suddenly our web got a lot of traffic. So, instead of increasing our server (we (think) don't have permission for that), we praying until the traffic back to normal.
10 minutes later, it does.4 -
Working on Python+Flask delpoyed on bluemix. The app failed to start. After 4 hours of debugging by all the 4 members of thr team, we together found that there was a tab in an otherwise space intended file, which was tripping bluemix.
This a during a hackathon
Resolved it 20 mins before submission
We won the hackathon!2 -
The best dev team I have been with is during college where the three of us who were working at a maker space would go to various hackathon and stay up all night to build cool stuff! (We won prizes at quite a few hackathons too!) The other two are pursuing their masters in a different college now, I miss going to hackathons with them :( Hoping that we get to go to a hackathon together soon!2
-
Long time ago had a really painful client. Everyone had an attempt at training the said client. However, the client just didn't get the system at all and kept asking lots of questions.
It got to the point where one poor developer had to make a set of screencasts of him using the system and performing basic operations.
I recall how absolutely insane it was that in addition to the hours of trading time we had provided we were sending him links to video files we'd created.
It was literally face palms all around and so bad it was sort of funny.2 -
so I left uni after my PhD and joined a start up where the boss is a Cambridge grad who does coding and is like 50 years old (he never told us the true value), the CTO is very talented and another dev who quickly became my best friend and me doing data science. the 4 of us worked together like friends and the efficiency was fantastic, there's no bureaucracy bullshit or shit boss talks. We built the whole thing from scratch (okay I admit they did most of the building) and to this day, we work just has we have been.
-
When me and 2 friends/officemates of mine, formed a freelance team to work part time for us to pay the bond contract on our full time job. We were able to leave 9 months after forming the team.3
-
Me and my friends are having a all nighter coding sesh, because the presention day was near, then my friend's mom ordered some pizza. We had set a rule where, everytime someone finish a functionality/module, that someone can get one pizza. I can totally say it was a productive night, and the presentation went unexpectedly well.1
-
The moment the product owner we were working with almost had a seizure.
Ps: Sadly, he's still alive and continues being a dick 😑 -
Best team experience?
Well, first I'd like to mention that after some more experience in the field since, I realize that this company had some pretty terrible management infrastructure...
Nonetheless, I think my best team experience had to have been during my first programming job because my project manager... WAS A FREAKING DEVELOPER! It wasn't his job to be a developer obviously, but we were a small team essentially developing waterfall style, and he had to pick up the slack now and then for certain issues. The man was a genius and everyone appreciated him because you could talk to him about anything dev related and he would get it. The rest of my team was also very chill too, so it was all in all just a fun experience, stressful as it may have been at times.
I have not since had such a diversified project manager 😟 but then again, not the PM's job to touch code...2 -
When someone creates a new bug and leaves without fixing it.
And the next day you can see everyone around his desk with unfriendly faces waiting for a fix. -
Today morning my sales manager calls me and tells there is a bug in one of the integration module and he tells the client has called us yesterday pls come early to office today and fix it. I asked which end point they have issue, he replies I don't know. I don't know what is the bug where is the bug, but there is a bug when they send data to us, pls find and fix it before 11 am. The worst part of this is that integration module I never worked on and the person who developed it has left the company long before and there is no documentation. when I go to that folder I see many controllers and many end points. now how will I figure out the issue 😂 I don't even know the work flow of that integration. the bug reporter (my sales manager) don't even know at what end point what issue happened.1
-
Came across a method in the code base that returns a boolean.
It uses a ternary operator which returns true if the result is true and false.. you guessed it... if the result is false.
WHY NOT JUST RETURN THE FUCKING RESULT!!!
What. The. F#%#....2 -
Back in the day, I worked side by side with a designer that actually wanted to build things together, instead of having me answer the dreadful "can we build this?" question and him singlehandedly knowing what's best for the product, the client, the user, figuring out the UI/UX etc.
-
Our team is small but we pretty much always have fun times. Our bosses have been visiting us this week (they work in a different country) and we've been partying almost every evening, they even paid for it. Our new employee who starts officially next week was also invited. Such a great time!1
-
my first job is in a brand-new team, all team mate other than the manager are new grads from colleges. we r so engaged and dedicated our efforts to deliver something. and one day one of our team mate decided to resign due to family issues, we try our best throw him a farewell party, it is so emotional. now I have worked in a couple of teams, the spirit could not found after then.1
-
My first job was at an e-learning firm, and I was a part of the team that made the digital content.
The team had a really good spirit. Often too good, as our team manager often gave up on us and left our weekly status meetings because we were all just joking and having a good time.
Still, we usually did an OK job and delivered on time.
Those were good times. Now I'm just a single dev without a team in a pretty large company. Luckily, I'm away on paternity leave atm.2 -
Favorite memories by far were the foosball, beer, ping pong, and subtitled foreign movies while we waited for code to deploy to test environments.
-
Best team memory from university? That one time my groupmembers were helpful and I hadn't to do planning, coding and documentation all alone.1
-
a camp / meet up. walking around (lost) in downtown LA. stopping at every bar we found for a pint.
walked for probably 2 miles before we realized we were going the wrong way.6 -
Having competitions to name our branches after animals, and fun quizzes in the retrospectives to win cuddly versions of said animals. :3 good times.
-
Debate with fellow student:
Should the square within a PowerPoint slide (dedicated for a second projector video stream) be black or white?
"Of course it has to be white, otherwise we won't see the video stream!"