tablet

37 ms·

391.
A Curious Company(targetprocess.com)
1 points by tablet 15y ago|0 comments
392.
Patterns for Information Visualization: Information tells stories(targetprocess.com)
2 points by tablet 15y ago|0 comments
393.
Ask HN: Will you share company revenue/expenses/profit numbers with employees?
6 points by tablet 15y ago|3 comments
394.
The Future of Agile Software Development(targetprocess.com)
1 points by tablet 15y ago|0 comments
395.
Productive Meetings(targetprocess.com)
1 points by tablet 15y ago|0 comments
396.
10-5: Law of Skills and Success(targetprocess.com)
1 points by tablet 16y ago|0 comments
397.
Visualization: TargetProcess Company Infographic(targetprocess.com)
1 points by tablet 16y ago|0 comments
398.
Learning & Software Development. Multi-skilled Developer(targetprocess.com)
3 points by tablet 16y ago|0 comments
399.
10 Most Common Mistakes in Agile Adoption(targetprocess.com)
5 points by tablet 16y ago|0 comments
400.
Ask HN: Are the any personal benefits in time tracking on your daily work?
2 points by tablet 16y ago|1 comments
401.
by tablet 16y ago
>>Stuff I've tried is mostly about talking, trying different systematic models (time tracking, semi-micro management, constant reporting or leaving them more space, trying to get excited with new technical bits, giving them bonus, c
402.
by tablet 16y ago
I am curious what kind of motivation did you try? Also it is hard to work remotely and many people just can't do that.
403.
by tablet 16y ago
I've asked very similar question. Check comments in it as well Ask HN: Should you fire average devs and have only talented devs in a team? http://news.ycombinator.com/item?id=1634231
404.
Developers who play games better are better in software development as well(targetprocess.com)
4 points by tablet 16y ago|0 comments
405.
by tablet 16y ago
My code was not bad, but not superb. There was good architecture behind and a hundred of unit tests, but still time to market was top priority. So it was good enough and I think it is a waste to write perfect code for startup, since future
406.
by tablet 16y ago
Here are more details. dev 1. very slow, but solid. Need constant guidance to solve problems. However, can dig into boring/weird problems and reliable person. dev 2. distracted by interned and have problems with focus. Knows a little about
407.
by tablet 16y ago
OK, maybe wrong wording, but by average I mean people who will never exceed your expectations and have moderate problem solving skills/or development speed/or technical excellence attitude. I am thinking about tough decision now, and so fa
408.
by tablet 16y ago
why?
409.
Ask HN: Should you fire average devs and have only talented devs in a team?
10 points by tablet 16y ago|11 comments