Chapter 2: The Importance of Practical Learning

In the fast-evolving tech world, software engineers must continually adapt to new technologies.

For instance, expertise in Windows Forms development, once a sought-after skill, has diminished significantly, now overshadowed by newer technologies like Electron, which is utilized by Microsoft for developing Visual Studio Code.

To thrive in this industry, one cannot rely solely on a single skill throughout their career. Continuous learning is essential, yet many struggle with effective learning strategies. For example, a friend of mine would often purchase numerous books and online courses but would only read and watch videos without engaging in practical coding. He ultimately became discouraged.

In contrast, a competent software engineer approaches learning differently. Initially, they grasp the core syntax of a new language using freely available online resources. Subsequently, they embark on a small project that allows them to gain hands-on experience. As with swimming, mastering programming requires active participation; therefore, learning by doing is the most effective approach.

Chapter 3: Communicating with Product Managers

Collaboration between product managers and software engineers is critical for developing successful software. However, many engineers find it more comfortable to converse with fellow engineers than with non-technical colleagues. Poor communication between the product and engineering teams has led to the failure of numerous projects.

To enhance communication, engineers must first comprehend their roles. When developing a feature, three fundamental questions arise: What is it? Why is it needed? How will it be implemented? The product manager is responsible for clarifying the "What" and "Why," while the engineer focuses on the "How" and delivering a quality product.

A proficient engineer understands that the purpose of communicating with product managers is to clarify the project's goals rather than disputing decisions. Trusting the product manager and concentrating on high-quality execution is vital for successful collaboration.

Chapter 4: Effective Work Prioritization

As software developers, the likelihood of becoming overwhelmed with work is high. Therefore, mastering the art of prioritization becomes essential during busy periods.

While there are no strict rules, certain principles can guide prioritization:

• Issues affecting production should take precedence.
• Distinguish between must-have features and those that are merely nice-to-have, addressing the essential ones first.
• Typically, fixing bugs is more urgent than developing new features.
• For new feature development, prioritize based on stakeholder importance: significant customers > other clients > senior management > product managers > direct managers.

Ultimately, each engineer knows their work best, and the ability to prioritize effectively is a hallmark of a good engineer.

Chapter 5: The Value of Seeking Assistance

In the expansive field of software engineering, no one truly stands alone. It is impossible for anyone to master every aspect of the discipline. Thus, one of the most important skills for software developers is knowing when to ask for help.

For instance, a seasoned engineer with extensive Python experience may need to work with a new module or framework. While they could spend hours researching online, the most efficient solution might be to consult a junior colleague who has relevant experience.

Surprisingly, many senior engineers hesitate to seek assistance from their less experienced counterparts. A truly effective engineer recognizes that titles like "junior" or "senior" are less significant than the unique knowledge each individual possesses. While resources like Google and StackOverflow are valuable, the best asset is the talent within your immediate environment.

Chapter 6: The Importance of Moving Quickly

An effective engineer is always proactive. They won't remain stagnant in a company that isn't fostering their growth. If their personal development outpaces their company's progress, they will seek new opportunities. If no suitable company exists, they may choose to establish their own venture.

For additional insights, check out Garry Tan’s video “LEARN, EARN or QUIT.”

Thank you for reading! If you found this article helpful, please consider supporting me by joining Medium through my referral link. Supporting quality content is another great habit to cultivate.