Pet Peeves

So, I cracked open another programming book today (have stay current with the bullshit universities are filling programmers with these days) and saw something I detest. It's a lower level book with a focus on MIPS, and it's going through data size, and I see: "16-bit (Unicode character or half word)". Having written code to transform a codepoint sequence between UTF-8, UTF-16, and UTF-32, it slightly bothers me to see this. While I realize that there are very few instances when codepoints outside of the BMP are encountered, the BMP is still not all of Unicode. You need at least 21 bits to encode any Unicode codepoint. Should we really lie to children do to how complex the truth really is?

So [spoiler]/prog/[/spoiler], what are your pet peeves?

lol what

I hate homosexuals and negros.

>>1
So /prog/, what are your pet peeves?
BBCode failures.

It's things like that which don't let me sleep at night, OP.

My pet peeve is php ``programmers''.

My peeve are super anal code optimizing Nazis.  I don't mind people who believe in code optimization, but I hate the ones who are anal about *every* facet of it.
You can't even perceive the duration of a clock cycle.

implying we actually use the programming textbooks

>>8
[o][u]Back to /b/, please.[/u][/o]

>>8
'green text

>>6
My pet peeve is ``faggot quotes''.

>>9
Back ^to [spoiler]/bb[spoiler]c^ode_1⁰1/

To >>9, disregard my imperative in >>11, I suck cocks.

core2buio

Design Patterns™

Just thinking back to the first chapter of ``Head First Java'' makes me angry again.

>>14
I'm in two minds about Design Patterns, because we need to distinguish between those forced by the language and those that are caused by the problem.

>>15
Any particular solution will be formed by a combination of the problem and the language. I suppose occasionally, the language is the problem (aka. ``now you have two problems.'')
What 'we' need is to understand the distinction between normative and descriptive.