larsen

7 ms·

1.
by larsen 13y ago
Interviews about books, in the spirit of usesthis.com. I'm publishing a new interview every week (you can follow @bookflocks on Twitter for announces). There's still much work to do: . RSS feed . A page collecting all the books me
2.
Show HN: BookFlocks(bookflocks.com)
2 points by larsen 13y ago|1 comments
3.
by larsen 13y ago
You are confusing cause and consequence (nice pictures, tho')
4.
Tom Christiansen’s Materials for OSCON 2011(training.perl.com)
2 points by larsen 15y ago|0 comments
5.
by larsen 15y ago
One of my university professors some years ago said the source of Rogue was one of the C program he read. I've never been able to find it, and I am curious since then. Does anyone?
6.
Tapper - Automated Test Infrastructure(h-online.com)
1 points by larsen 15y ago|0 comments
7.
by larsen 16y ago
At $previous_job we were using RT to manage the spec -> dev -> QA -> deploy cycle. For each new task a new ticket is required. Project managers and team leaders split this ticket into smaller sub-activities (new tickets children
8.
by larsen 16y ago
I use git at work and for personal stuff. The learning path is maybe a bit steep if you come from things like Subversion, on the other hand I instructed a developer new to VCSs and so far he didn't complain, shoot his foot, or shoot mine :)
9.
by larsen 16y ago
Version control. You can observe the benefits even working alone on relatively small projects. And it's one of the pillars to experiment with more reliable ways of deploying software