Web Weekly: Vol. 12 min read
Here’s some interesting articles I found on the web this week.
I think the title is pretty self explanatory. Takeaways:
- Avoid leaving “dead” code lying around
- Remember to test upper and lower bounds of inputs.
- Use realistic data when performance testing your code. If they had used the expected rocket speeds, they would have seen the integer overflow error during testing.
- Verify your assumptions with your end user. Who authorized the “sequence of code should run for an extra 40 seconds after the scheduled liftoff”?
A simple reminder to “leave the camp ground cleaner than you found it”. Also, don’t let people trip over the same stone you tripped over.
Definitely going to use this as a reference the next time I need frontend design. Some of my favorite suggestions:
- Use near-black and near-white instead of pure black and white
- Use high contrast for important elements
- Everything should be aligned with something else
- Measurements should be mathematically related
- Use a line length around 70 characters
- “Our philosophy to scaling is simple, avoid premature optimization”
- “The user interface can be replaced by Google Forms. The database can be replaced by Google Sheets.”
- Focus more on the product/idea fit
- Save effort and money, until necessary
- This could work for several months (24 months for Levels.fyi)
High level explanation about CDNs role in website performance improvements. I love the “simple words” the author uses to explain the concept. Summary:
- CDN is a set of servers located geographically close to the users for accelerating the delivery of content.
- Browsers or Mobile Apps request static data from the CDN instead of the Origin server.
- The CDNs fetch the data from the Origin servers and cache it. The subsequent requests are served from the CDN server.
- CDNs improve performance, reduce bandwidth consumption, and improve availability of websites.
Warning: very nerdy read after the first few paragraphs.
- Sometimes you just have to build from scratch
- System Design is an underrated skill (back of the envelop math, hardware knowledge, data structures, etc.)
The opinions expressed here are my own and do not reflect any individual or organization from my past or present.