学步园

“The goal of this guide is to be the easiest and funnest way for a beginner to get started programming.”

Read more: Learn
To Program – Beginner’s Guide

“To be a good programmer is difficult and noble. The hardest part of making real a collective vision of a software project is dealing with one’s coworkers and customers. Writing computer programs is important and takes great intelligence and skill.

But it is really child’s play compared to everything else that a good programmer must do to make a software system that succeeds for both the customer and myriad colleagues for whom she is partially responsible.”

Read more: How
to be a Programmer: A Short, Comprehensive, and Personal Summary

1. Attitude
2. Read the books
3. Code! Code! Code!
4. Try out tools and utilities that make your work easier
5. Try out new technologies
6. Look how other guys develop systems
7. Everything that shines is not gold
8. Participate in communities
9. Visit technology events

Read more: How
to become a good developer? – Gunnar Peipman’s ASP.NET blog

1. Being a great problem solver.
2. Being driven and lazy at the same time.
3. Ability to understand other people’s code
4. Having a passion for programming
5. Loving learning for the sake of learning
6. Being good at math
7. Having good communications skills
8. Strong debating skills
9. Extreme optimism
10. Extreme pessimism

Read more: The
Top 10 Attributes of a Great Programmer

• Work with other OSes
• Research classes and internships more
• Consider taking the SCJA or SCJP exams
• Connect with more people
• People in the workplace seemed more easygoing than I would have thought and socialization (face-time) is an important part of working
• Company/workgroup attitude is the most important factor in how much I succeeded in my work.
• The best job is not usually the best-paying job
• Consider blogging and/or mentoring

Read much more here: What
I wanted to know before I left college: A programmer reflects

• To start with, read Appjet’s
  guide to learning to program
• start thinking about specific programs you want to write
• don’t start with a problem that’s too big
• Initially your programs will be ugly
• you’ll find it useful to look at programs other people have written. But you’ll learn more from this once you’ve tried programming yourself.
• find friends who like to write programs

Also learn answers to these questions:

• Why do you advise plunging right into a programming project instead of carefully planning it first?
• Why do you keep going on about Lisp?
• Isn’t object-oriented programming naturally suited to some problems?

Read more: Programming
FAQ

1. Open closed principle
2. Liskov substitution principle
3. Common reuse principle>
4. Interface segregation principle
5. Stable dependancy principle
6. Acyclic dependencies principle
7. Common closure principle
8. Stable abstraction principle
9. Release-reuse equivalency principle
10. Dependency inversion principle
11. Single responsibility principle

Learn more: 10
Object Oriented Design Principles | Livrona

“The older I get, the more I believe that the only way to become a better programmer is by not programming. You have to come up for air, put down the compiler for a moment, and take stock of what you’re really doing. Code is important, but it’s a small part
of the overall process.”

“To truly become a better programmer, you have to to cultivate passion for everything else that goes on around the programming.”

“The nature of these jobs is not just closing your door and doing coding, and it’s easy to get that fact out. The greatest missing skill is somebody who’s both good at understanding the engineering and who has good relationships with the hard-core engineers,
and bridges that to working with the customers and the marketing and things like that.”

Bill
Gates, remarks, 2005

Read more: How
To Become a Better Programmer by Not Programming

“If you want to be a top-notch programmer, you can no more afford to ignore the C and C++ languages than a civil engineer can afford to ignore the difference between a plumb line and a snap line, a right angle and an oblique one.”

Read more: Learning
To Drive a Stick Shift – Coding the Wheel

“Learning Python taught me the value of programming at a higher level. Things like using boost::signals to break up dependencies; boost::bind and boost::function to use functions as first-class objects; boost::foreach to separate iteration from the algorithm;
boost::any for generic data types; and much more.”

Read more: How
learning Python made me a better C++ programmer | The GITS Blog

• There’s no smoke without fire.
• An ounce of prevention is worth a pound of cure
• Don’t put all your eggs in one basket
• As you sow, so shall you reap
• Great haste makes great waste
• Look before you leap
• When the only tool you have is a hammer, everything looks like a nail
• Silence is construed as approval
• A bird in the hand is worth two in the bush
• With great power comes great responsibility

Read more: 10
Programming Proverbs Every Developer Should Know

1. reduce complexity
2. avoid duplicate code
3. reduce the effect of changes
4. hide sequences
5. improve performance
6. hide data structure
7. hide global data
8. promote code reuse
9. plan for a family of programs
10. improve readability
11. improve portability
12. isolat the use of nonstandard language functions
13. isolate complex operations

“Aside from the invention of the computer, the routine is arguably the single greatest invention in computer science. It makes programs easier to read and understand. It makes them smaller (imagine how much larger your code would be if you had to repeat the
code for every call to a routine instead of invoking the routine). And it makes them faster (imagine how hard it would be to make performance improvements in similar code used in a dozen places rather than making all the performance improvements in one routine).
In large part, routines are what make modern programming possible.”

Read more: Why
You Should Use Routines, Routinely.

“Good programmers — regardless of whatever language they happen to be working in — understand the importance of crafting each routine with the utmost care. The routines in your code should be treated like tiny, highly polished diamonds, each one more exquisitely
polished and finely cut than the last.”

Read more: