There’s that Carmack quote about anything the compiler will accept will make it into the codebase.
I think there’s a parallel where anything the SQL tables will insert will make it into the domain logic. It smells like Database Fixer routines to clear out “bad”, “dead” or “orphaned” rows, de-duplicate jobs that run nightly, &c. It’s a huge back door for inconsistencies to sneak in. The code should prevent such things, but bugs happen and rows end up getting inserted.
I think it’s more scary to not know SQL than it is to let a framework “handle it” for you.
There’s that Carmack quote about anything the compiler will accept will make it into the codebase.
I think there’s a parallel where anything the SQL tables will insert will make it into the domain logic. It smells like Database Fixer routines to clear out “bad”, “dead” or “orphaned” rows, de-duplicate jobs that run nightly, &c. It’s a huge back door for inconsistencies to sneak in. The code should prevent such things, but bugs happen and rows end up getting inserted.
I think it’s more scary to not know SQL than it is to let a framework “handle it” for you.
Nice to see F# get a little shout out.