4 ms·
His argument seems to be that it's a "myth" because you could do the same thing by explicitly listing out the columns. Which in no way makes the former a myth,
by corresation 13y ago
His argument seems to be that it's a "myth" because you could do the same thing by explicitly listing out the columns. Which in no way makes the former a myth, and it is just pure clickbait, as you said.
It gets much worse than just single table grab-alls, though. I once worked at a shop where they insisted upon prolifically using "select just about everything from every relational table, comprehensively joined to the n-th level" views as some sort of confused notion about code reuse, such that everything would then select from these master views. The end result was that it was incredibly frustrating trying to resolve performance problems, because literally everything was a performance problem. It was one of those instances where I shook my fists at every naive developer railing about purported premature optimizations.
- rhizome 13y agoThe more you implement techniques like master objects, the sooner you get to play with sharding! Mortgage-driven development: http://codemanship.co.uk/parlezuml/blog/?postid=147 http://codemanship.co.uk/parlezuml/blog/?postid=147
- mercurial 13y ago"Don't go out of your way to optimize prematurely" does not mean "architect your software in the opposite direction to industry common sense". "We will optimize later if needed" does not work at architecture level. That's why you prototype before committing yourself.
- corresation 13y ago"Don't go out of your way to optimize prematurely" does not mean It doesn't mean anything, because both optimize and premature are in the opinion of the viewer. There is no consensus on this at all, but it has been my experience that when those famous words are uttered, badness is about to occur.