_why's Poignant Guide to Ruby made programming fun for me again, years ago.
Michael Feathers's Working Effectively with Legacy Code is long and a bit dense, but it's an intensely practical look at navigating systems that are complicated, untested, and too big to fit in your head at once.
Sandi Metz's Practical Object-Oriented Design in Ruby looks like a simple primer on what OO is, but if one goes into it expecting to learn things it emerges as something much more multi-layered. I figure out something new every time I reread it. Her follow-up with Katrina Owen (99 Bottles of OOP) is also brilliant and is specifically structured to hack away at one's preconceptions.
James Coglan's JavaScript Testing Recipes is dense and not really what one would expect from a recipes book -- it's not "here's what to type in," it's about the theory of testing JS effectively. Because testing well changes the shape of your code, I learned a whole bucket about how to write effective, composable JS by paying attention to the edges of the book. I'm really looking forward to James's upcoming book on rewriting the Git internals in Ruby. (Disclaimer: he's a friend of mine.)
And then of course there's my book, Untangling Asynchronous JavaScript, which ought to be coming out in February or so. :)
Excellent! It seems like dropping everything and running towards whatever Sandi Metz has written is a pretty good policy, and I think the Poignant Guide probably gets the dubious honor of being the first programming text I ever read.
Testing theory is a huge gap in my knowledge, I'm definitely looking forward to exploring that book, and a HUGE congrats on getting so close to publishing! Let us know when we can buy it, yeah?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
_why's Poignant Guide to Ruby made programming fun for me again, years ago.
Michael Feathers's Working Effectively with Legacy Code is long and a bit dense, but it's an intensely practical look at navigating systems that are complicated, untested, and too big to fit in your head at once.
Sandi Metz's Practical Object-Oriented Design in Ruby looks like a simple primer on what OO is, but if one goes into it expecting to learn things it emerges as something much more multi-layered. I figure out something new every time I reread it. Her follow-up with Katrina Owen (99 Bottles of OOP) is also brilliant and is specifically structured to hack away at one's preconceptions.
James Coglan's JavaScript Testing Recipes is dense and not really what one would expect from a recipes book -- it's not "here's what to type in," it's about the theory of testing JS effectively. Because testing well changes the shape of your code, I learned a whole bucket about how to write effective, composable JS by paying attention to the edges of the book. I'm really looking forward to James's upcoming book on rewriting the Git internals in Ruby. (Disclaimer: he's a friend of mine.)
And then of course there's my book, Untangling Asynchronous JavaScript, which ought to be coming out in February or so. :)
Excellent! It seems like dropping everything and running towards whatever Sandi Metz has written is a pretty good policy, and I think the Poignant Guide probably gets the dubious honor of being the first programming text I ever read.
Testing theory is a huge gap in my knowledge, I'm definitely looking forward to exploring that book, and a HUGE congrats on getting so close to publishing! Let us know when we can buy it, yeah?