PSA for people who #code:
Looking stuff up does NOT make you bad at coding.
"Not having to look up stuff" is NOT the benchmark for a good coder, especially as coders have to look up stuff ALL THE TIME!
And I don't mean highly advanced stuff, but stuff like "How does division work again?" or "What's that function called?" or my personal favorite "How to I nest for loops in list comprehensions?".
It's ok if you have to look up stuff!
@maunzikation That's ok, too. Copy stuff and later maybe learn how it works. Or sometime in the future, so other stuff made you understand how it works and then it clicks. Or not.
Which is ok too.
(See "Me having to look up nested for loops in list comprehension for YEARS now." XD )
@minx I don't think I have ever done anything non-trivial and not had to look up some sort of documentation.
I still look up how for loops work in whatever language I am using if I don't have an example in the code already.
@minx Whenever I code anything and it runs correctly with no noticable bugs the first time scares me. The first time I can code anything without looking up every-other-chunk of what I'm writing just to make sure I'm using it right, I will be feeling terrified and/or realize I've been using this one particular language & framework for far, far too long.
@minx cc @jamey I was mob programming earlier this week and we had to look up the difference between `equal` and `eql` in our assertion library, and then clarify the difference between 'deep' and 'strict' equality… Because remembering those small details is hard, and not terribly useful.
I don't trust programmers who spend more time typing than reading.
@strand @minx Totes! To the point that I've been a little skeptical of programmers who spend a bunch of time deciding on the perfect keyboard. 🤔 (I suspect that language and tool choice and problem domain all influence the amount of typing you have to do, so I'm not going to make a blanket claim that typing so much means you're doing it wrong, but I've certainly wondered…)
@minx I'm doing a bootcamp right now and our instructors said the material purposely leaves things out here and there because it's important for us to learn how to look up documentation and stuff which has been VERY helpful (especially compared to the programming classes I took in college and eventually gave up on)
@minx In fact I would argue that not looking up code (in books or online) can be a problematic thing in cases where isolationist behaviour leads to lack of cooperation, or a lack of curiosity for creative solutions borrowing ideas from others. In many cases there is a correlation between the ever self-sufficient rockstar hacker stereotype and the Not Invented Here syndrome.
It's an egotism problem, and it has nothing to do with introversion.
argh I terminated a double quote string with a right paren maybe I'm not awake yet
“I never commit to memory anything that can easily be looked up in a book.”
That said, I think it’s worthwhile memorising (at least some of) the stdlib of your go-to scripting language, because being able to bang out a script very quickly is a real productivity enhancer