re: What’s something that should be obvious that developers seem to misunderstand? VIEW POST

FULL DISCUSSION
 

Some hot-takes:

  • OOP and Functional are not bad, they are different.
  • The best language for you is the one that solves your problem. Said language could be very different for someone else.
  • Documentation should explain why.
  • "Contributing" sections would be a lot more helpful if they also explained the directory structure and how to find things instead of just pointing to "good first issue"s. ("good first issue" is a great trend, not bashing here)
  • Some people don't contribute a lot to open source or have a ton of side projects and that's okay.
  • The best code is the code not written. (performance tip)
code of conduct - report abuse