3 ms·
I’ve always felt it strange that in almost every job I’ve had databases have been one of the most important pieces of the architecture but the least debated. I’
by chickenpotpie 6y ago
I’ve always felt it strange that in almost every job I’ve had databases have been one of the most important pieces of the architecture but the least debated. I’ve spent hours debating languages and frameworks, but databases always come down to whatever we have a license for/what others at the company are using. Engineering teams will always say they make sure to use the right tool for the job, but no one ever talks about if it’s right to keep using the same database for a new product.
- mywittyname 6y agoMy experience is places with DBAs tend to keep very tight control over database design than those who do without. I've worked at several places where developers did not touch the database schema. They couldn't even propose changes, instead, you'd give the DBA team the requirements and they would give you a solution.
- xiaodai 6y agobike-shedding at work. Everyone "understands" language but not too many DB systems.
- np_tedious 6y agoFor all their faults / gotchas / overhype, I found the NoSQL wave of 5-10 years ago made these conversions a bit more common.
- mbrodersen 6y ago> Engineering teams will always say they make sure to use the right tool for the job Yep they sure say that. While opening a tool box with very few tools in it. Sometimes only one.