"Be ready now! We're launching our new product at 0800!"

28 hours later, one registered customer

- you don't like math
- you don't like study
- you don't read documentation
- you throw out the manual
- you like to punch a clock
- you dislike books and reading
- you don't ever work more than 8 hours
- you can't tolerate the occasional weekend work day
- you fold under pressure
- you aren't good at crunch time
- you can't do on-call without committing seppuku
- you don't have attention to detail
- you aren't interested in technology
- you're not good at explaining things
- you can't deal with change
- you're not excited by the prospect of extreme variety
- you don't have the ability to focus
- you can't deal with ego without resorting to violence
- you can't deal with someone calling your baby ugly
- you can't discriminate between fact and opinion

And many, many more

Project Managers be like "hey bruh, I just wanted to put a meeting half way through your crunch for a deadline to make sure we can meet that dead line"

Shalom my dudes!
A quick GT from my college years:

>be me
>barely knew how to program but eager to learn more and more
>end of first semester, teacher assigns a couple of classic games for extra points
>battleship, pacman, sudoku, tetris, etc. All done in C
>end up with tetris
>2 days later I have the final build, including all the tech shit like walljump
>start thinking to myself "this looks really fucking ugly, what's wrong with me??"
>look up graphic libraries for C when a light flashes on my computer screen
>*NCURSES*
>the next 2 weeks were a montage of me learning linux, understanding ncurses and redoing my code (plus bug fixing)
>presentation day
>palms are spaghetti
>knees? Spaghetti
>arms? Spaghetti
>class is impressed with my work
>professor comes up to the board and tells me that I get a 0 because it wasn't "pure C"
>clenched my jaw and walked towards the dean office
>"hey, mind if I show you something?"
>open my laptop and show him the game
>he's having a blast since every time you do a 5 row crunch (a tetris), a piece of clothing of a random model comes off
>explain to him what happened in the classroom
>he looks at my code, runs it on a plagiarism checker and tells me that he will edit the grade himself
> a week later there's a 10 on my grading area
>feelsgoodman

Shit morning, I work in tech, so I guess it is related haha.

First, I wake up and it is cold. Like -12 degrees Fahrenheit. With wind-chill, feels like -29 according to Google. Then, while getting ready for work, my only belt breaks. Not a little, but literally splits in half! Fucking sucks, as my pants keep partially falling down and my shirt keeps untucking.

I go out in this cold that could kill a polar bear, go to start my car. Can you fucking guess? Dead fucking battery. Fuck! Now I am super late to work.

Make it to work, and guess what? My manager just promised 100% completion by Friday, and we are weeks behind! Fucking sucks... I think my coworker snapped, as he keeps hyperventilating at his desk for no reason. Oh and our best coder just quit...

Waiting to either wreck my car or find out my dog is dead when I get home...

Best: Finally left the video game industry for a "real" software engineering role!

Worse: Left work at an exciting studio and fun projects for shorter hours and more pay, and it's incredibly boring and I actually *miss* the crunch and chaos.

Last night I was exploring the feasibility of cracking the WPA2 key of my own router at home. I set out on a late night adventure, set up a couple devices and, knowing the default password convention of the manufacturer, setup a Hashcat instance with the relevant masks on my laptop, created a Crunch wordlist and ran aircrack on my Raspberry Pi 3, and thought "Hey - maybe there's something for Android too."

Hashcat on Android is a cat based social media app. I'm a little scared.

Been a while but I'm back with fresh rants.

If you look in my history you will see support wanted us devs to start paying for writing bugs. Now the release presentation has passed but we're still in crunch time because we can't put clients onto the new version yet. And in the meantime our coffee machine broke. So support has started to manually pour coffee, which was actual real nice of them.

Now yesterday I'm in a hurry and the coffee is out so I decide to pour a quick cup for myself with the leftover grounds. When I'm back at my desk I get a call asking if I just made coffee. I'm like yeah something wrong? Proceed to get chewed out for being selfish and that they see how it is with me, then get hung up on before I can even explain.

So yeah not only is my company too cheap to get a new machine, the lack of one causes drama.

Today however our network guy, who was present when my colleagues asked what was with the weird phone call, brought in his own machine and let me have coffee from it. Meanwhile suport can keep their crappy manual pouring. And I don't need to go into their office anymore.

Last week I sent a pic of Nestle Crunch chocolate to my friend in Whatsapp. Today he told me that he got an ad in Instagram for Nestle Crunch!! Holy crap!
We were trying to figure out how did it happen because we never discussed about the chocolate other than that image. Then I realized that Whatsapp and Instagram was owned by the same fucking company - Facebook!!!

