You're starting out as a Software Engineer. How do you develop problem-solving skills like a seasoned pro?

I taught Web programming at DePaul University. One of the first task that students learn to do is to displace a textbox on the browser; take what user put into the textbox; click a submit button; display customized information. Many learn to do it with no difficulty, with no excitement either. I then told them, Congratulations! You just made a Google-like application. Google takes a keywords using textbox and display customized information, just like you page. You are a little behind Google though, because you don't know how to search database and get result yet. But I can teach you that in two more classes. I can feel the excitement in the room now. Because I was not lying. Technology is lego pieces. Imagination builds the set.

In order to become good at problem solving you will need to study a lot of the problems you want to solve and the different ways those have been solved. IE: it is good to have an idea of the most common sorting algorithms out there. You will also need to learn where you can find the information you need, search engines are your friend. Last but not least, listen to your more experienced colleagues as they might have tricks up their sleeve that no internet search will reveal.

As a new Software Engineer, mastering problem-solving is key to your success. Start by thoroughly understanding the problem and breaking it down into smaller, manageable parts—something I’ve seen experienced engineers do effectively. They tackle each part one at a time, preventing overwhelm. The STAR method (Situation, Task, Action, Result) is also invaluable here: define the Situation, outline the Task, describe the Actions taken, and review the Results. This structured approach helps in navigating complex issues and finding solutions efficiently. Leveraging tools, practicing algorithms, and reflecting on your methods will further enhance your skills, helping you tackle challenges with confidence.

For me to get here in this competitive industry was the most important day, the day 0. The day which helped me grow and reach milestones. The day 0 helped me decide what to focus and what to not. The day 0 helped me what to prioritise and what not to. Coming to the problem solving skills I gained on this journey, I still remember in my initial software engineering classes days, I used to get stuck at problems a lot, like a lot. My teacher once told me “learn the basics, and you’ll find that complex problems become simpler and more manageable.” This brought me here.

- Understand your goals - Learn to communicate with stakeholders - Pick the right tools and learn them thoroughly - Learn Test Driven Design, it will save you a lot of grief - Never attach to a piece of technology, learn general principles - Simple things works; don't overcomplicate (KISS) - Learn SOLID and DRY principles - If you think you master something, it is time for school

One thing I found helpful is to practice writing good unit tests. Tests that you can trust allow you to make changes with minimal risk. Quick feedback allows for consistent practice which results in building strong muscle memory from trial and error.

I have found it immensely beneficial to regularly challenge your mind with dedicated mental exercises. Make it a point to solve at least two or three algorithmic problems each week or engage in similar cognitive tasks. Avoid the temptation to stick with overly simple problems; instead, push yourself slightly beyond your comfort zone. Dedicate at least an hour to deep thinking during these sessions. Within a few weeks, you'll begin to see significant improvements in your problem solvong abilities.

Looking back, I see that practice has always been my gateway to master my skill-set in cloud and software engineering. It started with late nights coding, building new projects to solve my own problems, and experimenting with new technologies. Each challenge and bug taught me something new and sharpened my skills. Through consistent practice, I’ve grown, and if I say I’ve grown, I have grown a lot looking back at the day 0. It’s this relentless pursuit of improvement that has shaped my journey and driven me forward in the industry.

Engaging with colleagues with how they have solved similar problems is one of the most valuable and quickest ways to learn. Without this interaction you are limited in how fast you can learn new concepts. I don't think I would ever have learnt how to build software as a finite state machine, for example, without having been shown by an experienced colleague how it neatly solved both my immediate problem and a range of other possible issues. The software engineering field is simply too vast to become proficient in every technique so it's valuable to learn from those around you what works well in your problem space so you can prioritise your learning.

During my SIH'23 days, I was a finalist working on a government project. For 48 non-stop hours, my team and I built the project in a city far from home. Despite our tireless efforts and unwavering commitment, we didn’t win. Our hopes were high, but we faced the sting of failure. That experience, while disheartening, taught me a vital lesson about embracing failure. Instead of letting it define me, I chose to see it as a learning opportunity. Each setback offered me valuable insights and pushed me to develop resilience. It reminded me that failure is not the end but a chance to refine my approach and grow stronger.

I have been a full time software engineer for 16 years now and I have never stopped learning about new technologies and advances. It's what makes this a rewarding career path, you will not be solving the same problems in a few years that you are now, or if you are you'll be doing it with a different viewpoint and an new set of tools! When you stop wanting to learn something new then that's when it's time to consider a new career path.