89 karma · joined June 29, 2015
I am reminded of a post a while back regarding AWS' issues affecting multiple data centres (I forget the specifics), and how their post mortem didn't appropriate blame on anyone (which it really easily could have), but rather their own checks and balances, which allowed the issue to arise in the first place. I do hope that when the dust settles we see a measured response rather than a witch hunt.
1. Dependency install was taking too long.
2. Inconsistent builds between devs because of no lock file.
3. Could not search the registry from the command line in a timely manner.
Having just done a quick test on a random project, I'm pleased to see that all of those concerns are now taken care of, plus the install (for this project at least) is ~30% faster than it is with yarn.A few years ago I'd definitely have trawled the App Store and I'm sure I'd have found Transit, but it just goes to show the power of a good, reliable interface and considered rollout to ensure you're always the go-to product if someone is aware of you.
It does. 5+ second load time over 4G before first render and even then it took a few more seconds to fully load...
That's such an eloquent way of highlighting the need for conceptualisation in engineering but also the struggle to convince others (investors perhaps) that you're not a complete nutcase when you think outside the box.
I was so fascinated with the survey results being statistically significant (and therefore thinking the more respondents the better) that I failed to realise that 5 people willing to take the time to respond, and 4 willing to share their emails is such a good starting point to get the ball rolling.
However... the website simply doesn't work. I get the feeling from it I should be able to simply enter my email address and copy the generated code, yet when I do so nothing happens, and unless my access token really is `abc123`, something's not right here!