Oleg Gaidarenko retweeted
Anthropic onboarding day: Michael Scott introducing Karpathy like he just signed Wemby in free agency.
Oleg Gaidarenko retweeted
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.
Always was confounded by the desire to update dependencies as soon as they released.
All those auto PRs by dependabots and such feel so nightmarish.
Debian people had a right direction in mind. Albeit radical, but right one
Oleg Gaidarenko retweeted
“If your $500K engineer isn’t burning at least $250K in tokens, something is wrong.”
Oleg Gaidarenko retweeted
Any software performance metric not actively monitored will inevitably regress over time.
Oleg Gaidarenko retweeted
We're talking about pre-commit hooks?
Nice. I hate them.
You should take as much compute time off your engineers as possible and put it on CI.
Oleg Gaidarenko retweeted
If there’s one thing I know about marketing to fellow engineers it’s that you cannot lie, it’s better to be overly humble otherwise someone will always call you on your bullshit. Which is a good thing.
Oleg Gaidarenko retweeted
Replying to @meaning_enjoyer
In practice it depends a lot on the details of what you're running.
Minimal computer:
- Relays (signal-driven switches) are arranged in patterns to make logic gates.
- Logic gates are arranged to create instructions.
- Switches on the outside take/show the input/output state.
Oleg Gaidarenko retweeted
Apple protected older batteries from getting more damaged over time by reducing the rate the CPU clocks up. They shouldn’t be fined at all.
It was literally an attempt to preserve older phones.
Wild that @Apple intentionally software throttled older phones and only has to pay 92 bucks a person. Should be a way bigger fine imo.
9to5mac.com/2024/01/06/iphon…
Oleg Gaidarenko retweeted
Glass frogs are named after the transparent skin that makes their internal organs visible.
Oleg Gaidarenko retweeted
the modern web experience is pretty weird isn't it
reddit has somehow become one of the most reliable places for finding actual humans with thoughts, as opposed to SEO optimized articles written purely to appear first on google but contains, not much, beyond chatGPT corpospeak
Oleg Gaidarenko retweeted
A school of juvenile striped eel catfish huddle closely together as protection from predators as they take turns feeding on the ocean floor.
📽: Abyss Dive Center Bali
Oleg Gaidarenko retweeted
Can anyone tell me why the public WiFi with an attacker in it is unsafe?
I can read all the targets traffic metadata but I can’t read their traffic.
Anybody? The ASD say it’s not safe but I’m not really sure why…..
If you can show me an attack that will do something let me know I’ll run it here now!
Oleg Gaidarenko retweeted
i loved my time at openai. it was transformative for me personally, and hopefully the world a little bit. most of all i loved working with such talented people.
will have more to say about what’s next later.
🫡
Oleg Gaidarenko retweeted
What are some examples of idiosyncratic computer usage?
- Use the browser URL bar to turn rich text into plain text.
- Open Photo Booth to check the webcam before joining a call instead of built-in functionality.
























