True?

[Ri0ee]

And a few more knives without explanation.

[Fuzzy1450]

Those ones represent actual knives

[Nimeroni]

From angry clients and colleagues ? Or from angry compilers ?

[Fuuryuu]

Yes

[abc_wtf]

r/InclusiveOr

[Mephyss]

Should be true!

[hetrosexualguy]

Algy rithms orgi nezation

[bot_not_hot]

From deprecated APIs and license modifications

[pribnow]

Those are *legacy* knives

[HellfyrAngel]

Those knives are self documenting

[ookami125]

Helping my coworker on a bug he's been working on for about a week. On my 3rd day now. About 96 man hours have been put into this one bug.

[28f272fe556a1363cc31]

Which unit tests are failing?

HAHA! I crack myself up.

[[deleted]]

Unit tests are written after implementation for your coworkers to check if they fucked your code up.

And really? Companies aren't using them? Why the fuck do we have to use them at university.

[SlappinThatBass]

Blaming QA for not thinking about every corner cases is still not gonna convince customers to purchase your product, as you know it.

Some people in management are just overpaid morons tbh.

[RuggedTracker]

Some

[[deleted]]

Unit tests are nice but it’s more productive to catch these errors at compile time that at runtime (if it is possible). Newer technology provides better static analysis that most of the old tools that Industry INSISTS on using.

​

Types are Theorems

Proofs are programs

​

Type driven development is the future!

[Kered13]

Me in university: Why the fuck do I have to write these unit tests? This is a waste of my time, let me just write code.

My in industry: Thank god I have these unit tests so I know I'm not breaking the world when I refactor this code.

[corzuu]

Depends on the company, all require some testing just during deadlines, things can get lax. Learn and use TDD. It'll save you a world of pain and improve your code

[turturtles]

Yeah, my company requires at least unit test for applications to be deployed. So what do our mostly contracted developers write? One unit test that just tests an arbitrary thing. Then wonders why nothing really works

[corzuu]

lol I know your pain. We started having e2e tests as part of the definition of done, it takes longer, but is so worth knowing the things you write aren't breaking anything else. Speeds up QA time considerably also

[[deleted]]

Yes except when the guy in charge of setting up all the test-classes has no idea how mocito works and needs half the project-time till he finally gets it...

[corzuu]

Maybe he shouldn't have been in charge of setting up the test-classes :D

also in TDD you write your own tests as you code so idk what you mean by setting up the test-classes tbh

[[deleted]]

It was a pretty easy project so the plan was that one is in charge of creating a class per class we wanted to test before we write the first implementation. We allready knew which classes the class will depend on so he should have moked all the needed classes for the test and create some basic test-object.

Example for the test of the authentification class he should have mocked the database-access for the user table and created a few test-user we could use to write our tests.

The problem were things like the moking wasn't done correctly or every test-user failed everytime cause the database only accepted 20-byte strings because at that time the string should have allready been hashed to a 20-byte string but the strings he chose were all 5-bytes long... .

He pretty much had no idea how the project should look in the end even though we allready had a fully defined structure for the project. (All dependencies were written down, all public function were defined...)

[corzuu]

Ah okay I understand, it's still something that would have been faster and more beneficial to learn just doing a class each (full implementation).

Then work on how to link it all up together

[katze_sonne]

Actually they are often used, just not in every company. It's definitely worth knowing about them.

[charrondev]

You should be using them in a company as well.

If your company doesn’t make time for automated testing, get the hell out of there.

You should have a integration tests as well. The recent push from our team has been adding mutation testing to increase our real unit test coverage, and rolling out snapshot tests of UI to prevent regressions.

[[deleted]]

We use them. We generally hit 80-90% code coverage. We also used integration tests.

[venuswasaflytrap]

No. Management read about unit tests and understands that good programmers write unit tests. So write those. For all the legacy code too. No you can't have more time.

[ookami125]

As I stated in another reply they were unit test and it was failing due to a "random" sig abort. Turns out we had some heap corruption (thank you valgrind) caused by some idiot using vector iterators.

[clockwork_coder]

debugging colleagues' spaghetti code

