I don't see anything on namecheap in there.
21,869 karma · joined April 20, 2007
Are you basing this on history and data because America is country of immigrants and its culture has survived for hundreds of years now by absorbing the cultures of immigrants and assimilating them within 1 generation. I haven’t looked at the numbers as closely but I feel that Canada and Australia have largely done the same. The countries with major issues are the ones with little to no experience with assimilation like France, Germany, or the UK
Also Japan and South Korea have tried nearly everything sans immigration like media (shows promoting Natalism), monetary incentives and other benefits, and so on, but nothing even made a dent except for immigration. Why do you think there are so many foreign workers in Japan now? For show?
Fertility imo is an even harder problem to solve than immigration issues because it’s not just a socioeconomic issue. Pollution with endocrine disrupters like BPA and PFAS are the likely culprits but they’re too embedded in our supply chain and there’s even less incentive to fix them
> It previously peaked at around 14.8% in the late 19th century. This started causing substantial anti-immigrant sentiment to emerge as it was felt to be having an overall negative affect on culture, society, labor, etc.
Yes, in the 19th century there was a lot of racism and prejudice directed towards the Irish, German, and Italian immigrants. Not surprisingly, they did not destroy US society or culture. Instead, the US absorbed respective parts of their cultures and assimulated all of their populations over decades. now they are an integral part of America
You've inadvertently described the US. A lot of our culture and traditions are a mismash of the immigrants who came before.
As for Japan being "pure" culturally, that's a fantasy conjured up by "nationalists" if you're generous or xenophobic racists when we're not.
The historical lineage of the Japanese includes continuous mixing with the Chinese and Koreans, alongside the Ainu and Ryukyuan. Elements considered central to traditional Japanese life were borrowed from neighboring civilizations like China, with Buddhism and rice cultivation being the most well known. I'm sure there are plenty of other examples, and we haven't even gotten to the modern era.
Pensieve is just spamming it with new python processes. When it's not eating up my CPU cycles, it keeps crashing my machine. Did you test this with larger code bases?
Pensieve isn't ready for prime time yet.
On Safari, fingerprinting doesn't survive in incognito mode. Same with Firefox.
Good thing I use different computers for different purposes, though it looks like using different browsers seems sufficient.
> a limited read of who you might be is someone who got into VR back then
Unfortunately, this description matches most of the other people in our demographics. I would go even further. Even if other people in our demographic experience modern VR, it’s still not enough motivation for them to wear a socially stigmatized face bucket for them. Anecdotally, I've bought several of my adult relatives VR headsets for xmas. Today, only one of them still uses it: one of their gen Alpha children
A lot of people in our circle are still delusional judging from the comments. Most adults do not accept VR. Meta failed even with their extremely generous subsidy, and more importantly even Apple failed convince adults with their world class industrial and UX team. Even their reputation as the most fashionable tech company wasn’t enough to overcome VR stigma even when they called it “spatial computing”
yes, and how do you prove that you both read and understand the code? saying you understand it does nothing especially when you no longer write the code.
> I have hundreds of repos at my job, some are in the 10s of thousands of lines of code, many are in the hundreds of thousands, and we still have a couple monoliths in the millions of lines of code range. Personal projects completely built with the LLM range in the 10s to 100s of thousands of lines.
Who cares because how would you be able to prove that? I can say the same thing.
> It's sustainable. LLMs have no problem working on all these projects and working on them across repos.
You have no proof of that especiall at scale. If anything all you're telling me, especially with your hard to believe anecdotes, is that you're not very experienced and you're very imaginative. It's also hard to believe anything that you've written because it makes no sense unless everyone above you isn't technical because what you're doing wouldn't fly anywhere that wasn't just a really small shop in the middle of nowhere with one or two apps.
> You haven't disproven shit using research papers using Claude 2
Compared to your anecdotes, those white papers are real work by credible professionals at respected institutions with real data that says definitively that YOU ARE WRONG. If you feel that they are wrong, feel free to prove it with specific examples and data. Right, you won't because of reasons...
I'm done humoring you. This was a complete waste of time.
I gave you real proof: real research in this field on the exact subject matter WITH data.
> You're really going to use papers from 2023 and 2024?
Vs what? Nothing? Ok, prove them wrong. anecdotes aren't proof
> I'm not even understanding your line of questioning here.
I've disproven your claim 3 times. You're not understanding anything because it goes against your narrative. If you didn’t write the code and you didn’t write any documentation about the code, then you have no proof that you know anything about said code base.
> Dude, maybe it's YOU guys working on small codebases
You're projecting. You can't vibe code large projects. It's not sustainable. if you are actually vibe coding actual large projects blind, it's only a matter of time before things go really wrong.
Anyone can make up a anecdote. In my case an agent was able to do a task in 10 min vs almost an hour without documentation. Citing an anecdote as “proof” isn’t good enough.
Here is my proof:
Hai, N. L., Nguyen, D. M., & Bui, N. D. Q. (2024). On the Impacts of Contexts on Repository-Level Code Generation. arXiv. https://doi.org/10.48550/arxiv.2406.11927 Cited by: 46
Jimenez, C. E., Yang, J., Wettig, A., et al. (2023). SWE-bench: Can Language Models Resolve Real-World GitHub Issues? arXiv. https://doi.org/10.48550/arxiv.2310.06770 Cited by: 4998
Zhang, F., Chen, B., Zhang, Y., et al. (2023). RepoCoder: Repository-Level Code Completion Through Iterative Retrieval and Generation. Proceedings of the 2023 Conference on Empirical Methods in Natural Language Processing. https://doi.org/10.18653/v1/2023.emnlp-main.151 Cited by: 698
> The code is the documentation.
No because it doesn’t capture the intent or the rationale why something was designed a certain way. Like why does it do some weird logic in this spot? What and why is being tested (a lot of tests are not straightforward)?
> Your two statements are contradictory here. Docs should be good enough so the llm doesn't need to read the codebase, but it should just summarize everything? You can't have both.
They are not contradictory. There’s this thing called a table of contents that summarizes large sections into a sentence or less, and links to said sections. Each section both large and small can also have a little paragraph that serves as a summary for the content to come. Sections can even have their own mini TOC. This enables an AI to be able to skip the parts it doesn’t need.
> All the LLM generated docs are causing friction
Ok, if you have a LLM generate your docs and you don’t vet it and make it your own, it doesn’t help you. Because again, how can you prove that you actually know the code base? Unless all you do is work on the same part of the same application day in and day out? Maybe the programs you’re working on is small or simple? How can you ever quickly ramp up when changing projects? This is assuming that you’re not just pairing vibe coding with manual monkey testing, or are you even validating anything when you’re not recording your goals in writing? Most of the cost in application development lies in maintenance and that is also where documentation benefits the most
But not as much of it since it has more context assuming the docs are good enough, which is my point.
> And I don't get where you think I'm telling everyone I don't have proof that I understand what my AI built.
Are you writing any of the code? Writing the tests? If not, then there isn’t any proof that you actually know the code base unless you have documentation. Even if you do know the code base one day, it’s not like you’re going to remember everything unless… you have documentation that quickly summarizes everything. Documentation isn’t just for AI. You’re likely also not going to be a company lifer so it’s also in your company’s interests for there to be documentation.
Also you’re telling everyone that you don’t have proof that you actually understand what your AI built. It may not bite your company now, but it will bite them one day.
This is a prime example of bad laziness. Tbf most companies like reducing as much cost as fast as possible while ignoring the potential downsides of it, so I don’t blame anyone taking on as many projects as possible.