Philip-J-Fry

I think it's just a matter of what people want from a city builder. Some people play the game to build the city they wish they had. While others play the game to build the city they've already got.

The line is don't push your religion in your science content. Not a hard line to not cross.

Destin of Smarter Every Day went down the drain in my books as soon as he published a video about Flagella, and ended it by suggesting it could be intelligent design and told viewers to read a book authored by someone who is a staunch believer of intelligent design.

Crossed the line as a science Youtuber. You don't need to be athiest to be a scientist, and he definitely isn't. But you should at least know the line.

Finding out this site is basically just a copy of something that already existed and something they knew existed just further degrades my opinion of him. Especially with it being littered with ads. The ad literally takes up half my screen.

LLMs change the calculus on DRY in some cases. I would say it's still very much a no-no on the frontend side of things. Code repetition is directly correlated with bad loading performance. When you're optimising for people on slow mobile connections, your HTML/JS/CSS being 500KB instead of 1.5MB matters a lot.

The folding/unfolding animation is one of the coolest I've seen from a foldable. So slick.

Lets consider something like the right to take sick leave. There is no strict definition of what "sickness" is. It is something that YOU feel impacts your ability to work. Maybe a bad nights sleep, sore back, headache, runny nose, bad tummy, etc. There's no need to provide any amount of proof to an employer when taking a single day off sick, and they need to pay at least the statutory sick pay, many companies pay full.

Most people agree that this rule works well in practice. Most people don't take a sick day because they don't feel 100%, even when its within their rights. If everyone decided to take Monday off because they're sick, that would be possible within the law, there's no need to provide proof you're sick. Yet, if that happened, the country would grind to a halt.

Now ask yourself, how could you implement that without eroding someone's rights and without introducing more friction?

Sometimes, you just have to assume that people are honest and won't take the piss out of the system. Or you have to introduce friction to discourage the exercise of their rights. The friction for sick leave is that you usually have to notify your employer ASAP and that you may have to fill out a return to work form.

Never really a sound argument.

It's like having new solar panels installed every week. Sure you're "profitable" on the $0.20/kWh you're selling your "free" energy at when you ignore the cost of the solar panels you're buying every week.

That doesn't apply to a corporate travel portal. If you're on the portal, you're booking a business trip. You're not going to not book a trip because it takes 1 click too many.

Yeah, I know the benefits. There isn't a lot of data transferred though. The GitHub repo for this robot has design decisions on it so you can read their reasoning for themselves.

At the end of the day, it's an open source robot so someone can implement these protocols if they see the reason to.

Yeah but not any language.

JSONRPC can be trivially implemented in any language which can read/write a Unix socket. Which is any language worth using.

It's the trade off for performance and accessibility.

Because now you're locked into the Rust ecosystem.

JSONRPC over Unix sockets is a better interface for language agnostic IPC.

That's a completely different class of robot. The Beni robot is just a toy, it's just connect the app and drive it around, record videos and do some fancy tricks like flips. It is not meant to be a platform you program yourself.

The Microduck is meant to be a hacker toy. Train it yourself, write software, hack it, etc.

It depends what you're trying to get for your daughter. Is it something to get her into robotics? Then probably the Microduck is the way. If it's literally just a toy, then the Beni robot is better because that's literally all it is.

I open it to do the daily puzzles. But it means that I'm subject to 1 or 2 cringe posts before I get there.

The top nav is completely broken for me.

Cerebras doesn't etch the model onto silicon though. They're basically just wafer scale GPUs. They're more flexible than etched silicon though because they can just run the next version of the model almost straight away.

"Do your own research" is definitely a defensible position. No one is saying take Claude's output as fact.

These people would still ask and waste your time without AI. The fact is, they don't even bother trying to find an answer themselves. And it's often something Claude is extremely good at finding out. Which is why my first suggestion was if you used Claude, then let the person asking know that it worked well for you and encourage them to use it. It's their own competency at their job to judge the output, they shouldn't be pushing the hard bit onto someone else.

If someone uses AI or some other research and then comes to you with their findings and other questions then that is infinitely better to me. I absolutely despise people asking me basic questions that involve me literally doing the research job for them.

