HNHacker News
TopNewBestAskShowJobs

bonesss

1,919 karma · joined April 20, 2017

o_o
submissionscomments
bonesss··on Microsoft's Copilot chatbot is running into problems
Working faster, but at what?

LLM workflow:

Describing to Claude that I need an edit made in the second paragraph of the third section feels easy, comfortable, and straightforward. I’m using my speech centers, speech to text, and then I wait for a generation during which I hit my phone or Reddit. Poof, the text flies out like magic, taking 20+ seconds, then I re-re-re-read it to make sure the edit was good and nothing was lost in that edit. Oops, the edit inverted the logic of the paragraph, lemme repeat the above… and again… time flies! 2 hours gone in a flash.

Old and boring workflow:

I gruellingly move my mouse to open a file, then take a coffee break. I come back and left-click into the sentence that sucks. I hit Reddit to deal with the anxiety… I think, boo, and then type out the edit I needed. It’s bad, I fix. Coffee break. Squiggly red line from a misspelling? I fix. I google and find a better turn of phrase, copy and paste it in manually with a little edit. Ugh. This sucks. I suck, work sucks. Time sucks. 35 entire minutes of my life has been wasted… time to get another coffee and check Reddit.

———

Working with an LLM is kinda like working under stage hypnosis. The moment to moment feelings are deceptive and we humans are unreliable recorders of time-usage. Particularly when engaged in unwanted effort.

Google has had all this tech for a minute. Their restrained application and lack of 10x-vibe-chad talk make me think their output measurements are aligned with my measurements.

1 rabbit hole hallucination wrong-turn can eat up a lot, lot, lot of magic one-shotting.

bonesss··on Microsoft's Copilot chatbot is running into problems
I see Microsoft throwing spaghetti at the wall just in time as “AI” functionality hits government and educational procurement procedures.

The copilot product is obviously borked, and is outshone by ‘free’ competitors (Gemini, ChatGPT). But since the attributes and uses are so fuzzy, they have a minimum viable product to abort meaningful talk about competition while securing big contracts from governments and delivering dog water.

My anecdotal observations of copilot are people using competing products soon after trialling. Reports say Anthropics solution is in widespread use at Microsoft… a bunch of devs on MacBooks and iPhones using Claude to build and sell … not what they themselves use (since they are smart and have taste?).

bonesss··on AI is killing B2B SaaS
I feel the market forces kinda point the other way, though, since the customization of the SaaS is also cheapening, but faster and more targeted than these internal teams. Over time I believe that’ll lead to more, not less, SaaS consolidation.

Let’s put the cost of code production at 0: regulatory compliance with payment processing laws or industry oversight is a recurring job that’s common for the whole industry when it changes. SaaS companies have hundreds of customers to attend, these become first class business functions. New demands won’t be in training data for LLMs, so someone needs to be doing this. SaaS has the funds and customer base to have dedicated experts at these functions, but it’s dead capital and nigh-impossible hiring in a tiny talent pool for the rest of the market… the delta to get Salesforce or SharePoint not to be total ass and fully customized is orders of magnitude smaller than detailing those foundations, and as people who sharecrop on platforms like those know, the devil is always in the details. Those internal teams just aren’t positioned to juggle both sides of that coin, they can’t be experts, mistakes can be existential, and the liability picture is so very ugly… coding is the least of it.

Into this, MBAs are not static. It’s not gonna take more than a few “vibe coding ate our CRM data” high profile snafus, or industry think pieces to map out why customization is faster/better/smarter, to get clear business dogma around this. A witty turn of phrase about focusing on your actual business.

I think ‘no one ever got fired for hiring IBM’ x 5 is on the horizon, and the evil marketers at Salesforce, MS, and the rest are gonna work hard to grow their piece of the pie. They have LLMs too, only with better models and unlimited tokens. And our executives will be checking directly with their LLMs about how to invest (the consultants, journalists, fanboys, and social media bots too…).

bonesss··on When internal hostnames are leaked to the clown
We all use floats down here.
bonesss··on A sane but bull case on Clawdbot / OpenClaw
It’s older than that - lots of my boomer bosses did it to seem cool over email in the late 90s.

I viscerally remember starting my day with my inbox saying “cum c me”… I know what you’re trying to do, bro, but damn.

We are young and old all at the same time.

