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
-
When you remember code from last night in the middle of your day and you know exactly where you fucked up.3
-
2 years into polytechnic I got my 1st big project as a subcontractor doing Symbian. No need to tell the company I presume.
Anyways, I was brought into the project just couple weeks before holiday season started. My Symbian programming experience was just the basics from school. 1st day I was crapping my pants out of anxiety. I pretty much didn't understand anything what my project manager or teammates were telling, so I just wrote EVERYTHING down on paper and recorded all the meetings to my laptop.
My job was to implement a very big end to end SDK feature. Basically from API through Symbian OS through HAL to other OS and into its subsystem. Nice job for a beginner :/
As the holidays were starting we had just drafted out the specification (I don't know how, because I didn't understand much of what was going on) and I got a clear mission from team lead. Make a working prototype of the feature during the time everybody else was on vacation.
"No problemos, I can do it" I BS'd myself and the team lead.
First 2 weeks I just read documentation, my notes and internal coding tutorials over and over again. I produced maybe couple of lines of usable code. I stayed at the office as late as I dared without seeming to obvious that I had no clue what I was doing. After the two weeks of staying late and seeing nightmares every night I had a sudden heureka moment. Code that I was reading started to make sense. Okay, still 2 weeks more until my teammates come back.
Next 2 weeks were furious coding and I got better every day. I even had time to refactor some of my earlier code so that quality was consistent.
Soooo, holidays are over and my team leader and collagues are very interested with my progress. "You did very well. Much better than expected. Prototype is working with main use case implemeted. You must have quite high competence to do this so well..."
"Well...I did have to refactor some stuff, so not 10/10"
I didn't say a word of my super late nights, anxiety and total n00biness.
Pretty much finished "like a boss". After that I was on the managers wanted list and they called me to ask if I had the time work on their projects.
Fake it, crap your pants, eat your crap and turn into diamonds and then you make it.
PS. After Symbian normal C++ and almost any other language has been a breeze to learn.2 -
Sometimes when I need a break from coding and life... I gather a bunch of wood and have a bonfire In my backyard late into the night and listen to Alan watts for hours... This guy is the most brilliant philosopher ever... There's something about a fire + a bottle of wine deep + Alan watts that simply puts me in the most peaceful state of mind I've ever had...
https://youtu.be/giZN0ZuDERY
17 -
For a developer 07:23 AM does not always mean early morning, it can also mean super late night coding ;)
-
Late night coding and my last git message is "changed a shit load of stuff...don't worry I got this"
Good thing this a personal project haha1 -
!rant
This is the second month that I'll actually earn money from developing software at my job, I'm so happy to finally see all the (self-)studying and late-night coding shed its fruits 😍6 -
Late night rant
You've been coding until 2 am. The moment you're about to get into bed (one leg already under the duvet) you have an epiphany about the code. Huge interior dilemma revolving around the "what to do now?" question.3 -
I worked for months staying up till 3am almost every night in order to collaborate with a team on another time zone. No one ever praised me or thanked me or gave me a pat.
Yesterday two members of that team stayed up till 2am once for the first time in their lives to make a release. They got immediately labelled as the most dedicated employees.
Okay, sounds fair.7 -
... late night coding session ...
... me, tired as hell committing last porting of changes ...
... git refuses my attempt for commit ...
....
$ git vommit -am ........
It's time to go sleep when you vomit instead of commit. -
Got a coffee grinder from my grand parents. Pretty old school, but I like it!! 😍
Just brew a big cup of coffee. It just tast delecious. ❤
8 -
I've been working on a proof of concept for my thesis for a few days and the async query calls drove me nuts for quite a while. I finally managed to deliver all query results asynchronously while still very much relying on a strong architectural design pattern. I am filled with caffeine, joy and a sense of pride and accomplishment.
1 -
You know that feeling when you're coding late at night and you get an error that you just can't parse with your tired brain, and go FUCK IT ALL, FUCK IT ALL
I'm having that feeling right about now...
6 -
Hello DevRant community! It’s been a while, almost 5 years to be exact. The last time I posted here, I was a newbie, grappling with the challenges of a new job in a completely new country. Oh, how time flies!
Fast forward to today, and it’s been quite the journey. The codebase that once seemed like an indecipherable maze is now my playground. The bugs that used to keep me up at night are now my morning coffee puzzles. And the team, oh the team! We’ve moved from awkward nods to inside jokes and shared victories.
But let’s talk about the real hero here - the coffee machine. The unsung hero that has fueled late-night coding sessions and early morning stand-ups. It’s seen more heated debates than the PR comments section. If only it could talk, it would probably write its own rant about the indecisiveness of developers choosing between cappuccino and latte.
And then there are the unforgettable ‘learning opportunities’ - moments like accidentally shutting down the production server or dropping the customer database. Yes, they were panic-inducing crises of apocalyptic proportions at that time, but in hindsight, they were valuable lessons. Lessons about the importance of thorough testing, proper version control, reliable backup systems, and most importantly, owning up to our mistakes.
So here’s to the victories and failures, the bugs and fixes, the refactorings and 'wontfix’s. Here’s to the incredible journey of growth and learning. And most importantly, here’s to this amazing community that’s always been there with advice, sympathy, humor, and support.
Can’t wait to see what the next 5 years bring! 🥂3 -
Just got Caffiene/energy drink vapes and they work like a charm within like five minutes. Productivity 💯 sleep 035
-
tl;dr
I am either the most responsible or the biggest idiot in the team
----------
TODAY.. oh boy.. fuck today. Like literally tuck this day and this shit. We ware doing releases for an integration we ware working on for ~1.5 months ... Aaand things went wrong - I guess we didn't make a sacrifice to the release gods - finally at around 8:30pm, being pretty much the last in the whole fucking office after a few last minute fixes I get my skinny ass on my way to grab a Corona and enjoy the public holiday tomorrow ...
Aaaaand I wish that was it, it turns out some things ware forgotten by.. well everyone aaaaand shit doesn't work (ofc ffs, why should it).. I see a slack notif and the feeling of dread gets me a couple of messages back I promise I'll be there in a couple of hours tops..and here I am ranting doing shit covering my desk with "food", hating my fucking self...
Me and the Head of Dev are literally the only ones working ATM... -
late at night..
should I keep coding
or.. you know, me alone with dark room, internet and laptop..4 -
Time for late night coding, debugging, thinking..been busy since I woke up, work, college, exams, work..work while waiting for an exam..
Coffee - check
Cigarettes - check
Music to keep me motivated - check
Laptop still not lagging - check
Will probably want to sleep in couple of hours - check -
Was coding all night & fell asleep at 3:30 AM. I was late for school so my mom was pissed at me. ☹️1
-
Machine learning is hard! Spent a whole day with Weka and it's Neural Networks. God my brain. There is too much to know before being really equipped to use this tool... especially from code.6
-
Software Engineer
Nerdious Geekius
The elusive Software Engineer is a nocturnal creature, rarely found at their desks before 10 or 11 in the morning, but often staying late into the night. They dislike being interrupted while at work, and it theorized that their penchant for twilight hours is an evolutionary adaptation to reduce breaks in their trance like state of coding.
Not surprisingly, Software Engineers are solitary creatures, except for occasional gatherings called "code reviews". In these gatherings, engineers gently pace around a clearing, sizing up each others work. Although occasional battles will erupt, they mostly end without injury and the engineer will retreat to their desk and continue to hibernate.
Fun Fact: Software Engineers have been know to kill each other in brutal fights over identation styles -
Do you guys know the feeling when your opening PR on side project late at night..
The CI takes forever to make all the analyses and checks and you almost fall asleep because your so fucking tired? -
When writing my term paper.
Did some caffeine and teeine fueled rage C++ coding.
Codes over the day and night.
On a sunday until moday morning at 5.
Started way to late.
Fucked it up. -
How many of you get late to your office/college/school bcoz of working late night on your side project.
I missed my 1st lecture today as well...4 -
2am: I can just go to bed at 4am and get 4 hours of sleep and be fine
4am: Eh, I'll just sleep at 6am and take a nap before work.
6am: Who the fuck needs sleep? That's why I bought coffee -
When I'm about to start a late night coding session I like to brew a pot of green tea. In theory there is less caffeine than coffee.1
-
From few months I was coding late night like 3 to 4 AM but now I can't sleep at night at all 🥺 shit man some time I just think through this and go to mountains 😞10
-
I have found that once you work for a company where you have to implement everything in its raw form using the raw language and raw logic, you really have to know what you're doing and knowing some basic/medium programming and having some algebra knowledge doesn't cut it (unlike some people think).
I've been at two sides of the coin: I worked for a company that had everything in place, a framework that handled all edge cases and what not and I just had to focus on user stories, but I also worked for a company where I had to do everything manually.
For example, at the latter company I had to know Discrete Mathematics; truth tables to their most convoluted and disgusting form, having to be able to apply this on a late Friday night with a headache and lack of food and sleep with the PM stressing out.
I've had to deal with NOT AND OR AND OR AND OR AND branches or whatever, where an OR behaves like an AND and if you want a value between an AND AND and an OR, you'd have to do a NOT OR.. to think about latches, all in my head, sigh, anyway, within limited time constraints, without even having time to write tests, having to make sure that everything checks out while the client is breathing down my neck. Yeah, not such fun times.
I'm happy for those of you who can just write some moderately difficult logic but you don't have to break your head over doing everything manually, as if you're in the coding stone age and nothing is taken care of.
Companies like these make me want to run away.3 -
CodingRoom room = new CodingRoom();
room.lights = true;
// or
room.lights = false;
// how do you like it?12 -
Coding late at night to meet a deadline, feeling tired so I decide to finish it off early in the morning and my mind is like..
-
When coding in bed late at night, sometimes the cat mewls outside the door.
Unfortunately she sounds like the baby from Eraserhead and damnit if that isn't off-putting :/
It's creepy as hell. -
Ah, the ancient art of copy-paste development – where originality goes to die and bugs come out to play. It's like a cursed incantation that tempts even the best of us into the dark abyss of shortcuts.
You think you're saving time by copying that snippet from Stack Overflow, but little do you know, you've just invited a horde of gremlins into your codebase. Suddenly, your once-cohesive architecture looks like a patchwork quilt sewn by a drunkard.
And let's not forget the thrill of debugging when you realize that the copied code references variables that don't even exist in your context. "Ah, yes, I remember copying this gem at 2 AM. What could possibly go wrong?"
But wait, there's more! Copy-pasting also introduces a special kind of chaos when updates are needed. You find yourself fixing the same bug in five different places because you couldn't be bothered to encapsulate that logic in a reusable function.
So here's a heartfelt salute to all the copy-paste warriors out there, bravely navigating the treacherous waters of borrowed code. May your future coding endeavors involve more thinking, less CTRL+C, and a lot fewer late-night bug hunts!1 -
Couple of questions? What's to late to stay up coding or what's to early to start coding in the day?
I'm personally always mindful of my health.5 -
That thing where you stay up way too late and end up dereleasing and refactoring a huge chunk of The Monolith....
Top Tags
Weekly Rant
View