If they come to me like "Hey, I have X problem, I used Claude like you suggested and it came out with this response. I'm not 100% sure it's correct because of Y. Would you be able to take a quick glance to see if it's on the right track?". I am much happier with this question because it's clear they have actually tried to research themselves.

Ignoring someone who doesn't even do the most basic research is 100% a defensible position. People should be doing their job.

Literally just ignore these people if they don't get the message. Let them complain to their supervisor and hopefully their supervisor will bring up the fact that you asked them to use AI instead. It's an easily defensible position. Some people need to learn the hard way.

Public embarrassment is also good. I've done it and had apologies off people. They tend to get the message pretty quickly if they're made to look dumb as fuck.

"Hey, here's what I found. By the way I used Claude to get this info. It might be worth trying that yourself if you have similar questions, it's quite good at this in my experience. Give it a go"

Give a man a fish, and you feed him for a day. Teach a man to fish, and you feed him for a lifetime.

I've seen two camps of people within the same company I work at. Some think AI is generating acceptable code. Others think it's generating slop.

I sit in the middle a lot of the time as my opinion on code quality vary depending on how important the code actually is.

I will say one thing, the people who I generally deemed as worse developers prior to the wide AI roll out are the ones that are more accepting of AI code. And consequently, they're the ones spending a magnitude more money each day. The people who were writing better code and, in my opinion, were stronger developers, are spending less on AI and are generating more acceptable code when they use it. And they can spot issues from a mile away, because they actually understand the code being generated. They're not just committing lots of redundant code.

We had an AI outage for a day or two a few weeks back. The reaction from some people was like it was the end of the world and they couldn't do any work. Some projects got put on hold because no one actually knew how to work on the code base without AI. Other, better in my opinion, developers just went shrugged it off and got on with their job.

AI over-dependence is a big issue that people will face more and more. Weaker juniors used to just be a bit slower and stagnate a bit, but they could still kinda work independently and understand what they were doing. Now they are almost entirely prompt monkeys, take away their Claude Code terminal and they are completely stumped.

When you're in the trenches actually making code changes yourself, you get irritated and are driven towards improving the code as you implement new features. AI never does because it never has to. And because you're not in the trenches, you don't actually experience the frustration of managing the code base. So from your tactical view everything is fine, and when you're reviewing an isolated change you don't have the context of everything the AI had to read and figure out to get there. If you had to wade through shit to figure out how to implement something, you'd have made those refactors a long time ago. AI just eats it up and serves you a new plate of slop. It's a blessing and a curse depending on who you ask.

AIs greatest strength is still throwaway code.

I think they're saying that the people who aren't software developers are playing around with Claude Code. And that's not what their job is and it's not what they understand. It's all good empowering people who aren't software developers but at the same time, it's not worth running your business on tools and software no one in your business understands. You need someone there who knows what they're talking about, even if it is just as a mentor.

I think of it this way. If AI could build the product alone, then why would it ever be worth more than the tokens you spent on it? I think this would hold true 99% of the time. It's literally like asking someone "Can you pay me $1m for new gadget? I hired this other dude for $20p/h and he made it in a week". It simply doesn't add up.

The 80/20 rule still stands.

In my real world use Luna is as useful to me as Sonnet. And it gets stuff done faster and follows my instructions more closely.

The port was line for line and full of unsafe code. It didn't prevent any bugs. They're not using Rust for its strengths.

A website shouldn't be pinning CPU or GPU. When people run a game they expect some sort of battery drain. People don't expect that some websites will thrash your CPU/GPU like a game.

One LLM prompt can't get you $500K. Why would someone spend $500k instead of just prompting themselves?

Don't you just throw all the washing into the washing machine, wait for it to actually do the work, and then hang it all up afterwards? It's like a 15 minute job max.

Who said they're new? Also, you can encounter new segfaults in a codebase just by executing code paths you haven't seen before.

Segfaults were a thing with the Zig version. Purely based on the fact it's a line by line translation of the Zig code to unsafe Rust, all the Zig code that caused segfaults is going to also cause segfaults in the Rust version. The Rust code won't fix it until they get to the point of refactoring it into idiomatic and memory safe Rust.

As far as I can remember the origins of Bedrock are the original console releases which couldn't ship a JVM. So a whole new codebase was developed, and ultimately it was more performant as it had to run on 7th gen consoles.