martiell

6 ms·

1.
The science behind data visualisation(netmagazine.com)
2 points by martiell 13y ago|0 comments
2.
Setting up a share option scheme: A Hard Lesson(blog.salientpoint.co.uk)
1 points by martiell 14y ago|0 comments
3.
HeadsUp Agile is now open source(headsupdev.com)
1 points by martiell 14y ago|0 comments
4.
Using zombies to teach kids geography(boingboing.net)
1 points by martiell 14y ago|0 comments
5.
by martiell 14y ago
That'd be awesome. :) If tig started "git rebase" (with or without -i) and then helped me through fixing any conflicts (merge tool?), that'd be awesome. I sometimes forget where I am during a rebase, so showing how many more commits to go w
6.
by martiell 14y ago
My favourite things about Tig: * It's fast. * It's there in the terminal, right where you're using git. * Hence, easy to use over ssh :) * Familiar keyboard shortcuts (press 'h' for help). * Combined log/diff view, where each sc
7.
by martiell 14y ago
The reason for lack of tests I see most often is that cost of set up (before writing any tests) can be high. This is especially true for inexperienced developers, and people using new technology stacks. Setting up unit tests is (in my exper
8.
Will Stephenson: What does Kubuntu really represent?(blogs.kde.org)
1 points by martiell 15y ago|0 comments
9.
Great Software Engineers(blog.kissmetrics.com)
1 points by martiell 15y ago|0 comments
10.
by martiell 15y ago
I don't see any mention on how to build outside the IDE (say, on a CI server). Are there Ant tasks? Maven/Tycho integration? These things are important. Where're the docs?
11.
"The cabin crew will point out your nearest exit now…"(blog.salientpoint.co.uk)
2 points by martiell 15y ago|0 comments
12.
Did PlayStation Network hackers plan supercomputer botnet?(theregister.co.uk)
1 points by martiell 15y ago|0 comments
13.
Goodbye SVN, Hello Git(sonatype.com)
1 points by martiell 15y ago|0 comments
14.
DI in Scala: Cake Pattern pros & cons(warski.org)
6 points by martiell 15y ago|0 comments
15.
by martiell 15y ago
A lot of the discussion seems to assume that a given developer has a constant level of productivity and hence, can be salaried according to that level. I'd say a developer's productivity can vary according to motivation; who they're working