标签：#watercooler

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.

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

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

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.

You wouldn't believe what they were preaching about in church this week. Normally, these days you walk in expecting to be bombarded with Bible verses and the classic "tell your neighbour to tell their neighbour" routine. But guess what, my preacherman was on point. The whole sermon was about how to realise your full potential and grow your career. And here's the interesting part: it wasn't aimed at the start-your-own-empire crowd. It was for the intrapreneurs , the people who'd rather climb high inside someone else's company than run their own thing. If that's you, this one's for you. So let me try to break it down in my own words, with a few of the insights I picked up from the preacherman (and a couple of my own). Let's begin. What is it that we actually need to do to discover ourselves and reach our full career potential? 1. Start Early There's a popular idea that life comes in four quarters: 0–25 — the learning phase 25–50 — the earning phase 50–75 — the serving / enjoying phase 75+ — the reflecting phase (You'll see different versions of this floating around, with different age bands; it's a framing, not a law of physics, so take the exact numbers loosely.) The first quarter is where the magic is supposed to happen. This is your discovery phase. You're meant to learn as much as you can, try different things, fail, get back up, and try again. This is where you find out who you actually are. If you spend this quarter as a couch potato, there's a good chance you end up miserable and stuck in the wrong career. Your environment matters too. Get born in India, you'll probably force yourself onto a cricket pitch, even if your real gift was on a tennis court; therefore, you have to force yourself into trying quite a number of things. For the parents reading this: give your kids as much exposure as you possibly can. Let them join different clubs. Let them be around different kinds of people. Someone out there might spot a talent you never even knew your child had. A lot

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

Hi, I'm Cesar, a Senior Software Engineer with 10+ years of experience. In 2023, I got sick and...

Introduction: The Question Beneath All Questions I think a lot of people are searching for the same thing but using different words. Some people call it: success happiness freedom purpose wealth enlightenment achievement legacy But underneath all of it is a deeper question: "What is worth dedicating my life to?" That question is harder than finding a job. It is harder than making money. It is harder than becoming successful. Because even if I get everything I think I want, I still have to answer: "Why did I want it?" Chapter 1: The Strange Reality of Modern Life We live in one of the wealthiest civilizations in human history. We have: technology beyond anything past generations could imagine medicine that would look like magic centuries ago instant communication across the planet access to unlimited information Yet so many people feel like they are barely surviving. Why? Because humans were built for survival. Our brains evolved to constantly ask: What could go wrong? How do I stay safe? How do I belong? Am I enough? Am I falling behind? The threats changed, but the machinery stayed the same. Ancient humans worried about predators. Modern humans worry about: money careers status loneliness comparison identity the future The battlefield moved from the physical world into the mind. Chapter 2: Money Is Not Evil — Money Is Power There is a tendency to pretend money does not matter. That is false. Money changes what is possible. Money can buy: freedom of time experiences travel education tools comfort opportunities the ability to help others A person with resources has access to a larger range of possible lives. Wanting money does not automatically mean being greedy. Sometimes wanting money is really wanting: freedom adventure security creativity proof that you overcame something The question is not: "Do I want money?" The better question is: "What will I use money for?" Money is a tool. A hammer can build a house or destroy something. The tool is not the meaning. The pu

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

I have been building software for sixteen years. I have four ambassador titles I earned honestly. And last week I sat at my desk at eleven at night, certain that everyone else my age was further ahead than me. You know that feeling. The one where you scroll past someone's launch, someone's promotion, someone's clean little success, and a cold voice says you should be there by now. It does not care what you have done. It only points at what you have not. For most of my career I treated that voice as a problem to solve. If I could learn one more tool, ship one more thing, earn one more title, it would finally go quiet. So I did. I learned the tools. I shipped the things. I earned the titles. The voice did not go quiet. It moved the finish line and waited for me there. Here is the opinion I wish someone had handed me a decade ago. Feeling behind is not a bug in you. It is the tax you pay for caring about the work. The people who feel the most behind are almost never the ones who are actually behind. They are the ones paying attention. They see the gap between what they made and what they meant to make, and that gap never closes, because the moment you get better, your taste gets better too. The gap is not evidence that you are failing. The gap is proof that you still have standards. I know engineers with twenty years and a wall of real accomplishments who quietly feel like frauds. I know brilliant people five years in, staring at a job market that feels brutal, convinced everyone else got a memo they missed. None of them are behind. All of them are exhausted from running a race that has no finish line, on a track only they can see. The comparison is rigged, and it is worth saying why. You compare your inside to everyone else's outside. You know your own doubt, your own half-finished drafts, your own two in the morning. You see their launch, their title, their highlight. You are matching your bloopers against their trailer, and then calling yourself slow. So what change

Nice to meet you! I'm Andrew It's been a year since I joined the community. I started developing a bit earlier, and changing my career just by learning and practicing is far from what I had planned. I cannot help but be thankful for each course and tutorial, and each developer and tutor who has shared some knowledge and wisdom with me. It is still too early to know exactly what I will fix, build, or vibe to improve the world, but I will do my best... print ( " Hola mundo, aquí vamos! " ) Follow my journey on GitHub "I'm curious to hear from others—what was the biggest challenge you faced during your first year of coding? Or, if you're just starting, what's one thing you're excited to build?"

A post on X last week: "The fact that people can't even reply to posts without AI anymore says a...