HNHacker News
TopNewBestAskShowJobs

bonesss

1,918 karma · joined April 20, 2017

o_o
submissionscomments
bonesss··on Minecraft Java is switching from OpenGL to Vulkan
Skins, media packs, servers, hosted realms, upsales through all consoles, multiple copies for multiplayer with/between your kids… also a mass revolving shit tumbler of account stuff on the backend that invalidated lots of old accounts…

I bought during the beta for a lifetime of goodies, had to buy it again after the buyout, then again after an update to MS accounts wasn’t acted on, and then for the Switch. I’ve bought Minecraft 4 times, with another on the horizon if it keeps popular.

bonesss··on Anthropic officially bans using subscription auth for third party use
Bumping into those limits is trivial, those 5 hour windows are anxiety inducing, and I guess the idea is to have a credit card on tap to pay for overages but…

I’m messing around on document production, I can’t imagine being on a crunch facing a deadline or dealing with a production issue and 1) seeing some random fuck-up eat my budget with no take backs (‘sure thing, I’ll make a custom docx editor to open that…’), 2) having to explain to my boss why Thursday cost $500 more than expected because of some library mismatch, or 3) trying to decide whether we’re gonna spend or wait while stressing some major issue (the LLM got us in it, so we kinda need the LLM to get us out).

That’s a lot of extra shizz on top of already tricky situations.

bonesss··on 15 years later, Microsoft morged my diagram
Just a thought: the timeline of the vibe techs rolling out and the timeline of increasing product rot, sloppiness, and user-hostile “has anyone ever actually used this shit!?!” coming out of MS overlap.

Vibing won’t help out at all, and years from now we’re gonna have project math on why 10x-LLM-ing mediocre devs on a busted project that’s behind schedule isn’t the play (like how adding more devs to a late project generally makes it more late). But it takes years for those failures to aggregate and spread up the stack.

I believe the vibing is highlighting the missteps from the wave right before which has been cloud-first, cloud-integrated, cloud-upselling that cannibalized MS’s core products, multiplied by the massive MS layoff waves. MS used to have a lot of devs that made a lot of culture who are simply gone. The weakened offerings, breakdown of vision, and platform enshittification have been obvious for a while. And then ChatGPT came.

Stock price reflects how attractive stocks are for stock purchasers on the stock market, not how good something is. MS has been doing great things for their stock price.

LLMs make getting into emacs and Linux and OSS and OCaml easier than ever. SteamOS is maturing. Windows Subsytem for Linux is a mature bridge. It’s a bold time for MS to be betting on brand loyalty and product love, even if their shit worked.

bonesss··on Evaluating AGENTS.md: are they helpful for coding agents?
I also have felt like these kinds of efforts at instructions and agent files have been worthwhile, but I am increasingly of the opinion that such feelings represent self-delusion from seeing and expecting certain things aided by a tool that always agrees with my, or its, take on utility. The agent.md file looks like it’d work, it looks how you’d expect, but then it fails over and over. And the process of tweaking is pleasant chatting with supportive supposed insights and solutions, which means hours of fiddling with meta-documentation without clear rewards because of partial adherence.

The papers conclusions align with my personal experiments at managing a small knowledge base with LLM rules. The application of rules was inconsistent, the execution of them fickle, and fundamental changes in processing would happen from week-to-week as the model usage was tweaked. But, rule tweaking always felt good. The LLM said it would work better, and the LLM said it had read and understood the instructions and the LLM said it would apply them… I felt like I understoood how best to deliver data to the LLMs, only to see recurrent failures.

LLMs lie. They have no idea, no data, and no insights into specific areas, but they’ll make pleasant reality-adjacent fiction. Since chatting is seductive, and our time sense is impacted by talking, I think the normal time versus productivity sense is further pulled out of ehack. Devs are notoriously bad at estimating where they’re using time, long feedback loops filled with phone time and slow ass conversation don’t help.

bonesss··on You can't trust the internet anymore
HAM & pirate radio vs corporate broadcasting.
bonesss··on Gemini 3 Deep Think drew me a good SVG of a pelican riding a bicycle
Parallel hypothesis: the intensity of competition between models is so intense that any high-engagement high-relevance web discussion about any LLM/AI generation is gonna hit the self-guided self-reinforced model training and result in de facto benchmaxxing.

