AWS just published an absolute banger of a paper at this year’s SOSP on their use of formal methods to validate S3’s new distributed metadata index.
I’m yet to read it, but it builds on their 2021 paper on verifying S3’s Shardstore with formal methods (which I absolutely loved!)
My current product engineering contract is wrapping up at end of December - what I am looking for in my next gig:
I own problems end to end, starting from converging on the PRD with the Product Leaders → aligning on architecture with senior engineers → final code implementation → QA → measuring the impact of the feature / enhancement / bug-fix via jupyter notebooks / analytics-dashboards → designing the next iteration
background:
- 5 years analytics at likes of mu sigma/ axtria/ flipkart →
- 5 years mobile games product management at the likes of EA / gojek →
- 5 years b2b product management at Target →
- product-engineering / Rust OSS last 6 months
I'd prefer to work on deeply technical problems, that is where my intersectional work from product / analytics can add significant value
I am open to dev advocacy / technical content collabs as well, have ~40k followers on twitter mostly in the dev ecosystem
Gotta love how the top 10 list is now ALL io_uring:
https://t.co/uEAqe2vP3N
also a new video as well. My son told me about it :)
https://t.co/xXXg0EMkR7
Competitive athletes also often consume stimulants like caffeine in high doses which can cause arrhythmias and can result in events like this. Not saying this is what happened in this particular case.
Competitive sports are always injurious to health but we can use the principles the athletes use to get results faster and in a safer way.
We should look at training and competition separately.
The coding interview is dead, at least for my team at Anthropic. I've seen enough to know that it no longer provides signal. I removed it from loops this month.
I have a spicy, optimistic take - I think there's an opportunity for junior engineers: https://t.co/PVvpQCbQtK
@amuldotexe You gotta psyop yourself to reduce the mental cost to action via an external source (guru, mentor or curated social media feed in my case).
In my case it was SM + mentors.
If you've ever wondered why smart TVs are so cheap, this is why.
@log4j rooted his Samsung and found an always-on hot mic, automatic content recognition, geolocation, network mapping, ad targeting and user profiling, shared with Samsung's "400 partners".
A lot of it can be blocked in <15 min, wrote a basic guide below.
What your TV is doing
The main culprit is ACR (automatic content recognition). Your TV screenshots what's on screen, fingerprints it, and sends it home to build your ad profile. Samsung does it every 500ms, LG every 10ms [1].
What is insane: it happens on connected devices too.
Plug in your laptop, your console, your work machine, and your TV can fingerprint that via HDMI [1].
He also found that if your Samsung doesn't have a mic, it'll look for one from a connected soundbar or bluetooth device.
https://t.co/vNdTnIQ6KF
It's on by default, and you likely agreed to it on the setup screen you clicked through in 10 seconds.
Step 1: Turn off ACR
Samsung: Terms & Privacy → Viewing Information Services
LG: Live Plus
Vizio: Viewing Data
Roku: "Use info from TV inputs"
Sony/Google TV: Samba Interactive TV
Menus vary by model, but those are the names to look for. While you're in there, opt out of interest-based ads, reset your advertising ID, decline every optional privacy agreement, turn off voice recognition, and delete apps you never open.
Step 2: Give smart devices their own network
Put the TV, cameras, speakers and vacuum on your router's guest/IoT network. The logic is simple: these devices rarely get patched. If one gets compromised (getting drastically more frequent with AI), it shouldn't be able to see your other devices or home network.
Step 3: Block trackers for the whole house with DNS-level filtering
NextDNS (cloud-based) is easy and has a solid free plan. Pi-hole is a little bit more work if you prefer self hosting. For simplicity we'll focus on the former.
1. Sign up at https://t.co/IwhafVWVM8 (free tier is plenty)
2. Privacy tab: add a blocklist (OISD is a good bet) and turn on Native Tracking Protection for Samsung, LG, Roku, Amazon (see attached image)
3. Setup tab: copy your endpoint
4. Paste it into your router's DNS settings as DNS-over-HTTPS/TLS (or use the IPs + "Link IP" if your router only does plain DNS)
5. Bonus: block outbound port 53 except to your router. Some devices hardcode their own DNS to get around you
Then open the NextDNS logs and watch how often your TV phones home. It's eye-opening. If an app or update breaks, find the domain in the logs and allowlist it.
Why they do this
TV prices are down 97% since 2000 [2]. Most of that is better manufacturing and brutal competition. But once margins on the hardware hit zero, the cost moved to you.
In Q3 2024, Vizio lost $6.7M selling TVs and made $115.8M in gross profit from ads and viewing data [3]. They've said on earnings calls that they keep TV prices low to grow the audience they sell to advertisers. Walmart bought them in 2024.
This isn't a conspiracy theory either. Vizio paid $2.2M to the FTC in 2017 for tracking 11 million TVs without consent. Last December, Texas sued Samsung, LG, Sony, Hisense and TCL over ACR. Samsung and LG have since agreed to stop collecting that data without explicit consent [4].
TL;DR
1. ACR off
2. Ads + voice off
3. Smart devices on their own network
4. NextDNS filtering on the router
Sources:
[1] ACR study: https://t.co/S1IS8lXNbA
[2] Cost of US consumer goods: https://t.co/nclXELXcbd
[3] Vizio Q3 2024: https://t.co/CrVbwc9ZXk
[4] Texas v. Samsung: https://t.co/wFOUdeh1if
@uds5501 Looking at the assembly output can get you very far.
He is talking about if the compiler could autovectorize the function. But in his case it didn't, so he hand rolled simd implementation of that function.
Spend two weeks writing down every piece of friction you run into or watch someone else run into. Don't fix anything yet. Just log it.
At the end of the two weeks, look for repeats. Pick the one that happens most often and affects the most people. Estimate, roughly, how much time it costs per month. Being off by half is fine. You only need to know whether it's 2 hours or 200.
Fix that one thing, properly, at the layer where it keeps happening. Then tell people it's fixed, and tell them roughly how much time it gives back. That last step matters more than it should. Invisible work stays invisible unless someone makes it visible, and you're the only one who knows it happened.
Repeat.
@amuldotexe@joy014 This is the trait that all successful problem solvers have. They learn just enough to solve the problem at hand.
I call it JIT learning.