Company has been rebuilding one of the core features - rendering statistical data in a grid. It had to render lots of different datasets dynamically with 10s of thousands of rows per page.
Frontend team at that time was struggling with the implementation and that's where the suggestion came from.
Reality being that different managers wanted their departments being feature owners and make changes themselves using tools they know. Basically SQL Server and T-SQL became a hammer and every feature or an issue started looking as a nail.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Can you tell me more about the context, like what language, framework, infrastructure, and business objectives led to this kind of thought process?
It was Microsoft stack. SQL Server, .NET.
Company has been rebuilding one of the core features - rendering statistical data in a grid. It had to render lots of different datasets dynamically with 10s of thousands of rows per page.
Frontend team at that time was struggling with the implementation and that's where the suggestion came from.
Reality being that different managers wanted their departments being feature owners and make changes themselves using tools they know. Basically SQL Server and T-SQL became a hammer and every feature or an issue started looking as a nail.