Re: WebCup 2015

From: Vy-Shane Sin Fat <shane_at_node.mu>
Date: Tue, 26 May 2015 11:39:34 +0800

On Tue, May 26, 2015 at 2:24 AM, Mohammad Nadim <nadim.attari_at_gmail.com>
wrote:

> Hello Vy-Shane,
>
> On 25 May 2015 at 19:24, Vy-Shane Sin Fat <shane_at_node.mu> wrote:
>
>>
>>> What I'm disagreeing on is the suggestion that it's okay to knowingly do
>> bad engineering in order to fit the client's budget. You're simply setting
>> your project up for failure if you do that.
>>
>
> Please don't misunderstand me. Or rather I must apologise for not putting
> my point(s) clearly. I'm no way compromising with bad codes, etc. First of
> all, coming to the WebCup, the team members should have paid attention to
> the criteria on which they were to be assessed. And good or clean code
> development was not a criteria. Personally I think that if this was a
> criteria, then the standard of the WebCup would have been higher. And yes I
> want a higher standard for the Webcup.
>
> Jochen often argues about "clean code development." Maybe he could push
> this concept into the next Webcup.
>
> Secondly, see the example I gave when replying Dhiruj's mail (the web form
> and the €500 example).
>
> When Yusuf, Sun & Yuv send their valuable feedback (see the archives), in
> no means i'm telling them "fsck with your code quality / coding standards."
> Not at all. I'm for good coding quality, good soft engg, etc.
>

I suspected that you were being more hyperbolic than serious. It just
happens to be one of the topics where I like to rant on at length ;-) I'm a
big believer in good code discipline - even down to the basics of how the
code is formatted, and yes, coding standards. If I encounter well formatted
code, chances are that the author has gone over his code with a critical
eye, and has at least reviewed it. If the code is poorly formatted, it's
likely that he's gotten to the point where the code compiles and does what
it is supposed to do, and he's moved on. My experience tells me that I will
find bigger issues than just bad formatting while reviewing the code. If
you care about the little things, you will care about the important things.
It's just good practice and good craftsmanship. Set the bar high. This
stuff is important.
Received on Tue May 26 2015 - 03:40:09 PST