5 ms·

I don't really get this "joke" but man do I hate the trend of removing any personality from code. Programming used to be FUN and a way to express yourself. Ea

I don't really get this "joke" but man do I hate the trend of removing any personality from code. Programming used to be FUN and a way to express yourself. Easter eggs exemplified this. Now its cold and business only.

GW150914 8y ago
Everyone who decided they’d rather have a giant paycheck than have fun made it happen. This site is full of people who make and made that choice, who chase VC money, and consequently have little right to complain about how corporate their working lives are.
- slededit 8y ago
  Money has always been around, but even "corporate" was not nearly as stifling. 90s era Microsoft code is quite colorful - as I'm sure it would have been at most other companies of the era.
  - quotemstr 8y ago
    Even today, the Windows source code contains quite a few long, narrative comments that are both historically educational and entertaining to read.
    - slededit 8y ago
      Shortly before I left someone on the coding standards committee espoused the idea that good code was code where you couldn't tell who wrote it. I feel as though the last vestiges of the BillG era died that day.
      - quotemstr 8y ago
        I've never liked style committees. I've never seen one do anything to actually improve code comprehension, but I've seen plenty of bullshit that kills velocity and sucks all the joy out of programming.
jkFeiwi 8y ago
This isn't an easter egg, nor a comment in the code. It's dab smack in the manual. Could distract or confuse someone just trying to look up a function. I say we keep the fun expression stuff in places where it won't get in the user's way of doing their job.
- slededit 8y ago
  Manuals used to be fun too - except for IBM's, those were never fun.
  - jkFeiwi 8y ago
    Jokes may be fun to write. But when you're scouring a manual for a needed function, and you're confronted with a smarmy joke, it probably won't be as fun (especially if you're reading the manual to troubleshoot something.)
    - slededit 8y ago
      It broke up the relative monotony of otherwise dry technical information. It has a similar effect when placed in code. In addition many companies used it as a form branding - "Hey we're not stuffy old IBM! We're Cool!". Back then manuals were also far more important, you couldn't operate the machine at all without one. Yet the jokes never managed to stop people from getting the information they needed. I think the real difference when it comes to manuals is most modern ones are not comprehensive. I could see being upset if there was a joke but no information on my actual problem.
    - TeMPOraL 8y ago
      It's in a separate box at the end of the manual for that function. It's generally like a footnote. It being there shouldn't distract or hurt you in any way.

GW150914 8y ago

Everyone who decided they’d rather have a giant paycheck than have fun made it happen. This site is full of people who make and made that choice, who chase VC money, and consequently have little right to complain about how corporate their working lives are.

slededit 8y ago
Money has always been around, but even "corporate" was not nearly as stifling. 90s era Microsoft code is quite colorful - as I'm sure it would have been at most other companies of the era.
- quotemstr 8y ago
  Even today, the Windows source code contains quite a few long, narrative comments that are both historically educational and entertaining to read.
  - slededit 8y ago
    Shortly before I left someone on the coding standards committee espoused the idea that good code was code where you couldn't tell who wrote it. I feel as though the last vestiges of the BillG era died that day.
    - quotemstr 8y ago
      I've never liked style committees. I've never seen one do anything to actually improve code comprehension, but I've seen plenty of bullshit that kills velocity and sucks all the joy out of programming.

jkFeiwi 8y ago

This isn't an easter egg, nor a comment in the code. It's dab smack in the manual. Could distract or confuse someone just trying to look up a function. I say we keep the fun expression stuff in places where it won't get in the user's way of doing their job.

slededit 8y ago
Manuals used to be fun too - except for IBM's, those were never fun.
- jkFeiwi 8y ago
  Jokes may be fun to write. But when you're scouring a manual for a needed function, and you're confronted with a smarmy joke, it probably won't be as fun (especially if you're reading the manual to troubleshoot something.)
  - slededit 8y ago
    It broke up the relative monotony of otherwise dry technical information. It has a similar effect when placed in code. In addition many companies used it as a form branding - "Hey we're not stuffy old IBM! We're Cool!". Back then manuals were also far more important, you couldn't operate the machine at all without one. Yet the jokes never managed to stop people from getting the information they needed. I think the real difference when it comes to manuals is most modern ones are not comprehensive. I could see being upset if there was a joke but no information on my actual problem.
  - TeMPOraL 8y ago
    It's in a separate box at the end of the manual for that function. It's generally like a footnote. It being there shouldn't distract or hurt you in any way.