why before what, what before how.

Over the years I’ve worked with a lot of different technologies and languages. Throughout it all I’ve had my favorites and frustrations, but at the end of the day I honestly don’t think one technology or language is *absolutely* better than another.

It really all depends on the task at hand…and to a lesser degree, your own personal constraints.

If you know what you want to do, figuring out how within a given technology or language usually isn’t so hard (mostly you just have to look it up).

And to go one step further, if you really understand ‘why’ you want to do something…figuring out 'what’ you need to do is a bit easier too (and the combination of the 'why’ and 'what’ *always* leads to a 'best chance’ at the 'how’).

So - worry about the 'why’…let it lead you to the 'what’…flesh that out as much as possible before you start focusing on, or arguing a lot about, the 'how’.

This post has received 17 loves.


SUBSCRIBE WITH YOUR EMAIL

ARCHIVE OF POSTS



This is the personal blog of Kevin Marshall (a.k.a Falicon) where he often digs into side projects he's working on for digdownlabs.com and other random thoughts he's got on his mind.

Kevin also talks in more depth about many of the these things around twice a month via his drip campaign and has a day job as CTO of Veritonic. You can also check out some of his open source code on GitHub or connect with him on Twitter @falicon or via email at kevin at falicon.com.

If you have comments, thoughts, or want to respond to something you see here I would encourage you to respond via a post on your own blog (and then let me know about the link via one of the routes mentioned above).