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 - "wk121"
About 10 years ago my wife and I were buying a house. We found out late that we needed a lot more cash than we had previously thought we needed, and the deadline to deliver it was just a few days away. After returning home from my full-time gig at about 6pm, I took a break for a bit and then worked all night on a job for a client to make up the extra money. When 7am rolled around I had just finished up. Then I went back to work at my full-time job, and later met with the client to present my work. It was roughly 27 hours at a keyboard for me. That effort made it possible for us to successfully buy our first home. If you want something badly enough, make it happen!8
C'mon guys! 80 hours, 70 hours, 40 hours... Are you humans or fucking robots?
Once I stayed awake 36 hours helped by energy drinks and I could barely remember my name.
I can't really imagine how somebody could write useful code with such a huge sleep deprivation.22
84 hours. Took alot of coffee and adderall. Had 5 projects with reasonable deadlines until mother fucking hurricane Katrina decided it wanted to be the best cocksucking blowing bitch around and knocked power out for two weeks. I managed to get 3 projects finished before i passed out for a day but two clients got pissed off cause their projects were late. They were pissed off even more when i had to pull the Forced Majeure clause cause they wanted to be bitches and didn't want to pay for my work
TL;DR: Hurricane didn't kill me so deadlines tried6
2 hours, maybe 2.5.
No one works for more than that, it's not how brains work. Or bodies for that matter, you gotta pee eventually.
OK maybe I'm pedantic and shouldn't count breaks... But then where lies the threshold? A fifteen minute coffee break? An hour long lunch break?
Could we use scrum storypoints to brag then (I once finished 12 points in a day!) — not really, because they're not standardized units of work.
Lines of code then? Well, the dev who copy pastes Java classes would beat the guy adjusting a dense Python script, without necessarily doing more.
No, the only true measure is of course grams of amphetamine per week, and in that metric I win from everyone.
3 days (62 hrs approx), only leaving my desk for toilet breaks and 2 hour naps/day. At the time I didn't have much of a resume so I had to convince the company I was trying to get into, that I have what it takes.
Planned it all out. I only had crackers, energy bars, chips, pepsi and water.
I didn't get the job BTW. They used me to get shit done and then never returned my calls.3
I often spend 10+ hours on laptop goofing around and sometimes being productive as well.
Once I spend nearly 14 hours to put my site live.
I am a tester and no nothing about coding, servers, deployment, etc.
I spend hours of Googling and trying and failing.
Finally I did it. But I had a headache which lasted for two days before I was able to enjoy the victory.
Fun times. Learnt a lot. Not just technical stuff but some life lessons as well.2
Friday 6pm to Sunday 6pm, with toilet breaks, snack breaks and a three hour nap on Sunday morning. Roughly 44 hours. It was a hackathon, Nov 2016. My team came in fourth place and the first three teams went to Germany!
Well, I got a well paying attachment from it so it didn't go all to waste.
Me and my laptop then...1
I worked 76 hours in a row once, when I first learned Laravel.
I wanted to see if I could clone a site I created 10 years earlier that took 2 months.
I took copious amounts of Adderall, though.
I don't recommend it.3
I go to bed at 9pm and wake up at 5. Sue me.
I like my beauty sleep. I’ve driven for 60 hours straight before but that jut isn’t fun. That’s like Los Angeles to Chicago and back. Actually though.
Hate doing it, sleep := good4
About 50 hours.
Client made HUGE changes to the design and functionality of an already fledgling site and my then boss wanted it ready to display in a board meeting the very next day. So I frantically worked through the night.
The meeting went well. They loved it. But the board had decided that they also wanted more input and had come up with some designs of their own... Which they needed for the very next day again.1
17 minutes without single break. That was longest nightmare for me. I had to write 6 lines of code... You know how that feels. My fingers were bleeding and my eyes were burning. Oh maan, I don't even want to remember that hard days.
2 weekend days, up to 4 am
Reason: Manager said on a Friday night "Release, what can go wrong?"
Everything went wrong!4
Im lucky to work for more than a couple of hours at a time before getting distracted 😅
I played world of warcraft for 14 straight hours once though. Does that count? 😁2
43, I was in college with chance for an scholarship. Got instructed to get the best possible grades, and teachers kept telling me to do better. Did 3 tests in a row, and went to hospital in the 4th one. Doctor said that the amount of coffee and meds I had took could've killed me if I was not lucky.
P.S.: After I got my grades and asked about my scholarship I was told that they gave it to another person that was "more stable" and "healthy"...
P.S.: I don't know if this counts as working6
36 hours here.
It wasn't really work, but I went to FOSDEM 2 years ago with a friend of mine that's also a hacker (hardware stuff mostly). So on Saturday we went to all the talks fully energised, when that was done we got back to his home to "sleep", but there's so many other projects to do!! At the time we felt like we really needed a weather fetching thingy in our IRC client (I think it was Hexchat) but that didn't exist yet. So we built it, kinda in a pair programming way, all night long. Oh, it's morning already?! Time to go to the Sunday talks! We were both complete zombies by then, but somehow I still remember a little bit of it.. some ass who was showing oh-my-vagrant (boring as shit) and some other stuff. All in all, 36 hours on the counter when I got in bed completely wasted, but it was so worth it ♥️
I was on a hackathon, we got time between Saturday 10AM until Sunday 5PM.
Most people went to sleep at some point, i literally used all the time i got and could submit a finished and playable game.
I felt drunk and incredibly dizzy at the end3
I currently work 60 hours a week, working two jobs just so I can earn enough money to pay off loans, get better equipment and basically just survive.5
In tech: too freaking many. A few days (I fell asleep at my desk for power naps).
Ever: 72 hours. I had 6 jobs with only enough of a break to drive to the next. Used lunch breaks to nap.
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
8, simply because I'm not payed for extra 😁 and neither I'm gonna accept if proposed with payment, I'm not that much greedy about money and I prefer way more the work-life balance2
10 Hours straight.
I thought a simple list in Android isn't a big thing, because I have made some css. I was so wrong.6
In the first few months that I took coding seriously, I used to see a feature in some android apps that I really liked and wanted to do. One night in my sleep, I don't know how, but dreamed about it's solution and how to achieve it. So I snapped out of sleep at 2 am and started working on it. I finished it at around 5 am, but I was too exited and happy to go back to sleep, so I kept adding things to it and expanding it until 8 am, when I had to go to work. And at work I had to code until 5 pm, although we had one hour for food and resting. That was the longest I coded!1
The most recent one.
13 hr of video lectures in around 17hr + 5-6 hr of textual stuff for the test i had today. So around 19/24 hr
I worked for 18 hours to complete my final JQuery project in University and deadline was in 24 hours.
PS: I got an A, no + because they don't use it.3
13, my boss told me multiple times to leave, but I had to (for myself) fix someones fuck up first otherwise interns had nothing useful to do in the morning.
Got the next morning a few hours off to make up for that time.2
Most hours of work at once?
A coworker and I did an allnighter because our boss gave us a tight fucking deadline (luckily that almost never happens).
We started normal work at 06:30 and were finisted at 09:30 the next day. Summed up break time: 1h 15m.
I remember that my coworker went home after that but fell asleep in the train and woke up 2 hours later half across the country. Poor soul.
When he left, my boss just arrived in the office and I had to stay 2 hours longer to fix bugs we implemented during our caffeine overdose...
It later turned out that the whole mess was useless, because the client put the project on hold. That was about 8 months ago, or 12, I don't even remember.2
I love to sleep, but once I stayed almost 26 hours making a front-end design as a test to enter to a company in Brasil. And here I am. Worth it.
BTW, I completed the test in 9 hours, I'm just adding more hours as everyone here hahaha. I stayed awake for 26 hours but had a normal day. Does it count?
29 hours straight. From a thursday morning at 8 to friday around lunch at 13. No sleep at all.
A coworker became a dad a week before, so now I had to complete his data migration project. Had not been involved in the project at any point until his son was born.
But I made it and got a bonus in the end👍🏻
96hrs (3 days), I was working with violent autistic kids at the time. Snow storm prevented coworkers from coming in, so I stayed.2
I've done 24hr - 36hr hackathons twice and won't recommend it to anyone XD. The toll it has on your body is huge. I literally felt I lost 1 year of my lifespan going through that hackathon. Lots of coffee and tea. Felt sleepy and had a headache for 2-3 days after that2
Max I ever permitted myself to work was 14 if memory serves me right. When you get tired, you stop writing code, and start writing bugs. Future you will be grateful you went the fuck to bed
36 in previous job (sysadmin) - had to run 3 shifts in a row. Boy was I a vegetable in the end....
18 in current job (java dev), when I messed up PROD db
Most hours worked in a row?
Most bourse worked in a row coding?
I don’t have time for anything else when I work 18 hour days.😐1
72 hours. It was an e-commerce project with a fucked up full of promises deadline. And at the end was not used.3
When I was freelancing and still studying 60 hrs a week.
~20 hrs. bread-and-butter job
~20 hrs. for University
~20 hrs. writing a full-stack application for a startup
I did that for about 3 months, afterwards I luckily had no classes left.
Only, the thesis is still open. But on the other hand, the freelance work for the startup was a pretty good reference for scoring an actual, well-paid position which made me leave my old job as well as freelancing.
Now I work roughly 40 hours a week with nearly as much freedom as a freelancer but less paperwork.3
36 Hours straight. Admittedly I was on a study drug for this.
I had a mobile application module. The whole thing was marked on a massive project that I hadn't touched... until 36 hours prior to the deadline.
Brought a shed-ton of study/concentration pills from the darkweb, and designed, programmed and deployed in 36 hours (for Android).
... Also got a first in that coursework... mhm..
... And slept for 4 days straight after...
So, listen Kids! Don't do drugs!1
Working at least 12 hr a day is in my daily routine.
Each minute must have an exact purpose and should not be wasted
(That is just a theory and does not mean that I actually manage to do it everyday)
Straight 72 hours.
- First launch of a new product.
- Less than ideal QA.
- Fires. Fires everywhere.
- Scrambling to cover feature gap.
my longest coding session was from 10am to 2am, so 16hrs
was in first semester of uni and we had to build the game "breakout" using a predefined guideline.
i had to program the collision detection of a ball against some blocks that had to be destroyed
took a long time for me to do the task, as i'm not the fastest coder (and often neither the smartest😅) and had to fight a bunch of bugs too.
in the end it kind of worked but the performance was horrible at best
24 hours while a "pool" in my school (pool is a two-weeks fast formation where you can work 24h/24 to understand how a programming language works)
It was a C++ pool with a garbage subject meant to reproduce the functioning of a factory with... Factories.
Unit tests were use to mark us, so you know the struggle6
I don't know how many hours in a row it was, but one month I put down about 340 hours of work.
My boss had taken upon this massive project with a deadline at the end of the month. I basically lived at the office (I actually spent the night there more than once), meanwhile he was out sailing.1
It was the last year of high school.
We had to submit our final CS homework, so it gets reviewed by someone from the ministry of education and grade it. (think of it as GPA or whatever that is in your country).
Now being me, I really didn’t do much during the whole year, All I did was learning more about C#, more about SQL, and learn from the OGs like thenewboston, derek banas, and of course kudvenkat. (Plus more)
The homework was a C# webform website of whatever theme you like (mostly a web store) that uses MS Access as DB and a C# web service in SOAP. (Don’t ask.)
Months have passed, and only had 2 days left to deadline, with nothing on my hand but website sketches, sample projects for ideas, and table schematics.
I went ahead and started to work on it, for 48 hours STRAIGHT.
No breaks, barely ate, family visited and I barely noticed, I was just disconnected from reality.
48 hours passed and finished the project, I was quite satisfied with my it, I followed the right standards from encrypting passwords to verifying emails to implementing SQL queries without the risk of SQL injection, while everyone else followed foot as the teacher taught with plain text passwords and… do I need to continue? You know what I mean here.
Anyway, I went ahead and was like, Ok, lets do one last test run, And proceeded into deleting an Item from my webstore (it was something similar to shopify).
I refreshed. Nothing. Blank page. Just nothing. Nothing is working, at all.
Went ahead to debug almost everywhere, nothing, I’ve gone mad, like REALLY mad and almost lose it, then an hour later of failed debugging attempts I decided to rewrite the whole project from scratch from rebuilding the db, to rewriting the client/backend code and ui, and whatever works just go with it.
Then I noticed a loop block that was going infinite.
NEVER WAIT FOR A DATABASE TO HAVE MINIMUM NUMBER OF ROWS, ALWAYS ASSUME THAT IT HAS NO VALUES. (and if your CPU is 100%, its an infinite loop, a hard lesson learned)
The issue was that I requested 4 or more items from a table, and if it was less it would just loop.
So I went ahead, fixed that and went to sleep.
The day has come, the guy from the ministry came in and started reviewing each one of the students homeworks, and of course, some of the projects crashed last minute and straight up stopped working, it's like watching people burning alive.
My turn was up, he came and sat next to me and was like:
Him: Alright make me an account with an email of firstname.lastname@example.org with a password 123456
Me: … that won't work, got a real email?
Him: What do you mean?
Me: I implemented an email verification system.
Him: … ok … just show me the website.
Me: Alright as you can see here first of all I used mailgun service on a .tk domain in order to send verification emails you know like every single website does, encrypted passwords etc… As you can see this website allows you to sign up as a customer or as a merc…
Him: Good job.
He stood up and moved on.
I WENT THROUGH HELL IN THE PAST 48 HOURS.
AND YOU JUST SAT THERE FOR A MINUTE AND GAVE UP ON REVIEWING MY ENTIRE MASTERPIECE? GO SWIM IN A POOL FULL OF BURNING OIL YOU COUNTLESS PIECE OF SHIT
I got 100/100 in the end, and I kinda feel like shit for going thought all that trouble for just one minute of project review, but hey at least it helped me practice common standards.2
From Friday 6 am to Tuesday 6am (108h i think)
I had to get a website up and running so i worked until 2 am and realized that no trains or.busses are going anymore until 6 am so i kept working, then suddenly, thanks to my adhd i went into hyperfocus and didn’t nt leave from the seat (other than to get coffee) until Tuesday morning
I had had so much coffee that my heart felt like it would be home half an hour earlier than rest of my body
After that i stayed home for 3 weeks not wanting to see a line of code or talk to any rubber ducks
Thankfully i was able to recover and apologize to my rubber ducks7
36 hrs !
Just reopened my first android app project and was truly disgusted by the code.
So thought I should refactor it and publish a new update 😐
The update is still due and I am banging my head on the wall1
I was developing an Android app during college training. I made the app in three days, actually, three nights.
Three consecutive nights of only coding had its toll on me. I got burned out.
I couldn't even look at my laptop. Every code I looked made me want to throw up. That's how much burned out I was.
Well, after three more days, the feelings of throwing up receded, and I was back on track.
This was my second worst burned out experience.
About 14 hours. From 10 AM to 12 PM.
It was a difficult problem on one of those algorithm practice websites, which I just couldn't let go of. I spent most of the time trying to micro-optimize and do the same (wrong) thing in different ways.
The next day, I managed to finish the problem in 2 hours using a different approach.
I learned a bunch of things from this:
- Algorithm analysis matters.
- If you spend too much time on a problem without taking longer breaks, you get stuck in a loop repeating the same mistakes.
- A fresh mind is significantly more productive and creative. Take a break, think about other things and let go of that mental baggage, you'll be surprised.
16 hours. my friend and i developed a game years ago, so we met every friday at 5pm after regular work. on saturday at 9 i went to the bakery to bring breakfast for my girlfriend. best three years of my life.
Well, in this field, the most I have ever worked in a row was 20 hours, in my last field of Aviation it was 28 hours.
24hours in row. Because i was making my app for few things. It had some bugs that i needed to take care of.
Wow I'm first!! Uhm... 8... I forgot to take lunch break cuz I was really busy or the code was really interesting...
If within 24 hrs... Maybe 12... I had to login at night a few times to finish urgent work (bug fixes)
15h/day for at least one month.
Manager to someone: How long do you think it will take you to build this?
Someone: Erm... 6 months.
Manager: Fine, I'm pretty sure you can do it in 3 months.
I was invited/forced to join someone's team because he could not do it in 3 months. Neither did we, but we managed to deliver the project in 4 months.
The dickhead manager got a promotion, money prizes etc for burning us out. I can't stand this kind of managers.
Neither I or someone work for that guy anymore.
If a Dev tells you it would deliver something in X believe him, he's telling you the best he can.1
I don't exactly know... but i'm preety sure that it was more that 12.
reason - someone's final project which had only 1 day left before the deadline.
On wednesday we always work from 10:00 untill 20-21:00 because of weekly meetings with product owners who have a full time job besides being a product owner..
Its okay, we get free food and often have a couple beers, but the last weeks its been killing me...
Other people bail out because they want to do something with their friends that evening but I always feel like its a commitment we made as a team so as lead dev I should be there..
Think next week im going to bail out for a time2
Not in a row but had to work 13h per days for 5 days in a row because of a huge ass integration I had to do before it was too late.
Made it, everyone was happy, was promised a bonus, never got it. Nice.1
My current boss. He is never in the office and all he does is telling in which direction he wants the company to go. The backoffice works scrum and they are for any person in the company the people to deal with.
They care for personal growth and also tell you if you can get more money from them for example travel expenses.
The techlead is a female developer. If you are stuck around the place she lives in she lets you stay over or bring you home even though thats a two hours drive.8
36 hours. In the first 2 Hackathons I ever participated. This includes the time I spent on eating free food, tea , dinner, mid-night snacks, tea, tea, morning snacks, lunch, evening snacks, tea, tea, dinner ........And Quizzes that I lost2
probably around 12hrs, back in my Uni days when a project needed to be handed to someone else for completion in the morning. I slept about 2,5hrs after I finished and then went to lessons.
Once when I attended Global Game Jam, I worked on a game pretty much 36 hours straight, excluding some lunch breaks. Didn't sleep for 46 hours.
Gotta say, was a pretty weird feeling to wake up to tuesday when I went to sleep like 4 AM on monday. I slept over 20 hours. I remember waking up at one point and thinking that I'm still tired, so I'll just go back to sleep.
That was the one time when I truly 'slept a day away'.
36 or sth..
Trying to fix production for xy client without them noticing someone fucked up everything with the previous deploy.. (wasn't me)..
Anyhow, managed to deploy my changes plus fix for the previous fuckup.. in the morning it all worked as it should.
Why it took me so long? Because why bother writing down what changeset was used for deploy.. It's much more fun to guess.. Multiple times.. Anyhow, I managed to figure approximate code for that deploy & merge my changes & fix everything.. + later found out looooads of uncommited changes on the guys computer.. :/ So yeah, never trust a bunneh!!
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
In one session 36 hours. I lost someone close to me and I kinda didn't leave my office for any form of social interaction for three weeks.
39 hours. Finished building an Excel tool to help me convert rows of data into Magento custom products in seconds instead of minutes. Then I used said tool on a huge load of data and worked my ass off to get it done by some deadline. I honestly forgot what for.
8:00 - 23:00 with a 10 min break in between to go get some food from the store next door..
Because stuff was promised to the customer and we were told about it on the previous day...
The customer needed it before Christmas, so we delivered on the 24th at 11pm.2
As a developer, the longest I've worked in a row was 15 hours, from 8am to 11pm. We had to migrate/onboard a project and after we thought everything is done, the client told us about some extra functionality which was "urgent" and he couldn't tell us the months we prepared the migration -.- But it wasn't that hard and our boss was really nice. He stayed with us, even he couldn't really help us, bought us some Pizza, paid for taxis back home and we could stay home or come late to work the next day. And fortunately, that doesn't occur regularly in my company.3
I worked for 16 hours straight without any break because client kept me on call with screen sharing on and asked me to solve all the bugs from last 6 months of coding because he wanted to go live next day.🤕
Ps: I was the only developer and the only tester of that project.1
Longest I've worked is about 15 hours.
I had a major project that I was working on for a while, and I kept going on and off on this project. One day I finally found the passion I guess, and just went full blown coding mode.
Basically managed to finish the remaining ~50% of the base that day.
Without a break this would probably be around 4 hours. After that I just loose all productivity. So there so is really no point in forcing it any further.
For working without sleep I have regular done stretches as long as 32 hours. With just breaks for food and a quick walk around. To keep my body awake.
Why you probably ask yourself, well this has several reasons. For me to get in the "zone" I have to be awake for at least 12 hours. I'm not sure why this is, but the combination of being too tired to get distracted and the increase in dopamine from sleep deprivation. Is I think what makes for this, or by now it might just be a placebo. But well it works for me.
So when a deadline gets near and I'm not going to be able to make it, which used to happen a lot because I used to have a lot of migraines. I would start working in the morning, trying to get things done but not being to able to. Then after a full workday would take a dinner break and get back in the office, at this point I get in the zone and time flies by as I work through the night. Next morning people are coming back in the office and I start another workday.
I try to plan this so I have a lot of meetings or other social work. I get really social and chatty after being awake for more then 24 hours. Because my problem solving skills have really declined after being awake for so long.
Now when I still used to drink, I would after this workday get some dinner and go out to a bar to have drinks with friends. To celebrate me having made my deadline and well I'm really social from being awake so long. And I stop overthinking everything.
Still looking for a way to get in the zone before being awake for so long, so any tips are welcome!
The most work hours in a row n a non-dev job were 14 hours, but they were the hardest.
During University I worked in a warehouse once a week. It wasn't that bad and I could rest my brain for 8 hours. But around Christmas time they wanted me to do some extra work (as well as everybody else there). So I had to carry 20kg packages for 14 hours. Three days in a row from 7am to 9pm. I had two travel two hours to work and home again, so I had to get up around 4:30am and went to sleep at midnight. I'm so glad it was only a student job and I don't have to do this in my current job. And I feel sorry for all those warehouse workers, who had to do this regularly.1
My first “business trip”,
From 8 AM to 00 AM, 15-16 hours?
For 6 days straight,
Over 2 weeks,
*I rested once during the first sunday, I got back home on the second sunday,
Because the stupid boss designed the “revamped” software without even checking the first one, it turns out to be a completely different software, we were making personalized softwares for different clients back then,
Hence our trip to “implement updates” become a trip to “fix and re create everything”,
Longest I worked non stop was about 12 hours, I ended up being kicked out of the uni labs as the uni was closing.
Honours dissertation was fun but #NeverAgain :P
The most I have worked on something is 14 hours. It was for a university project, that involved creating a "banking" app that was intended to demonstrate the use of an SQL database. I had a partner, and we had done nothing about the project until the previous day. We started working at 5 PM and the demonstration was at 12 PM (noon) in the next day. We used PostgreSQL for the database, and C# and Windows forms for the GUI. My partner took on the database creation and I took on the GUI. I had minimal experience with C# and had never worked with Windows forms or DB bridging in a program. On top of it, lack of sleep hits me really hard, so by midnight I was just like a zombie with near zero focus capacity. As a result, I ended up rewriting numerous components with identical logic and appearance and some different elements that could be parameterized, simply because organizing my thoughts to write proper code was out of the question in my condition. The writing, debugging, testing and packing of the project ended at 7 AM, the morning of demonstration. I slept for 3 hours and then met with my partner and headed to uni. I never left a project for the last moment again. We ended up taking a 9/10 grade.1
I worked for 14 hrs continuously for my school project which was the best and hard experience for me.
it still hurts... so much work for just few marks
Back in my classic asp days, I used to average 12 hour work days with a few 16 hour days as the deadline drew near. No pills, just caffeine, junk food and cigarettes.
I'm sure the way I behaved in my 20's has cost me a decade of my life.
The worst was an 19 hour stretch, but I started getting confused and puking so I slept for 3 hours before finishing and then presenting.
I'm just glad those days are behind me.
I think I'm way more productive and healthy now at just 8 hours a day.
I'd answer the question, but whenever I sit and I'm completely in the zone, there always someone who'll fucking tap me on the shoulder.
Despite the hoodie, earphones and the obvious fact that if I go any closer to the screen, I'd be stuck to it.5
10 straight hours for college project, I was so confident about getting a gold medal but lady luck says otherwise...
If you don't count meals/toilet breaks/shower then my record would be 15 hours straight (08:00-ish to midnight 24hr clock) for a crap-tier black-white Nonogram/Picross generator that outputs near unsolvable grids because I know sh[BLEEP] on the games' generation algorithm. Yey /s. Petition to open /r/shittyprograms in parallel to /r/shittyrobots to celebrate how shitty my piece of a generator is.
**18 fuckin hours with full concentration on this Friday starting from 9:30 AM**
I'd developed a big feature for this release and it was being tested by QA guys.
There was this fuckin QA who raised a bug on Friday morning saying that one of the work flow is not working as expected. I debugged it in various scenarios including the one suggested by that dick head but I couldn't reproduce it.
On stating that, QA got pissed and told me that I've not developed it correctly. *Yeah fuck head now you are telling me*
My lead asked me to make some changes in the flow and then check. Did that but no luck.
Finally at 3AM on Saturday, this fuckin nut job QA mails me saying that he was giving in WRONG Inputs 😡
Yeah. It was that bad!
The lost his I've worked in a row were 74 hours straight had a deadline and a project to finish back in uni. So I only got off of my laptop for lunch and dinner and natures call. I slept for 12 hours the next day...
Got an A on the project and got through the deadline....
Good old days
Two hours. At the most.
After an hour or so I just need to go and chat with people or eat something away from the desk or simply trot around.
And my job isn't even boring.
In my freshman year of college, I ran into a grouping of circular dependencies that were so intertwined it would have warranted a total rewrite. I spent 28 hours fixing it. I took over my dorms common area, had about 5 movies playing on repeat for background noise, and stayed in the same seat for the whole period.
It was rewarding, but also showed me how easily I can get tunnel vision on a task. Now that I've graduated and moved on to a real job, I have certain back ups to make sure I don't forget to eat or take my breaks. I almost got in trouble for not taking them when I first started.
Holy hell some of you people are crazy. 16 hrs for me. Usually when I get really pissed at a bug and stay up till 5 in the morning to fix it.
Seventeen. I worked for 17 hours to pull off a POC of a feature no one thought was possible (at that time). It wasn't clean beautiful code, but hey, it worked! It's live now and I still smile when the feature is used.
17h for 5 Days working on a 3D Animation for an App Award. tough days but it was quite fun. 8/10 would work like a slave again
Oh that time,
When I nearly hit the 48h.
With two 04-14h shifts without ANY break and constant crying from my colleagues.
And that flat movement of a friend in between. Where nobody did shit and I had to carry the washing machine one story downstairs. Alone. Because the other participants did not want to hurt their hands. Yeah.
In the breaks at home I ate and went on gaming, that pushed up I've been.
Those were the days in west Germany 'industrial centre' dip shit.
The war zones on humanity that piss me off.
And there still are those greedy pigs working off their asses, licking cunts for coins and mistreating their subordinates and families with 15 children (alternatively their BMW 3xx's) and partying 'friends' they only know by consuming the most industrial waste radioactive gym work out fist fucker 8000 *tm
Those were the days
It's hard enough to survive a whole work-week on 1-3 hours of non-deep sleep per night.
Being away from home for roughly 12 hours a day; only working about 8 on the clock, and still being on standby after hours.
Now you expect me to count all those hours? I'm too tired for that, haha :p
'bout 8 hrs on trying to read spaghetti that uni-mates wrote for a project to create a drunkgame webapp. We had a good time but their code lacked meatballs 👨💻☕
17 hours, trying to prepare for a live demonstration, never did figure out what was wrong with it (luckily the guys in the office managed to find the issue) but didn't make the deadline:(
8 hours ... maybe?!?! I agree with previous ranter who says we CANNOT work more than 2 hours straight without some sort of break.
Including breaks, but not including sleep ... once did 48 hours
40 hours straight. It was brutal and I won’t repeat that thing ever again. A government regulation at the last minute forced us to change parts of our financial backend
16h a day. I was late for a birthday present so I worked on it for as long as I could. It took me 2 months and I was not done in time...
I had eyestrain of death and all this trouble only for a freaking birthday present.
But the present was good, although it was incomplete.2
Worked from 09:00-00.00+ every day for 6 days straight, then for about 4 hours that Sunday (including over public holidays which were that week).
Clients agreed release date based on some interviews with publications, which meant the previous target date was moved up 2 weeks as they were pushing marketing for this new date.
Aside from having to implement a new 3rd party API which touched ~35% of the system there was a lot more that needed to be finished before release (including an entire user flow that was at the mercy of a 3rd party).
Safe to say I took a day or two off the week after.
4, for a school project (and I was in school too). I get distracted really quickly, so I never work for too long. This day I must have been really 'in the zone', because 4h is a really long time for me!
~16 hours. It was during the start of my career. Like every other project manager, mine had also made an unrealistic plan for the project I was on.
10/10 wouldn’t agree to work like that again.
I built a React plugin for the freeCodeCamp Test Suite recently. I wrote the essential code in about 12 hours. It was stressful, but rewarding in the end.
The most hours I worked in a row - more or less, going by the definition of having no time to enjoy any personal activities aside from sleeping - were about ~17h.
I specifically remember this event because of the amount of hours of pointless work that generally went into that project and there was this one time when we - not only me as a technician, but also most of the engineers - had to build hundreds of complex devices in-house to meet an important customer's deadline because we had problems with a subcontractor at that time.
We did it in time, there was pizza afterwards as well as some questionable sense of achievement, so apart from a wasted weekend and sore muscles in my hands for the next days I didn't regret it all that much. So yay, I guess.
I was working at a restaurant and picked up a couple shifts notrealizing they were all on the same day. Started at 5:30 am as the opener, orked my normal 3-close shift and left at 7am the next day after doing after doing the night cleaning job.
about 12 hours, from 8am - 8pm
We were working on an iOS build for a demo and were told that day was the deadline for having code merged. I got kinda shafted cos I needed someone elses code merged before I could finish mine. It got merged at like 5pm and then everyone went home leaving me with a ton of merge conflicts to deal with. I gave up at 8pm and went home. Found out the next day that the deadline was horse crap anyway....1
28 hours. It was my company's first react native project.
I had to learn it and finding it. At the end I fucked up the project just before deadline. So worked 28 hours row to fix it.1
3. After that I take a decent break (e.g. an hour) because my productivity and efficiency reduce, and I'm not paid by the hour so a sustainable, high quality output that fits in with my life is the objective.3
Around 14 hours. I was working on a very difficult (at the time, this was my intro level course) c++ project my professor assigned. No one could finish it despite the many hours we put in.2
Can’t remember the longest “consecutive hours” session, but had a few work days that probably lasted 14 hours ( had breaks though )
Did however do 7 months of work days starting at 6am and ending at 5pm, but had two long breaks most days.
Also did a 21 day working streak once, skipping 3 weekends.
Now I work comfortably 😬
13/14 ish, got very VERY deep into the zone on a side project. Wrote a shit load code but still got fuck all done 🙃
About 20 hours. We had a major campaign for a product launch back in the days when MSN Messenger was awesome. Hitting F5 in MS sql query analyzer to execute query again would show like 20K+ downloads each time, shit was crazy. Then we discovered a major fuck up. Turned out that someone made a mistake by making a guid static. In a personalized content generator. So, most users ended up with someone else's face inside their personalized MSN Messenger wink. Oops... and no, we didn't do code reviews nor TDD back then so we didn't discover it sooner. It was really awesome to see how much traffic MS could generate by just showing a banner in hotmail. Real crazy. Anyway, we fixed it, discovery of the actual problem did take some time though.
The longest would be around 5-6 hours. After midnight my brain function starts being limited so while I think I'm thinking correctly I'm really just being stupid.
19 hours because of one hell of a bug in the .Net Native compilation of my app.
Related to: https://devrant.com/rants/1543053/...
24.5 hours on one assignment. Finished with full marks for the testing. 16 marks for testing and 4 for code review that are yet to come.
I worked around 16hours straight, freelance project with a very tight deadline for a big company when I was still young and didn't have a lot of money, and experience. Got paid in time so all good :)
21 hours, i worked most with sane concentration.
I remember when i was fresh in programing, felt for the first time that i have challenge to solve and it was a chain reaction i kept doing tasks 1 by 1 and volla 21 hours are passed.
I came office at 10 am and left 7 am other day.
After Finnish my work i felt so relive like i have concurred the world lol.
It was a feeling like i have all the time in the world and this is what i am passionate about so all i have to dive in this field.
During this session when i gained the momentum of work i could see that the production become double triple as long as you get sync with your brain. Felt like you are in some other time space where you spend more time but in reality its less same as we dream.
Honestly couldn't batten it down, but it's probably somewhere around 3-4 hours. Did a few hacking competitions in college, and that's about the longest I can handle being fully productive. Nothing like a hackerrank from hell where the Perl interpreter didn't work (I know, Perl, yucky), so I was struggling to code in Python during the competition!
3 days when I had to complete documentation for an audit. I only returned to my room to shower and change clothes for the next day. That too I left at 8AM and returned at 09:30AM.
2 days when I had to complete setting up the office network over the weekend. Note that this was over a weekend.
And this is without counting the many hours I've spent semi-working at hackathons. I've gone up to 60 hours without sleep, coding the shit out of my brains.2
Not for too long, really. Around 12-13h in the office and next 4-5h for my personal project. For a week. Then I stopped crunching and went back to 7-8h in the office and 6-7h of personal project.
For the final week of a group project at university, the project members and I ended up staying in the computer labs pretty much for 5 days. Another project group did the same (to this day we're still good friends). Everyone brought in their PCs from home and we ended up sleeping in the labs overnight. None of us went to classes as it was pretty full on crunch time to get the project done.
When it was time to eat, we each took turns to go on a food run for everyone, like getting McDonalds, or getting everyone coffee or energy drinks. Of course it wasn't all just work. At the time Quake 4 was just released and we had some pretty epic matches at 3am.