etoxin

Or spec-driven AI development.

Hundreds of PR’s per engineer per day! They would have zero visibility of their code. Their AI’s would have no visibility of the million plus lines of code.

Sounds super stable and cool.

I think 75% is about right. It calls tools pretty well and has a good knowledge base. It's absolutely not 90% there, but 75% feels right.

I have not. We use openspec with our projects at work. To try and simulate a local rig without spending big cash. I use the hosted models and pay for them with the latest popular local model.

Most small local models don't get tool calling right, however the larger models are now doing this correctly now.

One thing local has not accounted for, is most productive engineers are running multiple cli chats at a time with git worktrees. I normally hover around 3 worktrees + cli-chats.

Also MCPs for programs like Chrome Dev tools or Playwright.

People who say MCPs are dead don’t understand how MCPs work or when to use them.

This was a proof of concept to see if a event driven like neuron inspired neural model could work. I heavily used gemini flash 3.5 to build my vision.

You should checkout the Gemini Protocol. https://en.wikipedia.org/wiki/Gemini_(protocol)

Here in Australia we have earths largest scale model of our solar system.

https://www.nsw.gov.au/visiting-and-exploring-nsw/locations-...

Same for us, stalled merge queue, reopened closed PR's, PR's missing on main page.

There is like 1,713 open PR's on the Bun repo. I'm assuming all are from Claude or robobun?. I guess this gives us an insight on what the claude-code workflow look likes. Crazy times.

I think we've hit the "who's the most reliable" stage for these tools.

We can now shop around easily. They almost all do the same thing now. The models are "Just Enough".

Astrophotography is having a bit of a moment right now. The barrier has been reduced greatly and there are some amazing OSS post processing tools.

Not a hoax, saw it in the news. I'm not at Amazon but can confirm massive productivity gains. The issue is reviewing code. With output similar to a firehose of PR's we need to be more careful and mindful with PR's. Don't vibe code a massive PR and slap it on your coworkers and expect a review. The same PR etiquette exist today as it did years ago.

I think we should still allow open contribution to OSS.

Maybe, a "Contributor Requests".

It would be a gate for new contributors. For maintainers, they would see what they have contributed to and see their new PR. It would show "open contributor requests"

Once approved, The PR will then appear under PRs.

And obviously this is opt in.

A powerful, open-source AI SDK with a unified interface across multiple providers. No vendor lock-in, no proprietary formats, just clean TypeScript and honest open source.

So, some history. When SPA's started to boom on the web JSDoc was a life saver for typing. Application state was getting more complex. We needed more guard rails.

Then Google Closure Compiler came along which added type safety via JSDOC and TS came along with (TS)JSDoc support and it's own TS syntax.

The community chose native TS and Google Closure compiler slipped away into the background.

So (TS)JSDoc support is a relic from when Microsoft was trying to get market share from Google.

Today in 2025, TS offers so much more than the (TS)JSDoc implementation. Generics, Enums, Utility types, Type Testing in Vitest, typeguards, plus other stuff.

Today I use TS. I also use plain JSDoc for documentation. e.g. @link and @see for docs. Or @deprecated when I'm flagging a method to be removed. @example for a quick look up of how to use a component.

TS and plain JSDoc are both important together. But (TS)JSDoc alone, is a relic of the past.

I'm seeing the same thing in Australia.

These new tech companies/existing companies were not here for the first wave of offshoring engineers many years ago. basically, the product/service degraded and they brought the product/service back onshore.

It's a cycle that will repeat. Product degrades, there will be public outrage, then they will onshore the product to fix the problems caused from offshoring.

Most people take photos of DSO's, but while you've got the gear, why not photograph the moon. It's also technically fun. Using a cooled camera, I video the moon/Jupiter at 20fps at 3000x3000. Then using software, I only take the frames where there is minimal atmospheric distortion. With the remaining frames, you stack them to get a very detailed image of the moon/planets.

Look up the other gear from ZWO the maker of the seestar.

And this varies widely between models based on how they are told to reason.

Some app devs use local models on local environments with LLM APIs to get up and running fast, then when the app deploys it switches to the big online models via environment vars.

In large companies this can save quite a bit of money.

Same here, everyday coding in Webstorm, Oh I have a task I can offload to copilot, I open VSCode and let a Github CoPilot Agent do that.

Knowing what tools are better for what really helps.

Arm amputee programmer here. There are some wild hardware solutions out there.

What I found best was

- a standard qwerty keyboard (I didn't want to be restricted to custom keyboards)

- A learning program called Five Finger Typist. https://www.spectronics.com.au/product/five-finger-typist-2-...

Basically I'm hybrid touch typing. Because I cover the whole keyboard as I type the chance for error increases the longer I type. I quickly glance to know where i'm aligned.

In hindsight I should have learnt to use the F and J notches more.

I have extensively remapped my IDE shortcuts to be easier to trigger.

jQuery has mostly been replaced by new browser apis. It was a great library that brought the web forward. It will still be around the web for decades to come. If you're updating to jQuery 4. Why not try switching to native js.

https://youmightnotneedjquery.com/

Or press K

Appears that only people from the northern hemisphere can order this, Shame.

Using a browser devtools performance profiler could confirm this. I highly doubt there's a 5 second setTimeout in youtube. More likely switching of browser technologies based on user agent.

I've just started hanging all my shirts. Basically I have a set amount of coat hangers. If i want a new shirt I need to sacrifice another. It also makes drying way easier. Out of the washing machine, onto a coat hanger, onto the washing line, straight into the wardrobe once dry.

Also used in supermarkets for planning. It's handy to see how much of product was purchased in week 34, spanning back a few years.

It's pretty common for cicd pipelines to generate static json like this to track environment info.