[ migrate ] the maxim of programmers

Programmers motto ,GHD Classic Straighteners
first extract a few classical (made minor revisions to replace some traditional terms):

programmers do not need a knife to kill, three needs to change like

program is built on fortune and intuition of a miracle.
if both have, it is impossible to achieve such a duration that demand.
adjust the demand is a miracle Tucao desecration.
and additional changes will believe in miracles is not seeking to reproduce the action.

additional requirement to determine delivery time can not be determined after,
after the additional requirement to determine the period of delivery can not be determined.
This is called

incipient source: a programmer's motto? but, or bug
--------------------------
programmers maxim (stolen as many)
translated
* プ グ ラ ロ の マ motto (Pirates of the long on し)
* http://mixi.jp/view_community.pl?id=1772737 <br Do not write their own programs, the main work is to confirm with the customer specifications.
* Most programmers do not face the customer.
* not the same with the PM. (What is more suitable translation of the heading you?)
1. 24 hours a day.
so-called
2. program does not run according to his own thought. Will run according to written.
3. requirements specification will be finalized after the program ended. Basic Specifications
see the achieved product to customers until behind the decision.
after detailed specifications will be determined by the consumer.
4. I am the path software is designed to export the conclusion in two ways.
First, the software is designed not simply to the obvious flaws,
or another the software is designed apt be complicated and namely there is no manifest failings.
- CARHoare
5. program code should not jot in the development of on-site! To customers that jot!
debug Do not make the deadline! On-line and then do it!
6. the screen is blue!
(International Space Station astronauts re-install Windows NT, the record of the prominent)
7. first said
8. There are views, then you write
9. programmers do not need a knife to kill, to change three specifications like
10. First of all first surmise others, the suspected person may solve the problem will out.
(Note: often Only loosen (loosen).
12. No matter how late to determine the size, closing time will never change.
This is the so-called
13. customers all feel that with the added prerequisite of water is not money.
14. to pay more instigate more concern about the guests.
15. at the scheduled development of stroke, even a child will always be blind to some of the counts.
business is always a bunch of do not know 1 +1 = 2 people.
16. a man we all hung hung.
17. bug spent the night may become a standard.
18. a nice size looking to find a genius than three mortal.
descriptions to ascertain a hundred bad for looking for a mortal genius.
19. Customized 30% of the price of the software secondhand in the confirmation specifications.
30% with the modified specifications.
30% by looking bug.
results reflected in the cost of the initial specifications of the proportion of only 10%.
20. is subordinate to the customers, SE,GHD Diamond Flag 2011, programmers are cattle.
guests on the SE for the money, the program designer, the customer is invisible virus.
procedures in addition to get that done outside,GHD NZ, there is no other way to get rid of.
21. Customers absence to be like the SE, to understand their own system development takes time and money, as presently as possible to determine specifications.
SE want to be customers like, then let the programmers dislike myself.
22. Many programmers have secretly SE with money to spare and then think about what the system wants to make their own,
yet no such opportunity.
23. extent of deterioration of the quality specifications according to the number and scale of change may be.
24. business is capable to achieve that utopian dreamers.
SE is convinced that can destroy via any obstacles adventurer.
programmers are being dreamers and adventurers thrown into the black sea drifters.
25. talented programmers first saw the design details of the first to understand the purpose of the program.
understand next try to obtain SE to clarify the means of work and unable to finish the job.
26. program is built on luck and intuition of a miracle.
if either have, it is impossible to achieve such a work such specifications.
modify the specification is a miracle Tucao desecration.
and additional alterations will believe in miracles is not seeking to procreate the action.
27. programmers listened
ah, like a dream.
28. The interest in writing programs for the people, the so-called technology is the programming language ability.
for of work, book programs for the people, the so-called technology is the logical cerebral and interpersonal communication skills.
programming language can look at manuals, customer interaction, no.
29. procedures prior to delivery system will continue to shrink.
to amuse the employer first with component definitions.
shouting Minister of the intended budget concession to the reality of the program.
in the use of the appointment, the Section Chief will try to identify their areas of responsibility decrement.
meeting in the details, the pate of the scope will shrink to remember the part.
30. SE needs residing power, programmers need gunpowder power.
31. time to quit the company, the work will become more.
32. the faultless program needs the perfect time and money.
listened that the U.S. misspent the citizen budget for NASA, but too feel that time with enough money.
33. the detailed design of the comments in the program code in the finish.
endorsement is the only means of self-defense, or at least permit yourself to understand.
34. There is still time to see if the program code to execute him.
CPU run faster than head cells faster. At least this time to rest.
35. exception to the program known as
36. The so-called fortuitous days,GHD Benefit Straighteners, if the community phones him a holiday
(Note) Japan, some companies have so-called Casual Day (do not dress a suit and days), routinely on a Friday, but ...
37. Hell, after a period of time, transform more full of murderous fury.
continue fjust aboutme time, but the words will become less grumbles become more imposing ridge cover in the atmosphere.
longer be sustained, but will be opened up, filled with vibrant sounds nigh.
this state is called
38. distant blaze will scald here.
39. prayer, and then (Abbey's slogan)
40. Program is not with the brain in idea, use the body to remember.
41. morrow a holiday, then died worth saying.
42. outdoor the rain yeah, yesterday below it?
43. heart does not break the (negative), the body will devastate.
bloody if it were not for yourself, himself will be killed.
44. client will prevaricate, the business will be a nightmare, SE will be daydreaming.
programmers are Diandian. (More to himself)
45. SE is always unreasonable (unreasonable) that unreasonable)
46. specifications as navigational designs, the customer is the sea currents. Volatile ocean currents, oceanic drafts to become garbage.
programmers must be at sea without charts to find the power of their own continent.
47. and then whining is going to pay.
48. more like a 10 seconds, you can not say
49. who is unable to remember the lessons from the animals that others have failed.
slit costs, change specifications, plus demand, grab up with the line, no one has ever memorize the lessons from the many failures.
50. practiced to boost the morale of the wizardry motto:
then ...
51. The so-called Jiao circumstance duration refers to the evolution site to the purchaser from the corporation as the daytime there.
52. procedures, SE, managers are not functional category. Is a duty.
53. Business is the most difficult to agree customers.
54. can quickly think of too many programmers solution.
a minute they could think of ways to write programs one day.
do not need to spend an hour musing solution, and then an hour to write programs.
- Jon Bentley
55. good size, can be penetrated from the no bug there.
is obviously bad design, why is this ...
56. on the line until after the debugging is called bug.
57. Additional requirements resolved period of delivery tin not be decided,
after the additional requirement to determine the period of delivery can not be determined.
This is called
58. In counting to the three mistakes will appear a error.
This is called the infinite loop bug.
59. foreboding always achieved.
programmers not to worry, but a sense of foreboding, it is the work of SE.
60. way to solve the hell is that customers disburse out the money.
61. do not comprehend the operation of the microprocessor genius who is found bug. And can not reproduce.
62. each meeting to change the specifications of the customer,
to await until he's operating manual before operating the program written to write out.
63. do not understand the time, Currency (long integer) than Interger (integer) easy to use.
Variant (strings, mathematics can be cached in the global variables) surpasses Currency (long int) cozy to use.
safety first.
(VB programmer says)
64. ah, that was Microsoft's specifications.
65. programmers are disappointed with the specifications, have to make customer dissatisfaction.
(That is to say written by programmers find it laborious to communicate with the regional is often a breach among SE)
66. program designers need the skills,
including negotiation, time management, business analysis,GHD Hair Straightener NZ, proposals, design ,GHD Hair, languages, architecture, maintenance, use.
SE lost the capabilities needed at the programming language, architecture, maintenance and use.
capability to project managers absence to re-lose affair thinking, proposal and design.
discount business needs the competence to re-schedule management.
67. precisely because of health, in array to do morbid things.
68. (This is not bug you?)
regulations, specifications, a specification friends. However, there is not the same thing with the specifications of friends.
69. That is what you said specifications.
70. development room with no windows, it is because in the quondam ...
71. Even if the specification is putrid.
72. SE: I did not approach.
PG: did not remark.
(met do not know who wrote the program, we are helpless state)
73. Why can not you two or three to get rid of his friends.
because of his previous two or three things that get you two or three to have been denied.
74. Fixed the bug is not just an ordinary bug. (Moves the bug will be considered specifications)
75. Today, a good clean-up bug, bug should die off it.
Huh? Windows is dead yo.
76. Customers do not think about the worst. Him to face the worst-case scenario, he would think the sky asking price.
SE fear the worst is to prepare for the worst.
programmers earlier than anyone anticipated the worst case, when ignoring the worst.
77. The only way to not produce bug, just do not write programs.
the second best method is to determine the schedule with the staff after each change specifications, are re-examined the whole project.
78. the mutual duty is the duty of programmers.
treatment positions? That is what? Good? I have not dined yes.
79. If you can be distracted to it, trying to find reproductive cycle work is not called
80. on professional programmers, the beautiful and natural process is easy logic, simple and elementary directions, rich commentary,
is newcomer programmers can quickly change hands in the process.
but to write such a program, you need a simple, simple, beautiful and specifications.
guests always like to do but unfortunately very complicated.
81. designers should not be asked producers to produce extra content than the design it ...
82. if it is act more than the specifications in the book, or just write the book according to specifications, SE will looking for programmers ballast.
so programmers only write specifications of the contents of the paperback.
83. SE of the programmers said
84. to look up specifications. Can not scamper the specifications.
85.
day, often refers to the 3 man-days, one month is 4.5 months often Oh.
86. half hours to lose half of the monomer testing and system testing,
and delivery will must add variant two months after the on-line.
87. to get the money to change the specifications referred to as
is so programmers to read.
88. tired. I'm somnolent. Can go family.
(exhausted, and I'm exhausted. so tired how. anyhow, specifications friends, though he's)
89. trying to dwindle costs, in line with ration, quality will decline, but do attempt sky quality is not good out where to work.
90. REDO in the end do not understand how to read has always been. Is the profit pail you, Lee for man, REDO you, is it red zero? Please add phonetic it.
(annotate: I am more troubled Linux)
91. It was written in the code comments in the diary. Like Even the Speaking of this, seems to have peruse
92. When students first see the computer
the premier period while the nation capable how to learn to use
tall educate and campus programming language
the community only to find themselves taking the wrong path
93. Do not let the boss when the business is better
ex series
1. Even if the program that there was no bug, the compiler will bug.
even now the compiler did not bug, OS will be bug. Even if everything is OK
bug, customers will resolve what is bug.
2. Specifications and specifications are assorted things.
3. is more momentous than the duration of inspiration and sleep.
4. important than knowledge and experience is manual and time.
5. like a dynamic, active words ...
6. After three days of the program code is written by somebody else.
7. (Hunting Line)
specification changes occur not in the room! Is occurring in the field!
8. (Hunting Line)
exception not occur in the simulation test! Is the only area on the line!
9. beauteous design three days perhaps tired of the design of three days
dirty used
10. bug is one of the sides and specifications
11. computer There is no bug, bug often people.
12. No material how the retard, no matter how sure, the line is not nap the night ahead. (RFC968)
13. Valuation experience necessitated 1% and 99% of the intuition
14. There is naught instantly to find any bug in the program directly on the line but also horrifying.
15.
* 』=『 programmers organized does not make sense that SE can be translated into program code of the main
* SE 』=『 rewrite dispute with the client specifications, after discussion with the programmers rewrite the specification, the program will persist after the ship's specifications were rewritten
* PM 』=『 modify your journal timetable set by the industry veterans who
* 『』 = pale and absence of statement folk
* 』=『 outsourcing programs to help not write full time workers who write programs
* 『』 = duplicate and glue coding work
* 『』 = refers to the monomer began to write the test program
* 『』 = debug code comments to work out fashionable colleagues
* 『』 = fuel in the burning butt of the project who
* 』=『 ship by half of the system to be completed merely ashore the line sides of the last tram day
* 『』 = manufacture average of going hours
* 』=『 hurricane holiday baby boom work for the industry's year holiday
16. who wrote the program code when the bug ran out of time, that person is probably not in the (Murphy Theorem?)
17. a last resort
hardware limits