"I'm the author of Python Crash Course, which is published by No Starch Press: https://nostarch.com/pythoncrashcourse2e" - author and OP
"I'm the author of Python Crash Course, which is published by No Starch Press: https://nostarch.com/pythoncrashcourse2e" - author and OP
Part of the answer is that "you should learn to code beyond basic syntax, so that you can be better than the computer".
What it doesn't mention is that the state of AI is also going to continue improving, so you're possibly entering an arms race.
But professionally, we may have to find new activities.
It's not at all the same medium. Unless you consider that the whole point of oil painting is to imitate realistic pictures...
As someone else mentioned, people play chess for fun. People do things that they will never be as good at as computers.
I don't buy this idea that people need to be the "best" at something to enjoy it. Living that way dooms you to always being unhappy
That being said, people still do things they're outclassed at. We still have blacksmiths.
My brother has figured he can make a great living out of gardening for people. Yes robots will probably do this one day, but will they to the same level ? Really who knows anymore?
I’m actually sure a lot of the more wealthy people he works for kind of also just like him and his company too. He’s a youthful fun guy with a lot of creative ideas.
The silicone value push for eternal life via the singularity and trips to Mars seems to be mostly fuelled by cults and the need to keep shareholder happy / profits coming in.
I don’t know if anyone else cares that much, including the bots themselves. Time will tell.
It's really clear how useful these tools are to many experienced programmers, but I have no idea what impact they'll have on people who are new to programming. Most of the write-ups I've seen so far have been from people who already know how to code. I think it will be some time yet before we really see how effectively people who know nothing about programming are able to use these tools for learning.
You need the disclaimer. The reason why is because no one can read your intentions, they can only guess your intention from your actions.
By waiting until a 3rd party disclosed this information a little bit of trust was automatically lost.
I believe you, but this really isn't how maintaining credibility with a conflict of interest works.
You also don't have to add a "disclaimer". Just mention anywhere that you wrote a book on programming. You can say it abstractly like that if you don't want it to be an ad. Considering how much this experience informs your argument, it should be pretty easy to work in.
And thank you for your book. I've recommended it to many people.
I ended up doing a lot of reflecting about the comments people made. I think I've gotten used to writing for an audience that already knows that I'm the author of PCC, and I start to assume that anyone else will see that quickly as well. Do I really need to add a disclaimer any time I write about the process of learning to code, or its ongoing relevance? I'm not asking anyone to respond to that, especially on an old post, but that's the question that I kept coming back to for a while.
I realize that a post like this, shared with a larger audience, at this point in time, warrants a disclaimer. I've been a member of HN for over ten years, and I value my reputation here. I'm sorry if I misled anyone as they went into reading this post. I didn't add a disclaimer right away because I've made a habit of not responding too quickly to feedback on the internet when I'm not sure exactly how to respond.
I ended up adding a disclaimer, but that was well after this had dropped off the front page. I didn't put off adding a disclaimer to mislead anyone, it just took a while to think through all this. I will be more careful about which posts need to include a disclaimer from this point forward.
I know few people will see this, but if anyone sees the surrounding comments after the disclaimer is there I'd like them to see this context. Thank you all for the critical feedback. As uncomfortable as it is sometimes, it's part of what I've always appreciated about HN.