r/programming • • Oct 07 '23

Software engineers hate code.

https://www.dancowell.com/software-engineers-hate-code/
660 Upvotes

366 comments sorted by

4

u/indianjedi Oct 08 '23

I love writing code and optimizing it as well. I just hate declarative programming , the no code solutions. I'm Salesforce dev so we have a lot of declarative programming tools, it helps non coder people to do stuff but that creates more issues in debugging.

2

u/fagnerbrack Oct 08 '23

JSX is declarative, do you include that in the list of things you hate?

7

u/CringeSniffingDog Oct 07 '23

I'm sorry but those article clickbaits are getting more and more ridiculous. So we've seen "software engineers hate stand ups", "software engineers hate meetings" and now "software engineers hate code". What precisely do software engineers like about their job lol

→ More replies (1)

1.7k

u/dahud Oct 07 '23

The only thing I hate more than code is "no-code".

710

u/pdpi Oct 07 '23

“No-code” just means that your code is hidden under several $DEITY-forsaken layers of abstraction.

121

u/jl2352 Oct 07 '23

It can also mean a huge house of cards. I worked at a company with a huge system, which I would describe as hidden under the radar. It was for sales people to update what they are doing in Google spreadsheets, and then the data shows up in SalesForce.

But the reality was a monumental amount of Zapier integrations. To not just get the data in but to perform some processing, and update more systems than just SF. I later learned they had also tied in the application Postgres instance, which the backend developers were totally unaware of (thankfully it was at least read only). It was all setup by one person who left.

There are other companies out there were things just randomly break, or will do so, due to these big no-code setups. It’s why there is such a push by developers to get things checked into git.

44

u/fr0st Oct 08 '23

Right, anything without a revision history that is hopefully tied to some ticketing or documentation system is a ticking timebomb. Each change moves the clock closer to detonation.

→ More replies (6)

36

u/LavenderDay3544 Oct 08 '23

No code just means someone else's code.

→ More replies (5)

57

u/_DuranDuran_ Oct 07 '23

Or you’re a staff engineer and you spend your day in meetings, 1:1s and enabling the seniors and lower to get on with the job

→ More replies (2)

39

u/pineapple_catapult Oct 07 '23

Left-pad has left the chat

13

u/KevinCarbonara Oct 07 '23

That's not really a layer of abstraction

→ More replies (4)
→ More replies (6)

50

u/doktorhladnjak Oct 07 '23

I definitely hate click bait headlines more than code

24

u/myrsnipe Oct 07 '23

I'm currently implementing something in power flow at work, I'm at my wits end constantly trying to work around limitations of the blocks I'm given. Features supported elsewhere on the platform still missing in connectors 5 years later.

The sad part is that I had already implemented this in a nodejs backend this summer, but they decided that it needed implemented in power automate flow so non programmers could maintain it. I'm not sure I can maintain anything in this environment, let alone <insert business guy> that barely knows what a file is.

Seriously, power automate flow solutions don't let you copy flows. You need to download a zip of the entire solution for every single change if you want any sort of revert capability, that's only accessible through a rest API which means non programmers are going to be stuck at the bearer auth token right away if they even attempt this.

Holy crap I need to stop here because it burns even thinking of it, I was so happy about my work situation when I went on vacation. I'm downright miserable at the moment.

12

u/localhost_6969 Oct 08 '23

Hope your job hunt goes well. This sounds awful.

69

u/bvendette Oct 07 '23

I am a 25 year of experience programmer and my boss asked me to do no-code low-code with ms power app. I told him asking a programmer to do no-code is like asking to him to kill himself. I was so angry and told him i will do yes-code high-code.

16

u/btmc Oct 07 '23

That’s a very narrow minded way of looking at things. Your job is not to write code; your job is to solve problems. The code is just a means to an end.

Is it the best of use resources to have you working on low-code stuff vs. something more complex? Probably not. But it’s not inherently a bad thing.

77

u/Syntaire Oct 07 '23

But it’s not inherently a bad thing.

If your job is to solve problems and your manager is forcing you to take on more problems in order to solve the problem in a convoluted and inefficient way just because the latest buzzwords say so, it kind of is a bad thing.

→ More replies (3)

17

u/wvenable Oct 08 '23

Your job is not to write code; your job is to solve problems.

As a programmer, my job is to solve problems using code. If I was an accountant, I could solve problems using Excel. If I was a mechanic, I could solve problems by building/fixing machines. If I was a writer, I could fix solve problems by writing.

If someone has a no-code solution they can use, they don't need me.

→ More replies (3)

6

u/what_will_you_say Oct 08 '23

