I'm Just Trying To Keep My Love Alive... (Problem Solving, Part 2)

I always meant to do 2 blog posts on this. I'm glad this was the plan. 

Because I missed out some of the basic notes on the first one. But there was a LOT too take in.

Too much for my little brain. Oh, omg, omg. Am I committed? Do I seem committed to you? Sometimes I wonder if I'm not committed enough.

Then I realise I wrote 200 blog posts since June - and that's just the blog post (many or most of which are highly detailed and highly technical posts). I realise how many CodeWars problems I've solved; how much of my Python course I've done; how much feedback I've taken on.

How much more I've done.

How many PR's I've done.

Yes I am committed. I am SO committed omg.

I am EXTREMELY COMMITTED omg.

Problem Solving, Part 2

So here are the notes that I missed out the first time round from my Senior in my first post. We need to think about the feel of what the overall problem should be, and does this seem right? Like we need to ask ourselves these questions:

• Is what it's outputting going to be useful? Is what the function is outputting, and what the JSON is logging etc., is it going to actually be useful?
• Are the functions that I'm writing GOING TO BE REUSABLE?
• AND: LIKE JUST THINKING GENERALLY ABOUT THE WIDER PROBLEM AS OPPOSED TO LIKE HOW DO I WRITE THE CODE?

Cool, I got all the points out. But there is more to say here.

Halp.

In Summary

Junior engineers tend to focus in too much on the problem at hand, the immediate issue, whereas Seniors tend to see the bigger, broader picture.

They design for the overall, better outcome.

Just to recap what my Senior said:

"When I change code now I think about what I want the outcome to be. 

And I write the code to meet that outcome" !!!!

wow, wow, wow, wow, wow !!!

Actions:

So I need to: 

• CONSIDER WHETHER MY SOLUTION ALIGNS WITH THE FINAL DESIRED OUTCOME!!!
• !!!
• STEP BACK AND FOCUS ON THE OVERALL OUTCOME OR GOAL
• CLARIFY THE PURPOSE
• ASK: WHAT IS THE DESIRED OUTCOME, HERE?
• UNDERSTAND THE CONTEXT

Key Takeaway

Start by thinking about your goal first, rather than just getting caught up in the individual problems you encounter along the way, and then DESIGN THE SOLUTION TO FIT YOUR OUTCOME.