3 ms·

I suggest every developer write a database from scratch at least once, and use it for something real. Or, even better, let somebody else use it for something re

I suggest every developer write a database from scratch at least once, and use it for something real. Or, even better, let somebody else use it for something real. Then you will know "why database".

goerch 5mo ago
Hm, sometimes opening a book could do wonders? But these were the old times...
yubblegum 5mo ago
It's indeed an amazing design and implementation space to explore. If distributed it is nearly comprehensive in scope. (However, did lol @ your "every developer" - that's being super kind and generous or "developer" is doing heavy lifting here.)
traderj0e 5mo ago
My first time was with a Bukkit plugin as a kid. One of my updates broke existing flat json files. Someone asked me if it has MySQL support, I didn't know what that was, then realized oh this is nice. There are also things besides databases that I'll DIY and then still wonder why so many people use a premade tool for it, like log4j
subhobroto 5mo ago
I'll do one better. I suggest every developer learn how to replicate, backup and restore the very database they are excited about, from scratch at least once. I propose this will teach them what takes to build a production ready system and gain some appreciation for other ways of managing state.
- gf000 5mo ago
  If the app is not running, then `cp sqlite.db sqlite.db.BK`
  - subhobroto 5mo ago
    The if is doing a lot of heavy lifing there but with that out of the way you do make a strong case about "local first" apps. Nothing beats the simplicity of a simple `cp` but there are other tradeoffs to be made there. That's why I was encouraging people to make backups and restores of their DB because personally, it has made me appreciate why different designs exist and when to use them vs just slapping a DB connection to an RDS instance and calling it a day.

3 ms·

I suggest every developer write a database from scratch at least once, and use it for something real. Or, even better, let somebody else use it for something re

by jrecursive 5mo ago

I suggest every developer write a database from scratch at least once, and use it for something real. Or, even better, let somebody else use it for something real. Then you will know "why database".

goerch 5mo ago
Hm, sometimes opening a book could do wonders? But these were the old times...
yubblegum 5mo ago
It's indeed an amazing design and implementation space to explore. If distributed it is nearly comprehensive in scope. (However, did lol @ your "every developer" - that's being super kind and generous or "developer" is doing heavy lifting here.)
traderj0e 5mo ago
My first time was with a Bukkit plugin as a kid. One of my updates broke existing flat json files. Someone asked me if it has MySQL support, I didn't know what that was, then realized oh this is nice. There are also things besides databases that I'll DIY and then still wonder why so many people use a premade tool for it, like log4j
subhobroto 5mo ago
I'll do one better. I suggest every developer learn how to replicate, backup and restore the very database they are excited about, from scratch at least once. I propose this will teach them what takes to build a production ready system and gain some appreciation for other ways of managing state.
- gf000 5mo ago
  If the app is not running, then `cp sqlite.db sqlite.db.BK`
  - subhobroto 5mo ago
    The if is doing a lot of heavy lifing there but with that out of the way you do make a strong case about "local first" apps. Nothing beats the simplicity of a simple `cp` but there are other tradeoffs to be made there. That's why I was encouraging people to make backups and restores of their DB because personally, it has made me appreciate why different designs exist and when to use them vs just slapping a DB connection to an RDS instance and calling it a day.