Sam Karu

we’re hiring a growth intern at Logical (YC F25). shoot, edit, design, run experiments, manage creator campaigns, and ship under our accounts from week one. no 12 person marketing team to hide behind. $40–60/hr, leading to full time. bonus if you can work with us in SF. if this sounds cool, DM or apply below. hiring fast. ycombinator.com/companies/lo…

there hasn't been a single reason to think about building a website in php in like a decade. and now there's not even a reason to think about starting to think about building one.

cursor is cooked. it was good while it lasted.

in the age of claude, i'm way more impressed by the eng who spends an afternoon optimizing a feature than the one who's always itching to build something new

you know this is BS when swift is above javascript and python

great, but this graphic is irresponsible at best. the long standing norm in ML research is to give the highlight to the best performer in a row. everyone knows this. say what you want about @ylecun but he would've never allowed this.

nytimes absolutely cooked here

i've probably run 50+ interviews across Nvidia and Logical. here's why i think a unfamiliar codebase is good, 60 mins is bad and how leetcode can still work. - anything a human could do with AI in 60 mins, AI can do better alone. at Logical, we measure something called HAV (human-added value) aka the "meat proxy avoidance metric". even after 24 hour take-homes, we realized HAV was difficult to measure and you're basically operating in a noise band. - leetcode can still work, but only if you can get the candidate onsite. online is too easy to cheat these days. what we do - give a reasonably mature codebase. cold start, 7 days. you pick what to build. improvements, bug fixes, new features are all fair game. my experience - bug fixes tests grit. everyone likes adding new features these days, but the difference between vibe software and real software is robustness, speed, security. you have to do the unglamorous work. - improvements and new features test creativity. some smart people are too afraid to push the envelope. unfamiliar codebases show how people get up to speed. in a startup you can't spend weeks reading the codebase like a book. you learn by doing and breaking. you have to adapt to a system. tools, ci/cd, protocol. work trials are the only reliable indicator left.

this is like rating a movie by download speed. tokens/sec was never about model quality. it's a model arch and inference metric.

dragging screenshots of a timeline into figma is always painful. please add a reverse order toggle @figma

crazy that codex desktop was only released last february. that is borderline google holding back Bard levels of fumble from openai.

Gemini 4 Krypton was right there

the chatgpt grokbot is unironically gonna be called "chatbot" or something

if the model is that good why can't you ask it to build a sandbox good enough to contain itself?

just send the bill

communication is such a big part of what separates a great engineer from an okay one. especially now - not just the team, but your agents benefit from good communication as well.

google seems willing to die on the "we trained everything on TPUs" hill. the consumer doesn't care whether you trained on a toaster oven or wrote the weights by hand.