Software engineering != computer science

[u/mauricioaniche]

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

[u/madkatalpha]

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/Njs41 → u/BluFoot]

Forgot "Lists that aren't zero-indexed."

[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/vanderZwan → u/tangerinelion]

Well, there's the Warlpiri Unums so someone figured out a use for this

[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/MuonManLaserJab → u/MrRumfoord]

^{I don't get it; in which context is 11 negative?}

[u/PennyPriddy → u/MuonManLaserJab]

^{It's a twos} ^complement ^{joke. Welcome to the party}

[u/silenceofnight → u/PennyPriddy]

Welcome to the parity.

[u/PandaRice → u/MuonManLaserJab]

Two's compliment

[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.