I've stopped using Facebook, Instagram for a very long time and I have ad blockers on every electronic device I touch. So I never understood the gravity of people losing shit over privacy, until today. This indeed is creepy and it hit me real hard. I'm now reading all rants with "privacy" tags and methods to harden my devices to repel from those buggers.

After like half of a year crunch, when I was working 10-12 hours a day and no one was paying for overtime I was finally moved to next project. We are working in a field where everyone is completely new to it, except me BUT I didn't admit to that. I complete tasks faster while taking remaining time back!

Raging here, overheating really. One spends thousands on technology that is promoted with the catch phrase "it just works", yet here I am, after updating my fancy new emoji maker (iphone x) to 11.2 and then attempt to carry on working by compiling my code to test some new features. And...

oh, whats this xCode? You have a problem? You can't locate something? You can't locate iOS 11.2 (15C114)... sorry and you think that this "May not" be supported in current version of Xcode?

Let me get this straight you advanced piece of technological wizardy, you know you are missing something, you in fact know what it is, you can actually TELL me what is missing and yet, still, in 2017, you can't go FETCH it?????

Really? All you can do is sit, with that stupid look on your face, and watch the paint dry? Your stuck? That's it?

I hate you for the false pretense of advanced capability. and for your lack of a consistent dark theme so my eyes stop bleeding when reading your "I don't know what to do" messages...

By the way, maybe you can stop randomly crashing, or pinwheeling, I get that your bored as a machine designed to crunch numbers/data/code all day long and that for fun you feel you have to add some color to your subsitance. But stop it. Do what I'm told you can do, "JUST WORK" for once without me having to drag you forward kicking and screaming.

K. that feels better. Now for some whiskey.

Fuck this day!
Like really fuck it!
I have one of the most terrible crunch-time i ever experienced.
I’v been working 12+ hours every day with an ever-changing project timeline.
It started simple, we made a timeline, it was risky even then but it was realistic, we started working immideatly, everything looked good then a few days in BOOM! Actually our project management completely forgot client B’s projects soo we need to do that too with the same fucking deadline!!! (About 10x more work in waay less time)
Then this morning i got an email from the graphics team that we need to document our design process RIGHT FUCKING NOW! Because management wants documentations, in the middle of a fucking crunch-time.
Today it almost got physical with my project manager, i told him that he is not a programmer, i dont fucking care about his shit, just fuck off and let me work because we won’t be ready based on his unrealistic bs.
I feel like completely fucked over, like we were told 2 days before deadline that the whole company and people’s jobs depends on us now because if we wont finish this clients won’t pay.
WE ARE TWO PROGRAMMERS for studio of 10-12 people!!!
Soo i’w been thinking about getting the fuck out of here ASAP, i got an offer from a pretty big international gamedev company just what i needed, i already did their test before all of this, i passed A+.
We scheduled a skype interview for today. I had completely no time to prepare or chill off, just got out of the office, got into a starbucks and i’m interviewing. No time to even check my mic or internet, the call was so shit i could not hear anything, they neither because the plaza was loud af. Meanwhile im nervous about work, about the interview, about can they hear me at all because of the noise. I fucked it up. BIG time! I was so done i could not reverse a fucking string in c++ or explain what is a signed int!!!
Needless to say they said no.
Need time to think about it or realize what happened? Nice dreams. Back to the office and continue working.
I can’t do this anymore. My girlfriend came for me and took me home at 10pm but all i could do was stare at the floor on the subway. I don’t want people to lose their jobs but i just phisically can’t do this anymore.
Meanwhile any time i talk to my project manager about being tired he says like “hshshsbsb i have 60 hours in the last 4 days i got the worst part, i would be grateful in your place..” like fuck off dude, i dont give fuck about how you feel about this. This is not okay for me, you did this to the project, your fucking job is to manage it! I have one day off before going back to this, i have completely no idea what to do now...

[ps: this is not Nemesys. They did not let me work on my own stuff because i would be a competitor, so i left.]

