3 ms·
Sorry if that comes off as looking down on people, it is not meant that way, but I'm honestly a bit baffled how I meet many people to this day that still discov
by smoe 6y ago
Sorry if that comes off as looking down on people, it is not meant that way, but I'm honestly a bit baffled how I meet many people to this day that still discover schema migration tools as something new/special instead of just learning it as one of the basic tools of a developer.
I haven't written schema migrations by hand on a regular basis in like 12+ years, the very start of my career, so they were probably not even new back then. Am I just living in a bubble where those tools, while certainly not perfect, are heavily relied upon, whereas others prefer to do it (semi-)manually to have full control? How is the state of these tools in different stacks / environments?
- earthboundkid 6y agoI started working with Django professionally in 2013. At that time, migrations weren’t built in to Django, but there was a widely used plugin (South), which was subsequently integrated into Django core. I can’t really imagine managing a professional web app without a migration tool. Sound like a complete nightmare.
- chousuke 6y agoPerhaps it's just that in some cases, the tool is overkill? In one case, I wrote a super simple shell script to track applied migrations to a database that had until then been managed entirely manually; I didn't feel like it was worth the trouble to try and learn something more complicated just for that use case, since it took me about 15 minutes to write a script that worked well enough: it applied the migration scripts transactionally (transactional DDL rules), in order and did so idempotently. Granted, I'm not a software developer by trade; just a sysadmin who occasionally uses programming to solve problems. I imagine if I had to deal with actual software development I'd end up learning one of those tools eventually.