Message board for the users of flat assembler.
> Heap > 12 Steps to Better Code
Goto page Previous 1, 2
|17 Feb 2013, 14:32||
The same for me.
I know what to begin with, but I do not see the full picture until some
point in the coding of the beginning. So, I basically go from one sub-spec
to another one.
Say, I need a dialog for some project management in the IDE.
First, I create a dialog window itself with some controls and make it all
nicely painted, resizable, etc. Only, then I begin thinking in details what
happens if I click buttons or select some stuff from list(s), etc.
So, basically, I code "until it is done" and I like it overall.
But that method is hazardous sometimes, because it may never be done.
You can recall Duke Nukem Forever game. It was not done by the original
I think it is called "the feature creep" and Joel actually writes about it too.
|17 Feb 2013, 14:42||
[ Post removed by author. ]
Last edited by HaHaAnonymous on 28 Feb 2015, 21:25; edited 1 time in total
|17 Feb 2013, 15:16||
What is "spec"? Speculation?
No sarcasm detected.
"spec" from "specification"
In computer programming,It's a document describing exactly as something should be/is implemented. For example,you want to write a C compiler conforming to ANSI C 89 you need to get(buy) the file spec from ANSI. It's used to describe file formats too for example. "read the BMP file spec" etc.
It's just to you get the idea...
I'm not a native speaker of the english language. So, if you find any mistake what I have written, you are free to fix for me or tell me on.
|17 Feb 2013, 23:04||
|Goto page Previous 1, 2
< Last Thread | Next Thread >
Copyright © 1999-2020, Tomasz Grysztar.
Powered by rwasa.