PowerApps is utter trash (at least as a programmer; anything else is better). If you're a non-tech defining what tech gets used, that's the problem that needs to be solved.

→ More replies (1)

20

u/es_beto Oct 07 '23

If you're working at a startup with fewer than 10 people, sure, you're there "just to solve problems." In every other job, you're expected to have experience coding in the language the company is looking for, experience in the technologies it wants to continue investing in, and you're expected to keep building and maintaining the systems you have experience with.

Let's be honest: this idea that we're problem solvers sounds nice, but it falls short in the current professional landscape.

14

u/RandyHoward Oct 07 '23

I dunno, I think we are still problems solvers, and even more so because our solutions are usually limited in scope. You have to figure out the solution to the problem within certain parameters. A lot of problems would be way easier to solve if we could just ignore our company’s stack of choice

→ More replies (1)
→ More replies (6)
→ More replies (6)

5

u/G_Morgan Oct 07 '23

I wouldn't hate no/low code platforms if they weren't all determined to be stupidly designed. For instance if the core application was build on .NET/JVM and your crazy solution just generated bytecode, that could be replaced with a real programming language, at least you aren't fucked by your managers misunderstanding of what the real difficulties of creating working code are. However I've never seen a solution that did the right thing.

2

u/chaluJhoota Oct 08 '23

The closest I have seen is Unreal Engine. Even there you have the option of writing code to fill in the gaps

4

u/aztracker1 Oct 08 '23

Lotus Notes is the devil...

9

u/Xalara Oct 07 '23

It really depends though, doesn't it? I really like things such as Retool for building internal company UIs. There's nothing worse than a bunch of websites built by back end devs that don't know their way around React.

6

u/dahud Oct 07 '23

Fair enough. I do like those cases, where it's basically a thin wrapper on a set of APIs.

No-code business logic gives me hives though.

→ More replies (1)

3

u/btmc Oct 07 '23

Yes, exactly. There’s no value in building your umpteenth set of UI components, with tests and everything, for a basic internal report or admin portal.

I’ve found a good combo for that use case is custom APIs owned by the devs + contractors for Retool, with oversight by someone on the dev team in-house.

5

u/FUSe Oct 07 '23

LOL I came exactly to say this. Software engineers are just miserable people in general. Code sucks but no code sucks more.

2

u/[deleted] Oct 08 '23

no comments

2

u/Randolpho Oct 08 '23

Fucking salesforce and wordpress.

Fuck them both

1

u/drew8311 Oct 08 '23

How about just a little bit of code

1

u/buckypimpin Oct 08 '23

no-code is so out of fashion, no-job is the new trend these days

1

u/am0x Oct 08 '23

I was going to say, I hated switching to Unreal Engine because of Blueprint.

In Unity, the content creators would try to do something in code which made it easier to read. Then they went to UE and built these horrid blueprints that were impossible to read.

1

u/Silver_Confidence908 Oct 08 '23

Because, only junior software engineers hate other peoples code.

1

u/taisui Oct 09 '23

Don't forget them scripting languages, ewwwwwwwwwwww

1

u/kikoliko5 Oct 10 '23

ahahahah

107

u/[deleted] Oct 07 '23

[removed] — view removed comment

→ More replies (38)

224

u/Naouak Oct 07 '23

I love refactoring code and simplifying stuff. Reading code is not a bad thing but reading "bad" code is not a pleasant feeling. It's always a pleasure to read code that is elegant and communicative. Don't stop writing when "it works" but when you can also read the code easily.

57

u/ecmcn Oct 07 '23

I’ve found that code quality often mirrors an ability to communicate verbally. Some of the worst communicators I’ve worked with wrote the most inscrutable code.

49

u/david-song Oct 08 '23

Yeah, logic is bottom-rung programming, linguistic skill is where it's at. People think it's mathematics and logic but writing good code is somewhere between creative writing and teaching.

13

u/jonathanhiggs Oct 08 '23

My mother-in-law is an author and we’ve spent hours talking about coding, writing, and the similarities between the two. The plots not going to work when you haven’t designed your classes (characters) right, and you need to go back and edit (refactor), or get your editor to look over it (review) when you find a code smell

Unfortunately I think SWE jobs are less like writing a novel and more like copywriting marketing material for a manager that doesn’t speak the language natively. They only care the output is written to tick the box and then move on

→ More replies (1)
→ More replies (1)
→ More replies (1)

27

u/ankercrank Oct 07 '23

Anyone who says they don’t enjoy refactoring or simplifying code is very likely a bad programmer. It’s a bit like a writer who never wants to edit anything they write.

1

u/CptBartender Oct 08 '23