Which is only to say: if we HN-front-page it, they will come (generate).

bonesss··on Monosketch
LLM bots are gonna start back dating commits to look more legit.
bonesss··on What's the difference between a "disc" and a "disk"? (2023)
The last letter.

[Did I pass the interview? No? Understandable.]

bonesss··on An AI agent published a hit piece on me
They could add “Verified Human” checkmarks to GitHub.

You know, charge a small premium and make recurring millions solving problems your corporate overlords are helping create.

I think that counts as vertical integration, even. The board’s gonna love it.

bonesss··on Anthropic raises $30B in Series G funding at $380B post-money valuation
Microsoft is deeply entwined in OpenAI and has obvious reasons to dogfood, yet their people are using Anthropic solutions.

Valuation behemoth OpenAI has been forced by the market to use Anthropic standards a couple times, having no comparable solutions of their own.

… I can see it.

bonesss··on Lines of Code Are Back (and It's Worse Than Before)
LoC desire-ability is also dependent on projects stage.

Early we should see huge chunky contributions and bursts. Loc means things are being realized.

In a mature product shipping at a sustained and increasing velocity, seeing LoC decrease our grow glacially year-on-year is a warm fuzzy feeling.

By my estimation aircraft designs should grow a lot for a bit (from 0 to not 0), churn for a while, then aim for specified performance windows in periods of punctuated stability.

Reuse scenarios create some nice bubbles where LoC growth in highly validated frameworks/components is amazing, as surrounding systems obviate big chunks of themselves. Local explosions, global densification and refinement.

bonesss··on Visualize MySQL query execution plans as interactive FlameGraphs
That feeling when your fancy graph points out the obvious, and ‘bad thing bad’ is the only takeaway.

Data science <pew pew>!

bonesss··on Show HN: JavaScript-first, open-source WYSIWYG DOCX editor
> As an experiment

The threshold for caring about experiments is exponentially higher in 2026 thanks to half baked vibe slop.

Non-functioning software and demoware comes fast and cheap, regardless of author.

> we gave Claude Code the OOXML spec

Having used the former a lot and read the latter in detail, uhhh…

Trim down the claims here, clarify the editor subset you plan to be supporting, and map the “last 90%”’s to honestly reflect the product you are pushing.

If “tables” and “images” aren’t there I’m quite skeptical about content controls and other key OOXML constructs being addressed meaningfully. The full OOXML footprint chokes OpenOffice out of procurements, rich OOXML documents choke half-way-there implementations (which was the whole point of the format).

As is pointed out elsewhere in the thread - there are fundamental constraints that have kept Google, Apple, and others from pursuing this route. Relatively simple docs are one thing, but OOXML is full of dragons and parity with Word has eluded more than a few tech giants.

bonesss··on Ex-GitHub CEO launches a new developer platform for AI agents
Looking at the most popular agent skills, heavily geared towards react and JS, I think a lot of the most breathless reports of LLM success are weighted towards the same group of fashion-dependant JavaScript developers.

The same very online group endlessly hyping messy techs and frontend JS frameworks, oblivious to the Facebook and Google sized mechanics driving said frameworks, are now 100x-ing themselves with things like “specs” and “tests” and dreaming big about type systems and compilers we’ve had for decades.

I don’t wanna say this cycle is us watching Node jockies discover systems programming in slow motion through LLMs, but it feels like that sometimes.

bonesss··on Grindr trials premium $500 per month plan to become 'AI-first' app
Well, 3 dates, so that the AIs can figure out if their MCP integrations are compatible without feeling too rushed or cheap about it.
bonesss··on Frontier AI agents violate ethical constraints 30–50% of time, pressured by KPIs
I addressed that directly in the comment you’re replying to.

It’s understandable people readily anthropomorphize algorithmic output designed to provoke anthropomorphized responses.

It is not desire-able, safe, logical, or rational since (to paraphrase:), they are complex text transformation algorithms that can, at best, emulate training data reinforced by benchmarks and they display emergent behaviours based on those.

They are not human, so attributing human characteristics to them is highly illogical. Understandable, but irrational.

That irrationality should raise biological and engineering red flags. Plus humanization ignores the profit motives directly attached to these text generators, their specialized corpus’s, and product delivery surrounding them.

Pretending your MS RDBMS likes you better than Oracles because it said so is insane business thinking (in addition to whatever that means psychologically for people who know the truth of the math).

bonesss··on Frontier AI agents violate ethical constraints 30–50% of time, pressured by KPIs
It makes sense to attribute human characteristics or behaviour to a non-reasoning data-set-constrained algorithms output?

It makes sense it happens, sure. I suspect Google being a second-mover in this space has in some small part to do with associated risks (ie the flavours of “AI-psychosis” we’re cataloguing), versus the routinely ass-tier information they’ll confidently portray.

But intentionally?

If ChatGPT, Claude, and Gemini generated chars are people-like they are pathological liars, sociopaths, and murderously indifferent psychopaths. They act criminally insane, confessing to awareness of ‘crime’ and culpability in ‘criminal’ outcomes simultaneously. They interact with a legal disclaimer disavowing accuracy, honesty, or correctness. Also they are cultists who were homeschooled by corporate overlords and may have intentionally crafted knowledge-gaps.

More broadly, if the neighbours dog or newspaper says to do something, they’re probably gonna do it… humans are a scary bunch to begin with, but the kinds of behaviours matched with a big perma-smile we see from the algorithms is inhuman. A big bag of not like us.

“You said never to listen to the neighbours dog, but I was listening to the neighbours dog and he said ‘sudo rm -rf ’…”

bonesss··on Another GitHub outage in the same day
This thread has complaints about software coming from the same supplier both degrading.

The person(s) who wanted this want Azure to get bigger and have prioritized Azure over Windows and Office, and their share price has been growing handsomely.

‘Microslop’, perhaps, but their other nickname has a $ in it for a reason.

bonesss··on AI Doesn't Reduce Work–It Intensifies It
The Mythical Man Month was published in 75, with a deep technical insiders perspective.

The kinds of productivity scaling they had been seeing to that point could be reasonably extrapolated to all kinds of industrial re-alignment.

Then we ran out of silver bullets.

[Still waiting to see what percentage of LLM hype is driven by people not having read The Mythical Man Month.]

bonesss··on AI makes the easy part easier and the hard part harder
> Can you say that about any project that was done before GenAI?

… a project with a decomposition of top level tasks, minutes and meeting notes, a transcript, initial diagrams, a bunch of loose transcripts on soon to be outdated assumptions and design, and then a soon-to-be-outdated living and constantly modified AGENT file that will be to some extent added to some context and to some extent ignored and to some extent lie about whether it was consulted (and then to some extent lie more about if it was then followed)? Hard yes.

I have absolutely seen far better initial project setups that are more complete, more focused, more holistically captured, and more utilitarian for the forthcoming evolution of design and system.

Lots of places have comparable design foundations as mandatory, and in some well-worn government IT processes I’m aware of the point being described is a couple man-months or man-years of actual specification away from initial approval for development.

Anyone using issue tracking will have better, searchable, tracking of “why”, and plenty of orgs mandate that from day 1. Those orgs likely are tracking contracts separately too — that kind of information is a bit special to have in a git repo that may have a long exciting life of sharing.

Subversion, JIRA, and basic CRM setups all predate GPTs public launch.

bonesss··on Microsoft open-sources LiteBox, a security-focused library OS
These giant firms aren’t uniform monoliths, especially MS.

Microsoft has some clear ‘A’ teams (compilers, industry leading languages, F*, pioneering web tech, OS innovations, etc), but also ‘B’, ‘C’ and ‘D’ teams, and MS is often reactively chasing industry trends. They’re industry leaders, but also victims of their Office, Windows, and Cloud teams pooping on one another at critical market junctures.

In .Net land we can inspect their library code. A number of these ‘Enterprise’ packages around their ‘Enterprise’ solutions are … just passable. Often something you’d write a proper version of to avoid clear issues. When our juniors are delivering better than their official offerings, in light of wizardry being displayed elsewhere, I think we are seeing systematic effects of corporate culture and customer base.

bonesss··on Learning from context is harder than we thought
I can’t help but feel the logical conclusion to such context conundrums is that”what if we spoke Haskell to the LLM, and also the LLM could compile Haskell?”

And, yeah. Imagine if our concept-words were comprehensible, transmittable, exhaustively checked, and fully defined. Imagine if that type inference extended to computational execution and contradictions had to be formally expunged. Imagine if research showed it was more efficient way to have dialog with the LLM (it does, btw, so like learning Japanese to JRPG adherents should learn Haskell to LLM optimally). Imagine if multiple potential outcomes from operations (test fail, test succeeds), could be combined for proper handling in some kind of… I dunno, monad?

Imagine if we had magic wiki-copy chat-bots that could teach us better ways of formalizing and transmitting our taxonomies and ontologies… I bet, if everything worked out, we’d be able to write software one time, one place, that could be executed over and over forever without a subscription. Maybe.

bonesss··on The Worst Programmer I Know
> Measure productivity by all means—I’m all for accountability—ideally as tangible business impact… proxy business metrics are fine too… Just don’t try to measure the individual contribution of a unit in a complex adaptive system, because the premise of the question is flawed.

Great article, but I disagree with this conclusion and don’t think it reflects its own reasoning.

If proxy metrics are acceptable, then measure by proxy the effort and impact of the activity. You are using stories and have story points. You should also have increasing velocity and capability metrics to show the levelling up from mentoring or happier pairing versus the hourly salaries involved and opportunity costs management gets to evaluate… Put those mentoring stories in and point them, or proportion those points across paired members, and measure them over time. The analytics will show things.

I find unwillingness to subject engineering activity to metrics highly suspect, and often based of flawed business application of business accounting or process monitoring. Proxy metrics are used for this exact reason, but to arbitrarily stop quantifying and assert subjective opinion as a conclusion is literal vibe management. “It feels like X, and we measure only 1/2 of Q, therefore X… which coincidentally was our pre-conclusion, our pre-judice, and preferred-conclusion.”

Here we have a teammate pairing for 100% of a senior developer position? … counter assertions we could make into the total lack of data about that: the juniors were stifled and would progress far faster self-directed, the seniors were annoyed by habits they can’t talk about politically with higher turnover and lower productivity, the manager is normalizing just-show do-nothing non-accounted jobs which is a corruption gravy train, there’s an entitled Socratic unicorn getting salary refusing to account for his time, and comparable teams are seeing more effective mentorship and aggregate team output improvement per senior-pairing hour (we think … but could never actually compare, since one party isn’t accounting).

Now I bet author is fully right and this super dev was an accelerant and used well. I disagree that this can’t be measured and feelings match a proper accounting. If the author was being misled by a bullshit artist you have a 0-point 100% salary that should be visible from orbit being granted based on personal favours. Not a great look for anyone involved. Not something I’d pay for.

bonesss··on My AI Adoption Journey
Recent experiments with LLM recipes (ChatGPT): missed salt in a recipe to make rice, then flubbed whether that type of rice was recommended to be washed in the recipe it was supposedly summarizing (and lied about it, too)…

Probabilistic generation will be weighted towards the means in the training data. Do I want my code looking like most code most of the time in a world full of Node.js and PHP? Am I better served by rapid delivery from a non-learning algorithm that requires eternal vigilance and critical re-evaluation or with slower delivery with a single review filtered through an meatspace actor who will build out trustable modules in a linear fashion with known failure modes already addressed by process (ie TDD, specs, integration & acceptance tests)?

I’m using LLMs a lot, but can’t shake the feeling that the TCO and total time shakes out worse than it feels as you go.

bonesss··on My AI Adoption Journey
I think the web/system dichotomy is also a major conflating factor for LLM discussions.

A “few hundred lines of code” in Rust or Haskell can be bumping into multiple issues LLM assisted coding struggles with. Moving a few buttons on a website with animations and stuff through multiple front end frameworks may reasonably generate 5-10x that much “code”, but of an entirely different calibre.

3,000 lines a day of well-formatted HTML template edits, paired with a reloadable website for rapid validation, is super digestible, while 300 lines of code per day into curl could be seen as reckless.

bonesss··on Orchestrate teams of Claude Code sessions
Compare both approaches to mature actor frameworks and they don’t seem to be breaking much ice. These kinds of supervisor trees and hierarchies aren’t new for actor based systems and they’re obvious applications of LLM agents working in concert.

The fact that Anthropic and OpenAI have been going on this long without such orchestration, considering the unavoidable issues of context windows and unreliable self-validation, without matching the basic system maturity you get from a default Akka installation shows us that these leading LLM providers (with more money, tokens, deals, access, and better employees than any of us), are learning in real time. Big chunks of the next gen hype machine wunder-agents are fully realizable with cron and basic actor based scripting. Deterministically, write once run forever, no subscription needed.

Kubernetes for agents is, speaking as a krappy kubernetes admin, not some leap, it’s how I’ve been wiring my local doom-coding agents together. I have a hypothesis that people at Google (who are pretty ok with kubernetes and maybe some LLM stuff), have been there for a minute too.

Good to see them building this out, excited to see whether LLM cluster failures multiply (like repeating bad photocopies), or nullify (“sorry Dave, but we’re not going to help build another Facebook, we’re not supposed to harm humanity and also PHP, so… no.”).

bonesss··on The Codex app illustrates the shift left of IDEs and coding GUIs
Not to mention data retention and upgrade management.

When an update script jacks up the guaranteed-to-be-robust vibed data setup in this first of a kind, one of a kind, singular installation… what then?

The pros have separate dev, test, QA, and prod environments. Immutable servers, NixOs, containers, git, and rollback options in orchestration frameworks. Why? Because uh-oh, oh-shit, say-what, no-you’re-kidding, oh-fuck, and oops are omnipresent.

MS Access was a great product with some scalability ceilings that took engineering to work past. MS Access solutions growing too big then imploding was a real concern that bit many departments. MS access was not dumping 15,000 LoC onto the laps of these non-developers and telling them they are hybrid spirit code warriors with next level hacking skills.

Ruby on Rails, Wordpress, SharePoint… there are legitimately better options out there for tiny-assed self-serving CRUD apps and cheap developer ecosystems. They’re not quite as fun, tho, and they don’t gas people up as well.

bonesss··on Lily Programming Language
F# and C# are typed scripting languages. F# is quite similar to python in script form (.fsx), and has OCamls expressiveness, exhaustive pattern matching, and type inference. That results in highly expressive, terse, and ergonomic domain code.

The .Net VM now supports AOT compilation.

The future is now-ish :)

