HN user

baublet

109 karma

Full stack

Posts1
Comments24
View on HN

The most difficult codebases are those with every little thing some bespoke abstraction that went through 3 rounds of committee reviews that results in having to click through 12 files to figure out what anything is doing. Factory factory factories each with their own little frankenframework to understand before using anything.

We wrote a simple internal tool that looks at the that transcript and replaces all UUID and BSON IDs with lower cardinality placeholders (e.g., id-1), including replacing them in the output, and it instantly brought down common error and hallucination rates. I figure this tool lets you apply semantic tokens to the IDs too, e.g. user-1 instead of id-1. Stuff like this is useful for my team because we only use small, fast, highly available models for bulk classification, so we measure error and hallucinations where we can.

True! Although in a lot of Node you DO have a compile chain (typescript) you need to account for. There’s a transactional cost there to get these working well, and only sharing the code it needs. These days it’s much smaller than it used to be, though, so worker functions are seeing more use.

I make my comment to note tho that in many envs it’s easier to scale out than account for all the extra complications of multiple processes in a single container.

Reading the article, I didn’t see this answered: why not scale to more nodes if your workload is CPU bound? Spin off 1 cpu and a few gb of ram container and scale that as wide as you need?

e.g., this certainly helps when the event loop is blocked, but so could FFI calls to another language for the CPU bound work. I’d only reach for a new Node thread if these didn’t pan out, because there’s usually a LOT that goes into spinning up a new node process in a container (isolating the data, making sure any bundlers and transpilers are working, making sure the worker doesn’t pull in all the app code, etc.).

Side car processes aren’t free, either. Now your processes are contending for the same pool of resources and can’t share anything, which IME means more likelihood of memory issues, esp if there isn’t anything limiting the workers your app can spawn.

Still, good article! Love seeing the ways people tackle CPU bound work loads in an otherwise I/O bound Node app.

It was. In hindsight it signaled the beginning of the mass weaponization of the internet via social media. It also was NOT grassroots lol. It was very specifically and intentionally enflamed and groomed and funded by people like Steve Bannon and his good buddy Jeffrey Epstein. It wouldn’t have such a big Wikipedia article without them.

I think some displays allow fast enough updates for that. But the early versions of the Divoom didn't have enough docs and/or had broken firmware and wouldn't show any custom gifs I sent it. But it's been working great for me for a few years now as a wall clock/weather display.

Finally got around to writing it about this yesterday, actually. https://ryanmpoe.com/2026-01-03-weather-pixel-art/

Happy coincidence, OP!

Posted this because I didn't see it, just now getting back (toddler).

I started messing with this yesterday and was able to get a fully functional refactor engine (complete with code review, running tests, building TS, etc.) going in less than a day.

We were looking for a tool to bake into our developer tooling that supports things like this, and this GenAIScript project has been perfect so far. Definitely doesn't seem quite ready to embed this into customer-facing stuff, but I'm finding it tremendously helpful for LLM-powered tooling!

Many thanks, pelikhan, for publishing this!

I wouldn’t overthink their comment. It’s just a standard racism. Using DEI as slang for people of color is a 2023/2024 era dog whistle.

Concur. Elm is an excellent addition to one's development quiver. Its strictness made me a far better, more careful programmer, and the push toward functional, side-effect free programming styles (something also coming from the React community) has been a huge boon to the JS world. Loving the current state of JS!

They are shipped here over sea lanes made safe by the trillions the US and other countries pay to make them safe; to fly in airspace made safe and regulated by those same countries; to be shipped to individual stores over roads built and maintained by taxpayer dollars that allow such wide open shipping lanes; allowed to move from truck to store and stay in said store before the point of sale to me and other buyers safely by a police force also paid for by taxpayers.

Net neutrality has only existed since 2015. It's vital because it halted a bunch of attempts by cable companies to shake down businesses (small and large) and their potential customers for extra money for prime access to pipes. Dismantling net neutrality won't open up new markets. It will make cable companies the gateways to those markets, and essentially cripple innovation the same way cable companies crippled television by having an iron grip on channels, packaging, and all the other nonsense we deal with today in cable TV.