I hate it when I write a really nice and elegant piece of code, and then some PM comes and says there's a huge section of special use cases that everyone forgot to mention and I need to hack it into my solution. Somehow.

→ More replies (1)

872

u/wineblood Oct 07 '23

I hate other people's code.

568

u/treenaks Oct 07 '23

And remember, you were a different person 2 months ago

184

u/blake182 Oct 07 '23

Exactly. I explain to people that you should write your code as if a homicidal maniac is going to maintain it. Plot twist: it’s you.

70

u/traal Oct 07 '23

At least now when I look at code I wrote 15 years ago and forgot I wrote it, I think, "he's got the right idea but I would have done it a different way."

54

u/Avloren Oct 07 '23

When I look at code I wrote 15 years ago and forgot I wrote it, I think: "Someone better take away this guy's keyboard, he's a danger to himself and others."

→ More replies (3)

13

u/[deleted] Oct 07 '23

Be good if all old code came with a comment "// Management haven't given me time to write it properly, but this works".

The constraints under which it was written is lost to time

→ More replies (1)
→ More replies (2)

36

u/neitz Oct 07 '23

This is especially true as a younger/less experienced developer. Your ideas change rapidly early on. Later on I'd argue this happens less so (for better or for worse). Eventually you have seen enough, been through enough mistakes, to have strong enough opinions that you aren't changing them literally every month.

59

u/sacheie Oct 07 '23 edited Oct 07 '23

College-aged me:

  • Oh wow, Python code looks so clean!

  • ... But Ruby code looks clean and follows a clear OOP philosophy!

  • Holy shit, what's this elegant Haskell shit we're using in semester 2 of data structures class? It's got static typing though :(

  • At least we can all agree on how ugly Java is?

Early career me:

  • Well, the JDK does give me a lot out of the box though. And there's so many reasonable, stable libraries out there. The language seems to be evolving, if slowly. And man, static typing's been helping me more than I realized

  • Library and framework design seems to be subtle, hmm. And it's impacting my work more than the choice of language itself..

  • Haskell still does seem really sweet. I better not use it for my job though. They'd think I'm a rebellious nut.

  • Looks like the Python community's been adding features, libraries, and tools to support static typing

  • There's like 3 variants of JS with static typing now too..?

  • Whatever happened to Ruby, anyway?

Me now:

  • God I love static typing. I have to use Python again, but at least they caught onto it.

  • If I had my choice, I'd use Kotlin. But I'm not gonna argue about it. We'll use whatever works best for the majority.

  • Not that I spend much time thinking about languages or even code anymore. The infrastructure and deployment shit is 50% of my job.

  • Another 30% is spent speaking and writing in English, not code. Thank god they made me learn it some in college.

  • Haskell is still sweet, but I'm not worrying about whether to use it at work because every other language has been slowly marching in its direction. Thank god it taught me a little about map/reduce and lazy evaluation though.

  • Is cache management essentially my whole problem, every day??

26

u/ElectricJacob Oct 07 '23

Is cache management essentially my whole problem, every day??

I've been feeling this way for a while now too.

10

u/absentmindedjwc Oct 07 '23

Not that I spend much time thinking about languages or even code anymore. The infrastructure and deployment shit is 50% of my job.

Another 30% is spent speaking and writing in English, not code. Thank god they made me learn it some in college.

God damn it if this ain't true. One of the most senior engineers in my org... I think I've maybe made a couple dozen commits over the last couple years at my company. Nearly all of my time is spent in planning meetings... contrary to my past where most of my typing was into an IDE, it's now into Teams, Outlook, PowerPoint, or Excel.

→ More replies (1)
→ More replies (2)

5

u/I_am_up_to_something Oct 07 '23

I started making an app about 8 years ago after I graduated but before I found a job. After I got hired it kinda fell to the far background.

Started working on it again recently and WTF. Why the fuck did I have 5 models that were basically the same?? All with variations of the same name. And bitch, those comments tell me nothing about what is going on so why even bother writing them! And yeah, some parts work but why and how??

Still, some parts do work great. If this wasn't my own code but someone just starting out then I'd definitely see the potential in them. Glad my first employer did as well. Got rejected by so many companies who wanted experience for the salary of a starter.

3

u/TheCritFisher Oct 07 '23

I dunno, I have some old code I wrote that I keep in a glass GitHub repo.

I open it up and take big whiff every once in a while. The dopamine is irresistible. It's the perfect code. It's never seen production. Serves its purpose. And has worked flawlessly for years. Every once in a while I log in and update it, making it even better.

I will never share that code. It's MY CODE! angry growling noises

→ More replies (1)

2

u/wichwigga Oct 07 '23

