标签：#water

Labor Day in the US ✌️

AI is getting surprisingly good at planning trips. Give it a destination, a budget, and a few days, and it can generate an itinerary in seconds. Five days in Tokyo? Shibuya on Day 1. Asakusa on Day 2. Tokyo Tower on Day 3. Ginza on Day 4. TeamLab on Day 5. It looks perfect. The problem is… I might hate it. I don't like crowded places. I wake up late. I care more about food than landmarks. I don't want to spend half my trip rushing between “must-see” attractions. And I would happily spend $250 on one amazing dinner instead of visiting five popular tourist spots. The itinerary isn't wrong. It just isn't mine. And I think this reveals one of the biggest challenges for AI travel. Personalization isn't knowing where I want to go. It's knowing how I make decisions . For a long time, personalization in travel has mostly meant collecting preferences. Beach or mountains? Budget or luxury? Business or leisure? Window seat or aisle? But human travel decisions are much messier than that. Two people can have exactly the same destination, budget, and travel dates—and still want completely different trips. One person might want to stay in the center because they want to walk everywhere. Another might prefer a quiet neighborhood and take a taxi whenever necessary. One traveler wants to see everything. Another wants to do absolutely nothing before noon. One person sees a $300 hotel as expensive. Another sees it as a bargain if it means waking up next to the beach. The difference isn't simply preference. It's trade-offs . And that's where I think AI travel agents still have a lot to learn. The best travel agent isn't the one with the most recommendations. It's the one that understands your priorities. Think about what a great human travel agent does. You tell them: “I'm going to Tokyo.” They don't immediately send you a list of 20 hotels. They ask questions. “Is this your first time?” “Are you traveling with kids?” “Do you care about nightlife?” “Do you mind taking public transportat

Meme Monday! Today's cover image comes from the last thread. DEV is an inclusive space! Humor in...

After sixty-seven published posts here, the comments have become one of the best parts of the work....

I have been an office worker for several decades. When I started, the internet was still clearing its throat. Salespeople carried pagers. Windows 95 was teaching us that folders could live inside other folders, which felt almost philosophical. Documents traveled by fax or post. Work was slow and inefficient. Then came mobile phones, email, and the internet in our pockets. We could send more information than a human being could understand to the other side of the planet in a second. Work that once took a day took half a day. Then a third. We thought, “Wonderful. Now we can go home early.” Naturally, we did not. We poured new work into the empty space. Technology saved time, and we immediately gave that time back to work. It was rather like receiving a larger bowl and celebrating by filling it with more soup than we could eat. Now generative AI has arrived. It writes, calculates, summarizes, and never asks for a lunch break. Once again, it gives us time. Once again, we reward ourselves with more tasks, more speed, and less breathing room. People worry that AI will take our jobs. Perhaps the stranger problem is that it has not taken enough of them . Technology was supposed to make life easier. Instead, we have used it to become more efficiently exhausted. Why? Maybe human beings possess a peculiar and rather useless seriousness. We do not merely work hard. We work hard at looking as though we are working hard. So perhaps the next great innovation is not another machine. Perhaps it is this: Let us stop treating the appearance of seriousness as a virtue. A little idleness may not be laziness. It may simply be the time technology was trying to return to us.

Meme Monday! Today's cover image comes from the last thread . DEV is an inclusive space! Humor in poor taste will be downvoted by mods.

Luxury water can contain different minerals and taste noticeably different. But a remote source, alkaline pH, and high price do not necessarily mean better hydration.

Hackers are targeting internet-connected Siemens controllers used in water facilities around the United States.

Some fortnights the complaints scatter across a dozen topics; this one they clustered around two. Across the forums where paying AI users gather to compare notes, two things happened in the same window that left the same taste: the meter moved, and the mark landed. In both cases, something about the product changed without a clear announcement, and the users found out by running into it. Quotes sourced from: the OpenAI Developer Community and Hacker News. Every quote below was opened at its permalink and copied verbatim; each is listed with its handle, platform and date in the Sources section. We quote experiences, not verdicts — a forum post is one person’s felt reality, and we have framed it as exactly that. The $200 plan that lasted two days The loudest note this fortnight was the Codex usage drain. On the OpenAI Developer Community, a Pro subscriber posting as jjjnoronha laid out the damage plainly on 4 August: “I’m on the $200 Pro plan, and my weekly limit was completely exhausted in 2 days of serious development work. This is simply not viable.” He was refactoring a Rust backend with two agents running — one coding, one checking code quality — and described leaving Ultra mode on for three or four hours, which alone consumed 30% of his weekly allowance. But the complaint was not that the work was expensive; it was that the plan was sold with language suggesting far more headroom than what the cap delivered. “When someone pays for the highest consumer tier,” he wrote, “the expectation is capacity for sustained, professional work — not being locked out for the rest of the week after two days.” Others described something stranger. A user posting as kalani reported going to bed with 70% remaining after a Saturday reset, then waking up to find 0%. “Not like I had something running overnight, and yet all usage blocked until this next Saturday,” they wrote on 4 August. “Hard to trust a $200 / month service that is completely unpredictable about whether you’ll even be

