etoxin

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.

The Sunny 16 rule was coined as a guide when film cameras were the norm and light meters were not on all film cameras. Any relation to digital sensors is a coincidence.

side note: Film in sunlight is far more forgiving than digital. It handles dynamic range a lot better.

It would be cool if there were multiple games within a geoguesser game. Doom, Witcher, Battlefield, Red Dead.

you're right. I only read the title and very quickly. My bad.

Changing APIs. When the front-end gets JSON from an API. We really don't know what we're getting. We need to liaise with the API team to figure out how these APIs work and when they change, we don't know what changed. Luckily there is a new solution. End to end type safety. Using tools like graphQL allows FED build tools to get the entire API schema and bring that into the typescript build. If the API changes, your build will break allowing you to update your app to the latest API.

Maybe we need a new HTTP method "SCHEMA" that allows the app team to get the schema directly from the API and stop sharing postman links around in chats.

So in theory if we wet a surface painted in Vantablack (the darkest substances known) it should become even darker.

I bought a Anki Vector about a year ago to tinker with the sdk. After messing with the sdk, I left it turned on for the duration of the year.

I don't use any of the voice actions but its awareness in the environment I feel is enough. It sits in the kitchen and has prime position.

I could not classify it as a "Buddy" or "Friend" but I care about it enough not to turn it off.

I think the next stage for these social robots is to learn(AI) unique personalities. eg. Movements, noises, faces. So no two social robots are the same.