chaotic queer tech witch 
considering tearing away a layer of abstraction in some code i'm working on - this is good, right?
Prikaži ovu nit
context: currently funneling all database interactions through a nice interface/implementation but i feel like it railroads me into reusing general purpose queries rather than write smaller ones limited in scope and functionality
-
-
thinking about just... yeeting that class entirely, making a few reusable helper functions but otherwise just doing raw sql/Dapper at the call site. downside means DB stuff isn't centralised but it means more stuff is kept together where it's relevant, so idk
Prikaži ovu nit -
would also let me do batch queries and stuff without having to add a huge pile of hyper-specific functions the interface. might help perf a lot, too. tried googling around for other opinions but seems like most of the web is stuck on "you're not google, perf doesn't matter lol"
Prikaži ovu nit -
except i'm at a point where i'm trying to push as much as possible out of my shitty $10/month VPS handling 50+ queries a second so yes i think performance does actually matter in my case. and also wasteful programming is bad in any case
Prikaži ovu nit -
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.