This is the second in a series of posts about improving page performance. Part 1 discussed what we're measuring and how. A video of me talking about the performance issues discussed in this post. The problem For the job details page, we accept banners supplied by schools which aren't compressed as well they could be. Large images don't block the rendering of the main content, however they hog bandwidth, especially on mobile.
A video of me talking about the performance issues discussed in this post. How are we defining 'page load speed'? How quickly the user can see and interact with core page content after they navigate. Non-core content could be adverts, their user avatar, or recommended links. It's important they appear as quickly as possible but they're not the main reason the user navigated to the page. Where are the biggest gains to be made?
We have recently added a new feature that allows a user to upload a file from our webpage. We implemented this using redux-plupload, ClamAV and S3 to satisfy the following requirements: the file should be uploaded from the client to avoid excessive memory use on the server while streaming files. the upload must be secure and the file must be stored securely (and ideally encrypted at rest). the file should be virus free so that it can be downloaded without worry.
One of the issues of using public GitHub is that, well, it’s public. Even with the layers of security, it’s all your information ‘out there’. Somewhere. However, it is a fact of life that we all use GitHub and many large and small companies choose the hosted GitHub option over hosting an in-house, expensive GitHub Enterprise environment. The problem is that developers and operations folks sometimes push things into GitHub without thinking.
Much has been written about standing desks – from the gushingly positive to the crushingly negative. But following some back pain I’d had at the end of 2015, I thought I’d give it a go. After a little more than a month into the experiment, here’s the story so far. When I joined Tes in November of 2015, I had a normal desk chair setup. The chairs here are good – not as good as the Aero numbers that cosset your nether regions at some companies I’ve worked at - but nice enough.
This is a post about decentralised systems. Bear with me. I was reading this about an Internet primer in FHM magazine, dated 1995. The writer is about the same age as I was when the article was published. The tone of the piece is familiar. Back then, the Internet was seen as a minority interest, like drag racing or macramé. I recall having to tone down my enthusiasm for it in polite company.