Woo crunch time! The 3 panic attacks a day, no sleep, massive guilt complex, caffiene addiction, lack of seeing my wife, phone breaking(calling doesn't work), lawn needing mowing, upper management bothering all of my team, more guilt, more panic, inferiority complex, theory that coworkers think I am slacking, and technology just not working because the machine spirit decided I pissed it off is starting to get to me a little.

When something breaks 5 minutes before you leave the office:

Project manager, who i've complained in the past is neglecting critical things that he doesn't want to do, decided today to cancel our weekly planning meeting, to have the below conversation with me 1:1. Its very long, but anyone who has the will to get through it ... please tell me it's not just me. I'm so bewildered and angry.

Side note: His solution to the planning meeting not taking place ... to just not have one and asked everyone to figure it out themselves offline, with no guidance on priorities.

Conversation:

PM: I need to talk to you about some of phrasing you use during collaboration. It's coming across slightly offensive, or angry or something like that.

Me: ok, can you give me an example?

PM: The ticket I opened yesterday, where you closed it with a comment something along the lines of "as discussed several times before, this is an issue with library X, can't be fixed until Y ...".

"As discussed several times" comes across aggressive.

Me: Ok, fair enough, I get quite frustrated when we are under a crunch, working long hours, and I have to keep debugging or responding to the same tickets over and over. I mean, like we do need to solve this problem, I don't think its fair that we just keep ignoring this.

PM: See this is the problem, you never told me.

Me: ... told you what?

PM: That this is a known issue and not to test it.

Me: ..... i'm sorry ..... I did, that was the comment, this is the 4th ticket i've closed about it.

PM: Right but when you sent me this app, you never said "don't test this".

Me: But I told you that, the last 3 times that it won't be in until feature X, which you know is next month.

PM: No, you need to tell me on each internal release what not to test.

Me: But we release multiple times per week internally. Do you really need me to write a big list of "still broken, still broken, still broken, still broken"?

PM: Yes, how else will I know?

Me: This is documented, the last QA contractor we had work for us, wrote a lot of this down. Its in other tickets that are still open, or notes on test cases etc. You were tagged in all of these too. Can you not read those? and not test them unless I say I've fixed them?

PM: No, i'm only filling for QA until we hire a full time. Thats QA's job to read those and maintain those documents.

Me: So you want me to document for you every single release, whats already documented in a different place?

PM: ok we'll come back to this. Speaking of hiring QA. You left a comment on the excel spreadsheet questioning my decision, publicly, thats not ok.

Me: When I asked why my top pick was rejected?

PM: Yes. Its great that you are involved in this, but I have to work closely with this person and I said no, is that not enough?

Me: Well you asked me to participate, reviewing resumes's and interviewing people. And I also have to work extremely close with this person.

PM: Are you doubting my ability to interview or filter people?

Me: ..... well a little bit yeah. You asked me to interview your top pick after you interviewed her and thought she was great. She was very under qualified. And the second resume you picked was missing 50% of the requirements we asked for ... given those two didn't go well, I do think its fair to ask why my top pick was rejected? ... even just to know the reason?

PM: Could you not have asked publicly? face to face?

Me: you tagged me on a google sheet, asking me to review a resume, and rather than tag you back on 2 rows below ... you want me to wait 4 days to ask you at our next face to face? (which you just cancelled for this meeting)

PM: That would have been more appropriate

Me: ..... i'm sorry, i don't want to be rude but thats ridiculous and very nit pick-y. You asked my opinion on one row, I asked yours on another. To say theres anything wrong with that is ridiculous

PM: Well we are going to call another team meeting and discuss all this face to face then, because this isn't working. We need to jump to this other call now, lets leave it here.

Clients that ask you to build X and then when you ask about said details to know everything up front, you get a deer in the headlights look.

I get it, not knowing right away is fine, but 5-6 months later and still "not knowing", being absolutely lazy with no responses to questions or just dumping the work to me to figure out from whatever source material you got it from and force me to crunch to save your ass isn't fun for me and I really don't give a shit about how much praise you give me publicly for the job I did.

- Procrastinate 1 work day
- Try to crunch 2 work days into one
- Feel frustrated because there is not enough time
- Repeat

I am currently under a desperate crunch at work, trying to get things wrapped up before my honeymoon.

Of course, this is when My Greatest User decides he will come to my office no fewer than five times today. Not once was it for an actual, legitimate issue that he had not created himself. Here were the top three for today:

#3
MGU: "The scroll wheel on my mouse isn't working. I used to be able to scroll stuff with it but now I can't."
ME: *Looks at his mouse. All looks well.*
ME: "Show me what you're trying to do."
MGU: "I'm trying to scroll this Word document. See? It won't scroll!"
ME: ..."That's because there is nothing to scroll... The entire document is on your screen..."

#2
MGU: "I can't move my mouse off the edge of my screen! I used to be able to move it from my monitor to my laptop screen and I can't do it anymore!"
ME: "Did you move your laptop?"
MGU: "Yeah I moved it to the other side of the monitor. That shouldn't make a difference, should it?"

#1
MGU: "You know the DOS commands?"
ME: *Does a triple take.* ... ... "Huh?"
MGU: "The DOS commands. You know how you can use DOS commands to make the computer do stuff. Like Ctrl+M."
ME: "Ah. You're talking about keyboard shortcuts."
MGU (ignoring me): *Goes on a long, confusing explanation of something he's trying to do in Outlook and wants to know a keyboard shortcut for instead of clicking.*
ME: "I don't know what the shortcut for that would be and honestly I don't have time to look right now. I really need to keep working on this project."
MGU: "You don't know?"
ME: "Nope."
MGU: "Oh... I'd have thought that with being a programmer you'd have gotten into the DOS commands."

I have never been so tempted to quit.

I'm lead frontend developer/ consultant on a big government project, it's 10 days to release and I couldn't make it to a dinner with girlfriends extended family.

Pretty sure I just got dumped as she doesn't want to be in the way for my work so she is packing her stuff and leaving my apartment tonight.

relationshipsFailedDueToWork++

Stupid me.
We were on a time crunch for giving a demo. A friend wrote a piece of code and he said it was working exactly the way it should be and that we can directly transfer to my machine and run it. He ran the piece (on his machine to show me) and it worked.
I take the source from him transfer it on my machine (because mine was going to be used for the demo).
Demo begins, everything goes smoothly ...all up until the point of the last module demo. Alas, the transfered module didn't work. Tried debugging during the demo as everyone was cooperative and patient. Turns out I hadn't done an initial setup required for that module. Embarrassed! 😓
Should have tested before the demo. 😞
FML. But from that moment forward i make sure to test every code I get from others as well as the one I write.

For anyone planning to ask me, I don't remember what the piece of code even did. It was a small time side project with a company. Not revealing the company's name.

What if people, life, humanity, the universe is just a cluster of CPUs running a giant Recurrent Neural Network algorithm? 🤔

-Sun and food == power source
-People == semiconductors
-Earth/a Galaxy == a single CPU
-Universe == a local grouping of nearby nodes, so far the ones we've discovered are dead or not what same data transport protocol/port as us
-Universal Expansion == the search algorithm
-Blackholes: sector failures
-Big Bang == God turns on his PC, starts the program
-Big Crunch == rm -rf

Hitting a really deep, deep low in the manic-depressive roller-coaster of the development cycle:

There comes the crunch time. No meeting goes by hearing the odious: "We don't have time for that." - One critical component needs to be finished for Big Sur and instead of addressing the real issues we keep changing design and goal. One main dev already gave up fighting the PO and team lead(!) - and now I'm next. So that dev build this really clean and minimal library as the core part. But now it's just like, yeah, take that nice Porsche engine put it on the old rusty bicycle from the shed,.. but maybe because that's so shitty we need that specially formed exhaust pipe to tune it. Yeah, very 'agile' - Only thinking about it makes me shudder in disbelief and anger. I shouldn't take that shit so serious, be emotional about shit code, I know, but I can't. Let them drive some rounds around the block, if it runs at all,.. because until now we still didn't make it run on the fuckin' street. It's all so insane. Will make some nice fireball, when it goes up in flames.

Well, I have been part of quite some shitty projects. Real suicide commandos set out to fail, and somehow stood them through or made it even "work" though it should never have. But what enrages me here is, that it needn't to be that way. We had plenty of time. Our team was often rowing along in good rhythm. And now I just feel drowned in resignation and sarcasm.

I hate being in program purgatory. You don't know whether your program froze, or the CPU is hustling to crunch out those numbers. To kill or not to kill. That is the question. Q.Q

“Practical” tech interviews for senior roles (from my experience): DONT worry! We won’t give you any “leetcode” problems!! Instead, we’re giving you only 40 minutes to do this huge laundry list of tasks that are simple but hella time consuming. We want to see how fast you can type. So you have 40 minutes to write a mini app while we take note of the shit ton of simple errors you make due to the time crunch as your fingers burn through the keyboard and then wonder why no one can pass our “simple” tech exam!!!!

DAMMIT!! the only tech exams I enjoy are ones that involve refactoring existing code bc everything else is a fucking speed test! I’d also MUCH RATHER take these exams WITHOUT someone there taking notes like I’m a fucking lab monkey!

Recently i learned about pipes in C#. I made 2 simple console apps(client and server) in visual studio. They work flawlessly. After that i made plugin for unity that uses those pipes. (because i want to crunch numbers in .net 4.7 app and display results in unity). Every function in my plugin is wrapped in try-catch block. Unity frezzes/crashes everytime i try to use my plugin 😥

Roll into game development, preferably one with not so much crunch.

But i have yet to actually make my own game, the path behind me is filled with unfinished projects.

At least I'm a half decent backend developer.

What a week!!

Seriously exhausted. Crunch time to launch a brand new service... Pulling all nighters and stress.

Looking forward to having many beers with the boss to celebrate once it's a done and dusted.

If I'm not productive during the day, idk what you expect holding me 3h after work will do.

Maybe not keep your employees in perpetual crunch for 2 years, and then berate them for missing the deadlines that YOU SET!

My girlfriend, at the end of a totally unrelated bachelor's degree, has decided she wants to go into web design (or really design in general). Which is exciting cause her degree... Well, let's just say jobs aren't lined up.

I'm a front end guy and I have a lot of experience with UX, so time to crunch some learning in. Takes me back to my self teaching days haha, students becomes the teacher 🙈

My biggest influence on coding style is:
"If code make reviewer puke, code bad."

In all seriousness though, I think the biggest influence is seeing messy code and not trying to replicate that.
I think every code file, however ugly it is, tells you a story. Maybe the coder was less experienced, maybe it was written during crunch or the coder is an enterprise software engineer who has to make a factory for everything and everything is generic.
In my opinion there is no perfect code style. You do what's required and hopefully in your best ability, and, as a bonus, think of the person who has to look at your code next...

For me it's kind of hard to tell whether my code is good. I have no reviewer in the company, which brings the risk of writing code so only you understand it... but so far it has worked and I've definitely seen worse than my 1 year old files. 😄

Rant...ish? It's more mixed feelings...

Had my first day yesterday at a new job in a big company. I came dressed really nicely in a suit and tie. Went to orientation with everyone new coming in.

Felt like I made the right choice to up my effort in dress code.

Met with my manager, was led to my team. Everyone is dressed casually. Unshaved. Giving me hate stares.

Felt out of place. But kind of happy that I can try less.

Still. What's up with programmers and being toxic to people dressed nicely o.0 I don't need to look like I came out of crunch time every single day to prove my worth...

It's really weird getting these looks. It's almost like highschool all over again. When I let my mother dress me and looked like the nerdiest kid on the block...

Then again, today I'm wearing sneakers and causal clothes. I either feel like I cave in to peer pressure... But at the same time I don't mind it. Erghhh... Still hate this...

Mixed feelings... I donno.

I have a lot of fun during crunch time.

It's like running a marathon. It is both physically and mentally taxing, and I get a rush out of seeing how hard I can push myself.

But like a marathon, it suuuuucks if you are not prepared, or you otherwise didn't want to do that.

You hear that bosses?
Crunch is like running a marathon. That thing that people, who prepare for years to do, still causes them to piss and shit themselves while their nipples bleed. And that's when they are fully prepared. That is what you are asking your team to do without any notice ahead of time.

"Ok Derrick, I know you wanted to visit your family in the country this weekend. But we need you to run uphill, fuled only by diet dr pepper and fear of loosing your job, untill you pass out and need an I.V. to keep you from stroking out. '

Otherwise a lot of fun.

Producer: "We're in crunch mode."

Me: "I don't crunch. I glide."

It's hard for me sometimes to tell the difference between a dev who actually got fucked and a dev who just didn't know how to budget their time correctly...

I've had freelance web friends who will go out partying twice a week... I've also had freelance web friends who shutter themselves indoors the moment a project of significance comes up. Both types have complained to me about crunch time.

Obviously i can't tell a whole story from just a devRant thread, but for a select few of them i really feel like this person just had no idea what they were doing, were negligent, or estimated their time way under the cut.

I'm not calling anyone out, I'm just saying that when you post about crunch when the item is something fairly obvious you should've been able to catch within the first week of the project, it makes me doubt your sensibilities.

Obviously I'm not making any judgements or saying that i know even half of what you know about the project and the job, but I'm just saying a little more detail couldnt hurt...

With crunch time closing in, everybody but me seems to call in sick.
Nice move, colleagues, nice move.

I don't understand why managers are not held responsible for the under estimated timeline of the project, the developer will suffer from the overtime and crunch of coding.

Log 1:

Day 10 of crunch time. I have entered a sleepless zen state. Lord willing, I will be able to get 7 hours of sleep Saturday night. The building is terrifying at night, as there are a lot of noises. Security guards are nice, but curious to see me all alone. Must not show weakness in case they think numbers will give them an advantage over me.

Supplies are low. Only one type of energy drink left in the machine, and coffee gone for the night. My phone is out of fast data so Pandora is spotty at best. I have battery to get me through the night at least.

Tomorrow and Saturday decide the fate of the project. My team lead has not slept in at least 2 days. I feel guilty napping when I do, but she is driven like Ahab so I will let her obsession carry her.

If I am alive tomorrow I will report in.

Chances of getting all the bugs fixed before the demo...

"What do you think Abdul? Can you give me a number crunch real quick?"

I can't stand how big tech companies treat you like a child. Every fucking team bonding activity is more childlike than the other.

Its like they are about to bundle crayons and pizza next time you are on crunch.

junior developer raises an issue saying that there's an application deployment error on one of their dev clusters.

sysadmin asks them to go back and look at the error logs and come back with the problem.

they come back saying, "No space left on device"

sysadmin takes a look at server. finds this :

Terrible project with unclear requirement, lots of legacy and a client that doesn't know what he wants. Quite a bit of procrastination because of this situation, then crunch day & night to hold the deadline.

Then the project was scrapped.

Seriously guys, how do you deal when remotely collaborating with lets say not the most motivated and competent devs?

Our scrum team got formed about 6 months ago from leftover devs of other teams, choosing a couple competent devs at the core and other devs who were kinda gotten rid of by their old teams, and after 6 months of working together I can see why.

Situation is that we are 7 devs in our team and 4 of devs are not pulling their weight. They are seniors on paper, but in reality not really.

They rarely take something complex to work on and even if they do, they make sure they take as much time as possible. Two of them are contractors who I imagine decided to treat the job as a paycheck and nothing more. There is no initiative, no push to make things better and in general attitude is to do bare minimum: only what is being asked and then delaying the hell out of tasks.

Im not exaggareting: Im talking about every possible way of dragging out the tasks: delaying communication, sitting around for a few days while not asking for new tasks to work on if they are blocked, also avoiding standups. Working for days on very basic comments in their MR's. Getting "sick" for a couple days on deadline when things get tough, so that someone else would come in, refactor and save the day. Once or twice it could be a coincidence, but nowadays I can already guess ahead of time what kind of trick they will pull now.

Our project is an android app where we have to support few different tablets, so the most recent new trick that I witnessed is devs avoiding hardware delivers, sometimes for months. Idea seems to be if you dont ping your team that you dont have hardware, then you can avoid working on related tasks with that hardware.

Worst part is that they get away with it. Our teamlead is a senior dev who is first time teamlead, doesnt code anymore and doesnt want to rock the boat. He is the type of teamlead who sets arbitrary deadlines, makes it sound that they are urgent and takes a few days off in the middle of chaos just before deadline. Restrospectives don't help at all and if I try to bring up stuff directly to him he tells me to bring it up during retrospectives. We discuss issues, rant a bit ant then continue carying on like nothing happened and nothing changes.

So little by little in the past 6 months we came to this point where 2-3 devs are carrying the weight of the team and are in a constant crunch mode, while others are allowed to slack. Its becoming ridiculous.

Problem is that this is starting to affect our morale. Only way that is left to keep my sanity right now is to pull away sometimes and also slack. Then I come back at full capacity, give my best for a couple weeks until I have to go and fix some basic leftover task that has been purposefully dragged out for 2 months and left unfinished, then I just want to scream and I know that its time to disconnect again.

You know you're tired when you're setting up unit tests and you make more mistakes in setting up the tests than in the actual code.

"I am barely awake, it must be like 3-4 am. This has been a long day at the office!"

It is 11pm... Long night to go!

A production build of the hello world example for Blazor takes 5 seconds to launch. Half-baked, rickety sad excuse of a technology built in a crunch and never rebuilt correctly.

The simple yet surprising reason why it's so fucking slow is that Microsoft couldn't figure out a way to compile C# to webassembly while also beating others to market so they compiled the runtime to webassembly instead. The Fucking IL interpreter.

It's Friday...
It's crunch day...

Here in SG speak (Singlish), we say "chiong ah"... means "to rush"...

For the game devs out there … Is following a game developer career a good idea ? We always hear about crunch and no work life balance. Im thinking about changing my job( currently a dev at a fintech company) for a while and need some insights from you guys :)

