How do I writed softwares

Hey /prog/, how do I go from writing nifty little 200 line programs that don't do a whole lot to writing, say, an IRC client or something?

Is there a book?

you need to writed moar lines

Put a good amount of thought into design, then just begin writing and testing it component by component. The only danger writing large things by yourself is that you'll get bored halfway through and abandon it.

Learn about design patterns, development cycles (like the Spiral method for example), and how to properly organize your code.  Large systems aren't about programming anymore, they are about proper design.

>>4
and buzzwords ;)

Think up an ambitious program and dive into it. In my C class, Program #4 was coming up with a function to read sloppy user input, and Program #5 was a fake ATM that logged every transaction of every account. Even if the first thing you make falls through, you'll almost certainly come away with insight into getting the next one right.

Just avoid scope creep, plan out input and output, diagram what the program actually does before you start writing functions, and don't try to adjust its efficiency or otherwise polish it until you actually have it up and running.

>>1
The '80s and cool "look ma, space invaders in 200 lines" days are over, but fortunately we don't have to use basic anymore.

Like anyone before me, I recommend learning about program design (I didn't use the term "design patterns" on purpose) and finding out that churning out a ~5000 line program is not a big feat.

and never be afraid to admit that your orignal design may be completely dead wrong, too many screw ups happen because people insist their initial design is perfect and completely thought through, and then they end up at Y instead of B.

>>1
1. Think of something fun you want to achieve.
2. Design it properly. Don't care much for the cost of development.
3. Write it in a top-down style.
4. PROFIT

Do not care about lines of code, that's all bullshit; great stuff can be short and crappy stuff can be long; also, your programming style may produce twice as many or as little lines as the next guy.

Do not jerk off to design patterns or any buzzword either. Just  keep working and keep realizing stuff. It doesn't have to have a name as long as you know it's a good solution and how it works.

At your stage you may be more interested on low-level programming (i.e. C, plain C, not C++), which will help you have a crystal clear image of everything that's happening all the time, and will require you to write more elaborate software (using more lines of code so to speak).

LISP

beware the army of 12 year old autistics