This is an old unpublished post. Published now.
Bounds are important. Unbounded or only partially bounded resources and operations pose a risk to latency and availability of your service.
- Bound resource usage (e.g. limit thread pool size)
- Bound queries (e.g. put a where condition limiting the date range, don’t make it open on one side or worse both sides; if it makes sense use the”limit” features in queries)
- Bound time spent waiting on a dependency
On a similar vein, ensure you validate user input against limits before working on them or passing them on to dependencies.
Originally published at https://www.floatingpoint.ca on May 13, 2018.
This is an old unpublished post. Published now.
Good design can make a product look and feel amazing. As a developer who likes to build web apps, this is a skill I value and want to get better at.
I do a lot of information hunting and reading to get better at design. I am just going to curate that information in this post.
- The first most amazing “Design for Developers” video I saw: Design for Developers: Making your Frontend Suck Less
- Today I found this and this seems similar plus a few new things: Design for Developers
- Here is one from Google I/O 2012: Advanced Design for Engineers
Originally published at https://www.floatingpoint.ca on May 13, 2018.