Well today is shit, and we probably have to continue our 3 week streak of crunch time. FUCK!

Crunch time.

Crunch is coming....

So much work, so little time!

Be honest. Given that you're not in crunch mode. Do you actually work 8 hours every day?

I have had some days but usually it's impossible for me to do actual work as a developer for 8 full hours, 5 times a week.

I feel that (without meetings), my ideal schedule for days of normal workload would be 5 hours a day. I'm strictly speaking about focused work, actual programming. Meetings don't usually rack up more than 2-3 hours per week for me.

I do my best to be in the office during the expected hours but I can't help but feel that everything about my engagement, focus and contribution at work would be better if I could just stroll in around 10, well rested, do some actual work, take a short lunch break, go at it again and go home around 15:30...

Because I feel like this I quickly get judgemental about myself if I come in at 9 and leave around 16:30 too often during a work week.

What are your thoughts on this subject?

I have been on crunch time for so long, with so many hours I don't even know what day of the week it is. I legitimately had to look it up. I also calculated my hourly rate for the last 3.5 weeks, and I was making the same as a grocery store bagger! Being salaried sucks in times like this. I am paid peanuts.

Last night I woke up every 30 minutes in a panic I was late to work. This job is killing me, and all because the sales team sold the product on an unrealistic deadline, for no money...