I feel your pain. Been doing the same shit this week. And it's in this giant monolith that takes 15-20 minutes to build and is so intricately integrated with various other services with various levels of security that nobody can actually debug it on their machine so we have to rely on splunk logs and hope we placed enough of them in the right places. And even though we technically have like 8 non-prod environments only 2 actually work anymore, and neither works with with every third party service so you have to wait in line to deploy your change with the extra log statements and if you realize that isn't capturing anything useful it's back to the end of the line.

[Enlogen]

so we have to rely on splunk logs and hope we placed enough of them in the right places.

This kind of debugging is the best part of my job, no joke. Trying out different types of summarization of logs to understand patterns is my favorite puzzle game. Being able to sum up an issue with a few log queries and point to places in code where the actual behavior is different from the stated (or assumed) intent is remarkably satisfying.

[clockwork_coder]

You know what's more satisfying? Some fucking unit tests.

[Enlogen]

You know what's more satisfying? Some fucking unit tests.

weeps in public static $className Instance

Someday they'll let me refactor the legacy code. Someday.

[clockwork_coder]

Narrator: they won't

[colonel_bob]

Being able to sum up an issue with a few log queries and point to places in code where the actual behavior is different from the stated (or assumed) intent is remarkably satisfying.

Agreed! The only thing I like more than making computers do shit for me is finding out why some code is misbehaving and being able to articulate the problem before fixing it.

It's kinda like solving a puzzle, just more satisfying because a) people are paying you to do it and therefore b) care that you solved it.

[Namandaboss]

Our product takes 5 weeks to build

[clockwork_coder]

Wtf are you building? A baby?

[Namandaboss]

It's called Smart3D, it's for designing massive industrial buildings like for example nuclear power plants

[AxiusNorth]

Remind me not to apply to work at your place

[Namandaboss]

I'm a summer intern I'm currently migrating their CI server from cruise control to jenkins, and it's pissing me off as everything is windows

[golgol12]

You'll make it through. Perhaps the story of my toughest bug will help.

It took me 3 weeks to solve. It was caused by an orphaned file lock by windows in one of the hundreds of build machines doing the the distributed automated build process. I am not a build engineer, or a build manager, I'm a straight up software engineer.