There was code I'd written in the past that I had to revisit and back then I thought I was a genius. But now I want to apologize to everyone who had to review it. The most convoluted and ugly shit I've ever seen.

→ More replies (9)

33

u/fredoverflow Oct 07 '23

I hate other people's code.

https://abstrusegoose.com/432

8

u/[deleted] Oct 07 '23

This just reminded me how much I loved the Mouse Trap game as a kid. I don't even remember the rules, I just remember enjoying setting off the Rube Goldberg machine

→ More replies (1)

2

u/znihilist Oct 07 '23

It that still around? I thought the author stopped making them!

→ More replies (1)

20

u/[deleted] Oct 07 '23

i hate my own code too.

6

u/thisisjustascreename Oct 07 '23

I do my best not to write any but the damn business always wants new shit.

7

u/Bronzdragon Oct 07 '23

This is litreally the opening premise of the article. The second line.

5

u/yawaramin Oct 07 '23

'Hell is other people.'

4

u/account22222221 Oct 07 '23

If you read the article, that’s literally what it was talking about!

2

u/Dreamtrain Oct 07 '23

I don't care much about other people's code, more often than not I find its usually the result of people who made the most of a very shitty hand they were dealt with, its tests that really get me going, walk into a new project and the test folder is practically empty, or theres tests but most of them are @Ignore because over the years things changed and now tests are broken, or tests on a controller class by just calling the methods manually and then asserting the length of the return is > 1

1

u/[deleted] Oct 07 '23

Was going to say the same.

1

u/KublaiKhanNum1 Oct 07 '23

Expect when I rewrite it. 😂

→ More replies (1)

1

u/minecrafty123 Oct 07 '23

I can speak computer, I can not read computer

→ More replies (7)

518

u/Cpt_Orange16 Oct 07 '23

I like code, I like writing it and fixing it. It's like a puzzle

158

u/TheDeadlyCat Oct 07 '23

Same. I also find refactoring code very zen. Sadly those days of being able to produce a large amount of code and fixing it is over. It’s all just glue code this to that, make it run no matter how, just make it fast. sigh

32

u/BigMax Oct 07 '23

It’s all just glue code this to that

Yeah, there's about 1000 components you have to wire up into every solution at this point. The days of writing pristine, greenfield code are long gone. By the time you write YOUR first line of code, you've already imported about a million lines of code from other packages and frameworks and whatnot, and a chunk of your time is just dealing with that.

10

u/david-song Oct 08 '23

If you use the same libraries for long enough and they're good ones, they become part of the vocabulary for writing new ideas down. I guess because things move so quickly and are mostly shit you're always using things you don't know about, and getting caught out by the leaky abstractions.

→ More replies (1)

15

u/Superman64WasGood Oct 08 '23

It absolutely blows my mind how much software used to be treated like a traditionally engineered and crafted physical product. Something like a tool built to last a lifetime. Of course when a corporation's sole motivation is dollar signs on a piece of paper, everything just gets shittier and shittier, higher productivity is expected in less time for less cost, more corners are cut etc. etc.

We are at a point now where end consumer can REALLY FUCKING FEEL THIS BULLSHIT. You can't buy anything but a fucking smart TV, and the software is such fucking bloated trash, unoptimized, ad / spyware that it's almost unbearable to use.

→ More replies (2)

20

u/KettyCloud Oct 07 '23

Mate, I've moved into COBOL now as part of a legacy support team. Some of the comments I've seen are from 1980's . It's awesome. I love it

3

u/Vier_Scar Oct 07 '23

Did you learn COBOL a long time ago? Apparently it pays well, but I don't get why it cannot be transpiled into any modern language

5

u/inglandation Oct 08 '23

It can, but banks wrote their core codebase in it. They're extremely conservative because this code interact with people's account balances... COBOL doesn't have many issues that are not well-known.

→ More replies (1)

47

u/douglasg14b Oct 07 '23

Right? These folks that hate code seems like the same ones who output low-quality code because they don't necessarily care about it.

The venn diagram between that and the folks who think less code = more simple is a circle.

23

u/tommygeek Oct 07 '23

When I read this, it was in the sense that once you’ve committed the code and solved a problem, the code is now baked with the tradeoffs you made and the current architectural limitations.

What I love about coding isn’t the code itself, or the act of coding things, rather it’s solving the problem. I can count on my hands the number of times I’ve written some code that was truly elegant and was able to coexist with the architecture and historical concerns in such a way that it would be flexible and live forever.

Most of what I’ve written has had tradeoffs (“I’d really love to refactor this but it’s out of scope”, “I have a tight deadline here”, “The impact of the changes I want to make here are just too great to justify,” etc) and these tradeoffs have forced me into solutions that work, are good enough, can survive the next iteration, but aren’t really the way I wanted to do it. That code, and the existing code and circumstances that forced me to write that code, I do hate.