In addition, I am gaining weight, haven't seen my family for any significant period of time for ages, and Taco Bell knows me by name and order...

On that note, next Monday I am going to go into my boss' office, and demand like a 50%-75% raise! I am terrified! Haha

Migraines are fun though. THE PAIN PROVES I AM ALIVE!

Look what arrived just in time for another crunch time weekend. This ball will surely see some usage the next few days 😀
Thank you so much @dfox!

We all have that guy in the team who everyone loves because he is such a laugh, but doesn't do shit and we have to work extra to be able to barely meet the deadline

1) IList doesn't have an AddRange.
2) WPF bindings must be ObservableCollections
3) Comboxes using Event Notification on PropertyChange are originally developed by some dope at Microsoft who still doesn't comprehend Big-O
4) LINQ can only do so much...

It's Christmas. My gift from Santa is trying to get through an end of year crunch on a project that is made entirely out of hot sweaty year old garbage, and the garbage collector is a halfwit who comes seemingly only when they want to, regardless of when I call Dispose().

It's 12:26pm here. That means it's time for bourbon and a good bit of "F*** this, I'm done for the day."

About to go on crunch to release a feature that is late. I have my own blame to put on it, as I wasted a lot of time, but goddamn.

Every time I said we'd need to take time to test for corner cases and check for errors here and there, my boss told me I need not worry about it, it's just an MVP. Then the marketing people see the feature half-ready and start suggesting their own changes. Then the idea of the project is refined and changed, a new subfeature is added, new backend business logic is added, right as I'm about to finish the original core features. They have the full product in their heads and are already selling it to people while I'm still catching up with quite a significant number of tasks. Now I have to crunch to launch tomorrow morning.