bonesss··on X offices raided in France as UK opens fresh investigation into Grok
The part of X’s reaction to their own publishing I’m most looking forward to seeing in slow-motion in the courts and press was their attempt at agency laundering by having their LLM generate an apology in first-person.

“Sorry I broke the law. Oops for reals tho.”

bonesss··on Coding assistants are solving the wrong problem
Talking and typing feels far more productive that staring and thinking, and there is a cumulative effect of those breaks to check Reddit while something is generating.

Humans are notoriously bad at estimating time use with different subjective experiences and show excessive weighting of the tail ends of experiences and perceived repetitious tasks. Making something psychologically more comforting and active, particularly if you can activate speech, will distort people’s sense of time meaningfully.

The current hype around LLMs is making me think about misapplied ORMs in medium scale projects... The tool is chosen early to save hours of boring typing and a certain kind of boring maintenance, but deep into the project what do we see? Over and over days are spontaneously being lost to incidental complexity and arbitrary tool constraints. And with the schedule slipping it’s too much work to address the root issue so band-aides get put on band-aides, and we start seeing weeks slip down the drain.

Subjective time accounting and excessive aversion to specific conceptual tasks creates premature optimizations whose effects become omnipresent over time. All the devs in the room agreed they want to avoid some work day 1, but the accounting shows a big time commitment resulting from that immediate desire. Feelings aren’t stopwatches.

[Not hating on ORMs, just misusing tools for weeks to save a couple hours - every day ain’t Saturday - right tool for the job.]

bonesss··on Coding assistants are solving the wrong problem
> AI can write the code, but it doesn't refuse to write the code without first being told why it wouldn't be a better idea to…

LLMs combine two dangerous traits simultaneously: they are non-critical about suboptimal approaches and they assist unquestioningly. In practice that means doing dumb things a lazy human would refuse because they know better, and then following those rabbit holes until they run out of imaginary dirt.

My estimation is that that combination undermines their productivity potential without very structured application. Considering the excess and escalating costs of dealing with issues as they arise further from the developers work station (by factors of approximately 20x, 50x, and 200x+ as you get out through QA and into customer environments (IIRC)), you don’t need many screw ups to make the effort net negative.

bonesss··on xAI joins SpaceX
I think it makes more sense if you invert the manufacturing cycle.

Automated asteroid mining, and asteroid harvesting, are potential areas where we have strong tech, a reasonable pure automation story, and huge financial upsides. Trillion dollar asteroids... If we’re sourcing metals out there, and producing for orbital operations or interplanetary shenanigans, the need for computing and automation up there emerges.

And I imagine for the billionaire investor class now is the window to make those kinds of plays. A whole set of galactic robber barons is gonna be crowned, and orbital automation is critical to deciding who that is.

bonesss··on The Codex App
How come if I download code from GitHub, rename some stuff, and republish it under another license I’m a bad guy, but if I ask ChatGFY to do it for me I’m a 10x Chad? … someone is gonna figure that part out in court. I remember what code SCO used to make hay, and I know what side the MPAA, RIAA, Google, and NVidia Are gonna be on at the end of the day.

Replacing workers with things you can’t beat, sue, intimidate, or cajole? Someone is gonna do something to make that not cool in MBA land. I think if one of my employees LL-MessedUp something, and I were upset, watching that same person stealing my money haplessly turn to an LLM for help might land me in jail.

I kinda love LLMs, I’ve always struggled to write emails without calling people names. There’s some clear coding tooling utility. But some of this current hype wave is insano-balls from a business perspective. Pets.com X here’s-my-ssh-keys. Just wild.

bonesss··on The Codex App
My experience with good outsourcing firms is that they come back with heavily-documented solutions that are 95% of what you actually wanted, leaving you uncomfortably wondering if doing it yourself woulda been better.

I’m not fully sure what’s worse, something close to garbage with a short shelf life anyone can see, or something so close to usable that it can fully bite me in the ass…

bonesss··on Claude Code is suddenly everywhere inside Microsoft
I think you’re highlighting an aspect of agentic coding that’s undervalued: what to do once trust is breached… ?

With humans you can categorically say ‘this guy lies in his comments and copy pastes bullshit everywhere’ and treat them consistently from there out. An LLM is guessing at everything all the time. Sometimes it’s copying flawless next-level code from Hacker News readers, sometimes it’s sabotaging your build by making unit tests forever green. Eternal vigilance is the opposite of how I think of development.

