Things you are doing WRONG as a Software Engineer probably!

Summary

In this insightful video, the host, a seasoned software engineer, shares five common mistakes to avoid for career growth in the field. He emphasizes the importance of understanding code deeply, stepping out of comfort zones, reducing reliance on mentors, taking ownership of projects, and documenting complex parts effectively. The video also introduces 'Crio Doo', a platform for hands-on learning and building a strong portfolio, with a special mention of their SD fellowship program.

Takeaways

• 😀 Take the time to deeply understand the code you are working on, rather than just copying and pasting code snippets without comprehension.
• 🚀 Step out of your comfort zone by embracing new tech stacks and being open to switching projects or companies to keep learning and growing.
• 🔍 Avoid relying too heavily on mentors; instead, practice debugging and problem-solving skills by attempting to resolve issues independently before seeking help.
• 🏆 Take ownership of your projects and features by being proactive in suggesting improvements and taking responsibility for the end-to-end development process.
• 📝 Document complex parts of your work and present them in meetings to showcase your skills, increase visibility, and gain more confidence from your team.
• 🛠️ Write the design before the code to ensure a clear understanding of the project's requirements and to avoid potential pitfalls.
• 🤔 Reflect on common mistakes made by software engineers and actively work on improving these areas for personal and professional development.
• 💼 Embrace the opportunity to work on complex projects as they can lead to a steep career growth and demonstrate your capabilities to higher management.
• 📈 Prioritize continuous learning and adapting to new technologies to stay relevant and competitive in the ever-evolving field of software engineering.
• 👥 Understand the importance of communication and collaboration within a team, especially when presenting and discussing your designs and ideas.
• 🌟 Recognize the value of a strong portfolio with well-documented projects that can help in securing better job opportunities and career advancement.

Q & A

What is the main topic of the video?

The main topic of the video is discussing common mistakes that software engineers might be making in their careers and providing advice on how to avoid them for better career growth.

How long has the speaker been in the software industry?

The speaker has been in the software industry for 4 years.

What is the first mistake mentioned in the script that new software engineers often make?

The first mistake is writing code without fully understanding it, often by copying and pasting from other sources without delving into the nuances of the code.

Why is it important to understand the code you are working on?

Understanding the code is important for long-term learning and growth. It helps in becoming a better engineer and not just solving a problem temporarily.

What is the second mistake discussed in the video script?

The second mistake is staying in one's comfort zone, such as being reluctant to work with a different tech stack or switching projects or companies.

Why should software engineers step out of their comfort zone?

Stepping out of the comfort zone exposes engineers to new learning opportunities, challenges, and experiences that can lead to personal and professional growth.

What is the platform 'Crio.Do' mentioned in the script?

Crio.Do is described as the world's first experience-based learning platform for software engineers, focusing on learning by doing and offering real-world project experiences.

What is the approach Crio.Do uses for learning?

Crio.Do uses a 'learn by doing' approach, where learners engage with real-world projects as if they are working at top companies like Netflix or Amazon.

What is the third mistake mentioned in the script that new software engineers often make?

The third mistake is relying too much on mentors, skipping the process of debugging and self-learning, and going directly to mentors for solutions.

Why is it important for software engineers to debug issues themselves before asking for help?

Debugging issues independently helps engineers to develop critical problem-solving skills, understand the code better, and learn from the process.

What is the fourth mistake discussed in the script?

The fourth mistake is not taking ownership of the product, feature, or bug that one is working on, which can limit one's perspective and involvement in the project.

Why should software engineers take complete ownership of their work?

Taking complete ownership ensures that engineers are fully responsible for the quality and outcome of their work, leading to better results and a stronger sense of accomplishment.

What is the fifth and final mistake mentioned in the script?

The fifth mistake is not documenting complex parts of the project or feature, which can lead to knowledge gaps and difficulties for others who might work on the same code in the future.

Why is it important to document complex parts of a project?

Documenting complex parts helps in knowledge sharing, ensures that the project's design and logic are clear to others, and facilitates smoother collaboration and maintenance.

What is the advice given for presenting complex designs to a team?

The advice is to organize meetings to present your designs, which helps in showcasing your skills, gaining feedback, and building confidence among team members.