Are you a good developer? It's a question that all of us have asked ourselves countless times during our career. It usually happens when we're at our lowest, when a site runs into trouble, and you have no idea what's going on. Sometimes when you're trying to learn something new, and you just can't figure it out. If you were a better developer, would you have these problems? Are you a good developer?
Introduction & Explanations | 00:01:28 - Who is asking this question? - Imposter syndrome - What is a developer?
Breaking down large problems into smaller ones | 00:11:27 - Take a huge task that seems insurmountable and break it down into more attainable smaller goals that together, will achieve the objective of the huge task - Troubleshooting skills
Writing readable/maintainable code | 00:19:32 - Re-factoring - Descriptive variable and function names - Comments - Try to avoid hard-coding
Staying up to date | 00:31:15 - Tech moves fast - Try and stay up to date with new frameworks and tools (not all of them, there are too many, but enough to keep yourself relevant with what is popular)
Communicating effectively | 00:44:17 - Consistently answering messages - Attention to detail - Do not overcommunicate
Taking ownership of features and tasks | 00:53:52 - Completing tasks that have been in the backlog for a while (take ownership and get it done, good way to stand out in a team) - Connect and communicate with all stakeholders of an issue to devise and implement a solution
Mentoring/passing down knowledge | 00:57:29 - Pass knowledge to other team members, can help establish yourself in a more senior role - Writing documentation
Implementing solutions to problems | 01:07:27 - Developers are problem solvers