miniblog.

Fascinating to read about Discourse's user levels:

Python folks see me as a lisper, yet at the past emacs event someone said "oh, you're the Python guy!". I can't win!

Halfway through writing a Stack Overflow question, I realised what my problem was. It's an unusually good rubber duck.

It amuses me how the C standard tells you which parts are forward references: http://t.co/qiJRCYthLv . The document matches the language!

Dilbert summarising the traditional attitude of technology decisions http://t.co/ZgutQ4KC5E (oh, hindsight!)

.@melpa_emacs what's the significance of '1 / 2 / 3' on http://t.co/Ai8RILdXZV ?

Either modelling complex parse trees is painful in C, or I have much to learn about building complex structs in C.

Automating something allows you to deal with it at a higher level of sophistication. It's nice. E.g. 'sudo ...' vs 'deploy this app'.

Fascinating bug where changing the type exposes limits in GCC's register allocator with huge performance consequences http://t.co/o1ReECO0Bx

Why the Web of Trust Sucks

"[We need] cryptography that post-dates the Fresh Prince." PGP must die http://t.co/R9x2v89MJ0

Yet more NSA revelations. The Internet has become an astoundingly hostile environment.

http://t.co/1nWieBalwq Developer inequality and the technical debt crisis (interesting thoughts on the web as a platform)

Defining a kernel of web browser functionality: http://t.co/mxMv5wQM0z really nifty.

.@bruceconnor saw rich-minority today, I was wondering how it differs from diminish other than having a brilliant name?