sandal

7 ms·

1.
Spotting Hidden Dependencies in Incremental Changes(practicingdeveloper.com)
2 points by sandal 9y ago|0 comments
2.
Balancing competing interests in software projects(oreilly.com)
3 points by sandal 9y ago|0 comments
3.
An efficient approach to continuous documentation(oreilly.com)
3 points by sandal 9y ago|0 comments
4.
The importance of reification in software development(reddit.com)
2 points by sandal 10y ago|0 comments
5.
How to Grow from “Thought Leader” to Actually Leading(medium.com)
3 points by sandal 10y ago|0 comments
6.
Dealing with growing pains without sacrificing sustainability(oreilly.com)
4 points by sandal 10y ago|0 comments
7.
The critical role of systems thinking in software development(oreilly.com)
7 points by sandal 10y ago|1 comments
8.
The traits of a proficient programmer(oreilly.com)
3 points by sandal 10y ago|0 comments
9.
Five tips for exploring new project ideas(medium.com)
1 points by sandal 10y ago|0 comments
10.
by sandal 10y ago
The more meaning you pack into a message, the harder the message is to unpack. So there's this inherent tradeoff between "easy to process" and "expressive" -- and I imagine deciding which side you want to lean towar
11.
Empathy: The key to a successful software project(oreilly.com)
5 points by sandal 10y ago|0 comments
12.
Building a better code review process(oreilly.com)
4 points by sandal 10y ago|0 comments
13.
Overproduction in theory and practice(oreilly.com)
3 points by sandal 10y ago|0 comments
14.
Do you think the Ruby Hero awards should continue to be part of RailsConf?(twitter.com)
1 points by sandal 10y ago|0 comments
15.
Why you need to have strong product ownership(oreilly.com)
3 points by sandal 11y ago|0 comments
16.
Four kinds of people(medium.com)
1 points by sandal 11y ago|0 comments
17.
by sandal 11y ago
This is a followup essay that continues the discussion from "The Sad Graph of Software Death" .. which was discussed here a day ago! https://news.ycombinator.com/item?id=10826916
18.
Beginning to climb out of the software death spiral(tinyletter.com)
4 points by sandal 11y ago|1 comments
19.
by sandal 11y ago
Here's the followup essay, for those interested: http://tinyletter.com/programming-beyond-practices/letters/b...
20.
by sandal 11y ago
This is an accumulation over the 4 month period, not a total issue count on the tracker. So... there were already many issues in the backlog before the measurement window started, and 500 new issues were opened during the period. :-/
21.
by sandal 11y ago
My solution involves cutting that overhead, not adding to it. Most of the proposed fixes are ones I agree with in spirit, but implemented a little bit differently in practice.
22.
by sandal 11y ago
Well, you're pretty close to having written it yourself. :-) The benefit I had in this particular project is that I was an outside consultant with full access to everyone and everything in the organization AND the trust of some of the
23.
by sandal 11y ago
> I would give the same kind of advice that financial advisors give for getting out of credit card debt: "find the card with the highest interest rate, make minimum payments on all other cards, and pay as much as possible on the hig
24.
by sandal 11y ago
Spot on. These were huge issues in the organization I'm describing in this essay.
25.
by sandal 11y ago
You make a lot of good points, and I agree with most of them. The goal of the essay though is not to suggest that tracking issue count is a useful metric. Instead, what I'm suggesting is that if you see lots of stuff going wrong in a p
26.
by sandal 11y ago
The point of the essay is simply this: If you're seeing a massive amount of problems in your organization AND you have what appears to be a badly broken prioritization/triage/issue tracking process, you need to fix your triag
27.
by sandal 11y ago
I agree that's a problem worth fixing. No issue there.
28.
by sandal 11y ago
When I created this graph I was looking at historical data that existed before I got involved with the company, so I don't know the complete story on all of its details... But it's important to note that this is an accumulation
29.
by sandal 11y ago
Well, sure... IF you don't read the essay title, the graph title, the surrounding context, the paragraph directly after the graph, etc. I plan to fix this when I use this graph elsewhere, but I really don't understand this comment
30.
by sandal 11y ago
Keep in mind this is a 500 newly opened issues over a period of four months, and that the backlog did not start at zero. So this is thousands of issues accumulating over a year.

More ›