Gregory's ServerAll tech people should be forced to test their fancy new software on 5-year-old hardware with a rural internet connection.
 13 comments
@c0debabe It would really teach them to get rid of all the needless bloat and inefficiencies.  @XanIndigo It's not hard to simulate either. Create a virtual machine with lower settings, including a throttled network connection. @c0debabe The fact that it’s that easy just makes it more frustrating that they don’t  @c0debabe @XanIndigo throttling isn't everything though. Is it easy to simulate massive packet loss? @c0debabe @XanIndigo 'cause we're often on a phone network that's throttled to 15 KB/s (seriously.), but equally often on a network that uses really shitty wifi as the upstream connection – the place we're living doesn't let us have wired ethernet. @XanIndigo back when I had autonomy over my process I used to set the throttle in chrome dev tools to 2G just to see how whatever new feature I cooked up would behave. This saved me from *SO* many bugs.  @XanIndigo Which is why I only supply my users with 2017 MacBooks and 3G hotspots. Expectation management! ;)  |
@XanIndigo I've been saying this for years