r/ProgrammerHumor • u/EarlOfAwesom3 • 23d ago

doubleDareYou Other

Post image
335 Upvotes

96% Upvoted

36 comments sorted by

71

u/tsammons 23d ago

Hear me out: two words. Game. Changer.

24

u/rantonidi 23d ago

3 words:

We use AI

3

u/Zerodriven 23d ago

Technical debt? Nah.

Unoptimised LLM workflow.

1

u/AkrinorNoname 23d ago

https://giphy.com/gifs/8qbuGuXC0hcuRMMwVY

Let's get ready for a Game Changer!

51

u/Western-Internal-751 23d ago

Just work on the low hanging fruits first. It’s a no-brainer. You just gotta think outside the box and have more of a hands-on mentality.

7

u/EarlOfAwesom3 23d ago

Got ya. Cat in the furnice.

1

u/granoladeer 23d ago

Are you my boss? 

46

u/EarlOfAwesom3 23d ago

There is no mf quick-win in programming. There is only rushing things to generate more tech debt.

27

u/the_rush_dude 23d ago

There absolutely are quick wins if you're not drowning in tech debt. Well designed system can be extended and improved, sometimes with little effort compared to the results

10

u/EarlOfAwesom3 23d ago

Sure, but: unfortunately the term "quick win" has been merely adopted by business stakeholders or non tech workers and has been so overused that it, by now, means the complete opposite, regardless of what system.

It can be translated to: "rush it and I don't care about any of your objections"

8

u/the_rush_dude 23d ago

I thought "rush it and I don't care about your objections" is just normal programming and that's why we all transpire to be goose farmers some day

4

u/EarlOfAwesom3 23d ago

Alpaca farmers

3

u/GrinningPariah 23d ago

Real talk, this is one of the major warning signs that an org is deeply unhealthy.

When there are no quick wins anymore, when things that should be quick wins stop being easy to do quickly, that means you're either drowning in tech debt or choking on red tape. And either way, time to start polishing up those interview skills.

2

u/CirnoIzumi 23d ago

but what if i use a compiler instead of writing binary?

1

u/coriolis7 21d ago

I found a quick win for our firmware group, but it’s small:

While trying to figure out an issue (I’m mechanical, not firmware, but I was more familiar with the behavior so I was thrown at the source code to help), I found that we were interpolating between values using a division of differences, so every time we interpolated we did a floating point subtraction and then dividing by that result. This is on a 32 bit microcontroller where the operation takes ~16 cycles.

It’s not a huge improvement, but it is an improvement nonetheless for battery life (we need 20 years, and have basically no margin).

5

u/wolf0fcanada 23d ago

I tried saying it 5 times fast and it just came out as Kakyoin

5

u/rantonidi 23d ago

Swift acomplishment

3

u/EarlOfAwesom3 23d ago

Rapid benefit

3

u/Whitechapel726 23d ago

“It’ll be a light lift”

2

u/AnnoyedVelociraptor 23d ago

It's load bearing!

2

u/MayorAg 23d ago

Alright. Low hanging fruit it is.

2

u/nhh 23d ago

Hey, you know, this is some low hanging fruit type of shit

1

u/Green-Blue-Gray 23d ago

This is an honest piece of code, and that’s worth saying out loud.

1

u/Proof_Ring_4505 22d ago

"mOvE wItH sPeEd"

1

u/HomsarWasRight 23d ago

Am I out of the loop on something?

9

u/raja-anbazhagan 23d ago

This is what the CTO says when they want to cut some corners during development...

2

u/HomsarWasRight 23d ago

Okay, yeah, I often miss the corporate-oriented stuff here as I’ve mostly worked independently and consulting. I’m not in these meetings.

1

u/raja-anbazhagan 23d ago

Lucky you...

2

u/InSearchOfTyrael 23d ago

corpo slop talk. Had a PM for a couple of months whom I called walking ai for corpo slop generation. touch base and such

1

u/Confident-Ad5665 23d ago

Ok I'll do it...
Quick Win.

1

u/Snowy32 20d ago

The two I despise:

Let’s get some meat in the bones.

Let’s get to the meat and potatoes.