qubyte

I gave a lightning presentation on this subject last month. A better solution is to put the private methods into (sub)modules. This makes them public to the file system and gives you the ability to tune what you make public via your module API. Ideal for testing purposes and good for module structure in my opinion. The slides can be found here: https://speakerdeck.com/qubyte/writing-testable-private-meth...

Server Sent Events aren't used enough. I'm a big fan, so I wrote a little Node.js library which wraps (with options for preprocessing) an event emitter in an express middleware for the company I work for. https://www.npmjs.org/package/nudge

The bulk of the document is written in LaTeX, and it is possible that they used the listings package to write the code samples. See section 2.10 of The Listings Package document for variable column code samples. In more regular code snippets, the results can be very nice. http://mirror.ox.ac.uk/sites/ctan.org/macros/latex/contrib/l...

You should ditch CoffeeScript and do it in vanilla JS, if for no other reason than to avoid people like me telling you to ditch CoffeeScript and do it in vanilla JS. ;)

In all seriousness though, far beyond anything I was doing at 16. Kudos.

Security postmortems are a great idea. Until time machines happen.

Imagine if you're requiring that local module throughout your codebase. Now suppose that the module has become large enough to be come a directory. All those requires with the .js extension will break! If you leave it off, then no problem. Always avoid adding the .js.

I tend to procrastinate and troll stackoverflow for questions to answer. I'd be more productive, but now I'm trolling Hacker News instead.

Facetious, or an actual figure? If the latter, can you point us to a ref please?

Nice. I need to compare code written with highland to code with async.series/.each etc. (but not waterfall, I don't like that dude ;)).

I live within walking distance of the BT Tower, and the maximum I can get is < 1Mbps...

I believe python is popular these days, but I think C is still the language of choice. A few years back when I was a TA I was tutoring on a C course at Leeds university, and Sussex (where I did my undergrad) they're pretty hardcore, so I reckon it's still C with the occasional course in F77.

I started on emacs with that C course. These days I use sublime text for my own machines, and vim elsewhere (although I'm not very good). The end result of all this? I finish sentences with a semicolon and save with colon-w-q (or x, but wq is way more satisfying); :wq

It was an option the year before, but not enough people wanted to take it and the class was cancelled. I'm glad to have learnt C, because it came with an introduction to bash and ssh. Whilst the terminals we used were windows, we were logging into a linux box via putty. This way I got to learn the UNIX way of writing tiny, single purpose programs that operate on STDIN and STDOUT for piping together. I guess the philosophical education was at least as important as the code itself.

I want the education sector to start treating the ability to programme as they do literacy and numeracy. Everyone should know how to write a letter and read, but not necessarily write a novel. Everyone should know how to count, but not need to win the Fields Medal. I believe that everyone should be comfortable with looking at a script and tweak it to their needs, but not necessarily have to create a AAA game from scratch.

I was vaguely aware of programming as a child, but had no education (unless you count mailmerge and a broken floor-turtle) and certainly no encouragement at school (in the UK if my spelling hasn't given it away). I basically forgot all about it until the middle of my degree (physics) when C was mandatory. It took until two years after a PhD to work out that a career in programming was what I really wanted.

Do I regret the way I got here? Nope. I learnt a lot of cool stuff along the way. But had it not been for that C course I may never have worked out what I wanted. I got lucky, and luck should not be a factor.

I thought I'd put more detail in. The project is called ejecta-x. http://wizcorp.github.io/Ejecta-X/

There is an effort to port ejecta to android, which a company I used to work for is now maintaining. That means accelerated canvas for the big two.