What tools are you using? What settings? What process? What's your code review like?
I think this varies a lot. I find with a c++ project I'm working on that the LLM needs a lot of guardrails and guidance, and still gets a lot wrong. But with a vite/js project it often one shots complex and intricate changes in large codebases.
I gave it a try. Got a steam deck, tries steam os on my desktop.
I kept running into issues that took me time to solve. I understand that the only reason it took me time to solve these issues is because I'm new to it and that people who have been gaming on Linux for years already know how to solve them all. But what would happen was is I would sit down to play a game spend maybe an hour or two fixing issues and then after that I ran out of time to play the game. I kept this up for a couple months but honestly at some point I just gave up. Now I'm playing games on Windows again.
To be clear, I'm a huge proponent of Linux gaming. I just unfortunately am too busy these days to spend the time to get it to work.
The article fallaciously overstates the cognitive significance of shopping lists by misapplying general psychological concepts to a mundane habit. It relies on false cause and appeal to authority, conflating a standard compensatory memory mechanism with inherent intelligence. The author generalizes behavior, ignoring alternative motivators like memory deficits or anxiety. Furthermore, the piece lacks precise citations and improperly retrofits foundational research—such as academic note-taking studies—to fit its narrative. Ultimately, while it references factual cognitive capacity limits, the core claim that list-making signifies "sharper thinking" remains an unsupported editorial opinion rather than empirical science.
Any article that contains "Psychology suggests" isn't worth reading.
Writing actual code was maybe 10-20% of what I did. Most of it was meetings, design review, authorization requests, etc