bonesss··on Microsoft is walking back Windows 11's AI overload
Thinking hard about how CoPilot fits into the MS ecosystem (Power BI, SharePoint, Dynamics, Office entrenchment, etc), and how their consultant mills work, I’m convinced there’s a meaningful space for unnecessary, unpopular, or suboptimal LLM solutions that can still be wildly profitable for MS.

Like, just because the outcome sucks and the solutions are user-hostile, let’s not assume the decision makers are dummies. I see profit motives as the likely delta between their decisions and our userland expectations.

Let me run the MS LLM department and I could easily explain to the board why we’re about to see a big upsurge Azure, office 365 integrated, and MCP-based solution spending… hint: it’s because the machine god will tell the consultants AND the customer those solutions are what’s SmartGood. We’ll sell ‘em a box that tells ‘em what to buy (lul, subscribe to!), the profitability part kinda writes itself.

bonesss··on The history of C# and TypeScript with Anders Hejlsberg [video]
On the .Net VM you’re describing F#, mostly by virtue of being based on OCaml.

Contrasted with TypeScript and C#, F# is smaller, more expressive, stricter, with mature pattern matching and type resolution baked in from the ground up. F# was years ahead of the major languages on what are increasingly looking like ‘the basics’ around ADTs and immutability in modern distributed computing. OCaml and F# capture the linguistic high points of VB, Delphi, and C# with a broad spectrum of OOP(-lite) approaches, and have led those languages by decades on functional constructs that result in meaningfully tighter code. With the benefit of hindsight some approaches clearly map better to cloud computing and system verification.

F# also sits parallel to lots of living C#, objectively we see ‘less is more’. Less code per line, fewer lines per solution, terser and more LLM-efficient language. Error rates and refactoring costs are also meaningfully better IME, but harder to quantify in general terms.

bonesss··on Swift is a more convenient Rust (2023)
Microsoft’s market position is reliant on Linux and access to Linux development to keep Azure competitive. Cross-platform capabilities on the .Net VM are critical to compete with the JVM and associated databases. C# has been windows-first for a while, but the core cross-platform capabilities are not going to disappear, the tooling is all CLI based/capable now, the entanglements tend to be platform and service based.

That said, F# was years ahead of C# in features C# is still chasing, and is driven mostly by the open source community. That community is more in academic and finance areas where Linux-first is common. The language is standardized and plugged into VM improvements over time.

Frankly, I see the lesser degree of entanglement with MS corporate interests as a boon for the language and its ecosystems long-term utility.

bonesss··on AGENTS.md outperforms skills in our agent evals
About a year ago I made an ChatGPT and Claude based hobo RAG-alike solution for exploring legal cases, using document creation and LLMs to craft a rich context window for interrogation in the chat.

Just maintaining a basic interaction framework, consistent behaviours in chat when starting up, was a daily whack-a-mole where well-tested behaviours shift and alter without rhyme or reason. “Model whispering” is right. Subjectively it felt like I could feel Anthropic/OpenAI engineers twiddling dials on the other side.

Writing code that executes the same every time has some minor benefits.

bonesss··on AGENTS.md outperforms skills in our agent evals
Key differences, though:

Humans are reliably unreliable. Some are lazy, some sloppy, some obtuse, some all at once. As a tech lead you can learn their strengths and weaknesses. LLMs vacillate wildly while maintaining sycophancy and arrogance.

Human egos make them unlikely to admit error, sometimes, but that fragile ego also gives them shame and a vision of glory. An egotistical programmer won’t deliver flat garbage for fear of being exposed as inferior, and can be cajoled towards reasonable output with reward structures and clear political rails. LLMs fail hilariously and shamelessly in indiscriminate fashion. They don’t care, and will happily argue both sides of anything.

Also that thing that LLMs don’t actually learn. You can threaten to chop their fingers off if they do something again… they don’t have fingers, they don’t recall, and can’t actually tell if they did the thing. “I’m not lying, oops I am, no I’m not, oops I am… lemme delete the home directory and see if that helps…”

If we’re going to make an analogy to a human, LLMs reliably act like absolute psychopaths with constant disassociation. They lie, lie about lying, and lie about following instructions.

I agree LLMs better than your average junior first time following first directives. I’m far less convinced about that story over time, as the dialog develops more effective juniors over time.

bonesss··on Microsoft's Azure Linux
That completely glosses over the actual behaviour of Microsoft, and ignoring the kinds of career, business, project, and reputational damage those tactics did.

