377 karma · joined October 20, 2016
> The economy is more than a fifth smaller than it was at the end of last year. This fall is not as bad as the 22.7% decline in Spain, but about twice the size of contractions in Germany and the US.
I think Germany's handling was exceptional anyway, and for the US it hasn't hit fully yet. I reckon there's a lot more to come in the UK, as well, when the government furlough scheme comes to an end. And not to forget to mention the country is still in the Brexit transition period, which runs out at the end of the year.
I kind of expected it as it was too good to be true, but what annoyed me was that it took them a week to cancel it.
Edit: Better posted above: https://pbs.twimg.com/media/D3y037OW0AQmpAf.jpg
Edit: Just had a look, depending on the implementation, "dynamic power" usage is as low as 12.26 µW/MHz [1]
[1]: https://developer.arm.com/products/processors/cortex-m/corte...
It's just how it is here, sadly - I wish we could change it, and so does my boss.
Nobody is here for the money; we get to work on pretty cool projects with quite a big user base (we're talking millions of users and billions of request per day) - No. 6 Alexa rank for the U.K, and one of 2 non-startups in the Top 20. We have a lot of authority and a relatively relaxed work environment
The job description is pretty much on point - we're a small team of 4 engineers (one of whom is me). We build the API for iPlayer, which is used by the Mobile Apps, TV Apps and the Website.
We're heavily investing into personalisation and experimentation at the moment, working closely across all three platforms and finding the best ways to promote the right content to each user individually at the right time and in the right way. Another focus this year is on Live events, and Music, Sports and News content. There is scope to have a real impact on the product and consulting with architects and product managers.
Our tech stack is mostly Node.js, with several dozen microservices. We manage a couple hundred EC2 instances, dozens of Redis caches and databases, and half a dozen Postgres databases, with code deployed directly to production every day. We have 10% time, as well as days dedicated to personal objectives, and some working from home days.
Full job description: https://careershub.bbc.co.uk/members/modules/job/detail.php?...
And some more background about how we work in two blog posts:
https://iplayer.engineering/how-an-iplayer-api-engineer-deli...
https://iplayer.engineering/the-tech-stack-that-powers-bbc-i...
I wish I could change it, my boss wishes he could change it; it's just the sad and ugly truth.
The job description is pretty much on point - we're a small team of 4 engineers (one of whom is me). We build the API for iPlayer, which is used by the Mobile Apps, TV Apps and the Website.
We're heavily investing into personalisation and experimentation at the moment, working closely across all three platforms and finding the best ways to promote the right content to each user individually at the right time and in the right way. Another focus this year is on Live events, and Music, Sports and News content. There is scope to have a real impact on the product and consulting with architects and product managers.
Our tech stack is mostly Node.js, with several dozen microservices. We manage a couple hundred EC2 instances, dozens of Redis caches and databases, and half a dozen Postgres databases, with code deployed directly to production every day. We have 10% time, as well as days dedicated to personal objectives, and some working from home days.
Full job description: https://careershub.bbc.co.uk/members/modules/job/detail.php?...
And some more background about how we work: https://iplayer.engineering/the-tech-stack-that-powers-bbc-i...
We do have magazines and merchandise for some franchises, but as far as I know, those were secondary when it came to BBC Reith/Reith Sans. TV & Online are big, and especially when it comes to legibility across resolutions and encoding systems (PAL/NTSC/SD/Pixel Ratios/HD/4K/Mobile/High-DPI..)
The processor also periodically scans new log groups under the /aws/lambda/ prefix, and creates subscriptions for them if they don't exist already.
Speaking about, this may be a good candidate for a more in-depth blogpost
Ironically, my sister won that one with my design and won a 30-min flight in a "real" glider. That was probably ten years ago and I'm still sour.
It's open source, and getting widely adopted. It's very niche, but with a big impact - millions of people see graphics rendered by it every day, but only a few dozen use it.
I've used it in my student days at the student TV station - no budget means free is pretty much the only option, and I thought it was incredible that it's just rendering any HTML to make it look so professional - here my own football client from a couple of years ago [1]. And now the BBC does that same.
I could export all my Android (Nougat) messages and media, and restore it onto my iPhone (iOS 11).
It was a bit dodgy though - it asked me to install an old (custom?) APK first to export my messages, and the iPhone restore process looked like an actual iOS system restore..
Also, I'd be interested to find out why this is so massive? We've been waiting a long time for this, and I get that Lambda is complex with lambda@edge and all that, but how much tweaking does AWS do to the node runtime before they can deploy this?
Node 8 has been out for 10 months, and it's been LTS for half a year - or did they simply wait for it to be stable enough to run, or anything specific in 8.10?
I do not remember having had issues with it, but honestly, I don't think I actually have stats on that anymore.
I've just checked in S3, but it doesn't look like we have request or data transfer metrics enabled on the model bucket. I may enable those next week to monitor the effectiveness of our strategy better.
[0]: https://iplayer.engineering/evaluating-tensorflow-models-in-...