jakevoytko

6 ms·

1.
by jakevoytko 4d ago
My workhorse is Opus orchestrating Sonnet or Sol orchestrating Luna, depending on which ecosystem I'm using this week. I'm a backend engineer, so for tasks that either interact with the machine learning or client codebases, I have
2.
by jakevoytko 8d ago
For full context, here's the HN thread from the other side of the "Concurrent Work" section: https://news.ycombinator.com/item?id=49605915 Unlike the vanilla read of the OpenAI press release, it is much more
3.
by jakevoytko 8d ago
As someone who also spent a bunch of time benchmarking various techniques, this is as good as you can do without publishing a formal versioned benchmark suite that you want to maintain and run forever at immense cost to yourself. If you act
4.
by jakevoytko 10d ago
This was my instant reaction when I started using a Mac. But 15 years later, even knowing more tricks for interacting with it, it still baffles me. Once you've used Windows Explorer and a few Linux distro navigators, there's no de
5.
by jakevoytko 13d ago
Yeah this is what I pay for Zepbound through LillyDirect. I also eat less food and drink less alcohol than I used to. So the net loss is probably smaller, maybe $200/mo
6.
by jakevoytko 15d ago
As always, friendly reminder to lock your credit and enable your mobile carrier's protections against SIM swapping
7.
by jakevoytko 15d ago
My experience with output styles for long-running sessions is that Claude starts to forget the terse output style by the middle of the context window. Obviously I don't know if 5.1 suffers the same fate but I ran into this issue with b
8.
by jakevoytko 18d ago
This reminds me of my first job, where we did a lot of 3d modeling and mobile robotics research. When we were trying to reproduce motion bugs, a coworker of mine would track down our manager and put him at the controls. More times than not,
9.
by jakevoytko 27d ago
They see the entire universe building their own version of Claude Tag and custom internal bots connected to your internal ecosystem, and realizing that they can fight for some enterprise revenue within their own product that everyone else i
10.
by jakevoytko 28d ago
I worked at Etsy when it expired and the execs got this question a lot. The TL;DR is that the expected outcome is that it massively increases the support burden (wait I didn't mean to click that; wait I actually need to send it to anot
11.
by jakevoytko 1mo ago
Their argument is that the user almost always experiences the moment of interaction with the controls as a single decision with 2 branches, (a) the OS behavior matches my expectations and I won't change it, and (b) the OS behavior viol
12.
by jakevoytko 1mo ago
It's clear that we're not the audience; it writes to be read by its training evaluator, not a professional software engineer. Professional software engineers can't read this word soup and are desperately trying to find ways t
13.
by jakevoytko 2mo ago
I can take notes as fast as people can talk, but I'm much slower at writing so I needed to synthesize it into a condensed idea. It doesn't feel the same, to me at least.
14.
by jakevoytko 2mo ago
If you’re gonna be a hater you at least gotta do it right! The pricing and the securities fraud were two separate things you can count against him.
15.
by jakevoytko 2mo ago
It kept me listening. When I was on minute 70 of a boring lecture I started daydreaming. If I was writing even minimal notes, I'd need to briefly consider each idea and decide whether it was worth recording.
16.
by jakevoytko 2mo ago
It's very simple; If you work 10x faster, you need to release 1/10th the bugs as before for the user's experience to have the same level of bugginess. And we're not incentivized for this; we're still exploring how t
17.
by jakevoytko 2mo ago
This is great stuff; I've been prototyping with a few language-specific parsers like the Golang and the polyglot approach looks really helpful for me
18.
by jakevoytko 2mo ago
At the moment I'd check the sibling comment, which has a few links!
19.
by jakevoytko 2mo ago
My side project is now codebase explainability. I basically don't buy the premise that we just have to give up on comprehension as code generation scales; I just think that text is too limited by itself. So going a step deeper than ask
20.
by jakevoytko 2mo ago
Because for its entire existence, the top HN comment on articles is typically a contrarian take or pointing out flaws. This goes double for a study, where people just hunt for some aspect of the methodology they dislike. If you don't a
21.
by jakevoytko 2mo ago
Out of curiosity, what has changed over time that has made it more toxic? I left Google in 2015. It certainly had its share of toxic traits, but it was at the "what place doesn't?" level.
22.
by jakevoytko 3mo ago
Nah, "Any other vector DB" starts to fall apart once you need stuff like scripted scoring like OP uses. Then it starts to be a question of, "do you need ANN for performance?" since SQLite only does brute-force vector sco
23.
by jakevoytko 3mo ago
I needed to set up a VPS for my blog, so I gave Claude SSH access to a fresh Digital Ocean droplet and told it to set up a deploy with Ansible and harden the instance. It one-shot it in 15 minutes.
24.
by jakevoytko 4mo ago
That is indeed how things like copy/paste through the menus already work; you install an extension to get the clipboard permission or the browser limits you to keyboard shortcuts
25.
by jakevoytko 4mo ago
Applications like Google Docs would be impossible without each of the four things you listed being available. We had Google Docs that didn’t roll-your-own for each of the items in that list and it was called Writely and it was absolute dogs
26.
Why are we getting worse at software engineering?(bitlog.com)
3 points by jakevoytko 4mo ago|0 comments
27.
by jakevoytko 4mo ago
> The decision was made to go with Eclipse. Then it magically went into some sort of internal box/decision process, and came out IntelliJ instead. I've always thought this was because of a sufficiently highly placed Android per
28.
by jakevoytko 4mo ago
Yeah, a lot of people came of age with a "we'll fix it when it's a problem" mindset. Previously their codebases would start to resist feature development, you'd fix the immediate bottlenecks, and then you could kick
29.
by jakevoytko 4mo ago
The proof is in the pudding. At this point, there have been plenty of models that overperformed on benchmarks and underperformed on real work. So my stance is that I'm curious, I'm excited to see where it goes, and I don't be
30.
by jakevoytko 5mo ago
Yeah, this is exactly what I thought when I read this post. It seemed like the author either hasn't worked in big tech, or hasn't worked in the industry very long. It's extremely likely that the engineer who designed this was

More ›