Meme Monday! Today's cover image comes from the last thread . DEV is an inclusive space! Humor in poor taste will be downvoted by mods.

There is a comedy sketch from Bob & Tom that starts with a hilariously impossible promise: overnight delivery by train, from New York to Los Angeles. At one point, someone asks if they can really get a 2,000-pound package across the country overnight by rail. The answer is delivered with absolute confidence: “Norfolk and Waypal, overnight. Absolutely. Positively.” The name is doing some careful work. It lets you hear the phrase that nobody has actually said out loud. No way, pal. When I end up leading a project with six weeks left and something that feels like four months of work to do, I start the internal kickoff by telling the team to go watch that sketch. No other explanation. Just go watch it, then come back. Then I tell them: “Absolutely, positively, we will get you through it. There's Norfolk and Waypal, we are gonna to do it.” That does not mean we are going to do the thing exactly as it was originally promised. It means we are going to get through it. Absolutely. Positively. There is a difference. Laugh at the impossible first I think newer developers especially need permission to laugh at impossible requirements. An 800-pound gorilla from New York to Los Angeles overnight by train is impossible in a way that is easy to laugh at. A project that needs a full cloud environment, API work, a mobile application in the app stores, production deployment, security approvals, and a dozen other things in six weeks? That can feel less funny when it is sitting in your sprint board. But it may be just as impossible if we take the requirements literally. The first danger on a crunch project is shame. A junior developer can look at an impossible deadline and wonder if they are missing something. Maybe everyone else understands how this gets done. Maybe it is a talent problem. Maybe if they just worked harder, they could turn six weeks into twelve. Nope. Sometimes the work is just Norfolk and Waypal . Humor does not solve the problem. It lowers the temperature enough that

The island could capture billions of gallons of water a year if it implemented systems to catch it as it falls from the sky.

The mark flags anything Claude processed, even human writing it only edited.

Is Anthropic's new watermarking system a travesty? Some have taken to social media to complain that it is.

It's 4:50 on a Friday when the alert fires. A logging endpoint nobody remembers writing is copying customer records out of the database. Thirty-eight thousand of them. It's been quietly running for eleven months. You see it first. You understand it first: an old token, never rotated, someone's shortcut from a year ago that was never closed. You know exactly how to say it. In your own language, the sentence is already formed, precise, complete. Then the call starts. Eight people. The CTO, the client's legal counsel, someone from the German data protection office who joined without a word. Everyone is talking in English, fast. The lawyer says one thing, in a flat voice: under GDPR, you have seventy-two hours to report this from the moment you became aware. The clock started at 4:50. Now someone asks the only question that matters. "Do we know how they got in?" You know. You are the only one on the call who actually knows. You open your mouth and start to build the sentence in English: the token, was it "leaked" or "exposed," is it "left open" or "not revoked," and while you are still choosing the word, the CTO says "Maybe it was intentional. Someone inside." The room turns. Now they are looking for a person to blame, and the true, simple answer—that it was an old mistake, not a traitor—is still sitting in your head in the wrong language. Two minutes later someone has decided it was probably a rogue developer. The investigation will now point the wrong way for a day you do not have. You could have stopped it with three sentences. You had the three sentences. You just couldn't get them out fast enough while the clock ran. This is the part no one warns you about. In an incident, the language is not the small problem. It is the whole problem. The engineer who explains the breach clearly in the first five minutes controls what happens next. The one who can't watches other people decide, wrongly, in a language he understands perfectly but can't yet fight in. Test Yourself F

Reservoir has built an ultra-efficient water heater that can predict hot water demand, store energy, and detect plumbing leaks throughout a home.

Anthropic will extend support for watermarking AI generations for older models as well.

Meme Monday! Today's cover image comes from the last thread. DEV is an inclusive space! Humor in...

Cookie banners are still a nuisance. GDPR, the European privacy law, seems like a perfect example of...

Meme Monday! Today's cover image comes from the last thread . DEV is an inclusive space! Humor in poor taste will be downvoted by mods.