3 ms·
I used to be an academic; so I can appreciate the hard work that goes into writing software to support research is. A key problem is with this claim: "The pro
by jillesvangurp 6y ago
I used to be an academic; so I can appreciate the hard work that goes into writing software to support research is.
A key problem is with this claim:
"The programmers with the WhyLine were 4 times more successful than those without, and worked twice as fast."
That tells me the whole story. We have a researcher who developed a tool, then did some controlled study (involving students?), wrote a paper, and then moved on to the next project. Nothing wrong with that, from a research point of view but you should moderate your expectations. These tools are prototypes and effectively abanware. There is no community of users behind them. There is no community of developers behind them. That was never the intention. It's not even clear if they were ever supposed to do more than help argue some point made in a paper. These were never intended as proper tools but merely as prototypes for tools. Call it an MVP of a tool. There was nobody to take it from MVP to reality so the thing predictably went nowhere.
From an MVP to something that a developer would use is a whole journey. Mik Kersten, who is called out in the article, did exactly that. I remember his name from when I was still an academic, 20 years ago when he was involved with things like AspectJ, which was a research project that made the successful transition to the real world. He was part of a development team associated with a research group that did some awesome work. AOP survives to this day as a key part of e.g. hibernate and Spring. That's no accident. Mik and others worked on these and other projects for years with active support and a community of users. There were a few similar projects out there without this dedicated effort and they've slided into obscurity. E.g. IBM's subject oriented programming comes to mind.
This kind of effort ever happened with the tools in this article. It takes more than releasing some tool and then expecting user adoption. No offense, but academics tend to be not so great developers. It's a reason I left the academic world because I had more than a little impostors syndrome telling others how to develop software (my field was software engineering) when I knew I did not have a lot of bona-fide software engineering credentials because I did not engineer a whole lot of software. I've since fixed that problem.