Things I need to improve on: software engineering part 1

Of all the things that I need to improve on and I have a whole list of these lined up. Perhaps just general software engineering is one of them.

When I get to a new piece of code that symbolises a new ticket or a large problem I need to:

• Think about the outcome that is being achieved 
• Try to identify:
• What currently exists?
• What systems/ parts of the codebase are talking to each other?

I’ll repeat:

• Try to identify:
• What currently exists
• And then try to identify:
• What systems/parts of the codebase are talking to each other?

Try:

• Try drawing it out

Can you:

• Can you describe what is happening? Can you describe what is happening and point each step in that description to where that is happening in the code? Can you describe what is happening and point each step in that description to where that is happening in the code? CAN YOU DESCRIBE WHAT IS HAPPENING AND POINT EACH STEP IN THAT DESCRIPTION TO WHERE THAT IS HAPPENING IN THE CODE?

CAN YOU DESCRIBE WHAT IS HAPPENING AND POINT EACH STEP IN THAT DESCRIPTION TO WHERE THAT IS HAPPENING IN THE CODE?

And if Alan Turing were here then he too would say to me

• Can you describe what is happening and point each step in that description to where that is happening in the code?
• Can you describe what is happening and point each step in that description to where that is happening in the code?

Because that is what I used to do in my blogs and I used to do it sooo well. Because work code is harder than the code I learned to code on but that is okay and I can do it too. Because… because… 

Because I can’t write about work code in my blogs but what I can do is write a private document to myself as if I were writing a blog post. As if I were writing a blog post…