MS’s attacks on open source, open formats, and free software impacted and still impact democracies, developing nations, general computing capabilities, and create vast market inefficiencies. Looking at it as pure tech misses the forest for the trees. The corruption of the Office OpenXml process alone is a daily pox on the developing world. The tax impact of those entanglements is recurrent, and frequently hurts education and healthcare.

Also: if someone got burnt by some industry jerks and have had to deal with the fallout for decades, “it was 20 years ago” completely misstates the problem. Some BS was started 20 years ago, sure, but with daily crap-bowls that needed to be eaten every day in between. Entire careers have fallen into those cracks, armies of IT staff forced into suboptimal and broken workflows to satisfy decisions based on establishing and abusing monopolies.

Breaking a spine, even years and years ago, impacts the every day. Bitterness can be well deserved with an understanding of what was lost.

bonesss··on Microsoft's Azure Linux
The MS of today is actively reaping the benefits of the EEE & openly shady business years.

Their behavioural changes can be framed as an intentional reformation, but also as exhausting high-value targets, losing monopolies, and settling into profitable equilibrium out of necessity.

Modern competitors to MS are effectively immune to MS-EEE, in some cases by being way better at every aspect of it (MS IE is now delivered by Google based on forked Apple tech, and Office uses React, for quick examples…). MS pivoted to Azure-entanglements for their entrenched customers, which remains highly profitable, but have also had a marked decrease in engineering clout in certain key areas and still have a fragmented client/GUI ecosystem.

I’d contend they haven’t changed, they’re just cornered in ways they never were before so we see different behaviour. If MS controlled iOS or Facebook or WebKit or Search we’d see more classic plays reminding us who owns what.

bonesss··on Second Win11 emergency out of band update to address disastrous Patch Tuesday
I think that transition, from OS/Desktop company to a Cloud Services Provider, is where the rot comes from.

The financial incentives are to upsell incompetent IT departments onto forever subscriptions. The poor products lead to fat over-engineering in the cloud and huge running bills that are very hard to undo. Sloppy LLM integrations, and sloppy LLM advice about IT needs, would seem to feed into that same strategy.

bonesss··on How I estimate work
Engineer: “It will take me two days [of work].” Sales:”We will have your fix ready in three calendar days [today + 2].”

Actual work that week gives employee 3 hours of non-meeting time, each daily meeting adds 0.5 hours of high-urgency administrative work. Friday’s we have a mandatory all-hands town halls…

Repeat that cycle for every customer facing issue, every demo facing issue, and internal political issue and you quickly drive deep frustrations and back talking.

I think there’s a fundamental truth: no one in their right minds, not even motivated engineers, actually hears anything but calendar when getting “days” estimates. It’s a terrible misrepresentation almost all the time, and engineers do a disservice when they yield to pressure to deliver them outside the broader planning process.

Project schedules should be the only place that time commitments come from, since they’re informed with necessary resource availability.

bonesss··on What has Docker become?
Docker on Windows issues, back before WSL had matured enough, gave a pretty compelling argument for doing windows development on OSX inside a VM.
bonesss··on Nanolang: A tiny experimental language designed to be targeted by coding LLMs
This specification argument seems to boil down to: what if we used Haskell to describe systems to LLMs?

Many of our traditional functional languages, ML family in particular, let you write hyper concise expressions (pure math if you’re in to that sort of thing), craft DSLs of unlimited specifiable power (‘makeTpsReportWith “new cover page format”’), and also in natural language (function names like `emptied cart should have zero items`).

I think if we did that and leveraged the type systems of those languages and the systematic improvements we see from ADTs and pattern matching in those languages, combined with a specification first approach like TDD, that we’d have a great starting point to have an LLM generate the rest of the system perfectly.

… yes, that is just writing Haskell/OCaml/F# with extra steps.

… yes, that level of specification is also the point with those languages where your exploratory type-diddling suddenly goes ‘presto’ and you magically have a fully functioning system.

I guess I’m old-fashioned, but sometimes I wonder if compilers are good for what they’re good for.

bonesss··on I was a top 0.01% Cursor user, then switched to Claude Code 2.0
Ruby OnRails is an interesting hype counter point.

A substantial number of the breathless LLM hype results come, in my estimation, quicker and better as 15 min RoR tutorials. [Fire up a calculator (from a library), a pretty visualization (from a js library), add some persistence (baked in DB, webhost), customize navigation … presto! You actually built a personal application.]

