Sep 28 2008
Function vs. Non-Function and Weakness Assessment
I’ve thought about this concept before, but never heard it quite so clearly said than in Earl Beede’s “Functionality Is Cheap.”
The function is most assuredly the easy part — well, in most cases the functionality is the simplest part to think of — at least for me it is.
My problem has always been in design, project management, and architectural patterns. For a long time I considered myself to be a Solutions Developer because I’ve ideas aplenty, but my implementation usually falls short.
This is the primary cause for my absence as I’ve tried to focus more on learning HOW to be a successful programmer rather than more study of programming languages.
I’ve also since abandoned my flawed thinking that “just code something” is a viable option to an aspiring programmer — well, it isn’t.
This may hold true for geniuses or very talented programmers in general but for those who struggle to learn new ideas and concepts, just doing something is not an alternative.
First, assess your weaknesses — mine are that I cannot keep on track due to poor organization. Earl struck on a concept that we may not see ourselves and that is to separate our problems into smaller or more manageable problems.
Ultimately we ourselves have to step back and do a little “weakness assessment.” I think I’m on the road to recovery as a viable software and solutions developer by first admitting that I am weak in the non-functional sense.
No responses yet
Create a free edublog to get your own comment avatar (and more!)