HNHacker News
TopNewBestAskShowJobs

possiblemat

188 karma · joined April 30, 2007

10 My life as a programmer began with GWBasic.

After an unfortunate journey taking me through the restricted lands of Pacal, Delphi, VB, Java, C++, C#, I finally discovered Ruby and Ruby on Rails. Going from not knowing Ruby to knowing Ruby was for me a revelation of roughly the same order of magnitude as discovering programming. I discovered Git at about the same time I started working with Ruby professionally, and had the same kind of revelation about source control. Needless to say, both tools are now the underpinnings of most of the things I undertake programmatically.

I can be observed in the wild, sometimes going under the name of webmat. I ramble about software development (web and mobile), life as a developer and open source tools at programblings.com. I am the author of git_remote_branch, a free and open source tool that helps mere mortals like me trivially manipulate git branches published in shared repositories.

submissionscomments
possiblemat··on Plotly: The Web's first scientific graphing app
Well done guys. For good insights on how you could approach some UX challenges in a tool like Plotly, I highly recommend watching Bret Victor's "Drawing Dynamic Visualizations".

For the non-Plotly folks reading this, Bret's presentation is also very effective at blowing your mind in general.

http://vimeo.com/66085662

possiblemat··on Security Announcement for Devise (Rails authentication solution)
Just like with any technology stack.
possiblemat··on Core competencies of great hackers
What other things do you do regularly? Write emails, specs, contracts, documentation?

Of course you probably also do other stuff than typing on a keyboard. It's just that the keyboard often is the most efficient interface between you and your main tool, your computer.

I think typing speed is a good competency to improve to be more efficient in the next few decades.

possiblemat··on Wearing Out My Delete Key
What James is referring to is not necessarily stripping out big pieces of code when they've been working in production for a while. Rather the point is that in a given coding sprint, he gets the first thing that works going, then starts from there and rewrites them better if need be. So it's just an approach to developing a given method or class rather than refactoring for the heck of it.