Fundamental complexity, engineering, scaling gotchyas, accessibility needs, customer insanity aren’t addressed. RoR optimizes for some things, like any other optimization that’s not always a meaningful.

LLMs have undeniable utility, natural interaction is amazing, and hunting in Reddit, stackoverflow, and MSDN forums ‘manually’ isn’t a virtue… But when the VC subsidies stop and the psychoses get proper names and the right kind of egg hits the right kind of face over unreviewed code, who knows, maybe we can make a fun hype cycle called “Actual Engineering” (AE®).

bonesss··on Gas Town Decoded
I’m pro LLM and use them, but crikey: if they’re so good at code why aren’t these people with all the attention, branding, and connections in the world unable to capitalize them?

I believe Google that uses their internal Gemini trained on their internal infrastructure to generate boiler plate and insights for older, less mature, code in one of the worlds biggest and most complicated anythings, ever. But I don’t see them saying anything to the effect of “neener neener, we’re using markov chains so 10x our stock ‘cause of the otherwise impossible face melting Google Docs 2026.”

OpenAI is chasing ads, like Reddit, to regurgitate Reddit content. If this stuff is worth the squeeze I need to see the top 10 LLM-fluencers refusing to bend over for $50K. The opposite is on display.

So hypotheses: Google’s s-tier geniuses and PMs are already expressing the mature optimum application. No silver bullets, more gains to be had ditching bad tech and extraneous vendor entanglements (copilot, 365).

bonesss··on Gas Town Decoded
Anthropomorphizing chunks of your system is kinda weird given interactive chat as the UI to the LLM.

Akka and others have standardized names for all this stuff (and seem to fully know that a code ‘actor’ is code). These wheels don’t need reinventing (much less as ‘the Marvin’s’, a lovable set of bi-racial quadruplets who always get you where you’re going <rocket emoji>).

In fact, I dare say a lot of LLM fascination for orchestration is people unfamiliar with actor models and the level of elegance a properly expressive language lets them have.

bonesss··on Predicting OpenAI's ad strategy
I think having mixed economic interests is great when an advertising company is asking you, you execs, your engineers, and consultants to dump whole copies of project planning, business practices, and internal dynamics on their servers…

If I’m looking at ads for your shizz a) why can’t we just pay as a business expense, inline ads and B2B are an odd combo, and b) if this isn’t fully local tech I think there is a real challenge trusting MS or OpenAI to respect their contracts.

We’re not too far past these same dudes running around, violating NDAs, and launching product clones to eat partner businesses. Now ads? … trust? … scorpions and frogs, scorpions and frogs.

bonesss··on Cursor's latest “browser experiment” implied success without evidence
Hitting my head into buggy apps made by these AI companies and seeing them all be amazed in parallel that skills/MCP would be necessary for real work has me pretty relaxed about ‘our jobs’.

OpenAIs business-model floundering, degenerating inline to ads soon (lol), shows what can be done with infini-LLM, infini-capital, and all the smarts & connections on Earth… broadly speaking, I think the geniuses at Google who invented a lot of this shizz understand it and were leveraging it appropriately before ChatGPT blew up.

bonesss··on Cursor's latest “browser experiment” implied success without evidence
Hypothetically: what if they did check, only in order to ‘check’ they asked the LLM instead of manually verifying and were told a story? Or, perhaps, they did check manually but sometime after the files were subtly changed despite no incentive or reason to do so outside of a passing test? …

Humans who are bad and also bad at coding have predictable, comprehensible, failure modes. They don’t spontaneously sabotage their career and your project because Lord Markov twitched one of its many tails. They also lie for comprehensible reasons with attempts at logical manipulations of fact. They don’t spontaneously lie claiming not to having a nose, apologize for lying and promise to never do it again, then swear they have no nose in the next breath while maintaining eye contact.

Semi-autonomous to autonomous is a doozy of a step.

bonesss··on STFU
There is a substantial difference between people talking amongst themselves and one person on a phone.

Humans are social animals, we tune out conversations easily. Half conversations are just one interrupting, attention-grabbing … jarring start … … after … … … … another. It’s a series of unpredictable spontaneous one-sided outbursts, behaviours that otherwise belong to disturbed individuals.

Listening to people in the phone is inherently more annoying, backed by decent research IIRC.

← PreviousPage 10 of 32Next →