Explore >> Select a destination
|
You are here 
|
memalign.github.io | ||
| | | | |
mbuffett.com
|
|
| | | | | Just some quick thoughts on Gatsby and Next.js, after trying both for a project I worked on recently (this one). I've been a Next.js user for about a year, and for this project I tried to use Gatsby, with limited success. Hot-reloading Hot-reloading started out pretty shaky for me when I first tried Next.js about a year ago. But since 9.4 it's been spot-on. Gatsby hot-reloading mostly worked well, although if there was an error, the page wouldn't reload after fixing the code. Since errors happen all the time in development, it got pretty annoying to have to manually refresh after fixing every error. | |
| | | | |
davidbieber.com
|
|
| | | | | Spaced repetition is great for individual learners, but can we apply it to the preservation of institutional knowledge? What would that look like? Maybe it means dedicating some fraction of some employee time to revisiting old documentation and bringing it up to date. Maybe it involves periodic runthroughs of playbooks to ensure they're still working. Is there a reason to want the exponential backoff property of individual spaced repetition when applying it to institutions? | |
| | | | |
blog.jethro.dev
|
|
| | | | | ||
| | | | |
bdadam.com
|
|
| | | Boilerplate code for generating static websites with node.js, GruntJS and Assembe. | ||
