3 ms·
> I don’t disagree with your post, but what is the solution here? If you provide hardware for developers who build software with a direct user interface, don't
by toast0 6y ago
> I don’t disagree with your post, but what is the solution here?
If you provide hardware for developers who build software with a direct user interface, don't get them the best. Getting them the best for build machines, so they don't have to wait around for builds makes sense, but make sure the machines they run interactive tests and personal usage on are not the best.
When your developers have 16gb or more ram with 8 cores and a fast SSD and your users have 4 gb, a dual core 15w cpu, and a spinning disk, it can be hard to understand the sometimes huge difference in experience. And sometimes, it's actually not that much work to make things better for users with low end devices. The difference between high end phones and low end phones can be even more stark.
- seanp2k2 6y agoOn my last team, we would do QA on devices that ranged from “decade old + notoriously buggy implementation” to “new hotness, not even available to consumers yet”. The latest greatest stuff was more useful so the mfgs could understand what wasn’t done right there, but the old stuff is where our SDK team found the most value — if it ran fine there, it was pretty much guaranteed to be awesome everywhere else. Faster devices would just mask things like frame drop / memory leaks, but those good old low-end old devices were great for detecting problems and perf regressions. An anecdote that has long stuck with me from a bicycle mechanic back in the rust belt: ~“Anyone can make new stuff work well, but not many folks still have the patience and expertise to really make the older stuff shine, but it can and it does with a bit of care.” For work, I upgraded from an 8th Gen Intel 6-Core i9 laptop with 32GB@2400mhz and a 1050ti to a 5950x / RTX 3090 / 32GB@3600mhz with tight timings and it’s very noticeably faster for general desktop usage and development.
- rakoo 6y agoFacebook implemented "2G Tuesdays" (https://www.nbcnews.com/tech/social-media/facebooks-2g-tuesdays-slow-down-internet-employees-n452466 https://www.nbcnews.com/tech/social-media/facebooks-2g-tuesd...) where developers would get 2G speeds when doing anything related to the website. That gives them the experience of people with very poor connectivity and probably improve their experience. Just like you said, if it runs OK on 2G, it can only be fast enough on 4G
- deleted 6y ago[deleted]