I think we are in a price discovery phase overall for human labor.
Just like financial markets, this phase is very volatile. But today’s price can look much different in 1, 2, 5, and 10 years.
Right now there’s a lot of opportunity to disrupt companies who are moving much slower since adoption can vary greatly.
But I think in a few years this meta will be overcrowded. The overall skill/productivity gap across companies will be reduced and the bar for productivity will be raised.
There’s room for taking profits now from the productivity gains but I don’t think it will last long.
If AI is really increasing productivity enough to reduce headcount right now, it won’t be in future. If all your competitors are using AI as effectively as you are, can you still do this?
The world’s demand for productivity is limitless. As of right now you still need someone to at least install Claude Code and run the binary.
I constantly see people saying Apple displays are a terrible value. Last Apple display I had was the Thunderbolt 27 but from now on I'm sticking with Apple.
I've had nothing but issues with non-Apple monitors as well. Customer service ime is non-existent if you need a repair. For something I rely on to get work done, I'm starting to think the premium is worth it.
I'm an American that has been living in Asia for a years.
I actually hated the web design at first but now I much prefer it and find it difficult to use American apps with the modern tech aesthetic now.
I noticed that I started to get annoyed doing things like filling forms. I feel like American apps tend to reduce complex flows into simpler decisions but requiring more steps. It feels like my brain is wired to want to see as much information at once now.
Go into planning mode and plan the overall refactor. Try to break the tasks down into things that you think will fit into a single context window.
For mid sized tasks and up, architecture absolutely has to be done up front in planning mode. You can ask it questions like "what are some alternatives?", "which approach is better?".
If it's producing spaghetti code, can you explain exactly what it's doing wrong? If you have an idea of what ideal solution should look like, it's not too difficult to guide the LLM to it.
In your prompt files, include bad and good examples. I have prompt files for API/interface design, comment writing, testing, etc. Some topics I split into multiple files like criteria for testing, testing conventions.
I've found the prompts where they go "you are a X engineer specializing in Y" don't really do much. You have to break things down into concrete instructions.
Just like financial markets, this phase is very volatile. But today’s price can look much different in 1, 2, 5, and 10 years.
Right now there’s a lot of opportunity to disrupt companies who are moving much slower since adoption can vary greatly.
But I think in a few years this meta will be overcrowded. The overall skill/productivity gap across companies will be reduced and the bar for productivity will be raised.
There’s room for taking profits now from the productivity gains but I don’t think it will last long.
If AI is really increasing productivity enough to reduce headcount right now, it won’t be in future. If all your competitors are using AI as effectively as you are, can you still do this?
The world’s demand for productivity is limitless. As of right now you still need someone to at least install Claude Code and run the binary.