HNHacker News
TopNewBestAskShowJobs

richardk

291 karma · joined May 28, 2011

submissionscomments
richardk··on RetroShare: secure communications with friends
0.5.2a Debian GNU/Linux
richardk··on RetroShare: secure communications with friends
Seems nice, but not terribly stable, i.e segfault after giving my connection details
richardk··on Coding Skill and the Decline of Stagnation
It's comforting to see that other people fluctuate between thinking they're awesome and thinking they're awful.

Experience has taught me this:

Never build your self-esteem on comparison with another

And by that I mean, you should never judge your own programming abilities based on other peoples' apparent abilities. If you're programming new stuff regularly, enjoying it and listening to what other programmers have to say, then the chances are you're getting better at it, and that's enough.

richardk··on The Hungry Programmer
This is an interesting analogy, for me, it doesn't map though. I "believe", if you'll let me use that word, in code quality, so my attitude towards code quality is constant. I moved past the urge to knock out quick and crappy solutions as soon as I shifted my enjoyment from "getting a solution" to "getting the best solution I am capable of". That is, simply solving a problem doesn't feel good, I have to solve it as well as I can to get anything out of it.
richardk··on Deconstructing "K&R C"
Myself, I learned from K&R, and I thought it was great at the time, now I'm less sure of this.

I've heard that "A Book on C" is supposed to be a much better book for learning C

richardk··on Why I use vim
Am I the only person who thinks it's absolutely insane how much time people spend learning to use an editor?

Am I really supposed to believe that my time is better spent learning an editor than it is spent getting better at programming?

I honestly feel that learning these editors has more to do with gaining status than it does self-improvement.

Why should I have to spend hours consciously learning an /editor/. It's /just/ an editor, the interface should be good enough that I can just walk in and use it productively from the start.

For the record, I used vim for the first 2 years of my degree, now I use gedit. It certainly lacks some functionality, but it's generally good enough and feels like much less of a burden to carry: I'm free to focus on actual work.

richardk··on Farewell to MIT
I'm was writing a user-space thread library and I found your article "Implementing a Thread Library on Linux", a really nice article by the way, and then found "Farewell to MIT" just through browsing the site.

"Farewell to MIT" just seemed like such great advice, I was surprised when I found it hadn't already been posted here.

richardk··on My 2 hour morning project, route.im
Hmm, I was expecting some new/fun kind of output, for instance some map that approximates the route taken geographically.
richardk··on Life on the Command Line
"... In a typical gui file manager that kind of stuff is just not possible. The possibility space for what you can do is limited by the visual abstractions the original designer came up with for file manipulation. With command line tools that space is virtually infinite."

whilst i certainly agree with this, i would speculate that 80-90% of the average user's time is spent carrying out a handful of simple operations that are better catered for by guis. for the other 10-20% we have our virtually infinite space: the shell.

richardk··on Life on the Command Line
out of curiousity, does MPD/ncmpcpp make use of the shell? if it doesn't then i can't see how it'd be advantageous over a gui music player like rhythmbox
richardk··on Life on the Command Line
"What if this is precisely the problem? My guess is that an environment that don't makes you think also tend to discourage learning. This would be sub-optimal in the long term."

imo, we should be thinking about the task we are working on, not the interface we are using to accomplish our task, so the best interface is the one we don't even notice.

richardk··on Life on the Command Line
gui vs cli, interesting topic.

i used to use the command line for everything but recently switched to using guis.

switched mainly because gui applications seem nicer to me for completing common desktop tasks, for example listening to music, i can just click the rhythmbox applet and select a song as opposed to something like "mplayer ~/Music/some\ artist/some\ album/*" or manipulating files, it seems a lot nicer to me to be able to pull a file onto my desktop than type out (even with tab-complete) "mv foo ~/Desktop". ofcourse, there are exceptions when using a shell is much easier, for instance if i want to copy a large number of files whose filenames have some similar pattern.

it's also very nice to be able to install some new program and just use it, why should i have to read long poorly written man pages?

at the same time i still use a shell everyday, but as a programming/administration tool.

richardk··on Chocolat - the new editor
this looks so nice, i'd really like to see a gnu/linux port :)
richardk··on Isostick Aims to Alleviate Physical Disk Annoyance
presumably useful for older BIOSs that can't boot from USB?

but other than that, yeah... kinda redundant.

richardk··on Poll: Do you visit the 'new' section of Hacker News?
Rarely (only if there's nothing interesting on the main page)
richardk··on A very weird/creepy interactive girl, but great rendering
this should replace xeyes...
richardk··on Plan9 has been forked: 9front
https://code.google.com/p/plan9front/wiki/Mascot

lol

← PreviousPage 2 of 2