Comments on: Can you make small changes in an unknown language? http://polymathprogrammer.com/2008/07/30/can-you-make-small-changes-in-unknown-language/ Where entrepreneurship, mathematics and programming meet Wed, 28 Mar 2012 04:44:06 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Simple excerpts in WordPress | Polymath Programmer http://polymathprogrammer.com/2008/07/30/can-you-make-small-changes-in-unknown-language/comment-page-1/#comment-3448 Simple excerpts in WordPress | Polymath Programmer Wed, 06 Aug 2008 09:01:09 +0000 http://polymathprogrammer.com/?p=300#comment-3448 [...] First, I want to say that I have never learnt PHP. I’m also unfamiliar with the innards of WordPress. But I’m a programmer. The code doesn’t look too hard… so I’m still capable of making small changes. [...] [...] First, I want to say that I have never learnt PHP. I’m also unfamiliar with the innards of WordPress. But I’m a programmer. The code doesn’t look too hard… so I’m still capable of making small changes. [...]

]]> By: Vincent Tan http://polymathprogrammer.com/2008/07/30/can-you-make-small-changes-in-unknown-language/comment-page-1/#comment-3427 Vincent Tan Wed, 30 Jul 2008 13:15:47 +0000 http://polymathprogrammer.com/?p=300#comment-3427 Replication of existing faults is unavoidable if you just use the existing code as a learning template. I sometimes come across this situation when maintaining legacy code. My colleague and I discussed on it, and the best solution, other than rewriting large chunks of hard-to-find or hidden-in-obscure-places code, is to let it be. Our rationale? Be <a href="http://polymathprogrammer.com/2008/03/12/be-consistently-wrong/" rel="nofollow">consistently wrong</a>. This way, if we ever put our minds to go on a mass code correction rampage, the editing process is idiotically and mechanically consistent. As for your second point, it <em>is</em> hard to write something new with only a small code sample, a subset of its "true" language. In your example, I'd probably go learn the Windows API and use an existing system function if there is. I wouldn't know I have to write a new function if I didn't learn the ins and outs of the API. I was actually thinking of minor changes when I wrote the post. Code changes that can be extrapolated and intuited from surrounding code. This tests one's understanding of basic programming skills and grasp of business logic. Replication of existing faults is unavoidable if you just use the existing code as a learning template. I sometimes come across this situation when maintaining legacy code. My colleague and I discussed on it, and the best solution, other than rewriting large chunks of hard-to-find or hidden-in-obscure-places code, is to let it be.

Our rationale? Be consistently wrong. This way, if we ever put our minds to go on a mass code correction rampage, the editing process is idiotically and mechanically consistent.

As for your second point, it is hard to write something new with only a small code sample, a subset of its “true” language. In your example, I’d probably go learn the Windows API and use an existing system function if there is. I wouldn’t know I have to write a new function if I didn’t learn the ins and outs of the API.

I was actually thinking of minor changes when I wrote the post. Code changes that can be extrapolated and intuited from surrounding code. This tests one’s understanding of basic programming skills and grasp of business logic.

]]> By: Ben Barden http://polymathprogrammer.com/2008/07/30/can-you-make-small-changes-in-unknown-language/comment-page-1/#comment-3425 Ben Barden Wed, 30 Jul 2008 12:20:56 +0000 http://polymathprogrammer.com/?p=300#comment-3425 Depending on the language, I might be able to do it, but creating new code based on existing code has a couple of drawbacks. First, you may replicate any faults or bad practices that are present in the existing code. Second, if you're writing something that isn't already written for the system you're working on, you might have difficulties finding other code that will accomplish what you want. The second point really depends on what you're doing, but what if - to give a specific example - you need to access the Windows API in VB6 and no other function has done that yet? You can't do that in "pure" code. On the other hand, writing code in the same style as existing code keeps things consistent, even if it continues with bad practices that have been used in the past. Depending on the language, I might be able to do it, but creating new code based on existing code has a couple of drawbacks. First, you may replicate any faults or bad practices that are present in the existing code. Second, if you’re writing something that isn’t already written for the system you’re working on, you might have difficulties finding other code that will accomplish what you want.

The second point really depends on what you’re doing, but what if – to give a specific example – you need to access the Windows API in VB6 and no other function has done that yet? You can’t do that in “pure” code.

On the other hand, writing code in the same style as existing code keeps things consistent, even if it continues with bad practices that have been used in the past.

]]>