3 ms·
I agree with your point of developers being responsible for the performance. But I have a different experience (probably because we work in different areas):
by ratww 7y ago
I agree with your point of developers being responsible for the performance.
But I have a different experience (probably because we work in different areas):
Most the performance problems of the products I ever worked were purely systemic.
They boiled down to technologies and architectures having been chosen for "organizational" rather than technological reasons.
And "organizational" is in quotes because sometimes it was just blackmail: I worked with two developers who quit in protest after the prototype they wrote in Scala was deemed not good enough and dropped for... being too slow, ironically.
- Aeolun 7y agoAh, I can tell you such stories of a stack that evolved solely out of incompetence...
- Davertron 7y agoThis has been a major frustration for me as a UI developer on the current application I work on. The UI is often hamstrung by how the backend API was implemented. There are frequently cases where we stitch together pre-existing API functionality to make something work in a far-from-ideal manner just because it would take longer to do it right and no one is interested.
- ratww 7y agoI've seen a similar thing happen. It all started with good intentions, like only having simple endpoints that do "one and only one thing". In the end the backend was pure and beautiful, but the the frontend devs had to perform joins in the the client and make 21 API calls in a 20-item list and then everything goes to hell.