Saturday, 20 September 2014
In any experiment, great due diligence, etc. before, during and after is imperative.
Retrospect will ultimately determine the merits of the idea. After all, you don't know what you don't know. At the same time you don't know until you have tried.
On the other hand, I wouldn't shoot myself in the foot to confirm whether it hurts or not.
Tuesday, 8 July 2014
Whether time really exists or not, thus far "winding the clock back" is something I have yet to experience. So any time spent may as well have been worthwhile.
Hence, when evaluating the prospects of a potential solution, spend time wisely by getting a meaningful "wall-to-wall" overview and "feel" of the entirety from inception through to its logical conclusion before getting down to brass tacks i.e. the details.
Once deemed worthwhile as a whole and high level due diligence having been carried out, only then should the more detailed issues be attended to (e.g. the particular advantage of a feature, etc.).
If eventually deemed without meaningful value, minimal time will have been spent and therefore wasted.
Monday, 7 July 2014
|Image Credit: rafa-sf.deviantart.com|
If another business purpose can be served, a little bit of creative licence is permissible.
However, when deviating from the usual standard SAP usage, there is a primary proviso or so.
Take the time to recognize and evaluate potential conflict and limitations in the medium and long term of significant deviations before committing to a charted course.
Look ahead to ensure that you aren't building a future insurmountable roadblock.