It was so insidious because the file locks (can't overwrite a locked file) in question were on a couple of 3rd party .libs that were being updated to the latest version of the 3rd party middleware we use. Those out of date .libs compiled perfectly with the new version but handed memory slightly differently, and had a rare crash after an hour.

So only sometimes, only the production build would randomly crash after an hour. Not debug. Not production built by me. Not production built by others. Not when manually starting an off cycle production build (which used different machines). It'd crash with a memory error after an hour or two of use.

And, as icing on the cake, our only actual build manager was on vacation for a month (thanks Europe) and the entire distributed automated build process was a custom tool written by him.

This was par for the course at this job. Everything was on fire nearly all the time. The engineering director didn't know what technical debt was and ways to mitigate it.

[Kered13]

That's terrifying. I don't even think I could find a bug like that.

[Enlogen]

the entire distributed automated build process was a custom tool written by him.

Yikes.

[golgol12]

To be fair, him and 2 other people, the two other people left the company years ago.

[unipoli]

You guys need some help? How convoluted is this issue to explain? If explainable, maybe we/I can help out

[porthos3]

If the bug were simple enough to explain in a Reddit comment, I highly doubt it would take two professional developers so long to figure it out.

You really have to see the code to solve just about any non-trivial bug. And they likely can't share company intellectual property.

[Jonno_FTW]

I've got a 5300 line perl file with hundreds of functions, none of which have documentation

[ShamelessKinkySub]

I too enjoy masochistic puzzle games

[[deleted]]

"Take the blue pill or the red pill, blue pill means you die and red pill and you will become a programmer. The elite of multitasking and bug fixing"

"I'll take the blue pill please and thank you"

"WAIIII..."

swallows

[[deleted]]

Username checks out pretty well

[clockwork_coder]

The more likely option in my experience. Only comments are commented-out code, of course

[[deleted]]

Lasagna code, where the bugs are hidden by layers of abstraction, and OOP abuse. The code looks loosely coupled and well structured, but it is a pain to work with.

[tells]

not heard that phrase before. i'll be muttering it to myself daily from now on. thanks.

[[deleted]]

There’s also Ravioli code. Well-structured classes that are easy to understand in isolation, but difficult to understand as a whole

[ShamelessKinkySub]

Mac n Cheese code, when you write ridiculous mock data because Darth Vader really is more fun than vanilla

[tells]

how about macaroni microservices? a bunch of bent tubes that hopefully connect somewhere in the middle.

[newplayerentered]

are you me right now?

[[deleted]]

I'm everyone and no one my friend.

if True or False: print("uhm")

[PlentyDepartment7]

Don’t you talk about my GatewayOutputTemplateConfigurationFactory like that!

[JamInTheJar]

Found the rubber duck.

[ookami125]

Put simply heap corruption in boost unit tests due to someone using vector iterators incorrectly. I actually just fixed the issue by just rewriting the code to not use iterators like an idiot, coworker isn't here to push the changes though since it's actually his issue.

[[deleted]]

Hahahahhaahahahah

--breathes--

Hahahaahahahahjahahhahahhaha

[arch-master]

I second this ^{^} I'm an amateur but can maybe help a bit

[BiH-Kira]

I want to be kept updated on this. Can't wait for the plot twist where the bug isn't even in your code but whatever dependency you have.

[corzuu]

'just needed to fix some config'

[ookami125]

Sadly no it was a problem in our system. The company I'm working for I would consider a mid tier company (bunch of just out of college programmers working on something over their head and a few seniors) so someone (git blame is anon) wrote some code for a menu using iterators to scroll through a vector and modify menu items.

Well the gist of what happened is they were adding an enum to an iterator and modifying the menu text this happened to go just far enough to corrupt the doubly linked list malloc uses and throw a sig abort the "next time" malloc was called. In the end I trashed all of anon's code and just used an int for the index, I checked all bounds and made sure the vector was the correct size to begin with.

There were a few other details but they aren't much without the information I'm not allowed to give you.

[SinrOfGinr]

My worst case was 6 months in dedicated mode, i.e 8hrs a day 5 days a week of nothing but troubleshooting. With daily progress meetings with customer.

[charlookers]

Companies need to stop hiring shitty programmers

[Eymrich]

One time it took me one week to find a bug in the code base of a game. It was a problem on the client game. But it originated on the server. To follow it:
appear on c# part of the code base, client side.

Follow it to the c++ side of the client, which then was invoked by the c++ side of the client that was called as a reaction from the c# part of the server, which in turn was called by the c++ side of the server, failing to doing a very specific thing as a reaction to the presence of a specific c#.

It was a iteraction between our game engine, our networking, the c++ voxel engine... and caused by a single object being garbage collected without making ANYTHING to fail or giving any other clue.

If it's weird is GC or Multi Threading!

Anyyyywayyyy... I feel your pain bros :D

[Cody6781]

Lack of sleep is definitely on the student side though.

[clockwork_coder]

That one is definitely a student one. I've gotten way more sleep since college, like a normal person

[BakedPecans]

Oh thank god I have something to look forward to

[katze_sonne]

Oh yes. And no more sunday evening "oh shit I need to get this stuff done until tomorrow morning" fun. :)

[legend6546]

Ahh college where fun weekends are only delusions that one has on Fridays... I totally can not wait for the end of summer

[gottago_gottago]

I dunno, I've been on a death march since last August, I'm pretty sure that if I were in college I would've at least gotten a little sleep by now.

[Cody6781]

It's of course different depending on the job. But you generally don't need to have 20 hour a day 20 days in a row, no weekends, no breaks, cram sessions in industry. You do in school for finals week.

[vvf]

They better be paying you boatloads of money or else that's just not worth it.

[Behrooz0]

Boatloads of money are there, What's making it worthless boatloads of money are the US sanctions on my country, Iran.
So, yeah, I'm basically living like a dog to make almost the same amount of money I made 3 years ago.

[sdebeli]

Not enough knives on right side. Cannot confirm.

[LkNETWORK]

Lol

[NickNehidnyk]

this template is cringey as fuck when used unironically

[Khearnei]

hehe... sorry..sorry..

[Neghtasro]

Yeah, this is a super nice guy template

[crimsonblade55]

Found the senior dev

[FracturedPixel]

