3 ms·

Same here. I only have 2 years of experience, but right now my opinion is that this is not something you learn in a book (for the moment). You can learn how to

by Toine 11y ago

Same here. I only have 2 years of experience, but right now my opinion is that this is not something you learn in a book (for the moment). You can learn how to create clean, readable methods and classes with a book (1). You can learn how to refactor old methods and classes with a book (2). You can learn how to organize a small team to allow fast iterations with many books. But building a project lasting more than a few months with constant changes in the requirements, new developers every month, new SDKs and frameworks every 3 days, without the code rotting to death and everything going out of control is a different story, at least for me. I guess you just learn by watching old guys do what they do after decades of experience...unless someone has a magic book for me? (1) http://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship-ebook/dp/B001GSTOAM http://www.amazon.com/Clean-Code-Handbook-Software-Craftsman... (2) http://www.amazon.com/Refactoring-Improving-Existing-Addison-Wesley-Technology-ebook/dp/B007WTFWJ6 http://www.amazon.com/Refactoring-Improving-Existing-Addison...

Glide 11y ago
My personal experience is that I had to maintain a set of applications I wrote for a company. The same application had to be used repeatedly (3-5 times) a year because it supported a specific business processes. It was mundane work, but did it teach me how to organize because it made the pain of disorganized code very real. That one hack comes back to haunt you several times a year. I was lucky that this was one of the first things I had learned as a developer out of school. It was a little different because the projects were small enough to be solo, but it was humbling because all of the mistakes were my own.
sterlingw 11y ago
I just finished a book called "Practical Object Oriented Design in Ruby." It teaches you how to build OO applications that are pleasant to maintain. I highly recommend it. http://www.amazon.com/Practical-Object-Oriented-Design-Ruby-Addison-Wesley/dp/0321721330/ http://www.amazon.com/Practical-Object-Oriented-Design-Ruby-...

by Toine 11y ago

Glide 11y ago

My personal experience is that I had to maintain a set of applications I wrote for a company. The same application had to be used repeatedly (3-5 times) a year because it supported a specific business processes. It was mundane work, but did it teach me how to organize because it made the pain of disorganized code very real. That one hack comes back to haunt you several times a year. I was lucky that this was one of the first things I had learned as a developer out of school. It was a little different because the projects were small enough to be solo, but it was humbling because all of the mistakes were my own.

sterlingw 11y ago

I just finished a book called "Practical Object Oriented Design in Ruby." It teaches you how to build OO applications that are pleasant to maintain. I highly recommend it. http://www.amazon.com/Practical-Object-Oriented-Design-Ruby-Addison-Wesley/dp/0321721330/ http://www.amazon.com/Practical-Object-Oriented-Design-Ruby-...