80% of getting software engineers to work right* is environmental.
20% is education (15% co-creation patterns 5% techniques)
(*I’m my context of enterprise software development this is XP and TBD)
80% of getting software engineers to work right* is environmental.
20% is education (15% co-creation patterns 5% techniques)
(*I’m my context of enterprise software development this is XP and TBD)
He makes done really interesting points about the nature of work especially dividing it in to blue and red work (analysis vs execution).
It seems to align closely with your work (both past and present)
He makes done really interesting points about the nature of work especially dividing it in to blue and red work (analysis vs execution).
It seems to align closely with your work (both past and present)
Too often stories turn out to be wrong in subtle ways which make them hard to close. If the emphasis is on learning is clearer
Too often stories turn out to be wrong in subtle ways which make them hard to close. If the emphasis is on learning is clearer
Low tests coverage is always bad but high tests coverage is not always good.
What other one way correlations have you encountered?
Low tests coverage is always bad but high tests coverage is not always good.
What other one way correlations have you encountered?
assert_<some_point>_is_expressed_in_<some>_way
So that I could apply TDD
Could I get my AI to do this somehow?
assert_<some_point>_is_expressed_in_<some>_way
So that I could apply TDD
Could I get my AI to do this somehow?
More designing, more experimentation, less bug hunting and much better tests!
More designing, more experimentation, less bug hunting and much better tests!
Turns out that I had completely forgotten how some (most?) engineers work… everything everywhere all at once
Turns out that I had completely forgotten how some (most?) engineers work… everything everywhere all at once
Lesson 1: work in smaller steps
Lesson 1: work in smaller steps
How do you deal with this?
How do you deal with this?