3 ms·

I just don't think you're correct. I think that idea is why we have companies on their third rewrites and most codebases look like sphagetti with performance is

by Grimm1 6y ago

I just don't think you're correct. I think that idea is why we have companies on their third rewrites and most codebases look like sphagetti with performance issues abound. I think many domains are much more demanding but the people working on them don't know any better to avoid the pitfalls.

MuffinFlavored 6y ago
In my experience, he/she is correct. I do a lot of "plumbing". Take data from one source (database, API, vendor), massage it (map/filter/reduce/tweak/translate), send it back to client. Lots of frontend work is using the same paradigm (human input triggers events that interact with components to manipulate state and make network requests) over and over for different screens.
- PaulDavisThe1st 6y ago
  In the 80s it was called "application development" and it was the vast majority of jobs in the software industry. Database, forms software, user data entry, data presentation. The web has just replaced the technological components, but the basic model is more or less identical (and arguably still hasn't reached the same level of sophistication that the forms software of, say, 1988 had (though this is certainly arguable)).