Showing tag results for History

You have to understand decisions in context, and that includes knowing the problem it was trying to solve.

Just a lot of excited developers.

It doesn't mean anything special any more, but it once did.

By lining up two parallel arrays.

Putting together what we've learned, with a surprise.

Code sequences you will learn to recognize.

Taking shortcuts and combining steps, or omitting them entirely.

Implementing the receiving end of the calling convention.

Pretend it's on the stack, even if it isn't.

The stuff that didn't fit anywhere else.