I do mainly the backend parts, but while a frontend guy who knows his CSS does components and pages, I'm the one to figure out pretty much all logic, and how to stitch said components and pages together and how to make the frontend interact with the backend. I'm supposed to do this whole thing and also deploy it all. Hell yeah.

Better get started...oh look at this shiny new piece of tech. 3 days later with evaluation done on each usable tech alternative crunch the solution together in record time with tech most similar to your previous one.

I'm pretty much at my dream job currently. A lot of autonomy as a developer, solo projects, as there are only two developers in-house and each of us is covering roughly half of the systems, we rarely work on the same thing at the same time. We do have weekly sync checkins to keep each other appraised and offer a helping hand/eye when needed.

But.

There's always a but.

Our IT department used to service 500 to 1000 employees 7 years ago, and now, through growth, opening new sibling companies, and merging with our competitors we're at 6k, give or take.

Maybe it's the aftermerge crunch to harmonize our IT systems but I've been working 10+ hours from August. It's an interesting couple of new pieces of software that I'm writing but, the deadlines are pretty tight and business requirements are anything but tight still.

I love my job, but I wish to get the bigger stuff done soon so I can take it easy.

Last two week have been great.

Nothing to rant about.

...crunch is comming.😑

Customers CEO insists we need to start the 3 weeks to deliver crunch website project by having the hottest UX design on the planet done by a professional UX specialist specializing in hotness who might charge a lot and take a few weeks and leave us no time to deliver said hotness. Grrrr.
I felt like Sirus Black as a dog bouncing of the chest of the werewolf.
When I explained in full why it's a great idea to have a great UX concept, the project is an education website, for the government, and it's WCAG AA. Balanced against all the reasons that we had more urgent things to look at with such a short timeframe they insisted "The UX Guy" will save us. Dear fascist bully boy. I am a UX guy! I may not be "The UX Guy" but I remember when Javascript was for popups and the extent of most peoples PHP was sending forms via anonymous SMTP. I bet the design will look something like the CNN website or Apple.com. Both bastions of web accessibility standards. Grrrrrr.

