Couldn't the same statement, to some extent, be applied to using a sorting lib instead of writing your own sorting algorithm? Or how about using a language like python instead of manually handling memory allocation and garbage collection in C?

> What I want above all is AI that helps me become better at my job and continue to build skills and knowledge

So far, on my experience, the quality of what AI outputs is directly related to the quality of the input. I've seen some AI projects made by junior devs that a incredibly messy and confusing architecture, despite they using the same language and LLM model that I use? The main difference? The AI work was based on the patterns and architecture that I designed thanks to my knowledge, which also happens to ensure that the AI will produce less buggy software.

If you disagree with the above statement, try replacing "AI" with "Docker", "Kubernetes", "Microservices architecture", "NoSQL", or any other tool/language/paradigm that was widely adopted in the software development industry until people realized it's awesome for some scenarios but not a be-all and end-all solution.

While it's true that lots of those old appliances are easily fixable, depending on how old they are it's better to replace due to other factors.

I just recently replaced my 10 years old washing machine instead of fixing it. I was absolutely surprised by the difference. The newer one uses less electricity, less water, washes and dries in half the time, and is absolutely silent.

I only hope it lasts as long as the old one.

How many times have you read a story card and by the time you finished reading it you thought "It's an easy task, should take me 1 hour of work to write the code and tests"?

In my experience, in most of those cases the AI can do the same amount of code writing in under 10 minutes, leaving me the other 50 minutes to review the code, make/ask for any necessary adjustments, and move on to another task.

In less than 5 minutes Claude created code that: - encapsulated the api call - modeled the api response using Typescript - created a re-usable and responsive ui component for the card (including a load state) - included it in the right part of the page

Even if I typed at 200wpm I couldn't produce that much code from such a simple prompt.

I also had similar experiences/gains refactoring back-end code.

This being said, there are cases in which writing the code yourself is faster than writing a detailed enough prompt, BUT those cases are becoming exception with new LLM iteration. I noticed that after the jump from Claude 3.7 to Claude 4 my prompts can be way less technical.

Does this mean that you also don't use your bank Android/iPhone APP? So your entire financial life is handled via a browser?

Treat the AI as a freelancer working on your project. How would you ask a freelancer to create a Kanban system for you? By simply asking "Create a Kanban system", or by providing them a 2-3 pages document describing features, guidelines, restrictions, requirements, dependencies, design ethos, etc?

Which approach will get you closer to your objective?

The same applies to LLM (when it comes to code generation). When well instructed, it can quickly generate a lot of working code, and apply the necessary fixes/changes you request inside that same context window.

It still can't generate senior-level code, but it saves hours when doing grunt work or prototyping ideas.

"Oh, but the code isn't perfect".

Nor is the code of the average jr dev, but their codes still make it to production in thousands of companies around the world.

Yes, it WON'T produce senior-level code for complex tasks, but it's great at tackling down junior to mid-level code generation/refactoring, with minor adjustments (just like a code review).

So, it's basically the same thing as having a freelancer jr dev at your disposal, but it can generate working code in 5 min instead of 5 hours.

I was trying to prototype a system and created a one-pager describing the main features, objectives, and restrictions. This took me about 45 minutes.

Then I feed it into Claude and asked to develop said system. It spent the next 15 minutes outputting file after file.

Then I ran "npm install" followed by "npm run" and got a "fully" (API was mocked) functional, mobile-friendly, and well documented system in just an hour of my time.

It'd have taken me an entire day of work to reach the same point.

When Whatsapp launched, SMS still wasn't free, the exception being some carriers that offered "free" SMS to numbers of the same carrier if the sender was on a premium coverage plan. In sum, majority of the population was still paying $0,10-$0,20 despite already having data plans. So it was an easy win for WhatsApp.

As someone who has done physical therapy for different issues, this is spot on. Lower back issues were actually due to weak hamstrings, and ankle issues due to weak calves.

Doing daily mobility and strength exercises as part of my mourning routine improved my health as a whole. A couple months in, and all random aches, pains, and soreness that i'd feel upon waking up or during the day were simply gone. And it only takes me 30 minutes a day. It's a pretty awesome alternative to doom scrolling.