_ea1k

I'd expect that to get swiftly replace by something else.

A lot of people consider score keeping like this to be more important than the job itself.

I can't even say that they are wrong.

Yes, one of NVidia's selling points for the b200 is that performance per watt is better than before. High power consumption without controlling for performance means nothing.

This sounds like what PI planning is imagined to be in "safe".

Yes, that's exactly it. A lot of people have shown that gas trucks suffer range loss as well, but they start off with higher range and get refilled in <5 minutes.

The EVs lose enough range that they often need to be charged deep into the pack to make it to the next station, which leads to >40 minute charging sessions every 100-120 miles.

True, but regenerative braking eliminates most of that as well.

Reading this made me wonder if I have an alt account that I forgot about, because this is exactly how I think about our current state.

Hey, remote work isn't productive, lets go into an office and push all our code to github and deploy to Linux (both largely developed by distributed teams, thankfully without Zoom).

But you are right, organizational and productivity theater dominate at many companies.

The port count is a real problem on modern laptops. I like USB-C, but why are there so few of them? Having to have a hub for basic things is really annoying.

They must not use scrum or safe

I thought about making a joke like this, but I was afraid that it'd be closed as a dupe.

TBH, those tests are mostly marketing failures. EV trucks aren't really good at hauling trailers over large distances, as the aerodynamics produce a massive impact on range.

Multiple tests have shown this by showing 50% or more range reduction from pulling lightweight, non-aerodynamic loads.

The marketing failure is that the companies have allowed consumers to incorrectly extrapolate from this to thinking that heavy loads in the bed have the same issue. They actually don't as weight is a minimal impact on range.

Unfortunately, every thread about carrying sheetrock, rocks, mulch, etc shows how misinformed the average consumer has become in this space. It has to be a significant impact on sales, given that in the US these are the only heavy loads carried by >50% of the half ton pickups sold here.

IDK, some of the remote teams that I've worked on were only able to meet in person once per year, if that. They were very communicative on the tools that we had though.

Every time that I read this about remote work, all I can think is how much I miss IRC and the culture that came from it.

We were doing remote work effectively decades ago. Don't have hallway conversations to fix bugs? Easy, just post your problems on the team chat and someone (often one of several people) would love to drop by to help.

I'm not sure exactly all of the forces that have led to this changing so much, but I'm certain that merely blaming "remote work" isn't it.

Somehow we were better at using remote tools while literally in the same office than some teams are at using them now while fully remote.

TBH, I think covid and the push towards Zoom and others had a similar outsized effect. It made synchronous meetings nearly "free" for many more people.

We just need another tool for ranking tools via ToolRank. We'll crowdsource the ranking from a combination of user responses to the agents themselves as well as a council of LLM tool rankers.

Texas and Florida both have a lot of solar as well, with TX likely passing CA on battery storage over the next few years. Those states also have much cheaper energy than CA.

California's energy problems aren't due to the source of their energy.

The flip side to this is that perl often favored brevity over simplicity. It turns out that this is also a really useful attribute when working with LLMs. I'm not sure how confident I am here, but it really wouldn't surprise me if LLMs could both generate and explain remarkably complex perl code!

Was this written by one of the firms trying to justify the practice?

I sometimes wonder how different things might have been if Perl had been the dominant scripting language at the time that ChatGPT, Codex, Claude Code and other tools like that became available.

Would Python have been able to compete, in a world where Perl could be readily comprehended by LLMs?

So, maybe what killed Perl was lack of VS Code forks and lack of being agentic.

Why not https://github.com/hrrrsn/mcp-vnc ?

Yeah, I'm still confused as to why so many people in "AI engineering" seem to think that MCPs are the key to everything.

They are great if you have a UI that you want and it needs a plugin system, obviously.

But the benefits become much more marginal for a developer of enterprise AI systems with predefined tool selections. They are actually getting overused in this space, if anything, sometimes with security as a primary casualty.

For web apps, I'd guess that many of us already do that via Playwright or other MCPs. I'd bet there are people doing something similar with desktop apps too.

I've finally gotten around to learning Go this year and I'm having a pretty similar experience.

It really feels like a simpler language and ecosystem compared to Python. On top of that, it performs much better!

I thought the same. Having said that, the parenthesis in the example are really wrong for what they were trying to convey. I suspect that they built this sql sample for the document and made some mistakes in its generation.

Perhaps I could say, it isn't just generated--it is also hallucinated!

Yeah, for me Segway has been a great lesson in how patents can hold back innovation. It was a niche player that prevented others from trying to innovate on the form factor for a number of years.

I think you are describing it pretty well, and I've noticed the same thing. The farther into the future the forecast goes, the higher the probability is that it will look like the historical average.

One thing that I've found to help a lot is to go to weather.gov and look at the "forecast discussion". Often it will help to understand what types of uncertainties exist within the forecast.

It isn't unusual to see notes that make it really clear that 24-48 hour variations are expected, or that massive differences will exist based upon hard to predict variables. "Hey we think it will rain heavily as far south as X, but actually it might end up staying north of Y in which case X will stay dry"

It is easy to see how hard it can be even if the forecast itself turns out to be fairly accurate at a high level.

Isn't he a fairly minor shareholder?

It is crazy how paranoid people can be, IMO. They don't seem to understand that these companies don't really value one person's information highly enough to do stuff like that.

It is everyone's information that they value, not that one guy who goes to the trouble of killing the radio.

What law governs this? I'm familiar with a lot of restrictions on grid-tie systems, but I've never heard of it being this strict for something that could (presumably) be done without a back feed.

I mean, are you saying that someone sticking up a few panels+batteries to run an electric fence, gate, and camera system has to have permits?

This all seems strange.

ecobee is still cloud connected, but they work nicely with homekit. AFAICT, that enables local control. I can confirm that they work nicely with homeassistant via the homekit integration.