Compute Monthly

Treat new code like a contract. It should do no more and no less than the contract specifies.

Your code may be capable of handling the project requirements, but that doesn’t make it incapable of doing more or less than it’s supposed to.

Don’t allow your code to breach the contract.

It’s fun to play code golf, but have you ever tried code bowling?

The goal of code golf is to solve a problem with as few lines of code as possible. The goal of code bowling is the opposite; to solve a problem with as much complicated code as you can.

Just for fun, instead of trying to minimize the amount of code used, try to maximize it. You’ll gain a deeper understanding of what’s possible and what’s avoidable.

Crippled code is usually more dangerous than dead code. If it’s going to crash, it’d better crash hard. That way someone or something is more likely to notice it.

Do you have code that’s flying under the radar and doing harm?

Always build for concurrency when resources allow. Reusability and extensibility should be baked in, not bolted on.

Is there something you wish you built for two?

If you’re ever presented with a problem that leads you to think to yourself, “this would work if we had x or y process in place, or if so and so could do their job, or if the system was different,” don’t. Instead, try to work through the problem controlling only what you can control. What’s the real problem? Can you solve it with only what you currently have access to?

Take the Jugaad Challenge!