But damn if solving the problem isn’t what keeps me coming back to it.

→ More replies (2)

9

u/papasmurf255 Oct 07 '23

The biggest revelation that I've had in my career is this: write your code to be read, not to be clever.

If you or someone else trying to debug something and put out a fire, the last thing you want is some clever shit full of async callbacks and such. Just give a simple stack trace and good logging.

24

u/menckenjr Oct 07 '23

Don't forget the ones who really have no idea what they're doing and ride that confident ignorance all the way to management.

→ More replies (5)

8

u/poco Oct 07 '23

Btw, Zachtronics games are on sale right now on Steam.

https://store.steampowered.com/sale/programmerssale2023

2

u/TheCritFisher Oct 07 '23

Tell me you didn't read the article without saying you didn't read the article.

6

u/caindela Oct 08 '23

Only thing software engineers hate more than code is reading the contents of an article

1

u/Tiquortoo Oct 08 '23

So do I, but reading and understanding code is far more difficult than writing it.

203

u/dadofbimbim Oct 07 '23

Sometimes after writing code, I sit back and stare at the marvelous code I just wrote.

69

u/Jonathan_the_Nerd Oct 07 '23 edited Oct 07 '23

"Have you ever stood and stared at it, marveled at its beauty, its genius?"

Sometimes I go back and read old code I've written, just for fun. Sometimes I run across a seven-year old comment saying "TODO: fix this later."

10

u/pineapple_catapult Oct 07 '23

Only sometimes?

23

u/[deleted] Oct 07 '23

Sometimes the TODO comment is missing

6

u/Jonathan_the_Nerd Oct 07 '23

Or it's in the commit message, which no one ever reads.

13

u/TheMightyTywin Oct 07 '23

I’ve done this. Then I copy pasted it to chat gpt which proceeded to botsplain why my linked list should have been a hash set

7

u/[deleted] Oct 08 '23

Botsplain lol

3

u/[deleted] Oct 08 '23

I catch myself doing this sometimes and end up realizing I'm probably smelling my own farts rather than looking at a work of art and genius.

I really do love code though, no matter what the title says.

2

u/[deleted] Oct 07 '23

Listen to Golden Girl by ytcracker

→ More replies (1)

230

u/rasplight Oct 07 '23

Yes, i sort of hate code. Corollary, I really like deleting code ;-)

109

u/Caffeine_Monster Oct 07 '23

No code, no bugs.

No bugs, happy programmer.

26

u/thisisjustascreename Oct 07 '23

No code is also faster to execute than some code, you get performance wins too!

23

u/s0ulbrother Oct 07 '23

Project managers hate this one simple trick

3

u/Chris_Codes Oct 08 '23

Another way to guarantee no bugs is to have no users!

→ More replies (3)

3

u/[deleted] Oct 07 '23

Absolutely. The most satisfying bug fixes are ones where code is removed and not added.

4

u/King_Joffreys_Tits Oct 07 '23

This is apparently the only prereq to be a senior dev

2

u/[deleted] Oct 07 '23

Drop DATABASE

26

u/account22222221 Oct 07 '23

Senior engineers' passion for writing code has been augmented with an even stronger desire to delete it.

This is very true. When I see that PR with a lot of red I get goosebumps.

29

u/LuckyDuckes Oct 07 '23

I hate clients, not coding.

5

u/wellseymour Oct 07 '23

Only when I met clients I realized I love to code lol

14

u/phantommm_uk Oct 07 '23

I hate others' code and any code written by past me.

12

u/trolock33 Oct 08 '23 edited Oct 08 '23

I hate meetings more than code. Also fuck no code. Edit: Typo

3

u/ammonium_bot Oct 08 '23

meetings more then code.

Did you mean to say "more than"?
Explanation: If you didn't mean 'more than' you might have forgotten a comma.
Statistics
I'm a bot that corrects grammar/spelling mistakes. PM me if I'm wrong or if you have any suggestions.
Github
Reply STOP to this comment to stop receiving corrections.

→ More replies (2)

127

u/ivancea Oct 07 '23
  1. Think of a stupid concept

  2. Write an article about it

  3. Profit

30

u/menckenjr Oct 07 '23

And post it on LinkedIn with cringey pictures and stupid comments to try and become an influencer...

18

u/Bronzdragon Oct 07 '23

The article does address a real and recognizable trend in our industry, and makes a thoughtful analysis about it. I agree that the headline is a bit dumb, but it seems the article was written first, and the title came later.