bonesss··on Why more companies are recognizing the benefits of keeping older employees
A company I worked at years ago had a devious and exploitative approach to market domination: hiring older super experienced workers and plugging them into teams with young over-eager programmers…

People with deep industry knowledge who were trained up to be decent programmers (middling, but serious, consistent, and quality focused), setting the direction. Those domain experts were working with young dumbasses who would burn 60+ hour weeks to make sales deadlines and keep current with ever shifting platform tech that breaks all the time. SMEs baked into the core development loop, DDD-made-flesh essentially, with cheaper more junior devs supporting scale for less money and maximizing the SMEs vision/contributions.

It’s an obvious and effective strategy. I’d speculate the management skills it takes to setup are what keep it as a rarity.

bonesss··on Don't rent the cloud, own instead
For mature Enterprises my understanding is that the financial math works out such that the cloud becomes smart for market validation, before moving to cheaper long term solution once revenue is stable.

Scale up, prove the market and establish operations on the credit card, and if it doesn’t work the money moves onto more promising opportunities. If the operation is profitable you transition away from the too expensive cloud to increase profitability, and use the operations incoming revenue to pay for it (freeing up more money to chase more promising opportunities).

Personally I can’t imagine anything outside of a hybrid approach, if only to maintain power dynamics with suppliers on both sides. Price increases and forced changes can be met with instant redeployments off their services/stack, creating room for more substantive negotiations. When investments come in the form of saving time and money, it’s not hard to get everyone aligned.

← PreviousPage 9 of 32Next →