tag:blogger.com,1999:blog-7008386140022030691.post1063036103779089520..comments2023-05-10T17:21:18.242+03:00Comments on Anton: The ancient art of corner-cuttingAntonhttp://www.blogger.com/profile/06383611247281695315noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7008386140022030691.post-29635808729339601092012-06-16T23:52:50.453+03:002012-06-16T23:52:50.453+03:00You're back, great! :)
Yes, I think more of k...You're back, great! :)<br /><br />Yes, I think more of known issues, and thought like “yeah, that probably should be fixed, but I am so busy / tired / indifferent right now that I'll just leave it”. That's why I also like that saying — if you see a problem it is best to do something about it, since there are still many others that you don't see.<br /><br />And I do like your thought of directing the “seeing” towards the select priority goal, consciously or sub-. <br /><br />Thanks for sharing!Antonhttps://www.blogger.com/profile/06383611247281695315noreply@blogger.comtag:blogger.com,1999:blog-7008386140022030691.post-39739081581061216802012-06-16T19:35:53.390+03:002012-06-16T19:35:53.390+03:00To cut a corner, or not to cut a corner, that is t...To cut a corner, or not to cut a corner, that is the question! :) In my opinion, the question itself is flawed. The structure of the question provides you with a given reality with objects and possible actions. Corner. To cut. Not to cut. Choose one, along with possible conditions and corner cases.<br /><br />Wrong. There is no such thing as not cutting a corner. There is not such a thing as perfectness. Even if at one moment you think something you've done is perfect, the next moment you'll loose that feeling and will find an imperfectness. Especially in application-level software development. So all you ever do is cut a corner. But question is not even how much you cut each corner - some more, some less. <br /><br />Question is what you perceive as more important or less important. Not the corners themselves - say test coverage percentage in software development. But the goals of your work - say is it more important to protect customer from accidental security hole, or to provide him with configurability of security settings. When you decide which goal is more important, you write mostly those tests which move you to the chosen goal.<br /><br />My software development example is probably not very good. So I'll reiterate this in more general terms. Forget about Corners and Cutting. Think in terms of Goals and Actions leading to achieving them. In a sense this is a change from negative thinking of cutting to positive thinking of achieving.<br /><br />I like your friend's father's telling. And for me it means - never even think about cutting a corner, turn your head the way where there is no cutting to be done and go ahead keeping your head this way. :)Anonymoushttps://www.blogger.com/profile/12121825345765402895noreply@blogger.com