On Github hlian / 100-tips-for-writing-code
(alternately: fake it until you make it)
Pictured above: why the lucky stiff
how I know him
chapter 1 of 'the (poignant) guide to ruby'
how you might know him
still, to this day, the only ruby book that demonstrates how important metaprogramming is to Ruby
4 KB web framework (rails: ~50 MB)
as easy to write a native app as it is to write a website
[in /etc/hosts] 555.55.55.555 hoodwink.d
local http proxy + secret club = web graffiti
~ potion ~ Potion is an object- and mixin-oriented (traits) language. Its exciting points are: * Just-in-time compilation to x86 and x86-64 machine code function pointers. This means she's a speedy one. Who integrates very well with C extensions. The JIT is turned on by default and is considered the primary mode of operation. * Intermediate bytecode format and VM. Load and dump code. Decent speed and cross- architecture. Heavily based on Lua's VM. * A lightweight generational GC, based on Basile Starynkevitch's work on Qish, with ~4ms per GC on average with < 100MB heaps. * Bootstrapped "id" object model, based on Ian Piumarta's soda languages. This means everything in the language, including object allocation and interpreter state are part of the object model. (See COPYING for citations.)
.ooo 'OOOo ~ p ooOOOo tion ~ .OOO oO %% a little Oo fast language. 'O ` (o) ___/ / /` \ /v^ ` , (...v/v^/ \../::/ \/::/
unHoly: https://github.com/whymirror/unholy
To compile Ruby to a .pyc: > bin/unholy test.rb > PYTHONPATH=python \ python test.rb.pyc --- To translate to Python: > decompyle test.rb.pyc > test.py
http://viewsourcecode.org/why/
Joseph Campbell's Monomyth
here all the unknown realms that i know about
prints first 100 Fibonacci numbers
0, 1, 1, 2, 3, 5, 8, 13, 21, ...
(prints first 100 Fibonacci numbers)
0, 1, 1, 2, 3, 5, 8, 13, 21, ...
(prints "Hello World")
puts <<2*2,2 puts <<2*2,2 2
See also: Qlobe
// At this point, I'd like to take a moment to speak to you about the Adobe PSD format. // PSD is not a good format. PSD is not even a bad format. Calling it such would be an // insult to other bad formats, such as PCX or JPEG. No, PSD is an abysmal format. Having // worked on this code for several weeks now, my hate for PSD has grown to a raging fire // that burns with the fierce passion of a million suns. // If there are two different ways of doing something, PSD will do both, in different // places. It will then make up three more ways no sane human would think of, and do those // too. PSD makes inconsistency an art form. Why, for instance, did it suddenly decide // that *these* particular chunks should be aligned to four bytes, and that this alignement // should *not* be included in the size? Other chunks in other places are either unaligned, // or aligned with the alignment included in the size. Here, though, it is not included. // Either one of these three behaviours would be fine. A sane format would pick one. PSD, // of course, uses all three, and more. // Trying to get data out of a PSD file is like trying to find something in the attic of // your eccentric old uncle who died in a freak freshwater shark attack on his 58th // birthday. That last detail may not be important for the purposes of the simile, but // at this point I am spending a lot of time imagining amusing fates for the people // responsible for this Rube Goldberg of a file format. // Earlier, I tried to get a hold of the latest specs for the PSD file format. To do this, // I had to apply to them for permission to apply to them to have them consider sending // me this sacred tome. This would have involved faxing them a copy of some document or // other, probably signed in blood. I can only imagine that they make this process so // difficult because they are intensely ashamed of having created this abomination. I // was naturally not gullible enough to go through with this procedure, but if I had done // so, I would have printed out every single page of the spec, and set them all on fire. // Were it within my power, I would gather every single copy of those specs, and launch // them on a spaceship directly into the sun. // // PSD is not my favourite file format.
IPoAC has been successfully implemented, but for only nine packets of data, with a packet loss ratio of 55% (due to user error),[2] and a response time ranging from 3000 seconds (~54 minutes) to over 6000 seconds (~1.77 hours).
UDP was actually “designed” in 30 minutes on a blackboard when we decided pull the original TCP protocol apart into TCP and IP, and created UDP on top of IP as an alternative for multiplexing and demultiplexing IP datagrams inside a host among the various host processes or tasks. But it was a placeholder that enabled all the non-virtual-circuit protocols since ... without [people's] having to negotiate for permission either to define a new protocol or to extend TCP by adding “features”.
David P. Reed: TCP, UDP, end-to-end principle, Reed's law
matrix_plus(matrix_multiply(matrix_multiply(a, b), c), d);
(a * b * c) + d;
You deserve to use custom operators.
one folder per record("/db/user1")
one file per column("/db/user1/email", "/db/user2/email")
SELECT = grep(1), locate(1)
INSERT = mkdir(1)
DELETE = rm(1)
schema migrations = mv(1)
ours is a literate profession
you will want a developer diary at some point in your life
open source is a battle that we won, and we weren't sure if were going to
your library might be the next big thing
the gripping tale of how a young dentists' daughter saves the lives of her stupid friends over and over again
'Could we move this function to another file?'
'Mayhaps we please move this function to another file forthwith?'
it's extraordinarily easy to find and fix slow code
it's extraordinarily difficult to find and fix superfluous code
it's extraordinarily easy to add code
it's extraordinarily difficult to remove code
one crash takes down an entire process
there's about one crash every 1000 lines of code
so: one process for every 1000 lines of code?