Jakob Miksch4d ago
Jason Gorman

If there was a "Manifesto for Empirical Software Development", what might it advocate?

- Data over anecdotes?
- Experiments over debates?
- Skepticism over social proof?
- Hypotheses over opinions?
- Weight of evidence over follower counts?
- Efficacy over "That's how we've always done it"?

Apr 5 at 3:20amWeb
Show threadRyanParsley4d ago
@jasongorman data over anecdotes speaks to me more than the others. I feel people don't _get_ the difference between a hypothesis and hunch. Social proof sounds like evidence if you don't have the right context.
Show threadkit 🌬️🌦️4d ago
@jasongorman I often try to meet “best practices” with “best for whom, in what context?”
Show threadStephan Svoboda3d ago
@wlonk @jasongorman i use sensible default instead which sounds more like that it is a good choice but not the one and only dogmatic choice
(I think i read that term in a Martin fowler blogpost)
Show threadMatt Boehm4d ago

@jasongorman
Skepticism over social proof (or ad copy).

Actual definitions over common (mis)understandings.

Know why over knowing how.

Improving knowledge over adhering to dogma.

Actual progress over the appearance of progress.

Show threadJason Gorman4d ago
@bigolewannabe Testable definitions 🙂
Show threadmmirwaldt4d ago
+1 pragmatism over dogmatism
Show threadJason Gorman4d ago
@mmirwaldt Except that in software development "pragmatism" is often secret code for not doing something at all