1,348 karma · joined February 4, 2015
My mom worked at a gas station convenience story in an rough part of Atlanta (Bankhead) in the late 1970s/early 80s. Alcohol sales in Georgia used to be prohibited on Sundays, so the most addicted alcoholics would come into her store and buy pretty much anything that had any type of alcohol in it. She said every Sunday that they would almost always sell out of mouthwash, cough syrup, rubbing alcohol, vanilla extract, nail polish remover, and even windshield wiper fluid.
There supposedly was an agreement that Amazon wouldn't start provisioning them for a certain amount of time, but whatever amount of time was specified, they either didn't honor it, or it wasn't enough time.
We were also moving assets over to AWS, and all of these things going on simultaneously caused what we called the three-pocalypse.
We would occasionally run across issues with external sites or newly provisioned lambdas who were on Amazon's new 3.0.0.0/8 block, but we couldn't reach them because internally that IP address didn't exist.
At the same time, they would open up a small block to allow access to those external sites, and then some internal service would no longer respond. Repeat ad nauseam. It was also compounded by the fact that there are countless teams in GE and not everyone would connect with who made what changes.
I'm not 100% sure about the ATM though, I've never tried to use it, plus the interest rate for a cash advance is nuts.
This is your entire hand, and it's stored off-site and owned by a company who at any point in time can change their mind about that data and sell it to whoever will pay for it.
I recently bought a small USB-C hub that allowed you to connect to it with your own cable, and it has an HDMI port. I also decided to buy a longer, but cheaper USB-C cable to connect it to my machine, thinking it would work. Well the HDMI port wouldn't work at all. Everything else was fine. I actually ordered a replacement because I thought the hub was defective.
Come to find out, it will only work with USB-C cables with e-marker that allows a higher data rate. This info wasn't clearly stated anywhere, it was only listed deep in a support post. So that was a fun discovery...
When I read this, I think the sample size (n=110) is too small for all the various claims they're correlating out of it. Yes, It's a large enough sample size for statistical significance, but I think there are too many variations involved to make any definitive conclusions. Specifically with the concomitant treatments.
They also did not collect their own control data, but pulled SOC data from elsewhere. I don't think that's bad, but their control group was only 12 patients, and they even state in the paper that it's not large enough for sufficient results.
I do think the results are encouraging from my armchair analysis, and I think it would be good to see the data from a larger study (and a far larger control group), but I think it's far too early to make any real conclusions from this.
Anyways, I'll preface this by saying: while a member of my former team handled acquisitions and divestitures, I've never participated in one.
Most due diligence processes I've heard or discussed never remotely focus on the functionality of the technology. Even the guy on our team doing the auditing couldn't tell us what the company/product did until it was publicly announced. The process focused on data and compliance like verifying revenue, profits, patents assigned, tax records, SOX audits, data access logs, are these transactions valid, are there weird or flagged wire transfers, do all engineers involved have a wavier signed writing over all IP, does everyone have a non-disclosure signed, etc.
I could see how "does this product actually work" getting overlooked in the process, because their supporting and underlying data is probably valid.
However, I'll again mention that I have never actually done an acquisition audit (just worked close to someone who did), so maybe someone else can chime in and tell me about some process I just don't know about.
This is the talk I attended:
Sucks because they actually had some very impressive engineering going on at the time, and I really wanted to absorb some knowledge from those guys, but unfortunately it didn't work out. YikYak shutdown less than a year after my interview.
One of my absolute favorite memories growing up was when we did a camping trip during a field day. A field day is basically an annual global contest to see who you can contact and how far you can reach out. We setup a massive portable antenna in the woods, and I stayed up ALL NIGHT on one of our more powerful SSB radios reaching out to people all across the world. Like Ukraine, Denmark, Ireland, Australia, and more (I'm in the US). Young me was so fascinated with talking with those people, that I'm pretty certain it was one of the first times I experienced sonder.
SDR is fun, but no where near as rewarding as using analog.
The only blocker I've run across so far is that I can't compile Flutter apps for iOS unless I downgrade Flutter. Since I mostly use it to learn and not really leverage, it's not really an issue yet.
I was planning on upgrading to a new MBP next month, but now I'll just wait and see what the ARM machines look like before pulling the trigger on anything.
I believe their intention is that once you download an asset (e.g. song/video/movie), it's a tangible, portable copy that's yours to do freely as you will regardless of device.
You wouldn't be able to play music downloaded via Apple Music directly on just any generic music player (like a car stereo or a CD player) due to DRM and other various restrictions, so I don't believe that this would be exempt from that condition.
Granted it's rather far-fetched, but I thought that it could be a possibility.
They've had SO many issues with it. It has randomly died mid-performance, the tempo click has completely gone off the rails mid-performance, and the loops got transposed once into a completely different key mid-performance.
I use a 2012 MBP stuck on High Sierra. It has occasional issues when I record, but nowhere near the amount of issues that we experience at the church. I want to upgrade badly, but I really don't want to deal with those kind of issues.
Want to write a environment variable that lasts the lifetime of the current shell session? No way to do it.