Meta-Development: Difference between revisions
Jump to navigation
Jump to search
Adamcolton (talk | contribs) No edit summary |
Adamcolton (talk | contribs) No edit summary |
||
| Line 6: | Line 6: | ||
== Case Studies == | == Case Studies == | ||
* Hard to find bugs | * Hard to find bugs | ||
Take some larger open source code bases and come up with either a bug fix or add a feature as an exercise and watch how developers go about doing it. Look for what documentation they use, what tooling they use. And most importantly what bugs they introduce. | |||
== Selected Projects == | == Selected Projects == | ||
Latest revision as of 14:44, 11 May 2020
Users
- Find the bug
- Predict the output
- Programming exercise
Case Studies
- Hard to find bugs
Take some larger open source code bases and come up with either a bug fix or add a feature as an exercise and watch how developers go about doing it. Look for what documentation they use, what tooling they use. And most importantly what bugs they introduce.
Selected Projects
- Runtime analysis
- Test/Benchmark
Use static analysis to look for repeated patterns both at the language and bytecode level.
Recorded Pairing
I enjoy pair programming. Once there's a small group of developers, hell even just one other, I should start doing regular pairing sessions and recording them. This would create a record of how the code developed.