We are not
going to spend a whole lot of time looking at UML diagrams, sequence diagrams, use case diagrams,
and the like (although there will be some because, hey, we are code monkeys after all).
You are more than welcome to pick up any of the fine UML books out there for that.
CODE MONKEY? DID YOU JUST CALL ME A CODE MONKEY?!?
Some people consider the term code monkey to be derogatory, but I never have. To me, a code monkey is
someone who programs for a living and who enjoys writing code. I suppose by that definition you wouldn??™t
even have to earn a living from programming, so long as you love hacking bits. Either way, it??™s all about the
code!
By the way, just because someone is a code monkey doesn??™t mean they can??™t do architecture, and vice
versa. If you like all of the facets of building software, if you like being up ??™til all hours of the night trying to
figure out why your custom-built double-linked list is corrupting elements when you modify them, if you like
playing with that new open source library for no other reason than you??™re curious, if you like the feeling you
get from seeing a working application come spewing out the back end of a development cycle (even if it??™s
some otherwise dull business application), then you??™re a code monkey, plain and simple, and you should
never take offense to being called that name.
Pages:
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