Please enable JavaScript.
Coggle requires JavaScript to display documents.
The pragmatic programmer philosophy (Your knowledge portfolio (Goals (stay…
The pragmatic programmer philosophy
the cat ate my source code
Take responsibility
provide options, don't make lame excuses
Software Entropy
Entropy comes from physics that refers to the amount of disorder in a system
the broken window theory
bad designs, wrong decisions or poor code
Stone Soup and Boiled Frogs
start up fatigue
“It’s easier to ask forgiveness than it is to get permission.”
Work out what you can reasonably ask for. Develop it well. Once you’ve got it, show people, and let them marvel. Then say “of course, it would be better if we added .” Pretend it’s not important. Sit back and wait for them to start asking you to add the functionality you originally wanted. People find it easier to join an ongoing success. Show them a glimpse of the future and you’ll get them to rally around
remember the big picture
Good enough software
does not imply sloppy or poorly produced code
make quality a requirements issue
involve your users in the trade off
know when to stop
Your knowledge portfolio
expiring assets
invest regularly - as a habit
similar to managing a financial portfolio
diversification is the key to long term success
more diff things you know, more valuable you are
know the ins and outs of the particular tech you are working with currently;
smart investors balance their portfolios between conservative and high risk high reward investments
manage risk
buy low and sell high for maximum return
learning an emerging tech before it becomes popular
portfolio should be reviewed and rebalanced periodically
Goals
Learn at least one new language every year
read a tech book each quarter/ 4 books a year
read non tech books too
take calsses
participate in local user groups
expreriment with diff envir
stay current; subs to magazines etc
IEEE computing Society
ACM
get wired
Gurus
know what to ask
frame your question carefully and politely
sit back and be patient
Comms
know what you want to say
write an outline
plan a couple of strategies for getting them across
know your audience
Say you want to suggest a Web-based system to allow your end users to submit bug reports. You can present this system in many different ways, depending on your audience. End users will appreciate that they can submit bug reports 24 hours a day without waiting on the phone. Your marketing department will be able to use this fact to boost sales. Managers in the support department will have two reasons to be happy: fewer staff will be needed, and problem reporting will be automated. Finally, developers may enjoy getting experience with Webbased client-server technologies and a new database engine. By making the appropriate pitch to each group, you’ll get them all excited about your project.
choose your moment
work out what their priorities are
WISDOM
What do you want them to learn?
What is their interest in what you’ve got to say?
How sophisticated are they?
How much detail do they want?
Whom do you want to own the information?
How can you motivate them to listen to you?
choose a style
document
report
oral
make it look good
style sheet
page no. header /footer
check your spellings
get back to people