So this modeler on a Dev call, I have this new shiny model, let's release this to production mid November😳 (Seriously that's how he started out the first conversation).

2 min silence, everybody looks at each other for reaction, just like a TV shows !! 🤣🤣

And the my Manager lists out the things that would be required to before we ship this out.🤐

Modeler : Oh I guess we won't be able to deliver it this year.😤

I am like what were you thinking. Everything is not just import an Excel in R and crunch numbers and write reports and show graphs. is it?

There is a real development cycle that has to do all of the above on not so pretty data, at scale reliably for 100s of clients and not just your laptop.

So... there is a bank. And the website for example is using "https". Alright. But the Login consists your login ID (in the most cases your account number) and a Pin number ( only 5 chars) If i remember pentesting, crunch etc a pin or password with 5 chars (included special characters) is fast hackable or not? Or is it super secure cuz of the "https"?

Just spend the entire weekend preparing for, execution and cleaning up after a live stream.
When we'll, but holy shitfuck was it a stressful experience.

The guy in charge and with the vision pulled this one out of his ass, 12 hours before going live:
By the way, that system I talked about, where a moderator can pick comments from the YouTube chat, so that the hosts can look at the useful ones and choose to have them shown on the stream. Yeah, it doesn't work and you are better at programming than me, so you fix it.