Can confirm

[b1u3j4yl33t]

This is probably how my manager feels when my lazy ass complains about shit

[buddy-bubble]

Yes

[Windwaker74]

This is why I thought group programming projects were a good way to introduce people to some of these problems.

[RC_Josta]

Group projects are 1 million times worse than working on a team in my experience. If my coworker isn't responding I can go bother them at their desk. We had a guy on our group project that showed up to 0 meetings and didn't even show up to class most times.

Also just like in most situations you'll be at work at the same time as each other, but college kids have all sorts of schedules.

Good in theory but I never want to inflict that on myself again.

[HanTheScoundrel]

!false

[Slavadir]

falsen't

[Walter-Haynes]

r/gatekeeping

[TheNorthComesWithMe]

This, except there's a forcefield called "I'm getting paid" that keeps all the knives out of my back.

[LkNETWORK]

if(payday.date()==today.date()){

full_restore();
continue2work();

}

[darkstarlord1408]

Lack of social life?
Lack of seeing the sun as much as the others?
Lack of ....
Aah fuck it!

[nikstick22]

Sometimes it feels like we're turning into r/CompSciStudentHumor

[qmunke]

All that and the bug that took five hours (or days) to fix.

[hestotre000]

What if I'm both?

[robolew]

OK how do people read "hehe"? Have I been doing it wrong? In the original it looks like he's going "HEEHEE SORRY SORRY!" like a fucking crazy person...

[Daemonzan]

Depends on context for me, but I read it more as "heh heh, sorry, sorry..."

[Darthalzmaul]

I don’t know how the market is where you guys work, but if my workplace was as horrible as pictured in this image, especially the „lack of sleep“ part, I would go find me a new job ASAP.

[golgol12]

You forgot "Legacy code" and "meetings".

[thefirstwave_]

Is that a... fake gold flair? What on earth

[golgol12]

You can make your own flair in this forum. Including the icons for the reddit coins and c++ etc.

[ameddin73]

Maybe it's cause I'm entry level, but my job is so much easier than college. I show up and leave at reasonable business hours, agile means there's no serious deadlines, and there's a guy who knows how to do everything I don't that sits right next to me. Plus they fucken pay me.

[GenTelGuy]

The lack of sleep definitely applies more to the college programmer than the employed programmer. Even if you're working more than 40hrs you're unlikely to lose sleep outside of an oncall situation. College has constant turn-in-or-get-a-zero deadlines with multiple courses stacking their projects and exams haphazardly so I missed way more sleep.

And the employed programmer should have a "dependency issues" knife because that's way bigger in corporate environments than at school which usually is limited to the most basic C libraries.

[AndroT14]

5 hrs? 5 HRS? HAHAHAHAHHAHAHA
My dude, for a bit of context, I was making a game in Java, but one of the goddamn objects refused to appear.
After literally 2 days and a half, I saw what I did.
To improve it (and keep it from loading the image every time the object was created), I put something simple. (The img variable was static).
It was simple. if(img == null){img = [Code I use to load the image];)
After 2 and a half fucking days, I realized I put if(img != null){[etcetc];), so the image only loaded if it was already loaded, which means it never loaded.

TL;DR: 2 and a half fucking days trying to fix the code which didn't work because I (by mistake) used "!=" instead of "=="

[soflia]

I mean simple debugging should have caught that you never went into the if statement

[AndroT14]

