Another correlary: learn lots of languages, even if you’ll never use them. I never want to fall into a codebase that I’ve never even learned the paradigms. One procedural, one functional, one OOP, one interpreted, one compiled, one byte code compiled, one or two command line scripts, regex, all the structured data text languages: XML, CSV, JSON, YAML, TOML, … A JavaScript framework. HTML. A relational database, a non relational db. REST.
Should be enough to get started lol. But you learn something from each, about code architecture at least.
Always learn the languages preferred directory and repo layout structure, never invent your own.
So many problems can be solved by just reading the code. A corollary to this: make sure the code you write is readable.
Another correlary: learn lots of languages, even if you’ll never use them. I never want to fall into a codebase that I’ve never even learned the paradigms. One procedural, one functional, one OOP, one interpreted, one compiled, one byte code compiled, one or two command line scripts, regex, all the structured data text languages: XML, CSV, JSON, YAML, TOML, … A JavaScript framework. HTML. A relational database, a non relational db. REST.
Should be enough to get started lol. But you learn something from each, about code architecture at least.
Always learn the languages preferred directory and repo layout structure, never invent your own.