If you work on a lot of react projects, you’ve probably seen some interesting unit test suites. After all, there’s lots of schools of thought around how to properly test react applications, right? Some folks will
sinon.spy() everything and play with the
require lookup. Others might connect all their components to redux or graphql, and in so doing ensure that they can only test their components in the context of that state management.
Perhaps surprisingly, one of the most challenging things about operating RubyGems.org is the logs. Unlike most Rails applications, RubyGems sees between 4,000 and 25,000 requests per second, all day long, every single day. As you can probably imagine, this creates… a lot of logs. A single day of request logs is usually around 500 gigabytes on disk. We’ve tried some hosted logging products, but at our volume they can typically only offer us a retention measured in hours.
There are a lot of choices about what tools are the best for the job, especially for digital design. Learn about cost, availability, and tactile tradeoffs for digital drawing with Wacom or Apple Pencil.