There's very little, if any, incentive to do anything more securely than absolutely necessary. It is only a problem, when it is a problem and is treated that way in nearly every org I've worked in.
Reddit seems to have reversed course with making users sign in as well (or my adblock has updated and removed the forced login modal or something.) but my thought was simply: "Well, I guess I just won't view Reddit content anymore, big whoop."
> "Reddit seems to have reversed course with making users sign in as well (or my adblock has updated and removed the forced login modal or something.)"
I don't know if Reddit are doing it less now or not, but it's worth noting that it's always been somewhat hit and miss.
I suspect a mix of very data-driven testing (to try to show it to people who will login, and not show it to those who'll just bounce), and technical debt confusing things. But often it will vary not only from one person to another, but even for the same person between two different web browsers, or connected through two different IPs, or whatever.
Last week I was getting hit with the login requirement constantly, not at first but after scrolling a little bit or clicking on a link. This week, haven't seen that once.
No, it's like ordering a meal from door dash and saying "I got food." Using a tool does not mean you didn't do the thing you used the tool to do.
You're conflating "I made X" with "I personally did every part of X with no help," which is really not something to brag about as much as it is something that might fulfill your own personal sense of value.
That is almost to say that the only part of the project that matters is the code. But the code is only a tiny part. I take joy in describing the thing and bringing that vision to life.
> "I take joy in describing the thing and bringing that vision to life."
That's what management pats itself on the back for doing, the only difference being that it's taking credit for the work the LLM does instead of taking credit for the work of human subordinates. The trope of the "ideas guy" is derided for a reason.
I mostly agree with this sentiment, and have a hard time describing anything LLM generated as "mine". However, would you say that the designers at Apple, or Steve Jobs for example didn't "bring the Macintosh to life" because they didn't work on any of the engineering or code? It's a hard line to draw.
Leading a collaborative effort can obviously be described as bringing the project to life. People want to feel like they are collaborating with LLMs and are still the visionary in the process. As the performance of these systems improves that becomes less and less the case.
E.g. if Steve Jobs had simply handed a slip of paper to a team that said "make a new kind of computer", then no, he would not have brought the Macintosh to life.
No, its a very easy line to draw. Rallying and bringing together humans is COMPLETELY different than having an LLM do something. They are not comparable.
I completely disagree. The mindset that leaves you trapped is focusing on the destination and not the journey. I will never paint like Michaelangelo but it feels good to apply myself to the pursuit of painting, even if the resulting paintings aren't good.
"That is almost to say that the only part of the meal that matters is the cooking. But the cooking is only a tiny part. I take joy in describing the food I want and bringing that vision to life."
What are you trying to say?
There are a ton of people who care more about being able to make something they're imagining real than engaging in the process necessary to make it happen. This applies to food just as well as it does to software
It's a bad analogy, because unless you're cooking a recipe, cooking is about all the small decisions you're making during the process which could apply both to coding or the design aspect of building software with an LLM.
Except most vibe coders proudly admit that they don't even look at the code anymore. Can you really make those small decisions during the cooking process if you're not touching or even looking at the food at any point?
The distinction that can be drawn is between the code, and the user experience of the software. You may argue that the two are inextricably linked, but I don’t think that can be treated as an absolute principle.
I'd also say I've worked with many engineers over the years who were more focused on the software engineering aspect that the user experience. Depending on the use case for the software, that can absolutely end up being the limiting factor.
I agree if you one-shot something, but that hasn't been my experience at all (unless the initial prompt is so detailed that creating it took considerable time).
For me it's more like being a chef but having a cook to cut up things and start cooking them, but you decide when it's done, what spices to put, and how to serve it - arguably the most fun and creative part.
I don't agree. That would imply they asked for a piece of software and the LLM one-shotted it, but that's absolutely not what's happening in the vast majority of cases. If two people vibe code the same tool from the same high level desciption the results are going to be quite different.
LLMs are nondeterministic, good luck trying to measure performance at all, much less over time.
Lets say it has gotten worse? What are you going to do about it? Jump to Codex? Then what happen if you perceive that to be getting worse? Jump back to Claude? One of the many problems with these tools.
I remember when I had to boot up an old windows machine because TurboTax refused to run on a Linux (might have been something related to flash as well... been too long to recall), then I just ran Windows in a VM, then extensions allowed me to do User-Agent spoofing (honestly should have thought of this sooner), and now they don't seem to care at all. I did my taxes on OpenBSD last year.
One thing that I'm actually excited about regarding AI is that the pointless policy checkboxes that have never been effective in adding any actual security are even less so effective now that everyone can wield their very own security researcher.