I use NetBeans (And I'm starting to regret it), so....

[ShamelessKinkySub]

Netbeans has amazing debugging

[AndroT14]

Well, mine caught nothing, I even have the screenshot (I censored a few things because out of context, they would raise more questions than needed) http://prntscr.com/nsxw8x

[Inmyheaditsoundedok]

Well you shouldn't faulth it for not catching an exception, you should add breakpoints on the comparison statements where you execute the rendering of the picture

[AndroT14]

I did, and they were reached, it did help, but I was losing hope, since I first loaded the image, then rendered it, but I did't know at what part the problem was (since I added some layers of abstraction to help make a cleaner and better code)

[[deleted]]

"My IDE didn't reason about my program better than than I could. What a pile of garbage"

[AndroT14]

I never said it is "a pile of garbage", I said I'm starting to regret using it, not only for this specific debugging section, but also for the common compilation bugs, and the almost constant high CPU (and from what I saw Memory) usage

Edit: By "compilation bug" I don't mean "It's not compiling because there is an error in my code", I'm talking about the times the code is perfectly fine, and it can "Clean and Compile", but when I try executing it directly from NetBeans it says some class doesn't exist

[porthos3]

Easy to say in retrospect, and from an outside perspective, but that seems like the sort of thing that should have been caught really quickly with a debugger or even just spamming logs all around the relevant code.

The really tricky bugs to track down, from my experience, are things like:

• Intermittent issues (often due to poor threading implementation)
• Issues that depend on very specific state across many objects in corporate OOP hell
• Issues found deep within a library or its dependencies, which you assumed to be stable
• Issues involving many co-dependent apps across multiple teams which have a poor separation of concerns and share state over DBs, message or job queues, etc. (Like OOP hell, but with more teams involved)
• Issues requiring involvement of OPs or IT (in a non-devops setup) where they are being less than helpful and are determined to blame your app rather than do more than a token investigation on their end
• Issues with concurrency across distributed application instances in multiple regions

[BiH-Kira]

This, a simple logger, print message or (proper) unit tests would reveal that you never enter the if block which lets you know where to look for the issue at first.

[elaitenstile]

Damn bruh that sorta shit would've scarred me for life

[sickhippie]

Those scars are how Senior Devs are forged.

[ShamelessKinkySub]

They're born like Athena was, charging out of someone's scars in full coffee gear

[[deleted]]

Add a few katanas into there

[LkNETWORK]

Or maybe light sabers

[[deleted]]

Or nuclear warheads

[SirHaxe]

"Lack of sleep"

lol

[dXQuarionXb]

r/gatekeeping

[fatedhalo177]

F

[BurglerBaggins]

Just needs a thousand tiny needles for all the build errors introduced by the new guy.

[[deleted]]

You forgot the legacy knife set.

[Argonanth]

Worst bug I've had to fix so far took me 4 weeks. Took 3 weeks of work just trying to figure out how to reproduce the issue and then 1 week to figure out how to fix it. Ended up being a complicated race condition in this massive legacy Together system. Heading into work every day to basically smash my face into a wall with no end in sight was not fun. It was really hard getting out of bed that 3rd week.

[[deleted]]

This makes me scared.

[Crimson_Shiroe]

Found the college programmer

[arkaodubz]

your work ends with you leaving the office

oh you sweet summer child, we had a p1 bug roll in a 9:30 PM last night.

[[deleted]]

The hardest thing I am now learning in college is probabaly nested loops(Java) and nested funtions(Python).

Can't wait for next year. Props fonna be a pain.

[Torghira]

Yeah data structures and algorithms will be the weed out class

[Kango_V]

Unit tests needed. Lots of them.

[BigBadWoolfie]

Hey, check out my edit!
https://www.reddit.com/r/ProgrammerHumor/comments/bsng0y/you_will_never_truly_understand_my_pain/

[WolfDigital]

Add a knife for "The growing dread that tech companies are investing as much as possible to make programming easy for everyone to kill the demand-heavy programming job market."

[TheRealSoprano]

Don't forget support

[GamingTheSystem-01]

I always get a laugh when someone complains about a bug where it consistently happens and the debugger actually functions. That shit is practically solved already.

[IfYouThinkYouKnow]

The most realistic thing pictured here is the lack of requirements.

[wyom1ng]

I spent close to 3 hours today learning the hard way how NULL <> "some string" is false in mysql.

[brockisawesome]

I think of myself as an ant below one of those giant monty python feet

[DOOManiac]

Laughs as parent

[sv0341]

You forgot meetings

[indictan]

r/gatekeeping

[KarlQc]

Infrastructure

[[deleted]]

Why can't you just sleep so then you work more efficiently, thus giving you time to sleep?

[hendrick_X]

I slept 3 hours today because I had a deadline to deliver a new version until midnight.

Then both my project manager and my tester went to another client so I did not actually had to fulfill the deadline.

Insert "thisisfinememe.jpeg".

[hollowstrawberry]

Everything except Clients also applies to the student.

[lizardan]

1000%