4 ms·
Might work for a toy programming language and framework, but not for anything like C# and the .NET framework (especially when considering the different implemen
by gwervc 3y ago
Might work for a toy programming language and framework, but not for anything like C# and the .NET framework (especially when considering the different implementations), Java, etc.
- TheHumanist 3y agoAdvice like that above is honestly terrible for newer developers, I believe. It feels insurmountable for many people, myself included. I simply don't have the brain capacity to: A. Read an entire language's docs front to back. As you mentioned, maybe if it is some small, silly thing but for something like Python, Java, JS, etc... no fucking way. My brain would constantly glaze my eyes over. There is so much. B. Retain the information I just attempted to read. Again, there is so much. It's insanely unrealistic for most people, I would think. New developers see advice like this and immediately feel like they aren't cut out for this because people make this nonsense sound like something 'YOU MUST DO' to be a good developer. It's toxic, in my opinion. Maybe not intentionally so, but it really can kill a person's excitement.
- baq 3y agoMy usual recommendation is to read the table of contents of the manual. This is especially important for any database you might be using. Language... meh, maybe...? But the DB - please do.
- aleph_minus_one 3y ago> Might work for a toy programming language and framework, but not for anything like C# and the .NET framework (especially when considering the different implementations), Java, etc. This is rather an argument against C#, .NET framework, and Java. :-)
- raincole 3y agoGood luck telling your boss/client that you don't write C#/Java because "the document is too long to read cover to cover."