859 karma · joined September 9, 2024
Google launches largest office in India https://www.entrepreneur.com/en-in/news-and-trends/google-la...
Microsoft India head says no layoffs in India https://timesofindia.indiatimes.com/technology/tech-news/mic...
The significant shift comes a lot from how this country has massive systems in place to perform wage arbitrage through IT consultancies. Compared to Chinese industrial outsourcing (which requires capex), wage arbitrage is pure profit in that there's almost no overhead. So these IT companies got phenomenally rich. These companies have a US branch, usually having a manager based in the US while the others are based in India. So it's no longer getting the best and brightest through H1B, but just a way to make money off the vast difference in economic conditions between a third and first world country. And there's a direct incentive to depress the economic conditions of workers, because that's money right there. Then this goes into overdrive when many US companies realize it's even cheaper to do it themselves and set up shop in this country.
What happened to the US industrial base/blue collar workers is happening right now to white collar workers, except it'll go much faster because there's no physical equipment to move.
https://www.thehindu.com/sci-tech/technology/microsoft-confi....
1) +20k for those with advanced degrees
2) +80k L-1 visas, these are international transfer visas heavily used by WITCH companies. These are unlimited.
3) +160k OPT visas, these are 3 year work visas for international students who took a masters or PhD in the USA. This in particular is unlimited and has been growing at ~20% annually compounded for some time
4) +150k H4 visas, which is a dependent visa for immigrants who have some other visa
5) +65k F4 visas, which are for siblings of immigrants
Net is several hundreds of thousands of white collar workers enter the USA every year. This is an absolutely astounding amount, especially in proportion to how often it's talked about.
More fundamentally, SRS isn't a superpower because it's just very specific to creating a direct prompt retrieval. Generalization is poor. Even creating a graph of knowledge, is a chain of edges between bits of knowledge, isn't done very well here.
And I suspect there's a very deep, fundamental difference between recollection knowledge and logical-modeling knowledge. Recollection seems very similar to a dictionary access, and if you recorded the time to recall in humans I suspect they'd all be constant. But learning the knowledge of a logical model, like of a mathematical concept, appears to be vastly different and have very different time to compute.
Proponents of SRS will point out logical models need facts as well, like formulas, lemmas, etc. Which is true. But if you already grasped it before you'd grasp it faster the second time. So the practical use of SRS is a significant step above having a very well sorted and labeled notebook, but still way below becoming a genius.
The problem with it takes several times more effort to verify code than to write it. This makes intuitive sense if you consider that the search space for the properties of code is much larger than the code for space. Rice theorem's states that all non trivial semantic properties of a program are undeniable.
How wise it is to buy Cursor is another question. Current valuation has them at 100x revenue. And I suspect agentic products will be a lot less cash flow positive than traditional SaaS because of the massive cost of all that constant codebase context and stream of code.
Um, isn't that just a fancy way of saying it is slightly better
>Score of 6.81 against 6.66
So very slightly better
1) Identify and resonate deeply with developer issues (like Git, Linux)
2) Focus on executing a usable product in a very short time
So combined it's a really potent ability. If he had the personality he'd probably be a really great founder, but he has chosen to open source all his stuff.
A) Largely only want AI when they are blocked, and not all the time B) Want to consider options (which is how writing happens all the time, IMO)
Is really what sets your product apart. So I'm curious, how did you get these insights? Were you a writer and instinctively knew of these, and so you dogfooded your own product? Or did you do a YC style feedeback loop to writers to find this differentiator?
https://openai.com/index/learning-to-reason-with-llms/
The paper tested it on o1-pro as well. Correct me if I'm getting some versioning mixed up here.
1) AI undoubtedly has utility. In many agentic uses, it has very significant utility. There's absolute utility and perceived utility, which is more of user experience. In absolute utility, it is likely git is the single most game changing piece of software there is. It is likely git has saved some ten, maybe eleven digit number in engineer hours times salary in how it enables massive teams to work together in very seamless ways. In user experience, AI is amazing because it can generate so much so quickly. But it is very far from an engineer. For example, recently I tried to use cursor to bootstrap a website in NextJS for me. It produced errors it could not fix, and each rewrite seemed to dig it deeper into its own hole. The reasons were quite obvious. A lot of it had to do with NextJS 15 and the breaking changes it introduces in cookies and auth. It's quite clear if you have masses of NextJS code, which disproportionately is older versions, but none labeled well with versions, it messes up the LLM. Eventually I scrapped what it wrote and did it myself. I don't mean to use this anecdote to say LLMs are useless, but they have pretty clear limitations. They work well on problems with massive data (like front end) and don't require much principled understanding (like understanding how NextJS 15 would break so and so's auth). Another example of this is when I tried to use it to generate flags for a V8 build, it failed horribly and would simply hallucinate flags all the time. This seemed very likely to be (despite the existence of a list of V8 flags online) that many flags had very close representations in vector embeddings, and that there was almost close to zero data/detailed examples on their use.
2) In the more theoretical side, the performance of LLMs on benchmarks (claiming to be elite IMO solvers, competitive programming solvers) have become incredibly suspicious. When the new USAMO 2025 was released, the highest score was 5%, despite claims a year ago that SOTA when was at least a silver IMO. This is against the backdrop of exponential compute and data being fed in. Combined with apparently diminishing returns, this suggests that the gains from that are running really thin.