I really want us to change the narrative here. It& #39;s not hard but the distinction is important. Knowing syntax does not make you a "good developer". But you should absolutely spend time getting familiar and comfortable with it. https://twitter.com/florinpop1705/status/1262463666282213381">https://twitter.com/florinpop...
This is something that frustrates me a lot as I try to engage more with the learning community in tech. A lot of the advice y& #39;all are receiving is doing you a disservice. It& #39;s trying to protect your feelings, but leaving you with the wrong expectations.
I want to be clear on who I& #39;m talking to. Because there are many different reasons to learn to code.

If you are trying to get a full time job as a professional developer, you should work on getting comfortable with syntax and you should be able to type reasonably fast.
The reason for this is that producing the code is only a small part of what you do in your job. You should work to get to a point where producing working code is something you can do quickly. So that you can then engage in the hard part of this job.
You need to get tasks done in a reasonable amount of time. Stop listening to those people who say "it doesn& #39;t matter as long as I can do the work". There is an expectation about how long things take. The longer you take to do things, it will start to reflect poorly on you.
You need to produce code at a speed that helps you collaborate with your peers. It could be direct pairing, producing a proof of concept to show someone, moving quickly to fix a critical big that you introduced into production. You need to be able to keep up with your team.
There are lots of other good reasons why you want to make sure that producing correct syntax is not a barrier for you. It& #39;s not important in itself. But get good at it. It is critical to your ability to move to the next level as a developer.
The upside is that this will get better if you commit to practicing. Write more code. Don& #39;t worry about it being "elegant" or "performance" or whatever. Just practice writing code that works. Do it until you get faster and it& #39;s not a chore. https://twitter.com/polotek/status/1049298721702170624?s=19">https://twitter.com/polotek/s...
I want to be clear about a couple of things. Being able to type "reasonably fast" is not a high bar. I know it& #39;s difficult to convey specifics, so people will fill in their worst case scenario. We& #39;re not talking about 90 wpm.
Also, I didn& #39;t mention touch typing, because it is *not* a requirement. Your typing technique is not at issue here. Even hunting and pecking is fine if you& #39;re able to do it reasonably fast. Though you will probably receive some cultural judgment because people are assholes.
You can follow @polotek.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled: