A major problem with captchas is that OCR is good enough to fool it some of the time. Will machine learning do the same to Mechanical Turk?
miniblog.
It wasn't until I wrote a Scheme interpreter that I really understood the relationship between lists and cons cells.
Nightlight: An embedded editor for Clojure https://sekao.net/nightlight/ Very cool -- embedding an editor in the live application!
Perfection & Feedback Loops or: why worse is better https://www.slideshare.net/mobile/esug/perfection-feedback-loops-or-why-worse-is-better (on the striving for perfection vs iteration)
If you want to get your feet wet with Pharo Smalltalk, the videos and materials from the MOOC are now available! https://files.pharo.org/mooc/
Linux 4.8 would crash due to aggressive asserting: https://lkml.iu.edu/hypermail/linux/kernel/1610.0/00878.html (interesting thread: hard to segment critical code in a monolith)
Woohoo! Landed my first patch in Emacs core! https://github.com/emacs-mirror/emacs/commit/ed399f26fa78fa69171e32b34af9a77debf57fad 🎉
I'm surprised by how often Wikipedia is a good resource for technical documentation. I'm using https://en.wikipedia.org/wiki/Executable_and_Linkable_Format to write ELF files!
What's the antonym of 'hostile fork'? 'Friendly fork'? 'Affectionate fork'?
The author of nasm-mode has a great opinionated blogpost on different assemblers and their advantages/disadvantages: https://nullprogram.com/blog/2015/04/19/
Current status: replacing prog2, an emacs lisp special form, with a macro: https://gitlab.com/wilfred/emacs/commit/91967f11ed8a69ea29215e8219cafaef5f550fe2 Unsure if there's interest upstream.
Rust's error messages can refer to multiple parts of code, and include increasing amounts of prose: https://blog.rust-lang.org/2016/08/10/Shape-of-errors-to-come.html looks promising!
Design for experts; accomodate beginners https://pchiusano.github.io/2016-02-25/tech-adoption.html (on the relationship between language power, learning curve, and adoption)
Current status: experimenting with CI for @guilelang! https://lists.gnu.org/archive/html/guile-devel/2016-10/msg00007.html
I think three months is the perfect length for a side project. Long enough to build something cool without getting sick of it.
I end up regularly rebasing my feature branches as I work. Are branches the best abstraction? Perhaps patch sets are better.
Emacs command of the day: vc-region-history. This hidden gem shows a log of VCS changes in the current region!
A 500 line C program implementing a respectable amount of Common Lisp! https://web.archive.org/web/20070722203906/http://www.modeemi.fi/~chery/lisp500/
A cute touch in Emacs 25.1: executing the bytecode of a macro teaches Emacs to highlight it! https://github.com/emacs-mirror/emacs/blob/8cd975cebd588d5435fa2b333dba6c526e602933/lisp/emacs-lisp/byte-run.el#L209-L221
I've been kicking the tires on GitLab. It's not quite a snappy as GitHub, but the feature set is excellent.
Showing 181-200 of 922 posts