OH: "Dev 1 is on the frontend, and dev 2 is on the backend." "Oh, so you're basically a pantomime horse?"
miniblog.
Amazingly blunt phishing: http://t.co/QcwOFGDUJi is a fake site but visiting http://t.co/ZZZjPxlfE2 shows as http://t.co/5MnwNXanx1. Subtle!
I've realised I can't name a single large codebase that I would consider elegant. Can you?
Used #Python metaclasses in anger yesterday -- as with most metaprogramming, usually a bad idea, but occasionally a huge boon.
Announcing with-namespace.el, the namespace solution you didn't know you needed for #Emacs lisp! https://github.com/Wilfred/with-namespace.el
Upgrading to #Emacs 24.3? You probably want to recompile *all* your .elc files, or you will hit quirky issues like: https://github.com/mooz/js2-mode/issues/72
Treating v1.0 as an official release is incompatible with semantic versioning, since you might change your API before a 'grand unveiling'.
PyPI is painfully slow sometimes. We've bitten the bullet and started setting up pep381client internally so we can always set up a fresh env
That feeling when the act of writing a Stack Overflow question helps you solve the problem unaided.
This week has seen Pip 1.9 with SSL support, and a setuptools/distribute merge announced. Things are looking up for Python packaging!
I'm very impressed with Jedi for Python auto completion. Plugins available for all the best text editors...
Argh, Python's PIL has disappeared from PyPI. Googling suggests this has happened before, and Pillow is superseding PIL anyway.
For managing #Emacs depedencies, there's Carton, Pallet, EVM and EL4T. It's exciting to see many solutions being built. No clear winner yet.
Announcing loop.el, the Elisp loop structures you always wished you had! https://github.com/wilfred/loop.el #emacs
VP8 has patent protection from Google and MPEG-LA. Even Adobe are talking about adding it to Flash. Looks like it might win the format wars.
Duck programming: http://t.co/AhuX8Z9Huj
['Fizz'*(not i%3) + 'Buzz'*(not i%5) or i for i in range(1, 100)]
No true scotsman^W idiomatic code fallacy: http://t.co/v4s1mosMSK
To avoid confusion: s/fiancé/fiancée/ in my previous tweet.
Had a rather confused conversation with my fiancé -- eventually realised she'd interpreted 'pair programming' as 'pear programming'.
Showing 7,161-7,180 of 7,508 posts