First Rule of Programming Is Don't Program

#1

Post by cyman » Sun, Oct 25, 2009, 4:28 PM UTC

While us programmers tend to say "I'll just program it myself" it is actually much faster to:

- Buy an off the shelf program and take 3 hours to read their proprietary API for extra functionality.

- Use an existing library and read the documentation rather than building your own code.

- Use VB.NET or Delphi for the front-end user interface.

- Buy a properly documented royalty-free library for under $1000 rather than spend months integrating open source code.

- Use Python or VB.NET even tho it just feels right to use Java/C. (Ok, I said it. Now if I can only get this VB.NET flame shield program to finish loading.)

Unfortunately, us programmers tend not to do this. "Oh, we need a queue class? I'll just build it myself, takes like 30 minutes tops."

As coders, we need to think like an engineer who is building a car. No engineer building a car will make the engine or windshield themselves. But us coders do this all the time.

There are 2 parts to every program: [1]: The new scientific code/algorithm you are writing. Which is typically quite small. (5%) [2] Everything else. (95%)

How many times have I got that urge.. "I don't want to do the research. I want to jump right in.. I bet I can finish this tonight.." 90% of the code out there is already written. It is more about adding the glue. And of course, finding it and reading the docs.

Re: First Rule of Programming Is Don't Program

#2

Post by v4us » Sun, Oct 25, 2009, 4:41 PM UTC

Of course, "Don't PROGRAM" is a greate rule. If you can use libriry of algorithms or something else that is made by really professional programers and fulfit all your requerements it's good. To buy this library will save your time (=money).

But there are many cases when the best solution is to program. For example: Hi performance software development, sequrity issues and etc.

Re: First Rule of Programming Is Don't Program

#3

Post by olliesaunders » Sun, Oct 25, 2009, 4:41 PM UTC

I prefer: No code is better than no code.

Or: Programming takes eons.

Re: First Rule of Programming Is Don't Program

#4

Post by ilyak » Sun, Oct 25, 2009, 4:46 PM UTC

In Java, you usually do not invent the wheel but rather take an existing open-source jar.

Even those of them that aren't very good, sadly. But most are.

Re: First Rule of Programming Is Don't Program

#5

Post by tybris » Sun, Oct 25, 2009, 4:50 PM UTC

Not programming is hard work. You will spend about 90% of your programming time integrating other software whether you like or not.

By the way, the nr 1 rule is: context is everything. The nr 2 rule is: keep it simple.

Re: First Rule of Programming Is Don't Program

#6

Post by v4us » Sun, Oct 25, 2009, 4:52 PM UTC

tybris wrote: post #5

Not programming is hard work. You will spend about 90% of your programming time integrating other software whether you like or not. By the way, the nr 1 rule is: context is everything. The nr 2 rule is: keep it simple.

"keep it simple" is really good rule. But "Don't program" is good too. As i can see, many people try to code many complicated library methods even don'tknow about methods.

Re: First Rule of Programming Is Don't Program

#7

Post by nrr » Sun, Oct 25, 2009, 4:55 PM UTC

v4us wrote: post #2

Of course, "Don't PROGRAM" is a greate rule. If you can use libriry of algorithms or something else that is made by really professional programers and fulfit all your requerements it's good. To buy this library will save your time (=money). But there are many cases when the best solution is to program. For example: Hi performance software development, sequrity issues and etc.

I'm not sure your definition of high-performance software development and mine coincide here, in any sense imaginable.

In the programmer-performance sense, just snagging an off-the-shelf component and shoehorning it into your product will let you ship something far sooner than otherwise. Who cares if the code looks nice right now? Just ship the damn thing!

In the runtime-performance sense, the whole mess becomes a case of "someone else's problem." If you purchase a component, I'd say you have a lot of leverage to complain that a particular piece of software isn't performant or secure. If it's open source, write patches and, if politics becomes a problem, step on someone's toes.

Re: First Rule of Programming Is Don't Program

#8

Post by v4us » Sun, Oct 25, 2009, 4:59 PM UTC

nrr wrote: post #7

v4us wrote: post #2

Of course, "Don't PROGRAM" is a greate rule. If you can use libriry of algorithms or something else that is made by really professional programers and fulfit all your requerements it's good. To buy this library will save your time (=money). But there are many cases when the best solution is to program. For example: Hi performance software development, sequrity issues and etc.

I'm not sure your definition of high-performance software development and mine coincide here, in any sense imaginable. In the programmer-performance sense, just snagging an off-the-shelf component and shoehorning it into your product will let you ship something far sooner than otherwise. Who cares if the code looks nice right now? Just ship the damn thing! In the runtime-performance sense, the whole mess becomes a ca…

I ment runtime-performance.

Off-the-shelf components will make you to code fatster and prolly much more flexible. Don't programm is really greate rule.

Don't programm and keep your code as simple as possible

Re: First Rule of Programming Is Don't Program

#9

Post by barrkel » Sun, Oct 25, 2009, 5:00 PM UTC

As an odd corollary, in matters of system administration, the exact opposite is usually apposite: AUTOMATE EVERYTHING.

Re: First Rule of Programming Is Don't Program

#10

Post by v4us » Sun, Oct 25, 2009, 5:02 PM UTC

barrkel wrote: post #9

As an odd corollary, in matters of system administration, the exact opposite is usually apposite: AUTOMATE EVERYTHING.

It's kind of the same rule. AUTOMATE EVERETHING == Let something or someone todo your work == Use work of another people == use library == DON'T PROGRAM