-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
1776 lines (1521 loc) · 106 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!doctype html>
<html class="no-js" lang="en">
<head>
<meta charset="utf-8">
<title>Computer science aphorisms</title>
<meta name="description" content="Collection of aphorisms about computer science, with focus on programming and coding">
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- <link rel="manifest" href="site.webmanifest">
<link rel="apple-touch-icon" href="icon.png"> -->
<!-- Place favicon.ico in the root directory -->
<link rel="stylesheet" href="https://unpkg.com/[email protected]/build/pure-min.css" integrity="sha384-nn4HPE8lTHyVtfCBi5yW9d20FjT8BJwUXyWZT9InLYax14RDjBj46LmSztkmNP9w" crossorigin="anonymous">
<link rel="stylesheet" href="css/main.css">
<meta name="theme-color" content="#fafafa">
<meta name="google-site-verification" content="UbEY8kXrg4Dvc23Rn9HHvVO81VS0yLMDxpBoFdOx_Mg" />
<script src="js/main.js"></script>
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-16636362-2"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-16636362-2');
</script>
</head>
<body>
<div class="container">
<header class="header">
<h1>Computer science aphorisms</h1>
<p>Collection of aphorisms about computer science, with focus on programming and coding</p>
</header>
<main class="main">
<a id="sort-by" rel="nofollow" title="sort by author" class="pure-button">
<i class="fa fa-cog"></i>
sort by author
</a>
<article class="aphorism" id="90-of-the-functionality-d">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>90% of the functionality delivered now is better than 100% delivered never.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Brian_Kernighan" rel="author">Brian W. Kernighan</a></cite></footer>
</article>
<article class="aphorism" id="a-common-fallacy-is-to-as">
<blockquote cite="https://twitter.com/KevlinHenney/status/381021802941906944">
<p>A common fallacy is to assume authors of incomprehensible code will somehow be able to express themselves lucidly and clearly in comments.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://twitter.com/KevlinHenney" rel="author">Kevlin Henney</a></cite></footer>
</article>
<article class="aphorism" id="a-computer-lets-you-make">
<blockquote cite="http://www.defprogramming.com/quotes-by/mitch-ratcliffe/">
<p>A computer lets you make more mistakes faster than any other invention in human history, with the possible exceptions of handguns and tequila.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://it.wikipedia.org/wiki/Mitch_Ratcliffe" rel="author">Mitch Ratcliffe</a></cite></footer>
</article>
<article class="aphorism" id="a-great-lathe-operator-co">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>A great lathe operator commands several times the wage of an average lathe operator, but a great writer of software code is worth 10,000 times the price of an average software writer.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Bill_Gates" rel="author">Bill Gates</a></cite></footer>
</article>
<article class="aphorism" id="a-language-that-doesnt-ha">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>A language that doesn't have everything is actually easier to program in than some that do.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Dennis_Ritchie" rel="author">Dennis M. Ritchie</a></cite></footer>
</article>
<article class="aphorism" id="a-programmer-does-not-pri">
<blockquote cite="https://en.wikipedia.org/wiki/Brooks%27s_law">
<p>A programmer does not primarily write code; rather, he primarily writes to another programmer about his problem solution. The understanding of this fact is the final step in his maturation as technician.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Anonymous</span></cite></footer>
</article>
<article class="aphorism" id="a-programming-language-is">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>A programming language is low level when its programs require attention to the irrelevant.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Alan_Perlis" rel="author">Alan Perlis</a></cite></footer>
</article>
<article class="aphorism" id="a-programmer-is-a-person">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>A programmer is a person who passes as an exacting expert on the basis of being able to turn out, after innumerable punching, an infinite series of incomprehensive answers calculated with micrometric precisions from vague assumptions based on debatable figures taken from inconclusive documents and carried out on instruments of problematical accuracy by persons of dubious reliability and questionable mentality for the avowed purpose of annoying and confounding a hopelessly defenseless department that was unfortunate enough to ask for the information in the first place.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">IEEE Grid newsmagazine</span></cite></footer>
</article>
<article class="aphorism" id="a-system-with-300-boolean">
<blockquote cite="https://blog.devgenius.io/no-silver-bullet-65cba1775f9b">
<p>A system with 300 Boolean configurations has more test combinations (2 ^ 300), than the number of atoms in the universe (10 ^ 80).</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Unknown</span></cite></footer>
</article>
<article class="aphorism" id="adding-human-resources-to">
<blockquote cite="https://en.wikipedia.org/wiki/Brooks%27s_law">
<p>Adding human resources to a late software project makes it later.</p>
</blockquote>
<footer class="aphorism-footer">Brooks's law by <cite><a target="_blank" href="https://en.wikipedia.org/wiki/Fred_Brooks" rel="author">Fred Brooks</a></cite></footer>
</article>
<article class="aphorism">
<blockquote cite="">
<p>All problems in computer science can be solved with another layer of indirection. Except for the problem of too many layer of indirection.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/David_Wheeler_(computer_scientist)" rel="author">David Wheeler</a></cite></footer>
</article>
<article class="aphorism" id="all-programming-languages">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>All programming languages are shit. But the good ones fertilize your mind.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Reg Braithwaite</span></cite></footer>
</article>
<article class="aphorism" id="almost-anything-in-softwa">
<blockquote cite="https://en.wikiquote.org/wiki/C._A._R._Hoare">
<p>Almost anything in software can be implemented, sold, and even used given enough determination. There is nothing a mere scientist can say that will stand against the flood of a hundred million dollars. But there is one quality that cannot be purchased in this way — and that is reliability. The price of reliability is the pursuit of the utmost simplicity. It is a price which the very rich find most hard to pay.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Tony_Hoare" rel="author">C.A.R. Hoare</a></cite></footer>
</article>
<article class="aphorism" id="always-be-refactoring-if">
<blockquote cite="https://martinfowler.com/books/refactoring.html">
<p>Always be refactoring. If you touch the code, and you can improve it, improve it, but never optimise early.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://www.martinfowler.com/" rel="author">Martin Fowler</a></cite></footer>
</article>
<article class="aphorism" id="always-code-as-if-the-guy">
<blockquote cite="https://catonmat.net/popular-programming-quotes">
<p>Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">John F. Woods</span></cite></footer>
</article>
<article class="aphorism" id="always-implement-things-w">
<blockquote cite="https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it">
<p>Always implement things when you actually need them, never when you just foresee that you need them.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Ron_Jeffries" rel="author">Ron Jeffries</a></cite></footer>
</article>
<article class="aphorism" id="an-evolving-system-increa">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>An evolving system increases its complexity unless work is done to reduce it.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Manny_Lehman_(computer_scientist)" rel="author">Meir Lehman</a></cite></footer>
</article>
<article class="aphorism" id="and-as-any-designer-can-t">
<blockquote cite="https://leanpub.com/yourapiisbad">
<p>And as any designer can tell you, if your user expects your software to do something, that better be what your software does.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a rel="author">Paddy Foran</a></cite></footer>
</article>
<article class="aphorism" id="and-dont-ever-make-the-mi">
<blockquote cite="http://tinyurl.com/2kkl77">
<p>And don’t EVER make the mistake that you can design something better than what you get from ruthless massively parallel trial-and-error with a feedback cycle. That’s giving your intelligence much too much credit.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Linus_Torvalds" rel="author">Linus Torvalds</a></cite></footer>
</article>
<article class="aphorism" id="any-app-that-can-be-writt">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>Any app that can be written in JavaScript, will eventually be written in JavaScript.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Jeff_Atwood" rel="author">Jeff Atwood</a></cite></footer>
</article>
<article class="aphorism" id="any-code-of-your-own-that">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>Any code of your own that you haven't looked at for six or more months might as well have been written by someone else.</p>
</blockquote>
<footer class="aphorism-footer"><cite>Eagleson's Law by <span rel="author">Alan Eagleson</span></cite></footer>
</article>
<article class="aphorism" id="any-fool-can-write-code-t">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>Any fool can write code that a computer can understand. Good programmers write code that humans can understand.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Martin_Fowler_(software_engineer)" rel="author">Martin Fowler</a></cite></footer>
</article>
<article class="aphorism" id="any-organization-that-des">
<blockquote cite="https://martinfowler.com/bliki/ConwaysLaw.html">
<p>Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Martin_Conway_(historian)" rel="author">Melvin Conway</a></cite></footer>
</article>
<article class="aphorism" id="applications-programming">
<blockquote cite="https://en.wikiquote.org/wiki/Programming">
<p>Applications programming is a race between software engineers, who strive to produce idiot-proof programs, and the universe which strives to produce bigger idiots. So far the Universe is winning.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikiquote.org/wiki/Rick_Cook" rel="author">Rick Cook</a></cite></footer>
</article>
<article class="aphorism" id="as-a-rule-software-system">
<blockquote cite="http://quotes.cat-v.org/programming/">
<p>As a rule, software systems do not work well until they have been used, and have failed repeatedly, in real applications.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/David_Parnas" rel="author">David Parnas</a></cite></footer>
</article>
<article class="aphorism" id="asking-for-efficiency-and">
<blockquote cite="https://en.wikiquote.org/wiki/Programming">
<p>Asking for efficiency and adaptability in the same program is like asking for a beautiful and modest wife. Although beauty and modesty have been known to occur in the same woman, we'll probably have to settle for one or the other. At least that's better than neither. </p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Gerald M. Weinberg</span></cite></footer>
</article>
<article class="aphorism" id="at-some-point-software-de">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>At some point software design becomes less about what and more about when.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Kent Beck</span></cite></footer>
</article>
<article class="aphorism" id="beauty-is-more-important">
<blockquote cite="http://quotes.cat-v.org/programming/">
<p>Beauty is more important in computing than anywhere else in technology because software is so complicated. Beauty is the ultimate defence against complexity.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/David_Gelernter" rel="author">David Gelernter</a></cite></footer>
</article>
<article class="aphorism" id="be-conservative-in-what-y">
<blockquote cite="https://martinfowler.com/bliki/TolerantReader.html">
<p>Be conservative in what you do, be liberal in what you accept from others.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://datatracker.ietf.org/doc/html/rfc793" rel="author">Jon Postel</a></cite></footer>
</article>
<article class="aphorism" id="before-software-can-be-re">
<blockquote cite="http://www.defprogramming.com/quotes-by/ralph-johnson/">
<p>Before software can be reusable it first has to be usable.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Ralph_Johnson_(computer_scientist)" rel="author">Ralph Johnson</a></cite></footer>
</article>
<article class="aphorism" id="better-train-people-and-r">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>Better train people and risk they leave – than do nothing and risk they stay</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Unknown</span></cite></footer>
</article>
<article class="aphorism" id="c-is-quirky-flawed-and-an">
<blockquote cite="http://www.gdargaud.net/Humor/QuotesProgramming.html">
<p>C is quirky, flawed, and an enormous success.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Dennis_Ritchie" rel="author">Dennis M. Ritchie</a></cite></footer>
</article>
<article class="aphorism" id="c-makes-it-easy-to-shoot">
<blockquote cite="https://en.wikiquote.org/wiki/Bjarne_Stroustrup">
<p>C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do it blows your whole leg off.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Bjarne_Stroustrup" rel="author">Bjarne Stroustrup</a></cite></footer>
</article>
<article class="aphorism" id="code-never-lies-comments">
<blockquote cite="http://quotes.cat-v.org/programming/">
<p>Code never lies, comments sometimes do.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Ron_Jeffries" rel="author">Ron Jeffries</a></cite></footer>
</article>
<article class="aphorism" id="complexity-is-where-the-b">
<blockquote cite="https://twitter.com/highflyer910/status/956920707396620288">
<p>Complexity is where the bugs hide🐛🐛🐛</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://twitter.com/highflyer910" rel="author">Thea</a></cite></footer>
</article>
<article class="aphorism" id="complexity-kills-it-sucks">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>Complexity kills. It sucks the life out of developers, it makes products difficult to plan, build and test, it introduces security challenges, and it causes end-user and administrator frustration.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Ray_Ozzie" rel="author">Ray Ozzie</a></cite></footer>
</article>
<article class="aphorism" id="computer-programming-is-t">
<blockquote cite="https://en.wikiquote.org/wiki/Programming">
<p>Computer programming is tremendous fun. Like music, it is a skill that derives from an unknown blend of innate talent and constant practice. Like drawing, it can be shaped to a variety of ends – commercial, artistic, and pure entertainment. Programmers have a well-deserved reputation for working long hours, but are rarely credited with being driven by creative fevers. Programmers talk about software development on weekends, vacations, and over meals not because they lack imagination, but because their imagination reveals worlds that others cannot see. </p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Larry O'Brien</span> and <span rel="author">Bruce Eckel</span></cite></footer>
</article>
<article class="aphorism" id="computer-programs-are-the">
<blockquote cite="https://en.wikiquote.org/wiki/Programming">
<p>Computer programs are the most intricate, delicately balanced and finely interwoven of all the products of human industry to date. They are machines with far more moving parts than any engine: the parts don't wear out, but they interact and rub up against one another in ways the programmers themselves cannot predict.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikiquote.org/wiki/James_Gleick" rel="author">James Gleick</a></cite></footer>
</article>
<article class="aphorism" id="computer-science-educatio">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>Computer science education cannot make anybody an expert programmer any more than studying brushes and pigment can make somebody an expert painter.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Eric Raymond</span></cite></footer>
</article>
<article class="aphorism" id="computer-science-is-no-mo">
<blockquote cite="https://en.wikiquote.org/wiki/Edsger_W._Dijkstra">
<p>Computer science is no more about computers than astronomy is about telescopes.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Edsger_Wybe_Dijkstra" rel="author">Edsger W. Dijkstra</a></cite></footer>
</article>
<article class="aphorism" id="computers-are-like-old-te">
<blockquote cite="https://www.brainyquote.com/quotes/joseph_campbell_383491">
<p>Computers are like Old Testament gods; lots of rules and no mercy.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Joseph_Campbell" rel="author">Joseph Campbell</a></cite></footer>
</article>
<article class="aphorism" id="controlling-complexity-is">
<blockquote cite="https://en.wikiquote.org/wiki/Brian_Kernighan">
<p>Controlling complexity is the essence of computer programming.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Brian_Kernighan" rel="author">Brian W. Kernighan</a></cite></footer>
</article>
<article class="aphorism" id="data-dominates-if-youve-c">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>Data dominates. If you've chosen the right data structures and organized things well, the algorithms will almost always be self-evident. Data structures, not algorithms, are central to programming.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Rob_Pike" rel="author">Rob Pike</a></cite></footer>
</article>
<article class="aphorism" id="debugging-is-twice-as-har">
<blockquote cite="https://en.wikiquote.org/wiki/Brian_Kernighan">
<p>Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Brian_Kernighan" rel="author">Brian W. Kernighan</a></cite></footer>
</article>
<article class="aphorism">
<blockquote cite="https://nealford.com/books/productiveprogrammer">
<p>Developers are drawn to complexity like moths to a flame, often with same outcome.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://nealford.com/" rel="author">Neal Ford</a></cite></footer>
</article>
<article class="aphorism" id="dont-assume-anything-beca">
<blockquote cite="https://github.com/97-things/97-things-every-programmer-should-know">
<p>Don’t ASSUME anything because you’ll make an ASS out of U and ME!</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://twitter.com/gerardmes" rel="author">Gerard Meszaros</a></cite></footer>
</article>
<article class="aphorism" id="dont-repeat-yourself">
<blockquote cite="">
<p>Don’t repeat yourself</p>
</blockquote>
<footer class="aphorism-footer"><abbr title="Don’t Repeat Yourself">DRY</abbr> principle</footer>
</article>
<article class="aphorism" id="duplication-is-far-cheape">
<blockquote cite="https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction">
<p>Duplication is far cheaper than the wrong abstraction</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://sandimetz.com/" rel="author">Sandi Metz</a></cite></footer>
</article>
<article class="aphorism" id="each-pattern-describes-a">
<blockquote cite="https://www.ics.uci.edu/~pattis/quotations.html">
<p>Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it in the same way twice. </p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Christopher_Alexander" rel="author">Christopher Alexander</a></cite></footer>
</article>
<article class="aphorism" id="easy-to-use-and-hard-to-m">
<blockquote cite="http://www.principles-wiki.net/principles:easy_to_use_and_hard_to_misuse">
<p>Easy To Use And Hard To Misuse</p>
</blockquote>
<footer class="aphorism-footer">This principle is common wisdom among API designers.</footer>
</article>
<article class="aphorism" id="every-great-developer-you">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>Every great developer you know got there by solving problems they were unqualified to solve until they actually did it.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Patrick McKenzie</span></cite></footer>
</article>
<article class="aphorism" id="every-program-attempts-to">
<blockquote cite="https://en.wikiquote.org/wiki/Programming">
<p>Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.</p>
</blockquote>
<footer class="aphorism-footer"><cite>Zawinski's Law by <a target="_blank" href="https://en.wikiquote.org/wiki/Jamie_Zawinski" rel="author">Jamie Zawinski</a></cite></footer>
</article>
<article class="aphorism" id="everything-should-be-made">
<blockquote cite="https://en.wikiquote.org/wiki/Albert_Einstein">
<p>Everything should be made as simple as possible, but not simpler.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Albert_Einstein" rel="author">Albert Einstein</a></cite></footer>
</article>
<article class="aphorism" id="favor-object-composition">
<blockquote cite="https://en.wikipedia.org/wiki/Design_Patterns">
<p>Favor object composition over class inheritance.</p>
</blockquote>
<footer class="aphorism-footer">Foundational principles in “Design Patterns” book by the <cite><a target="_blank" href="https://en.wikipedia.org/wiki/Design_Patterns" rel="author">Gang of Four</a></cite>.</footer>
</article>
<article class="aphorism" id="fifty-years-of-programmin">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>Fifty years of programming language research, and we end up with C++?</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Richard_O%27Keefe" rel="author">Richard A. O’Keefe</a></cite></footer>
</article>
<article class="aphorism" id="first-do-it-then-do-it-ri">
<blockquote cite="https://twitter.com/addyosmani/status/314785735171518464">
<p>First do it, then do it right, then do it better.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://addyosmani.com/" rel="author">Addy Osmani</a></cite></footer>
</article>
<article class="aphorism" id="for-each-desired-change-m">
<blockquote cite="https://www.oreilly.com/library/view/refactoring-improving-the/9780134757681/">
<p>For each desired change, make the change easy (warning: this may be hard), then make the easy change.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Martin_Fowler_(software_engineer)" rel="author">Martin Fowler</a></cite></footer>
</article>
<article class="aphorism" id="fools-ignore-complexity-p">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>Fools ignore complexity. Pragmatists suffer it. Some can avoid it. Geniuses remove it.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Alan_Perlis" rel="author">Alan Perlis</a></cite></footer>
</article>
<article class="aphorism" id="functions-should-do-one-t">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>Functions should do one thing. They should do it well. They should do it only.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Robert_C._Martin" rel="author">Robert C. Martin</a></cite></footer>
</article>
<article class="aphorism" id="global-data-illustrates-p">
<blockquote cite="https://www.oreilly.com/library/view/refactoring-improving-the/9780134757681/">
<p>Global data illustrates Paracelsus’s maxim: The difference between a poison and something benign is the dose.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Martin_Fowler_(software_engineer)" rel="author">Martin Fowler</a></cite></footer>
</article>
<article class="aphorism" id="good-code-is-its-own-best">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>Good code is its own best documentation.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Steve_McConnell" rel="author">Steve McConnell</a></cite></footer>
</article>
<article class="aphorism" id="good-programmers-dont-jus">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>Good programmers don't just write programs. They build a working vocabulary.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Guy Steele</span></cite></footer>
</article>
<article class="aphorism" id="good-programmers-never-wr">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>Good programmers never write what they can steal or borrow.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Jeff_Atwood" rel="author">Jeff Atwood</a></cite></footer>
</article>
<article class="aphorism" id="java-write-once-debug-eve">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>Java: Write Once, Debug Everywhere</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Unknown</span></cite></footer>
</article>
<article class="aphorism" id="habits-affect-all-your-wo">
<blockquote cite="https://en.wikipedia.org/wiki/Code_Complete">
<p>Habits affect all your work; you can't turn them on and off at will, so be sure that what you're doing is something you want to become a habit. A professional programmer writes readable code, period.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Steve_McConnell" rel="author">Steve McConnell</a></cite></footer>
</article>
<article class="aphorism" id="hardware-eventually-fails">
<blockquote cite="https://twitter.com/compscifact/status/578907672294121472">
<p>Hardware eventually fails. Software eventually works.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Michael Hartung</span></cite></footer>
</article>
<article class="aphorism" id="hiring-bad-developers-is">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>Hiring bad developers is like drinking seawater. It seems to satisfy a need while actually increasing it.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Michael Nygard</span></cite></footer>
</article>
<article class="aphorism" id="hofstadters-law-it-always">
<blockquote cite="https://en.wikipedia.org/wiki/Hofstadter%27s_law">
<p>Hofstadter’s Law: it always takes longer than you expect, even when you take into account Hofstadter’s Law.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Douglas_Hofstadter" rel="author">Douglas Hofstadter</a></cite></footer>
</article>
<article class="aphorism" id="if-i-had-1-hour-to-solve">
<blockquote cite="https://en.wikiquote.org/wiki/Albert_Einstein">
<p>If i had 1 hour to solve a problem I'd spend 55 minutes thinking about the problem and 5 minute thinking about the solutions.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Albert_Einstein" rel="author">Albert Einstein</a></cite></footer>
</article>
<article class="aphorism" id="if-it-aint-broke-dont-fix">
<blockquote cite="https://en.wiktionary.org/wiki/if_it_ain%27t_broke,_don%27t_fix_it">
<p>If it ain't broke, don't fix it.</p>
</blockquote>
<footer class="aphorism-footer"><cite>Proverb</cite></footer>
</article>
<article class="aphorism" id="i-dont-care-if-it-works-o">
<blockquote cite="http://www.defprogramming.com/quotes-by/vidiu-platon/">
<p>I don’t care if it works on your machine! We are not shipping your machine!</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Vidiu Platon</span></cite></footer>
</article>
<article class="aphorism" id="i-have-always-wished-for">
<blockquote cite="https://en.wikiquote.org/wiki/Bjarne_Stroustrup">
<p>I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Bjarne_Stroustrup" rel="author">Bjarne Stroustrup</a></cite></footer>
</article>
<article class="aphorism" id="i-have-yet-to-meet-a-c-co">
<blockquote cite="http://www.gdargaud.net/Humor/QuotesProgramming.html">
<p>I have yet to meet a C compiler that is more friendly and easier to use than eating soup with a knife.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Unknown</span></cite></footer>
</article>
<article class="aphorism" id="i-have-yet-to-see-any-pro">
<blockquote cite="https://www.brainyquote.com/authors/poul-anderson-quotes">
<p>I have yet to see any problem, however complicated, which, when you looked at it in the right way, did not become still more complicated.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Anderson’s Law</span></cite></footer>
</article>
<article class="aphorism" id="i-know-testers-who-make-g">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>I know testers who make good devs. I know devs who make good testers. I know Scrum Masters who make good coffee.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">David Evans</span></cite></footer>
</article>
<article class="aphorism" id="im-not-a-great-programmer">
<blockquote cite="https://www.goodreads.com/quotes/tag/programming">
<p>I'm not a great programmer; I'm just a good programmer with great habits.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Kent_Beck" rel="author">Kent Beck</a></cite></footer>
</article>
<article class="aphorism" id="ive-finally-learned-what">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>I’ve finally learned what ‘upward compatible’ means. It means we get to keep all our old mistakes.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Dennie van Tassel</span></cite></footer>
</article>
<article class="aphorism" id="i-think-microsoft-named-n">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>I think Microsoft named .Net so it wouldn’t show up in a Unix directory listing.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Oktal</span></cite></footer>
</article>
<article class="aphorism" id="i-will-in-fact-claim-that">
<blockquote cite="https://en.wikiquote.org/wiki/Linus_Torvalds">
<p>I will, in fact, claim that the difference between a bad programmer and a good one is whether he considers his code or his data structures more important. Bad programmers worry about the code. Good programmers worry about data structures and their relationships.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Linus_Torvalds" rel="author">Linus Torvalds</a></cite></footer>
</article>
<article class="aphorism" id="if-a-feature-is-sometimes">
<blockquote cite="https://www.crockford.com/pp/better.pptx">
<p>If a feature is sometimes dangerous, and there is a better option, then always use the better option.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Douglas_Crockford" rel="author">Douglas Crockford</a></cite></footer>
</article>
<article class="aphorism" id="if-builders-built-buildin">
<blockquote cite="https://en.wikiquote.org/wiki/Programming">
<p>If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Gerald_Weinberg" rel="author">Gerald Weinberg</a></cite></footer>
</article>
<article class="aphorism" id="if-debugging-is-the-proce">
<blockquote cite="https://en.wikiquote.org/wiki/Edsger_W._Dijkstra">
<p>If debugging is the process of removing software bugs, then programming must be the process of putting them in.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Edsger_Wybe_Dijkstra" rel="author">Edsger W. Dijkstra</a></cite></footer>
</article>
<article class="aphorism" id="if-it-wasnt-for-c-wed-be">
<blockquote cite="http://www.gdargaud.net/Humor/QuotesProgramming.html">
<p>If it wasn't for C, we'd be writing programs in BASI, PASAL, and OBOL.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Unknown</span></cite></footer>
</article>
<article class="aphorism" id="if-java-had-true-garbage">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>If Java had true garbage collection, most programs would delete themselves upon execution.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Robert Sewell</span></cite></footer>
</article>
<article class="aphorism" id="if-the-automobile-had-fol">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>If the automobile had followed the same development cycle as the computer, a Rolls-Royce would today cost $100, get a million miles per gallon, and explode once a year, killing everyone inside.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Robert X. Cringely</span></cite></footer>
</article>
<article class="aphorism" id="if-we-have-data-lets-look">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>If we have data, let's look at data. If all we have are opinions, let's go with mine.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Jim Barksdale</span></cite></footer>
</article>
<article class="aphorism" id="if-you-can-make-something">
<blockquote cite="https://en.wikipedia.org/wiki/Don%27t_Make_Me_Think">
<p>If you can make something significantly clearer by making it slightly inconsistent, choose in favor of clarity.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Steve_Krug" rel="author">Steve Krug</a></cite></footer>
</article>
<article class="aphorism" id="if-you-cant-make-somethin">
<blockquote cite="https://en.wikipedia.org/wiki/Don%27t_Make_Me_Think">
<p>If you can’t make something self-evident, you at least need to make it self-explanatory.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Steve_Krug" rel="author">Steve Krug</a></cite></footer>
</article>
<article class="aphorism" id="-if-you-need-more-than-3">
<blockquote cite="https://en.wikiquote.org/wiki/Linus_Torvalds">
<p>... if you need more than 3 levels of indentation, you’re screwed anyway, and should fix your program.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Linus_Torvalds" rel="author">Linus Torvalds</a></cite></footer>
</article>
<article class="aphorism" id="if-youre-actually-doing-t">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>If you’re actually doing TDD, you're throwing away tests all the time, as your understanding of what the code is changes.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Kerri Miller</span></cite></footer>
</article>
<article class="aphorism" id="if-youre-willing-to-restr">
<blockquote cite="http://quotes.cat-v.org/programming/">
<p>If you’re willing to restrict the flexibility of your approach, you can almost always do something better.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/John_Carmack" rel="author">John Carmack</a></cite></footer>
</article>
<article class="aphorism" id="if-you-think-its-simple-t">
<blockquote cite="https://en.wikiquote.org/wiki/Bjarne_Stroustrup">
<p>If you think it’s simple, then you have misunderstood the problem.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Bjarne_Stroustrup" rel="author">Bjarne Stroustrup</a></cite></footer>
</article>
<article class="aphorism">
<blockquote cite="https://codecamp.ro/take-five-a-countdown-of-whats-essential-in-software-development/">
<p>If you think good architecture is expensive, try bad architecture.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Anti-pattern" rel="author">Brian Foote & Joseph Yoder</a></cite></footer>
</article>
<article class="aphorism" id="in-carpentry-you-measure">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>In carpentry you measure twice and cut once. In software development you never measure and make cuts until you run out of time.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Adam Morse</span></cite></footer>
</article>
<article class="aphorism" id="in-corporate-environments">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>In corporate environments the product don't have to be good. Sometimes they don't even have to exist... if you are a thoughtful developer, you are in the wrong place!</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Jeff_Atwood" rel="author">Jeff Atwood</a></cite></footer>
</article>
<article class="aphorism" id="in-my-experience-one-of-t">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>In my experience, one of the most significant problems in software development is assuming. If you assume a method will passed the right parameter value, the method will fail.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Paul M. Duvall</span></cite></footer>
</article>
<article class="aphorism" id="in-programming-the-hard-p">
<blockquote cite="https://twitter.com/CodeWisdom/status/1051828540277182464">
<p>In programming the hard part isn’t solving problems, but deciding what problems to solve.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Paul_Graham_(programmer)" rel="author">Paul Graham</a></cite></footer>
</article>
<article class="aphorism" id="in-software-we-rarely-hav">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>In software, we rarely have meaningful requirements. Even if we do, the only measure of success that matters is whether our solution solves the customer's shifting idea of what their problem is.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Jeff_Atwood" rel="author">Jeff Atwood</a></cite></footer>
</article>
<article class="aphorism" id="in-theory-theory-and-prac">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>In theory, theory and practice are the same. In practice, they’re not.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Yoggi Berra</span></cite></footer>
</article>
<article class="aphorism" id="it-assumes-that-coding-is">
<blockquote cite="https://blog.codinghorror.com/please-dont-learn-to-code/">
<p>It assumes that coding is the goal. Software developers tend to be software addicts who think their job is to write code. But it's not. Their job is to solve problems. Don't celebrate the creation of code, celebrate the creation of solutions. We have way too many coders addicted to doing just one more line of code already.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Jeff_Atwood" rel="author">Jeff Atwood</a></cite></footer>
</article>
<article class="aphorism" id="it-can-be-better-to-copy">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>It can be better to copy a little code than to pull in a big library for one function. Dependency hygiene trumps code reuse.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Rob_Pike" rel="author">Rob Pike</a></cite></footer>
</article>
<article class="aphorism" id="it-comes-from-saying-no-t">
<blockquote cite="https://en.wikiquote.org/wiki/Steve_Jobs">
<p>It comes from saying no to 1,000 things to make sure we don't get on the wrong track or try to do too much.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Steve_Jobs" rel="author">Steve Jobs</a></cite></footer>
</article>
<article class="aphorism" id="it-is-easier-to-port-a-sh">
<blockquote cite="http://www.gdargaud.net/Humor/QuotesProgramming.html">
<p>It is easier to port a shell than a shell script.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Larry_Wall" rel="author">Larry Wall</a></cite></footer>
</article>
<article class="aphorism" id="it-is-not-that-uncommon-f">
<blockquote cite="http://quotes.cat-v.org/programming/">
<p>It is not that uncommon for the cost of an abstraction to outweigh the benefit it delivers. Kill one today!</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/John_Carmack" rel="author">John Carmack</a></cite></footer>
</article>
<article class="aphorism" id="its-better-to-wait-for-a">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>It's better to wait for a productive programmer to become available than it is to wait for the first available programmer to become productive.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Steve_McConnell" rel="author">Steve McConnell</a></cite></footer>
</article>
<article class="aphorism" id="its-important-to-remember">
<blockquote cite="http://quotes.cat-v.org/programming/">
<p>It's important to remember that when you start from scratch there is absolutely no reason to believe that you are going to do a better job than you did the first time. First of all, you probably don't even have the same programming team that worked on version one, so you don't actually have "more experience". You're just going to make most of the old mistakes again, and introduce some new problems that weren't in the original version.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Joel_Spolsky" rel="author">Joel Spolsky</a></cite></footer>
</article>
<article class="aphorism" id="it-should-be-noted-that-n">
<blockquote cite="http://www.gdargaud.net/Humor/QuotesProgramming.html">
<p>It should be noted that no ethically-trained software engineer would ever consent to write a DestroyBaghdad procedure. Basic professional ethics would instead require him to write a DestroyCity procedure, to which Baghdad could be given as a parameter.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Nathaniel_Borenstein" rel="author">Nathaniel Borenstein</a></cite></footer>
</article>
<article class="aphorism" id="it-would-be-nice-if-produ">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>It would be nice if products and programming languages were designed to have only good parts.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Douglas_Crockford" rel="author">Douglas Crockford</a></cite></footer>
</article>
<article class="aphorism" id="javascript-is-the-only-la">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>JavaScript is the only language that I'm aware of that people feel they don't need to learn before they start using it.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Douglas_Crockford" rel="author">Douglas Crockford</a></cite></footer>
</article>
<article class="aphorism" id="keep-it-simple-make-it-ge">
<blockquote cite="https://en.wikipedia.org/wiki/Douglas_McIlroy">
<p>Keep it simple, make it general, and make it intelligible.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Douglas_McIlroy" rel="author">Doug McIlroy</a></cite></footer>
</article>
<article class="aphorism" id="keep-it-simple-stupid">
<blockquote cite="">
<p>Keep it simple, stupid!</p>
</blockquote>
<footer class="aphorism-footer"><abbr title="Keep it simple, stupid!">KISS</abbr> principle</footer>
</article>
<article class="aphorism" id="the-three-great-virtues-o">
<blockquote cite="">
<p>The three great virtues of a programmer are laziness, impatience, and hubris.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Larry_Wall" rel="author">Larry Wall</a></cite></footer>
</article>
<article class="aphorism" id="legacy-code-often-differs">
<blockquote cite="https://en.wikiquote.org/wiki/Bjarne_Stroustrup">
<p>"Legacy code" often differs from its suggested alternative by actually working and scaling.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Bjarne_Stroustrup" rel="author">Bjarne Stroustrup</a></cite></footer>
</article>
<article class="aphorism" id="linux-is-only-free-if-you">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>Linux is only free if your time has no value</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikiquote.org/wiki/Jamie_Zawinski" rel="author">Jamie Zawinski</a></cite></footer>
</article>
<article class="aphorism" id="oops-missed-one">
<blockquote cite="">
<p>Oops. Missed one.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Every Classical OO programmer</span></cite>, ever.</footer>
</article>
<article class="aphorism" id="managing-senior-programme">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>Managing senior programmers is like herding cats.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Dave Platt</span></cite></footer>
</article>
<article class="aphorism" id="many-good-programming-pra">
<blockquote cite="https://www.johndcook.com/blog/2012/01/17/expressing-intent/">
<p>Many good programming practices boil down to preparing for change or expressing intent. It seems to me that novices emphasize the former, experts the latter.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://twitter.com/johndcook" rel="author">John D. Cook</a></cite></footer>
</article>
<article class="aphorism" id="measuring-programming-pro">
<blockquote cite="http://www.defprogramming.com/quotes-by/bill-gates/">
<p>Measuring programming progress by lines of code is like measuring aircraft building progress by weight.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Bill_Gates" rel="author">Bill Gates</a></cite></footer>
</article>
<article class="aphorism" id="more-computing-sins-are-c">
<blockquote cite="https://en.wikiquote.org/wiki/William_Wulf">
<p>More computing sins are committed in the name of efficiency (without necessarily achieving it) than for any other single reason - including blind stupidity.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/William_Wulf" rel="author">William A. Wulf</a></cite></footer>
</article>
<article class="aphorism" id="most-managers-may-defend">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>[Most managers] may defend the schedule and requirements with passion; but that's their job. It's your job to defend the code with equal passion.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Robert_C._Martin" rel="author">Robert C. Martin</a></cite></footer>
</article>
<article class="aphorism" id="most-of-the-biggest-probl">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>Most of the biggest problems in software are problems of misconception.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Rich Hickey</span></cite></footer>
</article>
<article class="aphorism" id="most-of-the-good-programm">
<blockquote cite="https://en.wikiquote.org/wiki/Linus_Torvalds">
<p>Most of the good programmers do programming not because they expect to get paid or get adulation by the public, but because it is fun to program.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Linus_Torvalds" rel="author">Linus Torvalds</a></cite></footer>
</article>
<article class="aphorism" id="most-software-today-is-ve">
<blockquote cite="https://en.wikiquote.org/wiki/Alan_Kay">
<p>Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Alan_Kay" rel="author">Alan Kay</a></cite></footer>
</article>
<article class="aphorism" id="much-of-the-essence-of-bu">
<blockquote cite="https://twitter.com/CompSciFact/status/1118256525682802688">
<p>Much of the essence of building a program is in fact the debugging of the specification.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Fred_Brooks" rel="author">Fred Brooks</a></cite></footer>
</article>
<article class="aphorism" id="nine-people-cant-make-a-b">
<blockquote cite="">
<p>Nine people can’t make a baby in a month.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Fred_Brooks" rel="author">Fred Brooks</a></cite></footer>
</article>
<article class="aphorism" id="no-matter-how-slick-the-d">
<blockquote cite="https://gist.githubusercontent.com/bussiere/754086/raw/5a6d8b1ab07452b697b4bc1e895e8cad6b2f7510/citations">
<p>No matter how slick the demo is in rehearsal, when you do it in front of a live audience, the probability of a flawless presentation is inversely proportional to the number of people watching, raised to the power of the amount of money involved.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Mark Gibbs</span></cite></footer>
</article>
<article class="aphorism" id="no-one-in-the-brief-histo">
<blockquote cite="https://www.defprogramming.com/">
<p>No one in the brief history of computing has ever written a piece of perfect software. It's unlikely that you'll be the first.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Andy_Hunt_(author)" rel="author">Andy Hunt</a></cite></footer>
</article>
<article class="aphorism">
<blockquote cite="https://codecamp.ro/take-five-a-countdown-of-whats-essential-in-software-development/">
<p>Nothing is more dangerous than an idea, when you have only one idea.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://fr.wikipedia.org/wiki/Alain_(philosophe)" rel="author">Emile-Auguste Chartier</a></cite></footer>
</article>
<article class="aphorism" id="nowadays-hn-and-other-for">
<blockquote cite="https://www.amazon.it/Robert-Martin-Clean-Collection-English-ebook/dp/B00666M59G">
<p>...nowadays HN and other forms of type encoding are simply impediments. They make it harder to change the name or type of a variable, function, or class. They make it harder to read the code.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Robert_C._Martin" rel="author">Robert C. Martin</a></cite></footer>
</article>
<article class="aphorism" id="one-in-a-million-is-next">
<blockquote cite="https://en.wikiquote.org/wiki/Programming">
<p>One in a million is next Tuesday.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Gordon_Letwin" rel="author">Gordon Letwin</a></cite></footer>
</article>
<article class="aphorism" id="one-of-my-most-productive">
<blockquote cite="http://quotes.cat-v.org/programming/">
<p>One of my most productive days was throwing away 1000 lines of code.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://en.wikipedia.org/wiki/Ken_Thompson" rel="author">Kenneth Lane Thompson</a></cite></footer>
</article>
<article class="aphorism" id="one-page-principle-a-spec">
<blockquote cite="http://quotes.cat-v.org/programming/">
<p>One Page Principle: A specification that will not fit on one page of 8.5x11 inch paper cannot be understood.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://www.linkedin.com/in/markardis" rel="author">Mark Ardis</a></cite></footer>
</article>
<article class="aphorism" id="people-ignore-design-that">
<blockquote cite="https://twitter.com/frank_chimero">
<p>People ignore design that ignores people.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://frankchimero.com/" rel="author">Frank Chimero</a></cite></footer>
</article>
<article class="aphorism" id="perl-the-only-language-th">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>Perl: The only language that looks the same before and after RSA encryption.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Keith Bostic</span></cite></footer>
</article>
<article class="aphorism" id="php-is-a-minor-evil-perpe">
<blockquote cite="https://gl.wikiquote.org/wiki/Jon_Ribbens">
<p>PHP is a minor evil perpetrated and created by incompetent amateurs, whereas Perl is a great and insidious evil perpetrated by skilled but perverted professionals.</p>
</blockquote>
<footer class="aphorism-footer"><cite><span rel="author">Jon Ribbens</span></cite></footer>
</article>
<article class="aphorism" id="premature-abstraction-is">
<blockquote cite="https://twitter.com/CompSciFact/status/1145798010753945600">
<p>Premature abstraction is as bad as premature optimization.</p>
</blockquote>
<footer class="aphorism-footer"><cite><a target="_blank" href="https://twitter.com/ramalhoorg" rel="author">Luciano Ramalho</a></cite></footer>
</article>
<article class="aphorism" id="procedural-code-code-usin">
<blockquote cite="https://gist.github.com/Potherca/5cd28e2a812e5c65c9f7320e0726da18">
<p>Procedural code (code using data structures) makes it easy to add new functions without changing the existing data structures. OO code, on the other hand, makes it easy to add new classes without changing existing functions.</p>