CH

January 4, 2017

How to (actually) "learn programming"

Filed under: bitcoin, software development, tmsr — Benjamin Vulpes @ 3:03 a.m.

More or less the same way you learn any other very complicated craft with oodles of knowledge both formalized and oral: by finding the most strict and knowledgeable master you can, and slaving for him as best you can for as long as you can tolerate it. Proper apprenticeships are an unlikely model in the States, as everyone with 9 months of React under their belt expects 140KUSD per annum and a title, but you wanted to know how to actually learn programming.

Most masters that you'll find in the wild world of shartups are neither particularly masterful nor particularly willing to entertain your novicehood. This manifests in "industry" (to the extent that building javascript webapps might be called industry) as "software engineers" (lacking the "senior" honorific) train "junior software engineers" inserted into their organization by the Diversity Machine. This is not the sort of master you'll learn much useful from, regardless of what you think of the type of master you'd like to learn from.

Since you'll not find anyone to beat 40 years of slapdash hacks into your head on the shartup circuit, you're stuck learning from the cruel, busy, cryptic and reluctant peers of The Republic, who won't be particularly useful on the curricula front.

Reading:

- Applied Cryptography, Bruce Schneier (first edition)
Read the first edition, with the red BLUE (Red is the bullshit version. Kudos to mod6 for the catch.) cover. Schneier redacted all of the actual goodies so that he might land a job with people who find that kind of behavior appealing and not appalling.

- Common Lisp the Language, 2nd Edition, Guy Steele
The peers have largely settled on Common Lisp as a programming lingua franca. It's an entirely adequate language, featuring ~everything you'll find in "modern" programming languages like PHP or Python. While I'm not convinced that one can "learn programming" in any other way than by building things and practicing constantly and with a relentless eye towards self improvement, reading this book won't hurt you (too much).

Exercises:

- generate and secure GPG keys

This is the single most important task for anyone who intends to join The Republic. You must learn what it means to generate keys securely, how to use them securely, enumerate the kinds of threat you wish to secure your keys against, and then effect a system that tends to all of these needs.

You also must establish and practice your backup and restoration process for these keys. Everything dies, including computer hardware, so you must ensure that you do not fail to maintain access to the anchor to reality and key to the door of The Republic's forum.

- set up and operate a virtual server

While I cannot recommend that you make a permanent home in a virtualized server on someone else's hardware, you need a persistent Linux box that can do...things. It more or less doesn't matter which Linux you settle on if you're reading this for advice, but you should operate under the assumptions that a) you'll be relegating the machine to the dustbin at some point and b) you'll probably want to change Linux distributions as well.

- set up an IRC bouncer

If you have the remotest dream of anyone in The Most Serene Republic of Bitcoin giving a shit about you and your problems, you'll quickly discover the importance of maintaining your own connection to the forum and not annoying the peers by reconnecting constantly. Establishing and maintaining a persistent and robust IRC connection will teach you much about the Linux and IRC client you've chosen to operate.

- set up a blog

Recount your travails in "learning programming". Muse in public. Offer your thoughts that others may know them and contradict you. This is as close as you'll get to "having a master", so have opinions, be ready to defend them, and prepare to accept that you're wrong. Don't neglect your comment system and for the love of all that is holy don't outsource it.

- operate a server

There are many ways to get into operating your own hardware, and many tradeoffs to make in the hardware procurement project. Migrating from virtualized servers to your own metal in a datacenter somewhere will illuminate all sorts of dusty corners in your head where the advocates of feeding the world with McDonald's hide the assumptions they programmed you with as a child. This project will acquaint you with the engineering tradeoffs with which programmering as a career is rife.

- run a "The Real Bitcoin" node

Once you've grown into your own hardware and have at least 5GB of RAM and 200GB of disk to spare, consider operating a TRB node. TRB is downright finicky in constrained and virtualized environments, and you're on a course to digital literacy and self-sufficiency.

Projects:

- extend Diana Coman's "foxybot", a bot for Mircea Popescu's MMORPG Eulora

MP runs an MMORPG and encourages players to automate their activities in it. Diana Coman, the current project lead/developer (do forgive the possibly-insulting title) maintains and extends both the game's codebase and that of it's dominant bot "foxybot". The link to foxybot above has a list of features the playerbase would like to see implemented.