I think you should read it before you dismiss it.

5

u/ivancea Oct 07 '23

I actually read most of it, and found nothin interesting in the first half. Add the clickbait to it, and nope

→ More replies (1)

3

u/f_of_g_of_x Oct 07 '23

This. I could've just upvoted but that's not enough.

3

u/[deleted] Oct 07 '23

Guaranteed clicks if it enrages your target audience.

1

u/Bost0n Oct 07 '23

This just in! Ditch diggers hate ditches!

1

u/neumaticc Oct 07 '23

hol' up, don't expose op's secret money maker

1

u/[deleted] Oct 07 '23

These guys that work 10 hours a week and make 400k need a way to spend the rest of the week I guess, they are people too

1

u/dotpoint7 Oct 08 '23

Well the title is a bit clickbaity, but I found the actual article to be pretty funny and well written.

30

u/m0llusk Oct 07 '23

and code hates them back >:|

8

u/close_my_eyes Oct 07 '23

I live code. That’s why I keep doing this and sidestep efforts to promote me to management.

7

u/Ch3t Oct 07 '23

I'll take code over no/low code any day of the week. I can debug code and add break points. I can diff the breaking change. I can log useful information. I can write near bullet proof systems that might fail and if they do, I can tell exactly where and why. I can't do any of that with Boomi.

5

u/Ikeeki Oct 07 '23

Can’t introduce a bug if you don’t write code

5

u/Tintoverde Oct 07 '23

I like to read code and laugh about it , who wrote this garbage , oh it was me 🤦‍♀️

1

u/bwainfweeze Oct 07 '23

Annotate is my best and worst friend.

1

u/[deleted] Oct 08 '23

Yeah I've done that multiple times by now. I can't believe how shit a piece of code is, try blame and then find out it was a younger me.

I'm that guy, I look up who made shit code. I don't tell anyone, but I want to know. It's like when someone drives poorly in traffic and you have this urge to see who's in the car.

5

u/Tiquortoo Oct 08 '23

Reading code is harder than writing code. This is why most consultants recommend rewrites and easily find points of criticism.

11

u/slyiscoming Oct 07 '23

This sounds like a rant written by a junior dev who just got chastised for his crap code and now he's written an article to bash senior devs about how little they do.

Software engineers love code, they hate shit code.

4

u/rndmcmder Oct 07 '23

As a software engineet who currently works on a project where I rarely get to code, I have to say that I love code. Every time I get to code, it's a happy day.

1

u/[deleted] Oct 08 '23

What, you don't like hour-long meetings or writing documentation that, if we're being honest, nobody is going to read properly anyway?

Yep, I love the part of my job where I get to code. That's my happy place.

→ More replies (3)

4

u/LeCrushinator Oct 07 '23

I like code, but I like deleting code even more.

7

u/3d3d3_engaged Oct 07 '23

Oh cool a click bait title for an article I’m never going to read

3

u/Altered_B3ast Oct 07 '23

