Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment Re: Bad example (Score 1) 87

I recently bought a Fitbit, and one of the best features is the smart alarm clock. Instead of just going off at a particular time, it waits until you are naturally awake in the half hour leading up to the designated time. Much gentler and I greatly prefer it.

So there is a reason to pay more for a simple alarm clock, but mine does not require a subscription. If they start requiring one, I'll return it immediately.

Comment Re:No thank you. (Score 1) 41

No need to imagine, you have been able to do that for years. Nio has had battery swap stations running for some time in Europe, and they are great.

Faster than pumping dino juice, and the battery get is guaranteed to meet a minimum, high specification. Never heard of any problems, but if there were you would just swap it out again for a few Euros.

You have infinite battery warranty too because if you did ever manage to put enough miles on yours to wear it out, just get it swapped.

Comment Re:I've been using KDE for two months (Score 1) 27

Mate was a straight fork of Gnome 2, as such it's a 2 decade old time capsule.

A fork is not a time capsule.
MATE has had plenty of development in the 15 years that it has been in existence.

It started life as a direct fork, and quickly became its own thing.

Gnome 3 then made a series of idiosyncratic UI design choices which polarized the Linux community.

I think the bigger complaint was the loss of functionality. Simply... gone.
In the intervening time, the GNOME shell plugin ecosystem has effectively filled the gap, and more.
GNOME 3 was pretty fucking terrible at first, which is why I moved to MATE.

And if work imposes Windows 11 for my day job, I find XFCE/Debian on my home machine to be the least drama in terms of paradigms.

I'll never understand you XFCE fuckers ;)

Comment Re:"i need that small annoying snippet that does.. (Score 2) 84

But letting it loose on the big code at large is pretty dumb.

I do this frequently, with both packaged agents and my modifications to them, just to see what comes out the other side.
Sometimes it's great, sometimes it's pretty bad.
I do it as a side job, not my regular work, so the consequences of the failure are minimal- I just throw it away and try again with another modification.
If it were my actual main workflow... I think that would stress me the fuck out- each failure being significant wasted time and money.

Comment Re:At first (Score 2) 84

Professional dev in my third decade of experience speaking here.

Only second decade, here.

I rarely ever reach for them anymore. I sure would not rely on them over even an inexperienced junior dev, either.

I find them comparable, unfortunately. But my new hires may not be as good as yours.

Comment Re:Here's What Happens To Me (Score 2) 84

I call it the coding LLM Doom Loop.
A good bit of my effort with using LLMs has been in trying to avoid and correct it.
I've found it gets easier when you start to treat the LLM and its entire context window as a single unit rather than thinking about prompts.
Coding agents are variably successful at this.

For my own agentic tests, I've had good results "context engineering" the LLM to solve tasks reliably that it previously couldn't.
In the end- I'm not sure it's worth the effort, but hey, it keeps me entertained.

Comment Re:I'm tired of being lied to (Score 1) 52

Any kind of mass surveillance system? Absolutely. Any "brand of camera"? Of course not. The mass surveillance system is what did the work, not some random camera.

The effectiveness of a solution does not justify its existence. Nor should we have to weave an alternate reality to come to that conclusion.

Slashdot Top Deals

"A mind is a terrible thing to have leaking out your ears." -- The League of Sadistic Telepaths

Working...