Working in this environment will teach you about the wonders of C++ and Crystalspace; a programming language with which one must be conversant but that is not particularly...good, and a "game development engine" that isn't as loathsome as other engines respectively.

- (re)implement V

V is a hard crypto source distribution tool. Reimplementing a working V will demonstrate that you understand a foundational building block of our world.

- make a Lamport Parachute

Stan says it all, go read it.

- operate an IRC bot

trinque and I (but mostly trinque) have put some work into a Common Lisp IRC bot. Stand one up and keep it up.

- build and host a log viewer

If you're already operating an IRC bot (and when we've made it so easy for you to do so, not doing so begins to look a bit lazy), you may contribute to The Republic's own form of distributed redundancy: many different implementations of core functionality -- in this case, log viewers. Public logs civilize the chaos and noise of IRC, and cross-referencing upgrades logs to Talmudic stature. phf hosts the canonical logs at http://btcbase.org/log , I host a set at http://bvulpes.com/logs , and Framedragger hosts a set at http://log.mkj.lt/trilema/today .

This project will acquaint you with the miseries of building wwwtronic software. Implementing search and cross-referencing will teach you even more.

Coda

There is no point to "learn programming" if you're just going to further the works of evil by battling for the empire's hegemony with JavaScript and "mobile apps". If all you desire is a good job and enough money to pay for beer, food, and box for your meat so that you may attract a girl in her late thirties who's looking to settle, go sign up for your local code school, capitalize on their placement program, and settle down to devour your brain elsewhere. The Republic will continue to fight without you, ensuring access to strong cryptography (see: FUCKGOATS, the only high-grade entropy source on the market in the whole world), and a Bitcoin implementation that keeps pestilential currency-fascists and -devaluators at bay.

The reading section is currently woefully incomplete, indicative of both the reading I've done in the field and what I consider the utility of various "programming books". Suggestions welcome.

9 Comments »

  1. Now this is more like it.

  2. Mircea Popescu says:

    This project will acquaint you with the miseries of building wwwtronic software. Implementing search and cross-referencing will teach you even more.

    And implementing an automated summarizer will put you ahead of google engineering.

  3. Mircea Popescu says:

    PS. Knuth, definitely.

    • Benjamin Vulpes says:

      Mircea Popescu,

      The whole catalog? Any particularly educational specifics to recommend?

  4. Benjamin Vulpes says:

    Pete,

    I thought the quotes in the previous chapter's title would be a dead giveaway. A well...

  5. A) Watch Bill Gosper's LIFE and MACSYMA

    Part 1: https://www.youtube.com/watch?v=BpgA2oCQj9o
    Part 2: https://www.youtube.com/watch?v=PFxEyoujzxw
    Part 3: https://www.youtube.com/watch?v=ppnadmuDRIs
    Part 4: https://www.youtube.com/watch?v=5wmg7xZLtjU
    Part 5: https://www.youtube.com/watch?v=d_AXix3ALeM
    Part 6: https://www.youtube.com/watch?v=Cplgw4h_zgk

    B) UNIX-HATER's handbook: web.mit.edu/~simsong/www/ugh.pdf

    C) A Programmer's Guide to CLOS by Sonya E. Keene's

    D) Hackmem: w3.pppl.gov/~hammett/work/2009/AIM-239-ocr.pdf

    E) Compare SMBX: https://www.youtube.com/watch?v=V4HXPJtym2Q with Pixar: https://www.youtube.com/watch?v=__3aAOBWW60

    F) Read _all of_ PG's essays & Lisp documents.

    H) Read loper-os, from back to front. All comments, all links.

    I) Read all of the Naggum posts that show up in the logs.

    Many would recommend Art of the Metaobject Protocol, but I hated it. C2MOP (closer to MOP) has already been written, and works fine.

  6. Ben, as much as I love your rants against the Imperium, your practical posts are all the more appreciated, particularly given your considerably expertise in the field of "programming," and doubly particularly for ambitious know-nothings / devoted Mactards like myself.

    Also, what little I've been able to scratch of the surface of Knuth has been... revealing.

  7. Benjamin Vulpes says:

    Pete,

    While I appreciate the sentiment, configuring Apple/Google user interfaces and generally cleaning the Augean stables of other people's mistakes only counts as "programming" very weakly.

    But thanks for the kind words!

    --b

RSS feed for comments on this post. TrackBack URL

Reply

« Arrival --- How to (actually) "learn programming" »