4 ms·
The problem with this is that most systems designers think "end to end" means the data flow through a system from input to consumption and they're done. A huge
by balabaster 6y ago
The problem with this is that most systems designers think "end to end" means the data flow through a system from input to consumption and they're done. A huge majority of them fail to consider things like building, testing, deployment, environment configuration, scalability, maintenance, monitoring, disaster recovery, geo-replication, prevention of workflow bottlenecks and the n-thousand tiny pieces of the puzzle that go into ensuring systems function adequately and don't pertain specifically to the data they're trying to capture and utilize.
- asim 6y agoUnfortunately I think this is a limitation of experience. I personally started by racking servers, doing desktop support and similar before moving on to system administration, programming etc. Having the ground up understanding especially when you're supporting sales people for an end user product gives you great insights into the entire pipeline and flow of the system. Experiencing similar things at the juggernaut that as Google its hard not to end up with this sort of end to end understanding. I'm not sure how you give it to people in practice without actually making them do the work and go through all these stages or to at least be part of that process. On a more personal level, I have always enjoyed building things from nothing whether it be bikes, PCs, systems. So it might also just be a personality thing, where deconstruction and building for an end user experience matters.