Earlier quoted context omitted.
You were probably deficient in RESEARCH skills before. No offense to you, since I was also like this once. LLMs research and put the results on the plate. Yes, for people who were deficient in research skills, I can see 2-3x improvements. Note1: I have "expert" level research skills. But LLMs still help me in research, but the boost is probably 1.2x max. But Note2: By research, I mean googling, github search, forum s…
please don't change your comment constantly (or at maybe add UPDATE 1/2/3), because you had different words before, like you were saying something in this fashion: * you probably lack good RESEARCH skills * I can see at most 1.25x improvements - now it is 2-3x By updating your comment you are making my reply irrelevant to your past response
Labor market impacts of AI: A new measure and early evidence
301–310 of 584 posts
Re: Labor market impacts of AI: A new measure and early evidence
#302I'm working on a project right now, that is heavily informed by AI. I wouldn't even try it, if I didn't have the help. It's a big job. However, I can't imagine vibe-coders actually shipping anything. I really have to ride herd on the output from the LLM. Sometimes, the error is PEBCAK, because I erred, when I prompted, and that can lead to very subtle issues. I no longer review every line, but I also have not yet got…
> However, I can't imagine vibe-coders actually shipping anything. I'm a vibe-coder, and I've shipped lots! The key is to vibe-code apps that has a single user (me). Haven't coded anything for 15 years prior to January too.
Re: Labor market impacts of AI: A new measure and early evidence
#303One of the more interesting takes I heard from a colleague, who’s in the marketing department, is that he uses the corporate approved LLM (Gemini) for “pretend work” or very basic tasks. At the same time he uses Claude on his personal account to seriously augment his job. His rationale is he won’t let the company log his prompts and responses so they can’t build an agentic replacement for him. Corporate rules about s…
It's not his company that will train using his prompts. It's the personal account, unless it is fully paid and he's opted out of training on his prompts.
I’d argue this can’t be trusted either considering the AI labs already established they’re willing to break laws (copyright) if the ultimate legal consequence is just a small fine or settlement.
Re: Labor market impacts of AI: A new measure and early evidence
#304Re: Labor market impacts of AI: A new measure and early evidence
#305People who are saying they're not seeing productivity boost, can you please share where is it failing? Because, I am terrified by the output I am getting while working on huge legacy codebases, it works. I described one of my workflow changes here: https://news.ycombinator.com/item?id=47271168 but in general compared to old way of working I am saving half of the steps consistently, whether its researching the codebas…
The last time I tried AI, I tested it with a stopwatch. The group used feature flags... if (a) { // new code } else { // old code } void testOff() { disableFlag(a); // test it still works } void testOn() { enableFlag(a); // test it still works } However, as with any cleanup, it doesn't happen. We have thousands of these things lying around taking up space. I thought "I can give this to the AI, it won't get bored or c…
Re: Labor market impacts of AI: A new measure and early evidence
#306Earlier quoted context omitted.
I work as an ML engineer/researcher. When I implement a change in an experiment it usually takes at least an hour to get the results. I can use this time to implement a different experiment. Doesn't matter if I do it by hand or if I let an agent do it for me, I have enough time. Code isn't the bottleneck. I also heard an opinion that since writing code is cheap, people implement things that have no economic value wit…
+1 on the economic value line. Not everything needs to be about money but if you get paid to ship code it's about money. And now we have coworkers shipping insane amounts of "features" because it's all free to ship and being an engineer, it ends there. Only it doesn't, there's product positioning, UX, information architecture, onboarding and training, support, QA, change management, analytics, reporting… sigh
Tip to budding software engineers: try to not work in these sort of places, as they're about "looking busy" rather than engineering software, where the latter is where real long-lasting things are built, and the former is where startup founders spend most their money.
The last paragraph is where the tricky and valuable parts are, and also where AI isn't super helpful today, and where you as a human can actually help out a lot if you're just 10% better than the rest of the "engineers" who only want to ship as fast as possible.
Re: Labor market impacts of AI: A new measure and early evidence
#307Earlier quoted context omitted.
You were probably deficient in RESEARCH skills before. No offense to you, since I was also like this once. LLMs research and put the results on the plate. Yes, for people who were deficient in research skills, I can see 2-3x improvements. Note1: I have "expert" level research skills. But LLMs still help me in research, but the boost is probably 1.2x max. But Note2: By research, I mean googling, github search, forum s…
no worries, I do not get offended quickly. But I also think you are overestimating your RESEARCH skills, even if you are very good at research, I am sure you can't read 25 files in parallel, summarize them (even if its missing some details) in 1 minute and then come up with somewhat working solution in the next 2 minutes. I am pretty sure, humans can't comprehend reading 25 code files with each having at least 400 li…
In this example, if the 25 files are organized nicely, and I had I nice IDE that listed class/namespace members of each file neatly, I might take 30 minutes to understand the overall structure.
Morever, If I critically analyzed this, I would ask "how many times does this event of summarizing 25 files happen"? I mean, are we changing codebases every day? No, it's a one time cost. Moreover, manually going through will provide insight not returned by LLM.
Obviously, every case is different, and perhaps you do need to RESEARCH new codebases often, I dunno!
Re: Labor market impacts of AI: A new measure and early evidence
#308Earlier quoted context omitted.
You were probably deficient in RESEARCH skills before. No offense to you, since I was also like this once. LLMs research and put the results on the plate. Yes, for people who were deficient in research skills, I can see 2-3x improvements. Note1: I have "expert" level research skills. But LLMs still help me in research, but the boost is probably 1.2x max. But Note2: By research, I mean googling, github search, forum s…
Ok Mr. Expert Level Researcher, go back and read the comment of parent again to find out that it has nothing to do with deficiency in research skills.
Re: Labor market impacts of AI: A new measure and early evidence
#309Earlier quoted context omitted.
Advertisement is not that effective in general or just for certain channels, i.e. TV? Also what are you existing to?
So my understanding - from a friend at WPP who told me the same and from a freakonomics episode - is that advertising was wildly oversold before digital. When the metrics arrived with digital, they saw that advertising, in some ways, was just not as effective as they’d hoped. In some ways the ROI wasn’t there. Seth Godin agrees. He says that advertising in the digital era could be as simple as just having a good prod…
Re: Labor market impacts of AI: A new measure and early evidence
#310People who are saying they're not seeing productivity boost, can you please share where is it failing? Because, I am terrified by the output I am getting while working on huge legacy codebases, it works. I described one of my workflow changes here: https://news.ycombinator.com/item?id=47271168 but in general compared to old way of working I am saving half of the steps consistently, whether its researching the codebas…
However now that it's in the beta stage the amount of issues and bugs is insane. I reviewed a lot of the code that went in as well. I suspect the bug fixing stage is going to take longer than the initial implementation. There are so many issues and my mental model of the codebase has severely degraded.
It was an interesting experiment but I don't think I would do it again this way.