So far, no one else on board has developed symptoms, Maria Van Kerkhove, WHO acting director for epidemic and pandemic management, said at the press event. That’s “a good sign,” she said, but she added that the Andes virus has a long incubation period (around six weeks). Passengers are being advised to wear a medical mask when they leave their rooms.
At the same event, WHO director general Tedros Adhanom Ghebreyesus said he was in regular contact with the ship’s captain, who was reporting that “morale had increased significantly” since the ship started its journey to the Canary Islands.
What do we know about the Andes virus?
The Andes virus is the only hantavirus that is known to be transmitted between people. That transmission seems to rely on prolonged, intimate contact.
There was an Andes virus outbreak in Argentina around eight years ago. Between November 2018 and February 2019, there were 34 confirmed cases of infection, and 11 deaths. That outbreak was triggered when a person with symptoms attended a social gathering, said Tedros. “We are in a similar situation right now,” he said. “A cluster in a confined space with close contact.”
The fact that the 2018 outbreak was limited to 34 cases should be somewhat reassuring, he implied. “We believe this will be a limited outbreak if the public health measures are implemented and solidarity is shown across all countries,” he said.
How is hantavirus treated?
Unfortunately, we don’t have any specific antiviral treatments or vaccines for hantavirus. The WHO recommends early intensive care for people who develop symptoms. “This can save lives,” Anaïs Legand, WHO technical lead on viral hemorrhagic fevers, said on Thursday.
How did people get infected in the first place?
We don’t yet have an answer to that. But we do know that the couple who died had traveled through Argentina, Chile, and Uruguay on a birdwatching trip before they boarded the ship. That trip included visits to areas where species of rats that carry the Andes virus are known to live. The WHO is working with authorities in Argentina to try to retrace the couple’s movements on that trip.
Vibe coding has taken the development world by storm—and it truly is a modern marvel to behold. The problem is, the vibe coding rush is going to leave a lot of apps broken in its wake once people move on to the next craze. At the end of the day, many of us are going to be left with apps that are broken with no fixes in sight.
A lot of vibe “coders” are really just prompt typers
And they’ve never touched a line of code
Credit: Lucas Gouveia / How-To Geek
Vibe coding made development available to the masses like never before. You can simply take an AI tool, type a prompt into a text box, and out pops an app. It probably needs some refinement, but, typically, version one is still functional whenever you’re vibe coding.
The problem comes from “developers” who have never written a line of code. They’re just using vibe coding because it’s cool or they think they can make a quick buck, but they really have no knowledge of development—or any desire to learn proper development.
Think of those types of vibe coders as people who realize they can use a calculator and online tools to solve math problems for them, so they try to build a rocket. They might be able to make something work in some way, but they’ll never reach the moon, even though they think they can.
Anyone can vibe code a prototype
But you really need to know what you’re doing to build for the long haul
For those who don’t know what they’re doing, vibe coding is a fantastic way to build a prototype. I’ve vibe coded several projects so far, and out of everything I’ve done, I’ve realized one thing—vibe coding is only as good as the person behind the keyboard. I have spent more time debugging the fruits of my vibe coding than I have actually vibe coding.
Each project that I’ve built with vibe coding could have easily been “viable” within an hour or two, sometimes even less time than that. But, to make something of actual quality, it has always taken many, many hours.
Vibe coding is definitely faster than traditional coding if you’re a one-man team, but it’s not something that is fast by any means if you’re after a quality product. The same goes for continued updates.
I’ve spent the better part of three months building a weather app for iPhone. It’s a simple app, but it also has quite a lot of complex things going on in the background.
It recently got released in the App Store—no small feat at all. But, I still get a few crash reports a week, and I’m constantly squashing bugs and working on new features for the app. This is because I’m planning on supporting the app for a long time, not just the weekend I released it, and that takes a lot more work.
Vibe coders often jump from app to app without thinking of longevity
The app was a weekend project, after all
Credit: Lucas Gouveia/How-To Geek | ViDI Studio/Shutterstock
I’ve seen it far too often, a vibe coder touting that they built this “complex app” in 48 hours, as if that is something to be celebrated. Sure, it’s cool that a working version of an app was up and running in two days, but how well does it work? How many bugs are still in it? Are there race conditions that cause a random crash?
My weather app has a weird race condition right now I’m tracking down. It crashes, on occasion, when opened from Spotlight on an iPhone. Not every time does that cause a crash, just sometimes.
I don’t vibe code my apps that way, and I know many other vibe coders that aren’t that way—but we all started with actual coding, not typing a prompt.
Anyone can be a vibe coder, but not all vibe coders are developers
“And when everyone’s super… no one will be.” – Syndrome, The Incredibles. It might be from a kids’ movie, but it rings true in the era of vibe coding. When everyone thinks they can build an app in a weekend, everyone thinks they’re a developer.
By contrast, not every vibe coder is actually a developer, and that’s the problem. It’s hard to know if the app you’re using was built by someone who has plans to support the app long-term or not—and that’s why there’s going to be a lot of broken apps in the future.
I can see it now, the apps that people built in a weekend as a challenge will simply go without updates. While the app might work for the first few weeks or months just fine, an API update comes along and breaks the app’s compatibility. It’s at that point we’ll see who was vibe coding to build an app versus who was vibe coding just for online clout—and the sad part is, consumers will lose out more often than not with broken apps.
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
