902 karma · joined October 31, 2008
email: hackernews dut pistos aet purepistos dut net
open source: http://github.com/Pistos
> I've lost a friend, and it's been techcrunched.
I'm Canadian born and raised, with English as my first language. Honestly, I'm surprised to be told I'm that far below the median and average.
Interface issue (in Opera): There's no key to just submit the thought. None of these work: Enter; Shift-Enter; Alt-Enter; Ctrl-Enter. As a workaround, though, I see that you can use Tab, Enter. [edit] I just set up the thoughtback submission box as a custom search engine in Opera. So now I can enter thoughts from the address bar (and press Enter at the end).
I realize that it would just make things like Twitter, but I was interested to see other people's thoughts, and found no interface for that. Perhaps you could experiment with letting people tag some thoughts #public or such, or have a checkbox under the submission field.
https://www.google.com/intl/en-GB/+/learnmore/notifyme.html
which is a 404. I had to manually delete "-GB" to get a 200.
Generally, I reserve the "make sure it works" step for just before _pushing_ (i.e. making public), rather than just before committing.
I always use either `git commit -av` or `git add -p`, so I can preview what I'm about to do. I never use the freewheeling `git commit -m`.
stat = status
stta = status
satt = status
tat = status
co = checkout
fo = fetch origin
ff = merge --ff-only
ffo = merge --ff-only @{u}
po = push origin HEAD1) Sorting the string representations sorts in time order.
2) It eliminates ambiguity almost completely, because extremely few places use YYYY-DD-MM. The ambiguity of most ##/##/## dates is irritating.
* markdown (code blocks, anyone?)
* editing or deletion of comments
* grouping stories
* replying to comments by email
[Edit: list formatting]
Prospective candidates must:
* have code samples demonstrating adequate skill and knowledge in: Ruby, PHP, HTML, CSS, jQuery, SQL
* be very familiar with using: the shell (Linux/UNIX), SSH, git, MVC
* be able and willing to put in a minimum of 2 hours of billable work per week
* be able to touch base with me at least twice a week
Ideal candidates would:
* have experience with many of: Ramaze, AJAX, PostgreSQL, MySQL, an ORM, Google APIs, Pivotal Tracker
* be able and willing to put in 5+ hours a week
* be able to touch base with me at least once every 48 hours via IRC
The project involves a mix of technologies because we're transitioning from legacy code (PHP).
If you are interested, email me at [hnhiring.pistos aet purepistos.net] Code samples will be accepted in either tarball or URL form.
Thanks.
He produced code of quality on par with the rest of the team, and I never thought of him as having a final-product throughput less than the rest of us [who could type faster].
It's true that you can't hunt and peck and be even just a mediocre pianist, but performing music necessitates keeping tempo -- you must actuate your instrument at the right time, and poor mechanical skill on your part has direct and significant impact on the quality of the music. There is no such analogous requirement in coding, other than perhaps deadlines -- but that is obviously on an entirely different scale (no pun intended).
http://dev.opera.com/articles/view/getting-started-with-oper...
((57 395 520 000 000 (miles per year)) * (21 years)) / (35 000 miles per hour) = 3 928 593.15 years