Justin Etheredge points out the sartorial splendour of the technical class.
We really do look like a bunch of vagrants.
Read more →
Justin Etheredge points out the sartorial splendour of the technical class.
We really do look like a bunch of vagrants.
Read more →
Ripple is an interesting attempt to create an open, decentralised monetary system. The idea is to route payment from Alice to Bob (who don’t actually know one another) via any number of intermediaries whom they know, or who know one another. E.g. Alice might pay Charlie (whom she knows) $20, who then pays Bob (whom Charlie knows). It’s based on credit: each person grants people he knows a certain amount of credit, and thus a payment can move through the system.
Read more →
Ripple is an interesting attempt to create an open, decentralised monetary system. The idea is to route payment from Alice to Bob (who don’t actually know one another) via any number of intermediaries whom they know, or who know one another. E.g. Alice might pay Charlie (whom she knows) $20, who then pays Bob (whom Charlie knows). It’s based on credit: each person grants people he knows a certain amount of credit, and thus a payment can move through the system.
Read more →
A nifty little explanation about why a deeply-layered programming language can save time and money in the long run.
Read more →
A nifty little explanation about why a deeply-layered programming language can save time and money in the long run.
Read more →
PaperBack is free software which enables you to print data onto paper and read it back in via a scanner. With a 600 dpi printer and a 900 dpi scanner it is possible to store ½ megabyte of data per letter page; with compression, it’s possible to store about 3 megabytes per page (depending on the source data, of course — his example uses C code).
This is actually kinda cool: you could print out a few hundred pages and replicate the data on a CD; esp.
Read more →
PaperBack is free software which enables you to print data onto paper and read it back in via a scanner. With a 600 dpi printer and a 900 dpi scanner it is possible to store ½ megabyte of data per letter page; with compression, it’s possible to store about 3 megabytes per page (depending on the source data, of course — his example uses C code).
This is actually kinda cool: you could print out a few hundred pages and replicate the data on a CD; esp.
Read more →
Révènce writes that if a piece of code is not simple, it is wrong. He’s a bit emphatic, but in large part he’s correct. Programming languages that make complex things simple lead to code which has fewer errors. This is a major factor behind the high-level-language revolution: programmers are discovering that it doesn’t make sense to manage memory manually; that it doesn’t make sense to have to manually write out the components of a for loop; it doesn’t make sense to manually write the same boilerplate time after time.
Read more →
Révènce writes that if a piece of code is not simple, it is wrong. He’s a bit emphatic, but in large part he’s correct. Programming languages that make complex things simple lead to code which has fewer errors. This is a major factor behind the high-level-language revolution: programmers are discovering that it doesn’t make sense to manage memory manually; that it doesn’t make sense to have to manually write out the components of a for loop; it doesn’t make sense to manually write the same boilerplate time after time.
Read more →
In Unix there is a convention that filenames beginning with a dot (.) are not normally displayed unless one asks for them to be; they are thus usually hidden. A further convention holds that programs will look for settings files within a user’s home directory (his personal folder, if you will) and that these files will be hidden (i.e. have names starting with a dot). An example might be .bashrc (containing run commands for bash) or .
Read more →
In Unix there is a convention that filenames beginning with a dot (.) are not normally displayed unless one asks for them to be; they are thus usually hidden. A further convention holds that programs will look for settings files within a user’s home directory (his personal folder, if you will) and that these files will be hidden (i.e. have names starting with a dot). An example might be .bashrc (containing run commands for bash) or .
Read more →