Good bye sleep 😔

So this is what 'Crunch' feels like 😦

Game build on 12th Friday.
Crunch time ahead.

So, if anyone remembers my previous rants (or otherwise), the app I'm working on is finally going to release. We release in about a week and a half, despite having at minimum 10 days work + testing (not including all testing of aws migration that we still haven't fully completed) to even have an MVP.
This is all because the clients have been pushing a release date (16th July) in marketing. Oh, and the icing on the cake? Our boss agreed for a submission to app stores (back-end pending) on Friday (yes, in like 3 days) instead of the agreed next Wednesday date.

Side note: the client is coming over to our office for Thursday and Friday. Why? We are unsure.

I (frontend) was given 2 weeks to develop a new feature of the app. Almost after the end of 1 week, backend guy was finished with his code , with still bugs pending. Since backend wasn't ready for most part of the development process, I was working on my part, basically creating functionality and created views using the UI guys wireframes.

Now, we were on a time crunch , I didn't got enough time to improve the wireframes or to work with the UI guy . I released on staging environment and no one liked the UI.

App feature was supposed to be released on Tuesday. Shit hit the fan and i had to create a new ui, code the new parts of the app, do shit ton of other work and extending the deadline to today.

As of now backend code is still not fully functional,
app is ready but edge cases still not tested and I have to pull an all nighter to finish this fucking piece of shit.

That moment when the project lead shows up with a fake smile at 11pm Friday after a 3 week crunch and tells you the last two days of ridiculous overwork from 9 am to 6 am where pointless because Mr. big shot CEO has a better idea for the meeting with the client on Monday.
So now so we have to work over the clock the whole weekend to cover their managing failures.

Consecutive hours: ~24, it was a hackathon and not terribly interesting.

I did however have an exciting new experience this exam period; a 5 day crunch with strictly timed 6 hour sleep breaks, half-hour lunch breaks and the rest entirely populated by work. I live 5 minutes from the CS lab so this pretty much meant 18 hours of coding per day, 90 hours in total.

Think of this the next time you're trying to decide whether to announce that you aren't going to contribute to a group project.

I'm working on an internal overhaul for Orchid phasing out the last bits of code from May's crunch and making the loading pipeline much more transparent and easier to optimize, but I'm starting to get really tired of high theory and tree walking algorithms.

What are some light hearted projects that can benefit from a scripting language? I don't mind if existing scripting languages would be an objectively better choice, I don't want to build something perfect here, I just wanna have fun with this project again.

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.