And started their career as a sysadmin. I don't know Dana at all, but some of the best kernel and networking people I've met got their start as sysadmins.
HN user
bbgm
VP at AWS. Run the Kiro org. Lapsed scientist (theoretical chemistry and bioinformatics). I dabble in synthesizers and photography.
http://deepaksingh.net
email: deesingh [AT] amazon DAWT com (for AWS related stuff) or deepak [AT] deepaksingh DAWT net (for everything else)
twitter: @mndoci
Somewhat unrelated, but the number of times I have invoked Ableton as a metaphor of challenging the status quo is quite high. I was a Cubase user before Ableton showed up and completely upended the DAW world. And they've kept going.
This is just what I've been looking for. I never warmed to Max for Live for mods. But the extensions SDK I can get behind.
Saw him play many times across multiple genres across 3+ decades from straight up classical to world music to electronica/tablatronics. Unfortunately never got to see him perform with John McLaughlin. He must have been 68 the last time I saw him live but still as good as ever. RIP!
Kris and I got to know each other a bit over the years. I still remember our first meeting vividly. We met for dinner at a Mexican restaurant in Capitol Hill and spent the evening talking containers, Linux, Kubernetes, and Open Source. This is a tough loss. I will take small in the fact that it happened doing the thing she loved.
I've had a Tesla (Model S) since early 2020 and once the initial allure wore offI've missed driving a BMW and once the i5 is here I'll be backing to driving BMW. The supercharger network is by far the reason I've stuck with the Tesla this long, but there's enough options now. The build quality, the drive quality, service quality, all of it is subpar. The Model 3 is a zippy car but the lack of an instrument cluster is a deal breaker for me.
Tesla deserve all the credit for getting everyone else to wake up. But they are so so at making a car I actually want to drive.
I used to use a phone as my backup camera when I was out doing bird photography. After a while I gave up. In variable light and high dynamic range conditions phones just don’t hold up (they do a better job with video). If you’re taking snapshots, nothing better than a phone.
I sold all my DSLRs over the past 18 months and jumped into the deep end. The lens systems are better, the cameras are better. I love having a histogram in the viewfinder. There's very little reason and battery life has never been an issue (it is for video but that's a different story).
I have a 9 year old who’s learning all about synths via a combination of the synths in garage band and my OP1. Great combo IMO
I’ve been a long time Spotify user but the difference in quality is very perceptible (to me at least) and I find myself using Apple Music a lot more.
lukehoban says it best in https://news.ycombinator.com/item?id=28711903 where he talks about the three things CloudFormation provides.
The Cloud Control API is an API to the resource model. It unlocks the ability for AWS teams to contribute to the resource model without having to worry about the rest of what Cloudformation does. As a service owner interested in contributing to other systems like TF and Pulumi, now I just have to contribute to one thing. In the medium/long term it's going to be a lot more efficient way to evolve how we all use AWS resources in our favorite Infrastructure-as-code systems.
Disclosure: Work at AWS (but not on the CloudFormation team)
That's not correct. There were Principal and higher engineers 13 years ago when I joined. 5 years ago, just EC2 had a fairly large number.
Amazon has long had a VP-level engineer track (Peter Vosshall was the first IIRC). Colm is very rightly one.
Haven't looked in any detail, but as I clicked around the thing that jumped out at me was how many in the "lower comp, higher returns" category were from healthcare/biotech. Wonder if there is a way to slice and dice by industry/segement?
I suspect that’s what you meant but just for clarity, Instance storage does persist for reboots (which is effectively an OS reboot), but not if you stop/start (or terminate) the instance.
You need to take into account the speed of light in fiber optics and switching latency. For fiber you're looking at about 5 µs/km
This video was shot in 2016 (at EC2s 10 year anniversary): https://www.youtube.com/watch?v=9Gk_I_0eMDA ... almost all of the folks in this video are still there.
That makes sense. Thanks a ton
Firecracker, Bottlerocket :).
On Fargate, you got the answer there.
Always. I just wanted to do it before msw :)
I am from AWS. Could we please change the title to say “Bottlerocket from AWS“. Like Firecracker [1] it’s explicitly not AWS branded.
This just got released. It’s a living source authored by senior engineers at Amazon and covers some of the best practices that we use at Amazon.
That is correct. Three lines, one for each processor type.
That's correct. The same commit allows you to run workloads across EC2 and Fargate (note that the discounting is different).
To be more specific, the first company I worked at had three co-founders; an algorithms person, a functional biology expert, and someone with experience in building software teams. The first two came from academia.
There are two areas where you can jump in more easily with a CS/software background. Many companies are building informatics/analysis pipelines. That’s likely closer to what you know and you can pick up enough biology along the way.
Alternatively there’s a lot of algorithm/classifier development you could jump into.
It’s usually easier going the other way though. Biology is a complex beast.
Like most things, this sounds good in practice but fails in reality. There are many AWS services that started with this question (Spot instances for one). But what people want to do with them is always something else when push comes to shove.
I've always felt there were a lot of background tasks that just need to be done but have no time sensitivity that could fit this model, but in reality it hasn't ever been something you can generalize to a point that it's worth building it out. Still haven't given up on the idea though :).
I am a meat eater. But growing up in India eating meat was rare (it was too expensive) and even in our house, vegetarian food was the norm. Being vegetarian in the US is not that hard, especially in a place like Seattle, but in India, it’s a non-event. Vegan food on the other hand would be hard.
With or without Firecracker the isolation models are similar.
One of the key things to remember about Fargate is the following.
Each Fargate task has its own isolation boundary and does not share the underlying kernel, CPU resources, memory resources, or elastic network interface with another task. (Source: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/...)
The other part is patching. We are (I work at AWS) responsible for patching the underlying hosts. More details at https://docs.aws.amazon.com/AmazonECS/latest/developerguide/...
That’s what most of the people I know do. I have three of my more common modes programmed in, but in the end they’re just starting points. Still a lot of real time tweaking, and sometimes the same shot with changes in the balance of ISO, Aperture, and shutter speed can be super interesting.