kunalb

For clojure, I'd actually recommend using light table. From my experience with the latest dev versions, the learning curve isn't hard at all and immediately having your code evaluated is pretty powerful and intuitive. [I started learning clojure recently as well]

True -- any visualization that doesn't get the message across is just about useless.

Luckily we have very tight feedback loops -- and I can push new versions every couple of hours so I can customize it really fast to suit their needs/mental models.

I disagree with this post: there's another use case for visualizations -- consuming data as fast as possible to take action (eg firefighting). I work on tools for engineers, and I've found that a rich, non-standard visualization that people can learn to parse quickly after a tiny bit of initial acclimatization -- but showing them exactly what they need can help a lot.

I just tried the Beethoven intro lesson for guitar -- first off, these are awesome for me as an almost-n00b guitar player!

Two suggestions:

- When you're holding really long notes the interval to see the next note is really small [the tab moves forward only once the long note ends so you don't have as much time to transition your fingers because you don't know/remember the next note; while in practice these should be the easiest transitions]

- Indicate the note lengths as well in terms of fourth or eighth notes, for those of us who like to count along.

My attempt at hammering the xkcd servers -- also colours missing tiles correctly (black/white depending on south/north): http://explog.in/xkcd.html

[edit: basically lays everything out in a single huge page so that you can scroll instead of dragging]

For those who don't tweak their toolchains spending one chunk of time and forgetting about them is obviously better than doing nothing else, but personally I recommend continuously evaluating what you do on the shell (well, obviously this can be generalized, but I won't go there) and tweaking away your pain points and repetitive tasks.

Some specific recommendations --

- Keep a version controlled `dotfiles` folder, link important files to it and share it across dev envs.

- Add shortcuts to modify your vimrc (<leader>v) and apply it (<leader>V) to help you tweak fast and get instant feedback.

- Using an approximation of REPL for any work I do has been the single largest productivity boost I have: minimize keystrokes between (Write Code) <> (Build/Compile/Run/Whatever/Get feedback) <> (Write code). I started using vimux recently (lets you run commands in a split pane without actually leaving the pane with vim installed) and have never been happier.

- While speaking of nice fonts to write code in, http://www.google.com/webfonts/specimen/PT+Mono is a new favourite of mine. Of course, your mileage will vary.

(edit: formatting)

I think that you _can_ join ml-class and db-class right now (the currently on going set of courses). It's only ai-class that has closed enrollment.

I think you're referring to Knuth -- in the introduction to TAOCP he compares the series to a cookbook, comparing recipes and algorithms.

You might want to edit the title and prefix an "Ask HN:" so that more people can respond to your question.

Hmm. 1) Fake name, yes -- I wasn't aware of that practice; not that common in India, at least in my friend circle.

2) That was what I meant -- syncing actual details with your anonymous persona.

I am supposed to _start_ work at FB assuming I get a visa.

I'm a bit curious about why a search for name won't show the alternate persona? I've had friends who made 2 profiles and both used to show up whenever I typed their name in; and his # being listed publicly doesn't affect the argument either way.

Edit: Reply to child comment by jarofgreen: apparently the comments are too deeply nested to reply directly: "using FB wrong therefore deserves to have his privacy violated"

I've never stated that he _deserved_ to get his privacy violated; it's simply that the behaviour of any s/w is based on what settings you choose. Your argument would have to be that it's the S/Ws fault for not being transparent enough/not easily understandable enough leading the user to be misled - but the general response seems to be that the s/w is actively out to get the user.

I'm not sure that's such a huge sin -- technically I think FB says that you cannot have more than 1 account/actual person; I'd imagine when this `feature` was baked in the engineers didn't imagine that anyone would maintain an account that 1) they would keep hidden from friends _and_ 2) add their phone numbers to.

At the very least, the friend could have blocked the set of people he didn't want to know about his preferences from the "gay" account: otherwise what stopped a simple search by name from showing both accounts?

I'm not particularly sure about this, but why would revealing the people who have stored YOUR phone number to YOU be such a big deal?

I'm assuming phone number verification checks that you own the number via SMS; so it just acts as a reverse-stalker (I'd be worried about people I _don't_ know having my phone number saved).

I'm an amateurish PHP dev; so I can't suggest specific projects to get into. BUT I've found the best way to go about getting into any open source project probably would be:

- Choose a project you've used if you can. (I went with WordPress for example)

- Decide whether you want to try helping out with the core project or you would prefer to make an add on

- Make sure you follow the docs, get the build for the project ready -- or at least try to following what the project's docs tell you to. Do your personal best to get a hang of the source--particularly the area where you're aiming at. Try your hand at writing some code.

- _Now_ reach out to the core developers and the community (IRC, mailing lists, forums)-- discuss any problems you faced getting your dev set up ready, writing/testing code or any concepts you didn't understand (don't ask stuff that can be answered with a lmgtfy), your idea. Ask for a simple bug to fix if you haven't managed to find anything.

- Develop it further -- get feedback from devs and end users -- release/submit a patch. Based on feedback, iterate and release the next version/new patch. Repeat!

[edit] Corrected formatting

noprocrast is time based. this extension only lets you submit links, and view the discussions of "Show hn" links that you created. visiting any other discussion on hacker news redirects you to a quote by richard hamming.

Win: Crimson Editor -> Gvim Linux: vim -> Gvim

A small chrome extension I've written by digging through the way facebook loads ticker updates: lets you check the feed without having to visit facebook.

All completed in 24 hours -- started by learning how to write a chrome extension, pretty printing and reading fb javascript, lots of hit and trials to find out what worked and what didn't -- and finally releasing it on the app store.

Slightly better screenshot here: http://explog.in/blog/2011/09/22/Chromicker/

For a concise, very readable book that I've used to get myself up to speed with algorithms in preparation for interviews you can try reading Algorithms by Papadimitrou, Dasgupta, Vazirani. You can grab a pdf at [Papadimitrou's website][1].

[1]: http://www.cs.berkeley.edu/~vazirani/algorithms.html