But this is the minimal bundle size!!!
Its 2010. A customer emphatically criticizes that our webapp doesn't work at all for him on his new iPhone.
No, not because the CSS is off, or the design isn't sized well enough for his fingers. These factors we had already addressed. The app just works slow. At least for them, when they need it most.
Quickly, we identify the problem. cellular networks have lower bandwidth and larger performance deltas. The data the app requires to display a page must go down! Dramatically!
Long story short, after an engineering cycle we manage to cut our page dependencies by 80%. We proudly exclaim the problem solved and ship to customers. Only to get the exact same feedback
It still doesn't load when I need it the most!
What happened? I'm sure you already have a couple of ideas on your mind. And you would be right. Things that happened
Doesn't really matter. The fact is that we ended up in one. A local minimum. Thankfully it only took us one iteration to find out about it. In past years I unfortunately had the opportunity to work with organizations that didn't catch it early on. Allowed it to grow roots, corporate engineering principles and even its own managers.
I think it is important to act on such intel once it becomes apparent and things like these do happen. Just ensure you have an environment where everybody can admit to it and move on and ideally, try not to get caught up in one. In engineering circles creating solutions is the easy thing. Identifying what it really is you need fixed is much harder. So, stay vigilant! And maybe try to ingrain this process into your organization instead of championing it alone.
Hi, I am Kiriakos. I am a software engineering practitioner with a career that started somewehere in the past millenium. I like thinking and discussing about engineering and the organizations that engineering happens in. If you like that too or if you think "Hey this guy could help me improve my software engineering origanization" then feel free to reach out!
