Hmm... I mean, these all seem like mistakes I could make and I don't think I'm the "worst kind of coder". The currency one I learned a while back, but it's not

Hmm... I mean, these all seem like mistakes I could make and I don't think I'm the "worst kind of coder". The currency one I learned a while back, but it's not like I intuited using integers by default. Value being a reserved keyword, I'm not sure I'd know that and I do Postgres work as part of my myriad duties at the startup I work at. Maybe I'd make that mistake in a migration, maybe I have already. In a way, is it much different then what we do now as engineers? I'm hard pressed to call it much of an engineering discipline considering most teams I work on barely do design reviews before they launch in to writing code, documentation and meeting minutes are generally an afterthought, and the code review process while decent isn't perfect either and often times relies on arcane knowledge derived over months and years of wrangling with particular <framework, project, technology>. It's pretty neat, presumably it'll learn as people correct it, and it'll get better over time. I mean it's not even version one. I get the concerns, but I think they're a bit overblown, and this'll be really useful for people who want to learn how to code. Sure they'll run into some bugs, but, I mean, they were going to do that anyways.