Find the problem, then the solution


I found myself making the mistake I read about a lot of times. 

It turns out we have to migrate parts of an existing solution to a different platform and I had all this questions about how to organize the new solution and I realised, hold on, I must first have a deep dive into the existing code and then start thinking about the new solution and how to architect it.

I was so easily driven to think about the solution that I lost sight of the problem, terrible and now I m advertising it… 

Maybe it was just the idea of going through the existing code disgusted me so much that I didn’t want to think about it? or maybe its the fact that reading code is harder that writing it?

Hopefully I learned from it.


No Responses Yet to “Find the problem, then the solution”

  1. Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: