how 2 create a software
-
Well, you will need a few things. 1) A Computer, with a monitor, keyboard, mouse and all the normal bits. (You can get one from eBay) 2) A Compiler / linker / doobry. (You can get one from those kind people at microsoft) 3) A good Idea for a program. (You can get one from your mates) 4) A very large collection of Ones and Zeros. (You can get them from me - I have a large stock of spares, some new, some used). Very cheap prices in bulk. Now, organise the Ones and Zeros so that they fullfill your Idea. Pass the Idea through the Compiler / linker / doobry so that the Computer can understand them. Run the compiled Idea on the Computer. Simple, isn't it? Now you just have to wonder why we all go to school, then university, and slave for a number of years in the industry before we call ourselves Software Engineers.
OriginalGriff wrote:
Now, organise the Ones and Zeros so that they fullfill your Idea. Pass the Idea through the Compiler / linker / doobry so that the Computer can understand them. Run the compiled Idea on the Computer.
If you have 0's and 1's why use compiler, organise them is such order that the computer understands them :). Intel books with machine instruction codes can be useful!
-
OriginalGriff wrote:
Now, organise the Ones and Zeros so that they fullfill your Idea. Pass the Idea through the Compiler / linker / doobry so that the Computer can understand them. Run the compiled Idea on the Computer.
If you have 0's and 1's why use compiler, organise them is such order that the computer understands them :). Intel books with machine instruction codes can be useful!
-
OriginalGriff wrote:
Now, organise the Ones and Zeros so that they fullfill your Idea. Pass the Idea through the Compiler / linker / doobry so that the Computer can understand them. Run the compiled Idea on the Computer.
If you have 0's and 1's why use compiler, organise them is such order that the computer understands them :). Intel books with machine instruction codes can be useful!
The Compiler converts the Ones and Zeros into blocks of 32 bits, so that the Computer can execute them - I thought everybody knew that!
-
OriginalGriff wrote:
Now, organise the Ones and Zeros so that they fullfill your Idea. Pass the Idea through the Compiler / linker / doobry so that the Computer can understand them. Run the compiled Idea on the Computer.
If you have 0's and 1's why use compiler, organise them is such order that the computer understands them :). Intel books with machine instruction codes can be useful!
I forgot, sorry, that some Computers only use 8 bits, so you will need an AngryCompiler to assemble seven Ones and Zeros together with a Parody bit into a byte before you can execute on those...
-
The Compiler converts the Ones and Zeros into blocks of 32 bits, so that the Computer can execute them - I thought everybody knew that!
Everybody also should know that: -blocks of 32bits are still 1's and 0's -fact that cpu's architecture is 32bit doesn't mean it has 32-bits blocks inside, most of instructions inside x86 are 2 byte long (not counting params, fe. most move-if commands are 0x0F 0xXX /r, where /r is register param) -That doesn't stop you to program in machine code by yourself :). Create *.COM file and write pure machine (16-bit though) code with any hex editor :).
-
Well, you will need a few things. 1) A Computer, with a monitor, keyboard, mouse and all the normal bits. (You can get one from eBay) 2) A Compiler / linker / doobry. (You can get one from those kind people at microsoft) 3) A good Idea for a program. (You can get one from your mates) 4) A very large collection of Ones and Zeros. (You can get them from me - I have a large stock of spares, some new, some used). Very cheap prices in bulk. Now, organise the Ones and Zeros so that they fullfill your Idea. Pass the Idea through the Compiler / linker / doobry so that the Computer can understand them. Run the compiled Idea on the Computer. Simple, isn't it? Now you just have to wonder why we all go to school, then university, and slave for a number of years in the industry before we call ourselves Software Engineers.
-
Errrhmmmm ... I don't think I see Testing in there!
10110011001111101010101000001000001101001010001010100000100000101000001000111100010110001011001011
Pfft... like that matters.
-
-
Luc Pattyn wrote:
can't test without specs...
I wish every company I have worked for had believed that...
OriginalGriff wrote:
I wish every any company I have worked for had believed that...
Fixed that for you
Never underestimate the power of human stupidity RAH
-
Luc Pattyn wrote:
can't test without specs...
I wish every company I have worked for had believed that...