When it comes to designing tools and workflows and generally thinking about how biotech data teams should work, it’s often useful to split up users into two buckets that I call keyboard users and mouse users. Keyboard users are the ones who like to write code. They store data in CSVs, parquet files and databases, and share analysis results through Github links and Jupyter notebooks. Mouse users are the ones who prefer point-and-click tools with graphical user interfaces. They store their data in spreadsheets and BI tools, and share their analysis through slide decks and spreadsheets, sent as email attachments.
Is the keyboard mightier than the mouse?
Is the keyboard mightier than the mouse?
Is the keyboard mightier than the mouse?
When it comes to designing tools and workflows and generally thinking about how biotech data teams should work, it’s often useful to split up users into two buckets that I call keyboard users and mouse users. Keyboard users are the ones who like to write code. They store data in CSVs, parquet files and databases, and share analysis results through Github links and Jupyter notebooks. Mouse users are the ones who prefer point-and-click tools with graphical user interfaces. They store their data in spreadsheets and BI tools, and share their analysis through slide decks and spreadsheets, sent as email attachments.