stsquad

Looking forward to seeing that one again - 4 away on our watchlist.

Why is Janeway wearing black gloves in this?

Heh - that's the next episode on my Voyager watch through with the family. They already think Janeway is badass so I think they will be up for her fighting space Nazis.

I don't know. If holodeck tech is constantly manifesting and removing matter from the holodeck I can imagine having an external transporter system trying to resolve stuff in that shifting mess would be quite tricky even with those Heisenberg compensators.

Are you talking about Vehicle Excise Duty? All cars pay that although at various rates, the more CO2/km attracts higher rates, going far above what the EVs pay.

I personally have email integrated into my editor (mu4e) so I can apply patches and search code directly from the email thread. It handles threads and searching really well.

Issue triage, code exploration, extracting information from disparate sources, first pass code review. There are loads of use cases that it's potentially useful.

For me it's a lot better at extracting the requirements for a CPU feature from a 10,000 page architecture reference manual than I am.

I have API access at work because I don't want to be tied to a UI. I'm very aware of the cost because I'm trying to see where it offers good value for money.

Of course things like the deep research and notebooklm are covered by the Google workplace fees which while including more than the personal plans are also a fair bit more expensive.

Your making a big assumption extrapolating from one particular study involving Java code and a static analyser.

How is that patch sloppy?

I feel the term slop is being overused to cover anything an LLM has touched. If I ask an agent to re-read a mail thread for me and apply the changes to my tree to review is that slop? Would you feel better about it if I copy and paste from email to code in my editor?

I've just been doing a bunch of bug triage which was mostly driven by the agent although I checked the issues where it had commented. Was that slop? Ironically a lot of the issues where AI generated although for the most part more complete than a lot of the purely human submissions we get. Are those bug reports slop? What about the poorly drafted human ones?

That's not kernel policy but LF guidance. From the kernel's point of view patches still have a high bar to pass to get merged and I don't think we have enough data yet to see if LLM based submissions to the kernel have a higher or lower error rate than humans.

I certainly feel the uptick in LLM reports though - one of the projects I'm working on is seeing a deluge of them at the moment.

I've vibed a bunch of apps and scripts and it's great for that project you never found time for. Importantly they where all local and ultimately throw away things.

The idea of relying on vibes for production seems insane to me. The most important thing about software engineers is not how fast they can type.