How not to structure database-backed web apps: performance bugs in the wild

Re:How not to structure database-backed web apps: performanc... by bodas on Thursday June 28, 2018 @05:37AM (#17415385)

That's a good thing, I think. Programmers should have a good understanding of general algorithms but it's up to the frameworks themselves to reduce the need to be "mastered". I don't want to spend time mastering a particular framework because that knowledge is not portable across languages.

[ Parent | on HN ]

Re:How not to structure database-backed web apps: performanc... by Nokinside on Thursday June 28, 2018 @06:09AM (#17415541)

I suspect it's good thing also. It may also be the only way to scale programming into larger groups.

You can differentiate the workforce. Programming by copy pasting example code withing frameworks may allow skipping the requirement to understand general algorithms.

Less required expertise means less pay and cheaper products. You hire 10 low-paid easily replaceable code monkeys who slap together pieces of software from ready components. It's like like assembly work. Then you hire one guy who knows things to supervise them and solve the problems when they can't figure them out. It's like blue collar assembly workers and engineers.

[ Parent | on HN ]

Re:How not to structure database-backed web apps: performanc... by cleong on Thursday June 28, 2018 @11:45AM (#17417855)

I think part of this is the industry and part of it is the technology. Entire languages in the web are basically meant to be glue. Embedded usually has different requirements from Web, memory and performance are real problems you run into fast if you don't know what your doing. Where in web, memory and performance are a problem of economics, everyone is being served from a cluster that can be scaled if the software is shoddy.

[ Parent | on HN ]