Youre jumping to conclusions. Bigger companies missed bigger problems in their reviews and QA. Why should they be wanting their cursorrules in there, and what kind of mental gymnastics is it to conclude that they are vibecoding based on that. You don't need it committed, you don't even need it to be in the project directory.
x1gma
It's definitely badly communicated and suspicious, I just called out jumping to extreme conclusions based on a suspicion alone. There probably will be people who are gonna review the code and see how much of it is probably LLM generated, and then we will know. I still think that it's pretty much impossible to vibe code something on that scale, but I haven't seen their cursorrules either.
Absolutely, I do them daily, what about you?
Just because they are using Cursor, it doesn't mean that they are vibe coding. Anyone grabbing their pitchforks for that and screaming "they are vibecoding" only shows their own incompetence.
If they would be vibecoding, their whole software would've gone to shit long ago.
Just because some random people without an engineering background are using vibecoding to push their broken slop, it doesn't mean that any kind of AI assisted coding is bad.
Unless there are those who need certain words for their jobs, I can kinda understand why Microsoft wouldn't want emails from work addresses to go out with political agendas... for either side.
Sure. Then block both sides, and not only the one not bringing you money.
Work emails should just be about work. Too many people use their work emails like a personal email... with their banking, shopping, etc. That's what personal email addresses are for.
No one uses their company email for their personal banking, simply for the reason because if you'd leave, you'd lose your access, and since most companies run behind firewalls, vpns, 2fa tokens and similar additional credentials, it's simply harder to use.
This policy should go for many non-work related topics too. IT can unblock the words for certain users who need to use them for their job.
Of course, let's waste resources to maintain idiotic blocklists that are out of date the moment they are rolled out, and additional resources to make the blocklist actually work. Palestine, p4lestine, pale s tine, p a l e s t i n e, paleztine. Need more?
You're not at work for someone with this kind of unhinged mentality watching you working for 8 hours a day straight with no breaks and no distractions. You're there to get your work done. In my current team, we've had the best ideas talking about our problems at the coffee machine. I personally focus best when I have music on. We're doing sports together once a week on a company fitness incentive, which boosted our team dynamic massively. None of this would be possible in such a controlled environment.
"Googling a lot while coding" is not even remotely close to vibe coding, please don't gaslight yourself into that.
When you read up on things, you know what you're looking for. You read a potential solution (e.g. part of a documentation, an example, someone else's solution, a solution to a similar problem), you think about it and transfer that to your own problem, with your own code, with your own thoughts.
Using AI support is totally fine too - it's a smarter code completion, nothing more. It might spit out something wrong, something partial, something good. You might ignore it as with the regular completion. In the end, it's still you thinking about it, modifying it until it works, and doing your thing.
"Vibe coding" is basically saying tech jesus take the wheel. And it might go well for someone who cannot code, who managed to create their small game or some website. It will go horribly wrong for any project handling user data, sensitive data, or something that needs to be maintained after. We've had more than enough examples of that.
The worst kind of shorts are the ones pretending to present serious content.
Of course you crammed all related parts about any current war into a maximum of 60 seconds or summarized the latest news.
Fuck you to anyone doing this.
Quality journalism:
Yesterday, we reported on actors using Russian IP addresses to breach the National Labor Relations Board immediately after DOGE engineers obtained "God-tier" access. According to whistleblower Daniel Berulis the intruders used newly created DOGE credentials and techniques “consistent with sophisticated Russian intelligence operations.”
Shocking, if inexperienced, young idiots get to do whatever they want in critical systems, shits gonna hit the fan.
Any IT system DOGE touched should be considered compromised, not because of "sophisticated" state agents, but because you've had those idiots touching it.
Remember the first days of post-Musk twitter? Yeah, now imagine that with older, more brittle systems, way less experience in the staff, more AI slop, less time and way more god complex.
Also, still waiting for the day those "journalists" will learn that an IPs geolocation does not have to be the actual source...
Und du denkst das interessiert unsere "Partei der Mitte" die auf über hundert Seiten aufgeführt hat welche deregulierenden, verfassungswidrigen und hirnlosen - von moralisch-ethisch verwerflichen mal gar nicht erst angefangen - Maßnahmen sie treffen möchte?
Da wird die genauso rückgratlose EU bestimmt helfen. /s
How is this more repairable than any other cable? Their repair instructions are literally "get a bunch of tools, cut that thing open, resolder and reseal". Is their "repairable" aspect that they are only using shrink tubing on the outside of the plugs saving money on material too? Yeah, I bet I'll need to repair those a lot.
Also, those are some fucking expensive cables.
Why the fuck is everyone gaping their assholes for DOGE's fascists?
Money. Musk probably just buys people to grant his moron squad access.
What an amazing conclusion, and the best part is, no matter what you've been waffling about before - it's always right. Can we stop calling random things AI slop and telling to be careful bEcAuSe iTs Ai sLoP, and go back to being cautious until something has been reviewed properly? Being careful with random stuff from GitHub you install and run in your private network?
Your whole comment may have been AI slop as well. "From a quick glance at the repo", you should be careful! Thanks, Sherlock.