joshuamoyers

unrelated to this, but this company randomly reached out disclosing a vulnerability to us (test environment, synthetic tenant). on the one hand, thank you, it’s patched. on the other - we do not have a bug bounty program and this is not welcome. having agent swarms randomly breaking in to environments and then marketing their services in the disclosure is not an ideal sales tactic, in addition to being illegal.

so ironic to see “load bearing” in a comment about removing AI. certain phrases have been ruined by fable/opus 5 for all time.

i think 1 billion DAU is the exception here, so I would not expect everyone to constantly caveat personally.

YMMV but I think its going to always be important to acquire almost all the knowledge necessary to go to the metal, then allow the tactical to bits to atrophy over time. What remains is all the bones of the first principles understanding - and that will serve you well indefinitely.

An analog for you: I started in software pre-cloud, with a primary focus on web technologies, but at various times learned c/c++/asm/compilers/operating systems/algorithms. I audited many classes, but one instructive one was a course called nand2tetris (going from nand gates to hardware simulated CPU to peripherals to operating system to programming languages and compilers to application layer). Understanding the global through lines in computer science give you immense power.

Does my work as a CTO mean I use this information all the time? Absolutely not. Did I benefit from figuring out how computers work generally throughout literally my entire career? Absolutely yes.

I am actually relatively AI-pilled compared to the average Hacker News reader, but I am against outsourcing fundamental understanding to AI in all forms. Does that mean I write code by hand often anymore? Very infrequently.

I think it'd be very hard to achieve viable tokens/s or get arithmetic intensity to be high enough in general, since many cases in existing training and inference are memory bandwidth limited. Definitely seems possible to conceptually have a slow pipeline that is distributed though.

it seems to be something that’s similar to the class of optimizations associated with with linear or state space attention when things models often do is once they figure out an optimization like this they create a ratio between full resolution blocks and blocks that have the optimization implemented.

I think the primary reason it works is because the difference between K and Q, which is not all that obvious is that it’s allowing the model to have an asymmetric relationship between tokens, so one token can attend to another without the reverse being true. It seems to me if you just have a single value that you’re representing symmetric relationship, which might degrade the quality of reasoning over a set of tokens, but also is probably possible.

article points out a real problem - simplicity is one of the hardest things to achieve. the act of reduction is important.

buts its a refreshing that there is an initial list of half baked projects, i suppose meant to evoke horror at the untidiness and wasted time. but honestly each of those projects sound cool as hell. not necessarily durable - but who cares. i’d argue there is a skill, one that is different than traditional programming, that the author was building up over that period.

discipline is important. focus is hard. but allowing yourself to play is not a bad thing at all and i dont think building little interesting side projects should be a shameful act.

we’ve been struggling with review throughput. this actually seems worthwhile to build at this point though i remain fairly skeptical of workflows that are agent-only, at a point it seems like the only practical solution.

we are finding lots of value in self review. its the “imagine you are doing a synchronous paired review with someone - anything that is difficult to explain, has a code smell, doesnt fit the architecture of the system around you, write a comment.” then at the end, agents do a good job of looping over PR comments.

the second thing would be a guided, educational code review tool - there are a few attempts at this, but nothing that has a good enough interface to actually stick. organize hunks by semantic importance, spend some tokens exploring the surrounding systems, showing how new code, public apis and data model flow with the existing design, and allow a human to traverse larger PRs more quickly.

thank you to cloudflare for publishing this.

> But for me, it becomes the event my whole day starts to revolve around. I have to break out of my flow, put my tasks on hold, take the call, and then get back into context. In the end, a 10-minute call can cost me several hours of focus.

Occasionally I get this feeling for a large customer meeting or a public talk, because there are consequences and serious prep. But this is just trying to normalize extreme social anxiety and call it a management style.

One reason you get together to talk is so you can hash out details on potentially ambiguous topics, so you don't head in the wrong direction causing net negative contribution.

Another is that people are not automata. Humans require inspiration and motivation and you need to reinforce the vision of what you are building and why. Its also even sometimes a reasonable idea to ask about how their life is going and check up on their family and pets and career aspirations.

In general, some people should not be managers, and there is plenty of room in the world for super ICs.

except agentic engineering mostly invalidates this with regard to marketing websites. nothing is really all that hard to implement on mostly static site.

i appreciate the sentiment to a certain extent - its not going away, skate to where the puck is if you care to do so. but the writing is repetitive and theres an entire repeated paragraph (bullet to paragraph form). there are also lots of things to be worried about even for the most seasoned individuals in terms of half decade increments conservatively. assuming large parts of swe become commoditized in the form of paying a handful of frontier model providers more and more of the share of what was once swe wages, the high end is what survives. high context fox-like (a la terrence tao's foxes and hedgehogs) are guiding ai to build - and then they are eventually displaced as well. extreme societal pain seems like its on the horizon assuming we dont have some incredibly unlikely massive mobilization towards post-work post-scarcity thinking with active social safety nets. economic diffusion probably means this is a little further away than we think, but time moves pretty damn fast.

i love how half the comments are literally doubling down and simultaneously angrily complaining about auto-scroll. hacker news has become worse than mid 2000s irc.

you cringe while simultaneously posting a github link with your “current setup” - do you see the irony?

I think this is the right take. I usually am aligned with most of what Anthropic is doing, but cutting off OAuth login from open harnesses was a bad move. My guess is there is some serious worry/overlap with the Cursor's of the world - e.g. folks who will be competitors in the future who are taking advantage of cheaper Opus rates/loss leader from them while simultaneously building a competitive model (Composer).

Also, nice clever optimization here. Lots of low hanging fruit in harness land.