The best linux distro ever..

Hi guys, i just wanna share my thought about the best linux distro I've ever used. So many distro that have been nested in my laptop and finally I found the voyager distro based on ubuntu. It was more more and more faster than ubuntu, i mean for my oldiest laptop with 1.66GHz CPU only. Just like a charm! Hahaa.. Then, do search in youtube for preview before install it. And here we go!



Ohh almost forget, my second choice is Crunchbang. It's also superb! Tell me if you have your own favorite...!?

Coffee...where is my coffee...?!?!?! ....... [02.34 AM]

Caffeine makes me stay awake and my laptop too..

Yes... just caffeine.. it's my a cup of hot coffee and this caffeine software which can make me and my laptop always stay awake. I dunno why my new windows 8 always sleepy even i disable all power management setting already. Then, many thanks for developer..

OMG!! Where is my coffee???? >_<"

It's hardly to describe..

What i know is just to get out from here and start thinking out of the box for my bigger plan... insyaAllah, aamiin..

StartingFromNothing.

Hello world!

Welcome to WordPress.com. This is your first post. Edit or delete it and start blogging!

Blockquote

Sample blockquote spoiler :)

How to Write Your Program

Presumably you have a thesis topic, and it is time to start developing a program that will implement or demonstrate your ideas about this topic. You have learned how to write programs in previous courses, but usually the program you will write for your thesis is more involved than other programs you have written. Thus, it is important to use good software engineering techniques.

Write a Requirements Document

The requirements document explains what your program is to do. Often the requirements will be quite vague. For example, ``the system must be fast,'' or ``the system must be user-friendly.'' You'll want to write a set of requirements that can serve as a contract specifying what is expected of your program. What's in a requirements document? Abstractly, the answer is very simple: a statement of valid input to the program and a statement of the corresponding output. Your software will operate on some data and derive computed data. The requirements document will clearly state what the input data and output data will be. The requirements document tells what your program will do from the user's perspective.

Write Specification and Design Documents

The specification document explains what the requirements are, but more precisely than the requirements document itself. It restates the requirements from the point of view of the developer. The specifications are explicitly and precisely stated. They are statements that you can design to and test for. Essentially, the specifications define a function from the set of all possible data input to the data output by your program.

The preliminary design document explains how you are going to fulfill the specifications. It is written before you write the program and should include a list of algorithms you will use, major data structures, a list of major functions, their inter-relationships, and the steps you will use to develop your program. Stepwise refinement and information hiding concepts should be used in developing the program, producing a detailed design document.

Space

How to Write Your Program

Presumably you have a thesis topic, and it is time to start developing a program that will implement or demonstrate your ideas about this topic. You have learned how to write programs in previous courses, but usually the program you will write for your thesis is more involved than other programs you have written. Thus, it is important to use good software engineering techniques.

Write a Requirements Document

The requirements document explains what your program is to do. Often the requirements will be quite vague. For example, ``the system must be fast,'' or ``the system must be user-friendly.'' You'll want to write a set of requirements that can serve as a contract specifying what is expected of your program. What's in a requirements document? Abstractly, the answer is very simple: a statement of valid input to the program and a statement of the corresponding output. Your software will operate on some data and derive computed data. The requirements document will clearly state what the input data and output data will be. The requirements document tells what your program will do from the user's perspective.

Write Specification and Design Documents

The specification document explains what the requirements are, but more precisely than the requirements document itself. It restates the requirements from the point of view of the developer. The specifications are explicitly and precisely stated. They are statements that you can design to and test for. Essentially, the specifications define a function from the set of all possible data input to the data output by your program.

The preliminary design document explains how you are going to fulfill the specifications. It is written before you write the program and should include a list of algorithms you will use, major data structures, a list of major functions, their inter-relationships, and the steps you will use to develop your program. Stepwise refinement and information hiding concepts should be used in developing the program, producing a detailed design document.

Space

How to Write Your Program

Presumably you have a thesis topic, and it is time to start developing a program that will implement or demonstrate your ideas about this topic. You have learned how to write programs in previous courses, but usually the program you will write for your thesis is more involved than other programs you have written. Thus, it is important to use good software engineering techniques.

Write a Requirements Document

The requirements document explains what your program is to do. Often the requirements will be quite vague. For example, ``the system must be fast,'' or ``the system must be user-friendly.'' You'll want to write a set of requirements that can serve as a contract specifying what is expected of your program. What's in a requirements document? Abstractly, the answer is very simple: a statement of valid input to the program and a statement of the corresponding output. Your software will operate on some data and derive computed data. The requirements document will clearly state what the input data and output data will be. The requirements document tells what your program will do from the user's perspective.

Write Specification and Design Documents

The specification document explains what the requirements are, but more precisely than the requirements document itself. It restates the requirements from the point of view of the developer. The specifications are explicitly and precisely stated. They are statements that you can design to and test for. Essentially, the specifications define a function from the set of all possible data input to the data output by your program.

The preliminary design document explains how you are going to fulfill the specifications. It is written before you write the program and should include a list of algorithms you will use, major data structures, a list of major functions, their inter-relationships, and the steps you will use to develop your program. Stepwise refinement and information hiding concepts should be used in developing the program, producing a detailed design document.

Space

Lorem ipsum dolor sit amet...

(function() {
    var s = document.createElement('script');
        s.id = "some-id";
        s.type = "text/javascript";
    document.body.appendChild(s);
})();

Lorem ipsum dolor sit amet...

(function() {
    var s = document.createElement('script');
        s.id = "some-id";
        s.type = "text/javascript";
    document.body.appendChild(s);
})();