| |
| ▲ | fragmede 3 days ago | parent [-] | | Respect to you. I ran out of energy to correct people's dated misconceptions. If they want to get left behind, it's not my problem. | | |
| ▲ | munksbeer 3 days ago | parent [-] | | At some point no-one is going to have to argue about this. I'm guessing a bit here, but my guess is that within 5 years, in 90%+ jobs, if you're not using an AI assistant to code, you're going to be losing out on jobs. At that point, the argument over whether they're crap or not is done. I say this as someone who has been extremely sceptical over their ability to code in deep, complicated scenarios, but lately, claude opus is surprising me. And it will just get better. | | |
| ▲ | int_19h 3 days ago | parent [-] | | > At that point, the argument over whether they're crap or not is done. Not really, it just transforms into a question of how many of those jobs are meaningful anyway, or more precisely, how much output from them is meaningful. | | |
| ▲ | munksbeer 2 days ago | parent [-] | | I don't agree. I've recently started using claude more than dabbling and I'm getting good use out of it. Not every task will be suitable at the moment, but many are. Give claude lots of direction (I've been creating instructions.txt files) and iterate on those. Ask claude to generate a plan and write it out to a file. Read the file, correct what needs correcting, then get it to implement. It works pretty well, you'll probably be surprised. I'm still doing a lot of thought work, but claude is writing a lot of the actual code. |
|
|
|
|
