Skip Navigation

Programmer Humor @programming.dev

cm0002 @lemmy.world

17h ago

True Spaghetti code

24 comments

BUT WHY IS THE RAM GONE?!?
- RAM is temporary, meeting the minimum viable product standard is forever

All fun and games till the PO requests some new feature or change and some poor soul has to add that into your code trying not to break it
Bonus points if the poor soul is you
- Faster to rewrite the whole thing

The Pirate's Code Style and Documentation Standard....be more like guidelines.

COBOL has entered the chat: If it ain't broke don't fix it.
- Given the engineer's amendment to "If it ain't broke, don't fix it." is usually "If it ain't broke, it doesn't have enough features yet.", I can only surmise that COBOL must be one of those languages that are so terrible that they deter their programmers from wanting to do that.
  
  I once had to modify some COBOL code. It's a highly organized language, not terrible. But because it's old there's a shortage of people now who are good at it or want to learn it. You pretty much have to decide your career is going to be working on old code.
- If it ain't broke don't fix it.
  I loathe that line
  
  If it ain’t broke… maintain it.
  
  +1 - the word "loathe" doesn't get used often enough. The only time I remember hearing it in a movie was in Sixteen Candles.

My boss once asked me whether their entrance test was too hard after several candidates sent him something that wouldn't even run.
- That's an instant ego boost
  
  Should working code even be part of an interview? Seems like a situation rife with abuse.
  Need free contractors? Just put your code issues up as a 4hr take home interview test.
- Good old fizzbuzz. https://blog.codinghorror.com/why-cant-programmers-program/
  
  Classic write-up!
  Although, now that I'm an interviewer, I kind of despise FizzBuzz, because nobody thinks clearly during a high pressure interview.
  Whenever possible, I love to talk with a candidate about some concrete past source code they claim to have written. I've better luck putting the candidate at ease and then talking through their contributions to the code.
  Of course, when I get enough candidates who shared source code, I don't even invite the ones who didn't share source code for an interview.
- I thought my entrance test was far too easy, I only had to create a blog in my web framework and show doing the basics like validations, secure parameters, etc.
  I learned later on that most couldn’t pass because they came from other languages and thought they could get by without knowing anything.
- One guy completed it, so it was just perfect

It worksish, but look at it the wrong way and it'll collapse entirely.

I wrote "some code" back when I was a child, if you asked me to explain how it works all I could tell you is "through the power of santa's little helper".
- You've been naughty this year! you're getting a sack of ~~coal~~ template errors!

24 comments