The 15 Books that All Programmers Must..

Num	Title	Authors	AMZN Rating (5 max)	Innards
1	The Pragmatic Programmer	Andrew Hunt, David Thomas	4.5	Don’t  get married to anything; pay attention to what you're doing and try to do it better; experience --> confidence. Adopt early; Be inquisitive; Be a critical thinker; Be realistic; Be a Jack of aT; Care about your craft and think about your work! Build your K portfolio - good ideas - invest regularly!
2	The Art of Computer Programming	Donald Knuth	4.4	really, when will you finish if you start?
3	Don't Make Me Think	Steve Krug	4.5	about usability
4	Coders at Work	Peter Siebel	55	interviews with famous coders
5	The Mythical Man Month	Frederick Brooks	66	About project management
6	Code Complete	Steve McConnell	77	Aaaa
7	Cracking the Coding Interview	Gayle Laakmann McDowell	88	bbbb
8	Soft Skills : THe Software Developer's Life Manual	John Sonmez	99	cccc
9	Zen and the Art of Motorcycle Maintenance	Robert Pirsig	111	dddd
10	Clean Code	Robert C. Martin	222	eeee
11	Continuous Delivery	Jez Humble, David Farley	333	ffff
12	Working Effectively with Legacy Code	Michael C. Feathers	444	gggg
13	Code: The Hidden Language of Computer Hardware and Software	Charles Petzold	555	hhhh
14	Programming Pearls	John Bentley	666	iiii
15	Introduction to Algorithms	CLRS	777	jjjj

What I Like Most About bash - Really

Hoorah! I just found out bash was created by a black man. What a pleasant surprise.

Aha - Jason Cannon's average-rated work is available for free today :) Get it while you can for $0.

Yikes, at Tip #5, you see why it only gets three stars - for command subs this guy says use backticks - when that's what got the dinosaurs. Use $( command ) dude!

A good one, that I didn't know : !# is an alias for the current command line and words are ordered starting with 0. So, in the below command.

$ mv report.txt $(data +%F)-report.txt   # basically timestamping

you can do

$ mv report.txt $(data +%F)-!#:1          # cute?

QED

The Kiczales HtDF Way

To design Functions :

1. Signature, purpose, stub.
2. Define examples, wrap each in check-expect.
3. Template and inventory.
4. Code function and body.
5. Test and debug till done.

signature : type of each arg, separated by spaces, followed by -> type of result.
purpose - a meaningful one line statement.
stub : syntactically complete function definition that produces a value of the right ype. This makes it possible to run examples even before the function design is complete..

You ain't got UBC under your thumbnail for nothin bro.