bits

And for addition (section 15.18.2): If an integer addition overflows, then the result is the low-order bits of the mathematical sum as represented in some sufficiently large two's-complement format.

It makes sense to use unsigned for sizes to save a bit (or 32 bits per size).

For example, with about 33 bits of information, one can identify any individual on this planet.

For example for multiplication (section 15.17.1): If an integer multiplication overflows, then the result is the low-order bits of the mathematical product as represented in some sufficiently large two's-complement format.

I mean, even if I limit myself to lodash/underscore, bluebird, and jQuery, I've got a lot of overlapping bits in there...

Did the bloke in the video ever find out what the missing bits were for?

Note that it should not take many bits to profile us in a way that is useful, while still respecting our privacy.

The most general approach I see, and the one I take, is to start with computable sequences of bits.

However, if you use C, your domain is bits and bytes, not abstract things — because this is what C is created to work with.

Not sure how ssize_t works, is it 64 bits then?

(And it's pretty common to hear people say that the bits that persist, like e.g.

We are continually striving for the highest quality, and work in small focussed teams following bits of Scrum, bits of Kanban, with a healthy dose of Extreme Programming (p.s these aren't buzzwords, we mean it when we say we do this stuff).

Section 6.7.2.1/10 of the C99 standard says: "The order of allocation of bit-fields within a unit (high-order to low-order or low-order to high-order) is implementation-defined" There is no guarantee on the order of the bits inside a bitfield.

I'm probably in the minority here, but I think that starting with the low level - bits, data representation/interpretation, and logic (which leads to CPU operation) - is the best path to go when starting to learn programming, because it really dispels a lot of the "magic" and mystery behind computers that can confuse beginning programmers when their code doesn't work as they expect.

Bits and pieces of both your comments are correct.....