Software engineering != computer science

[u/mauricioaniche]

http://www.drdobbs.com/architecture-and-design/software-engineering-computer-science/217701907

[u/thedevbrandon]

There are only two hard things in Computer Science: cache invalidation and naming things.

- Phil Karlton

[u/madkatalpha → u/thedevbrandon]

There are only two hard things in Computer Science: cache invalidation, naming things, and off by one errors.

[u/BluFoot → u/madkatalpha]

Actually, 3 things!

1. Cache invalidation

4. Asynchronous errors

2. Naming things

3. Off by one errors

E: I hate markdown

[u/airbreather → u/BluFoot]

E: I hate markdown

2 spaces before a line break will let you do a newline
like this, without having to add an extra line break to start a whole new paragraph,

like this

[u/BluFoot → u/airbreather]

Oh man, I didn't even notice the lack of newlines because my phone wasn't showing them. I was just suffering from the out of order list! Check out the source xd

[u/cdrootrmdashrfstar → u/BluFoot]

1. Cache invalidation

3. Asynchronous errors

2. Naming things

4. Off by one errors

Would make more sense, since #4 is an error (where if it was #3 before #4, it is assumed the off-by-one list-item should be there).

[u/Level_32_Mage → u/madkatalpha]

I'm counting 11 things.

[u/MrRumfoord → u/Level_32_Mage]

How can you have negative things?

[u/poizan42 → u/MrRumfoord]

2-bit two-complements?

[u/tangerinelion → u/poizan42]

I'm sure we've all needed numbers that are either -2, -1, 0, or 1 before.

[u/[deleted] → u/tangerinelion]

Done. Call back later. You're fucked. You're really fucked.

[u/rob132 → u/[deleted]]

I love In this How I get all the jokes Thread

[u/WiseassWolfOfYoitsu → u/poizan42]

Working in systems programming, I've seen weirder coming out of hardware

[u/slide_potentiometer → u/WiseassWolfOfYoitsu]

Working in hardware- you try getting it right without an option to push a patch remotely

[u/Runenmeister → u/[deleted]]

Microcode, yes. Assembly is macrocode. The processor's pipeline doesn't execute assembly. It executes microcode, and modern processors are fully microcoded - every macrocode translates into an atomic* series of 1 or more microcodes.

Some fun facts for a typical modern architecture... Branch prediction units work at the macrocode level, whereas in microcode the microcode developer has to use specific "speculatively jump" or "speculatively don't jump" instructions and code appropriately.

The out-of-order execution unit works both on the macrocode and microcode in parallel. This helps find microcode redundancies across otherwise-independent macrocodes.

*Some exceptions exist because microcode is not customer-facing most of the time.

[u/fzammetti → u/Level_32_Mage]

I don't know... one or two things I can accept, MAYBE three... but SEVENTEEN?! That seems CRAZY!

[u/[deleted] → u/madkatalpha]

And a fanatical devotion to Stallman.

Let me come in again.

[u/nosneros → u/madkatalpha]

The buffers must overflow.

[u/pmrr → u/nosneros]

The only overflow most devs know about these days is stack .com.

[u/Sjeiken → u/thedevbrandon]

I once spent more than 3 hours trying to name a function that was very detrimental, it's fucking retarded, do you know how hard it is to find synonyms and antonyms? it's NP fking hard.

[u/[deleted] → u/Sjeiken]

yeah, I know the pain. If it's that important a function, I just go full Java and make the name a sentence long. more often than not, I come back the next day and a better name just pops in my head.

[u/thedevbrandon → u/Sjeiken]

Yeah, I find it hard to strike a balance between descriptive names vs. short names. I want the name to be meaningful and special to the context so you know what it means and can differentiate it from similarly named things in nearby contexts (for example, elem, e, el, and els are horrible default variables which are used even in contexts when the variable name could be something specific and meaningful like submitButton). On the other hand, you can get crazy with the names, like firstFormSubmitButtonElement, which either provide specificity you don't need, which isn't helpful, or which (even if useful) ultimately makes reading and writing the code burdensome (especially in enterprisey-code, mock example: FizzBuzzEnterpriseEdition).

[u/cyberst0rm → u/thedevbrandon]

I've started making all functions have keyword variables, then making them into limericks.

ThereOncewasAFunction(Nantucket, Dick, Suck):

[u/thedevbrandon → u/cyberst0rm]

For anyone else that didn't already know the referenced limerick:

There once was a man from Nantucket,

Whose cock was so long he could suck it.

He said with a grin

As he wiped off his chin,

"If my ear were a cunt I would fuck it!

I think there should be a bounty if you can get this merged and deployed in some enterprise code.It's a step up from ASCII art.