3 ms·

I've been stuck working on a problem for the last two weeks, I know this by the lingering feeling of dread, and anyone can tell by the empty squares in my commi

by wrnr 7y ago

I've been stuck working on a problem for the last two weeks, I know this by the lingering feeling of dread, and anyone can tell by the empty squares in my commit heat-map. How can metrics help me make progress, except to tell me to try something new: Read papers, study similar solutions, reach out to other that can help. Nothings has worked so far, but it does not deter me. I did learn a curious fact about the productivity of the most prolific writers, musicians, comedians and other creative professions. Count the number of words written, notes composed and new jokes, then divide those by a reasonable number of working hours, let's say 5 days a week with 8 hours of work over the productive period in their life. Unfortunately, I can't find the exact numbers anymore, but it was staggeringly low, something in the vein of 1 word written per hour, 1 note composed per day, and one new joke per week. Sure there are things to be learned from data, just not always what fits the agenda of the managerial class.

darkerside 7y ago
Yeah I'm gonna need a citation on that one Chief
- darkerside 7y ago
  > Unfortunately, I can't find the exact numbers anymore, but it was staggeringly low, something in the vein of 1 word written per hour, 1 note composed per day, and one new joke per week. This is so ridiculous as to be offensive. Bring the downvotes, I don't care.
Retric 7y ago
It’s closer to 1 word per minute than per hour. A 120,000 word novel / 50 weeks / 40 hour weeks / 60 minute hours = 1 word per minute. However that’s in terms of a finished product which typically has a lot removed or edited over time.
deleted 7y ago
[deleted]
Scarblac 7y ago
Write down what you do. Regularly talk to a colleague about your thoughts, it helps to get them clearer. And some things just need weeks of reflection, research, trying things out. Rome wasn't built in a day. When you'll get there you'll have produced something of actual value.
stult 7y ago
I find the best way to deal with long running, difficult problems is to (1) document what you are doing and (2) prototype as fast and often as possible. That way you have a measurable record of a systematic attempt to tackle the problem. If the team metrics don’t capture that, you have an easy argument to make that they should and a practical way to do so (commits to a readme or wiki or prototype branch are measurable). It also helps your teammates and managers identify when you are spinning your wheels and need help. As a tech lead/architect, I find prototypes and documentation about a hard problem extremely helpful for identifying when I’ve made a bad technical decision and selected an approach that simply isn’t efficient or workable. Otherwise, it’s hard to distinguish between that and when the individual dev is simply not up to the job. It’s also much easier to solicit feedback when you’re stuck if you can offer a record of what you have tried.

by wrnr 7y ago

darkerside 7y ago

Yeah I'm gonna need a citation on that one Chief

darkerside 7y ago
> Unfortunately, I can't find the exact numbers anymore, but it was staggeringly low, something in the vein of 1 word written per hour, 1 note composed per day, and one new joke per week. This is so ridiculous as to be offensive. Bring the downvotes, I don't care.

Retric 7y ago

It’s closer to 1 word per minute than per hour. A 120,000 word novel / 50 weeks / 40 hour weeks / 60 minute hours = 1 word per minute. However that’s in terms of a finished product which typically has a lot removed or edited over time.

deleted 7y ago

[deleted]

Scarblac 7y ago

Write down what you do. Regularly talk to a colleague about your thoughts, it helps to get them clearer. And some things just need weeks of reflection, research, trying things out. Rome wasn't built in a day. When you'll get there you'll have produced something of actual value.

stult 7y ago

I find the best way to deal with long running, difficult problems is to (1) document what you are doing and (2) prototype as fast and often as possible. That way you have a measurable record of a systematic attempt to tackle the problem. If the team metrics don’t capture that, you have an easy argument to make that they should and a practical way to do so (commits to a readme or wiki or prototype branch are measurable). It also helps your teammates and managers identify when you are spinning your wheels and need help. As a tech lead/architect, I find prototypes and documentation about a hard problem extremely helpful for identifying when I’ve made a bad technical decision and selected an approach that simply isn’t efficient or workable. Otherwise, it’s hard to distinguish between that and when the individual dev is simply not up to the job. It’s also much easier to solicit feedback when you’re stuck if you can offer a record of what you have tried.