Earlier quoted context omitted.
If you were curious about learning the guitar, would you first purchase the best 10,000$ guitar you could find at your local shop? No; you'd find some cheap guitar to play on initially to see if you could actually make a habit out of practising the guitar. Now if it turned out that you didn't like it, you have minimized your financial losses. Similarly, some people don't know English. Maybe they're curious about prog…
> And? Does that give your argument more weight? Yes because he is potentially one from the target audience of this. If somebody isn't willing to put in the tiny bit of effort to learn the tiny bit of english required for programming, they're not willing to put in the huge amount of effort that is required to learn programming anyways. We have enough horribly documented code that needs maintenance, there is no need t…
No, because he already knows English.
The proclamation "We should tax the rich less" is a self-serving sentence whether it comes from someone who was born into wealth, or it comes from someone who became rich later in life.
> If somebody isn't willing to put in the tiny bit of effort to learn the tiny bit of english required for programming, they're not willing to put in the huge amount of effort that is required to learn programming anyways.
I think you're coming from the viewpoint of "what would I do to learn programming if I had started from scratch today". But like I've argued, this is not a good view of the process of learning to program! It's more like you are vaguely interested in some discipline or skill, or might need it for something, and so you want to dip your toes in it. You have no idea whether you will like it or not, or how far you will take it. To put up all these demands -- what they should learn and focus in order to in time become your ideal programming colleague -- is just too much to demand of someone who is just exploring a new world to them and don't know where it will take them, if anywhere. How about they learn to actually put things like for-loops, if-statements and such together, before you demand that they should embody all the skills to write great documentation, use best practices, and whatever else?
Just think of all the different things that are "bad practices" that even experienced developers can manage to do with a clear conscience. You can't pick one aspect and demand that a green programmer should have the personality and disposition to know beforehand that such things are "bad practices". People can learn and change.
But why even bother. These topics just devolve into downvote/upvote battles.