Discussion about this post

User's avatar
Kevin's avatar

As someone who has been working on academic projects as a software engineer, one aspect that will be hard to replicate is that as a founder and VC, Nat already had the respect of many software engineers, and thus he could make this a high status thing to work on. A great way for a smart programmer early in their career to get some success and reputation.

Most academic projects, if you do some brilliant software engineering to achieve some research goal, no other software engineers will be able to evaluate your work, and few will pay any attention. And the pay is typically bad. So it’s just really hard to recruit smart software engineers to work on these academic projects.

I’m not sure what to advocate as a solution

Expand full comment
John D Buhrmann's avatar

I love this "distributed model" of problem solving! So you get all kinds of individuals interested in outcomes, and much more creativity is invested over the course of the project rather than with a traditional NIH project model. Just this "distributed model" plus the creative leadership that determined they needed to resource full-time coders to effectively get the job done was not lost on me. This is the very pinnacle of innovation that should be emulated by NIH grant recipients et al.

Expand full comment
2 more comments...

No posts