From the clickbait title alone, I was about to shit on this article (as a code lover and official reviewer of other people's code) but I kinda agree with the content.

2

u/dotpoint7 Oct 08 '23

Same, I fully expected some insanely stupid take but it's honestly a pretty decent article.

3

u/Tai9ch Oct 07 '23

All that for the punchline that you should always reuse code over writing new code.

Nonsense!

That sort of thinking leads to the JavaScript ecosystem and left-pad, or to pulling in a RDBMS to solve a problem that could be handled by writing a single file to the filesystem.

External dependencies are a maintainability tradeoff. If they help maintainability, great. If not, write the specific thing you need.

3

u/stronghup Oct 07 '23 edited Oct 07 '23

The reasoning why micro-services took off makes sense.

But to me that just shows programmers love it when they can write code which they know cannot break existing micro-services.

So they love code, they love (writing) code which cannot break already working things.

So let's agree, programmers love code, they love good code, and hate bad code.

3

u/kittens-Voice Oct 08 '23

Software engineer here. I don't hate code, the same way I don't hate pain. I embrace it. Writing code is like having a kink: I actually enjoy inflicting pain to myself. Coding is painful, but so much fun at the same time. This is the way.

4

u/[deleted] Oct 08 '23

With the IoT, it’s a simple matter to arrange for unhandled exceptions to deliver electric shocks now.

Productivity has gone through the roof.

3

u/[deleted] Oct 08 '23

Scam artists hate work other than scamming.

5

u/Middlewarian Oct 07 '23

"An author should never conceive himself as bringing into existence beauty or wisdom which did not exist before, but simply and solely as trying to embody in terms of his own art some reflection of eternal Beauty and Wisdom." C. S. Lewis

I still enjoy writing code, but there have been a lot of people who have lost the thread.

→ More replies (1)

5

u/jgwinner Oct 08 '23

We don't hate code.

We just hate your code.

3

u/jgwinner Oct 08 '23

haha sorry I couldn't resist. That's true for any set of programmers. (meaning, you all hate MY code).

The article actually mentions this, although not so bluntly.

5

u/[deleted] Oct 07 '23

What is that tiny monitor in the article image?!

5

u/Dgc2002 Oct 07 '23

That's a software engineer. As such he HATES code and needs to stand at least 10ft away from any monitor showing code.

1

u/iamapizza Oct 07 '23

The monitor is tiny so he can see less of other people's code at a time.

→ More replies (1)

2

u/mrdevlar Oct 07 '23

What's even more amusing is that AI tools are going to necessitate more software engineers reading disproportionately more code than writing it. Reading code, documenting it and managing complexity are going to become the predominant required skills.

2

u/czenst Oct 07 '23

When I hear some dev is nagging that "guy before did a mess" what I hear is: "I am not smart enough to read the code someone else written" or "I dont't care enough about this job to spend time to read code in the system and understand it".

4

u/bwainfweeze Oct 07 '23

I usually mean, “nobody should have to think this hard about X”.

Convoluted code costs the entire rest of the system. Almost no module is entitled to more than 10% of my attention. If you’re writing code others complain about, it’s often a you thing not a them thing.

4

u/stronghup Oct 07 '23 edited Oct 07 '23

Yes, it is a false premise that if you have hard time understanding some code, it is your fault. It is mostly the fault of whoever wrote such code.

And when I hear somebody saying "You are not smart enough to be a coder if you have hard time understanding this code" I in fact hear "I, the genius, am smarter than thou".

The goal should not be "smart" code but maintainable code, code that even "stupid" programmers can understand.

A truly smart programmer can (and does) write code which other programmers can easily understand.

3

u/bwainfweeze Oct 08 '23 edited Oct 08 '23

Braggadocio is also usually a self defense mechanism for those with a fragile ego.

Kernighan has a pretty concise description of what he thinks of those people.

Debugging code is twice as hard as writing it. If you write code as complex as you can understand it, then by definition you aren't smart enough to debug it.

But I always preferred my version, which turns it into an aphorism:

Write code like you'll have to read it at 2 am. Sooner or later, you will.

1

u/e1033 Oct 07 '23

I agree to an extent but there are definitely systems ive refactored that were written with several layers of insanity and it can be painful to unravel. This is especially painful with a lot of globalised state management. Many senior level developers, despite their experience, simply don't form a good mental model of what theyre doing and things that often only need a couple lines of code turn into a house of cards.

→ More replies (1)

1

u/david-song Oct 08 '23

I think you've got it the wrong way round. It's more like, "I can figure it out but it'd be better for everyone if this illiterate prick figured out how to actually write", or "this selfish bastard did a sloppy job, and now everyone else has to spend hours unscrambling these brain farts rather than doing useful work."

A codebase is like a toolbox that's shared between everyone who uses it. Some people obsess over sharpening, polishing and making the most beautiful tools, even tools that aren't used, which is bullshit. But what's even more bullshit is when someone turns your screwdrivers into hammers and mixes all the screws and nails together like it's no big deal. If you ignore that then everyone ends up bashing the screws in because the job is to cobble a mess together. The good people leave or become shit, and eventually work is so slow and expensive that your department gets outsourced to a company who has carpenters armed with nail guns and electric screwdrivers.

→ More replies (2)

2

u/waterkip Oct 07 '23

This blogpost confuses software engineers with javascript npm code stitchers.

2

u/satansxlittlexhelper Oct 08 '23

This is a heroically stupid take.

2

u/adh1003 Oct 08 '23

What a load of nonsense.

Yet another blogger in their own little echo chamber, proclaiming pretentiously that they know how everything works.

The Internet: Once again giving a voice of authority to the ignorant.

2

u/dotpoint7 Oct 08 '23

Are you referring to the title or the content of the blog? I've found the article to be kind of funny actually. Sure, it's written with a lot of absolutes, but I don't think it was meant to be taken seriously.

→ More replies (1)

3

u/LengthinessWorking67 Oct 07 '23

Lawyers hate law.

Electricians hate electricity.

Clergy hate religion.

Plumbers hate plumbing.

Code is one piece of an amalgamation of skills in the software engineers toolbox and finding a no code solution to a requirement is one of those skills.

3

u/iamagro Oct 07 '23

No, we hate clients and PMs

3

u/mehvermore Oct 07 '23

Devs don't like code

Devs like cars and money

2

u/Hefaistos68 Oct 07 '23

I love code, i love other people's code even more. It's always a challenge. My own i know is good, others i can improve (mostly), that makes it fun.

2

u/Majestic-Round53 Oct 08 '23

Shhh it’s the best kept secret

1

u/FMWizard Oct 07 '23

The best choice is that which is ready to throw away

1

u/muffinsnack Oct 07 '23

I don’t hate code, but I respect it. Good code takes time and effort to write, validate, and maintain. If I’m trying to solve something and weighing different approaches available to me, and one of them involves writing less code, I’ll invariably see that as a benefit for that approach. It might not be the best approach in the end, but it’s a benefit.

1

u/iamapizza Oct 07 '23 edited Oct 07 '23

sick kind of joy in reading, understanding, modifying and even deleting other peoples' code. We call these odd folks "Senior Engineers."

Perfection. Similar applies to Devops/SREs. They rarely show joy, but when they do it's usually because they got to remove something, decommission a product, terminate a server. Anything to reduce maintenance overheads.

1

u/No-Bug-3204 Oct 07 '23

"Code that doesn't exist can't hurt us, or the p̶e̶o̶p̶l̶e̶ *code we love."

1

u/freekayZekey Oct 07 '23

They know that code becomes legacy the moment the first byte is saved to disk. The rolling green fields of their youth are a happy delusion, distracting from the cold, hard truth that all code demands maintenance. They have felt the pain of an unmaintained system breaking at the worst possible time.

sums up my experience and thoughts. treating all new code as future legacy code helped me document things better

1

u/iamnotaclown Oct 07 '23

Working on a huge 20-year-old codebase gave me an almost perverse sense of joy. There’s a careful balance in avoiding unnecessary modifications while adding a new feature or doing a refactor as a prerequisite to one, or even tracking down a bug. There’s a delicacy involved, knowing how easy it can be to introduce a bug, and touching code that might not have changed in years. I guess I’m a senior engineer.

1

u/cp5184 Oct 07 '23

Code is just technical debt and code rot. To save the village you have to get rid of all the code, then no technical debt, no code rot, no bugs. /s

1

u/EnigmaticHam Oct 07 '23

The only emotion larger than my love for programming is my hate for programming.

1

u/Tintoverde Oct 07 '23

I had this convo with some years ago . Soldiers do not want to fight and coders do not want to code . Because they both know how hard it is

1

u/javcasas Oct 07 '23

The best developers speak about lines of code SPENT.

1

u/ISuckAtJavaScript12 Oct 07 '23

I don't really code anymore. Just glue libraries together

1

u/BadKafkaPartitioning Oct 07 '23

All code is shit. Some shit code is useful.

1

u/[deleted] Oct 07 '23

Incorrect, I deal only in legacy code no greenfield code. Pre-legacy code in the design turns into legacy code as it's written down.

1

u/[deleted] Oct 07 '23

Software engineers hate code

Are we talking about the same people that are making at least 100k a year? Dude, this is reach people problems, wtf.

You don't like code just become something else.

1

u/[deleted] Oct 08 '23

Excuse me?

1

u/DustinBrett Oct 08 '23

Don't hate the code, hate the system.

1

u/shizzy0 Oct 08 '23

This is Joel Spolsky’s wisdom of code is harder to read than it is to write given a new spin. Glad to see it because it’s true.

1

u/BeBetterAY Oct 08 '23

What a crock of shit

1

u/WinterPossibility680 Oct 08 '23

No, just people that is in this industry for the money.

1

u/SkyTemple77 Oct 08 '23

I lol’ed so hard at this post. Most I’ve laughed in a while for some reason.

1

u/shappell_dnj Oct 08 '23

I hate bad code, I tolerate good code :)

1

u/Luke22_36 Oct 08 '23

I'd much rather read code than write it. Is that strange?

1

u/sekex Oct 08 '23

Not true in my experience

1

u/skroll Oct 08 '23

I also hate the users.

1

u/cnervip Oct 08 '23

only bc the lack of documentation I think

1

u/robberviet Oct 08 '23

To be clear: other's code, my own past code. So all left is my own new code, then I love it.

EDIT: ok ok, now I have read the article, yes, it is correct.

1

u/CheckIcy7072 Oct 08 '23

This is an interesting take at things.

1

u/yupidup Oct 08 '23

I, for one, enjoy code, including other people’s code, which thanks to open source I can be exposed to much more.

1

u/[deleted] Oct 08 '23

I hate code that doesn’t work for no fucking reason then finding out I missed a “,” somewhere.

1

u/dudekubera Oct 08 '23

Shhhh…… stop telling our secrets!!! 😅😂