---
title: "Comment by Dayul Lee on \"Stop Letting AI Write Your Database Migrations\" | Hashnode"
description: "This hit close to home! I’ve been migrating parts of my project to Go lately, and your post is a huge reality check. It’s easy to forget that AI produces valid"
url: "https://hashnode.com/posts/stop-letting-ai-write-your-database-migrations/69fb6cab50ecad45334d12e6/comment/69fde91ff239332df4c8f323"
---

[Discussion](https://hashnode.com/posts/stop-letting-ai-write-your-database-migrations/69fb6cab50ecad45334d12e6)

Comment [Stop Letting AI Write Your Database Migrations](https://hashnode.com/posts/stop-letting-ai-write-your-database-migrations/69fb6cab50ecad45334d12e6)

[Dayul Lee](https://hashnode.com/@dayul)

[May 8](https://hashnode.com/posts/stop-letting-ai-write-your-database-migrations/69fb6cab50ecad45334d12e6/comment/69fde91ff239332df4c8f323)

This hit close to home! I’ve been migrating parts of my project to Go lately, and your post is a huge reality check. It’s easy to forget that AI produces valid SQL but ignores production scale and lag—I’m definitely going back to double-check my migration files now lol.

[Syed Ahmer Shah](https://hashnode.com/@syedahmershah)

[May 8](https://hashnode.com/posts/stop-letting-ai-write-your-database-migrations/69fb6cab50ecad45334d12e6/comment/69fde91ff239332df4c8f323#reply-69fdeb58f239332df4ca4506)

Strategy happens at the keyboard. Scalability isn't a prompt; it's an engineering choice.