(at least at our company. Mileage may vary.)
We have a lot of different specialties at our company. Backend, frontend, mobile, machine learning/AI, etc across many different languages and frameworks. However, regardless of specialty, there are some common skills, methodologies, and theories that every software engineer at our company should know; some core competencies1 Many of these do come with what we feel are fair assumptions (e.g. if you know how to fix
merge conflicts in
git, we feel it's safe to assume you know the basics of a
mergeconflicts, how to fix
undefined. With Python, understand a
TypeError: 'str' objectis probably because strings are immutable data types. Et cetera. Understanding errors and why they commonly occur, will make you a better programmer, better at debugging, and give you more insight into the language/framework.
This list will probably continue to grow. I'm sure we missed some things. You can contribute to the list by submitting a pull request on Github or in the comments below.
We should also point out that this list is probably not complete and will continue to grow. This is certainly not a list of the only things a software engineer needs to know; just the things they should know. ↩
This file lives in a repo where we have began to build collection of resources useful to our company and, we believe, to other startups as well. ↩
Download our Incubator Resources
We’re known for sharing everything!
Save more time, get more done!
Innovate from the inside
YOU MIGHT ALSO LIKE