Help with Junit

[Junilu Lacar]

Paul Clapham wrote:

Junilu Lacar wrote:Again, some of the key things are mastery of the medium...

And later you mention some concepts related to that idea. People in my generation read and re-read Zen and the Art of Motorcycle Maintenance to reinforce our belief in the value of quality. You may find it interesting if you hadn't already heard of it.

Thanks, Paul. I read that book early on in my career. In fact, when we get into these kinds of discussions, I'm often reminded of the idea of Chautauquas.

[Giovanni Montano]

Prasanna Raman wrote:Thank you for all the great posts! Any books that you all recommend not just for testing but to improve the overall design thinking as a developer?

The ones I've read so far are

Clean Code
Refactoring (parts of it)
Effective Java

Learning, learning learning.
The best suggestion is working with people that can review the code you write.
I suggest you to read Clean Architecture from the same author of Clean code, is crazy man, and there you find ton of suggestions to refactor, comply with dependency injection, interface, re usability and even prevent problems
then I would read TDD with growing objects. Before you run the test that fails, then you start to build your logic, then you make the test passing, refactoring.
Then if you quote that 3 old books you are gonna love refactoring legacy code.

Still you are not a developer, you need years of trials and error with Senior that are going to correct you. If you do not have them, post online, do a github project, and most important read Head first design patterns. Beginners green horns often fall to understand how to implement strategy pattern and interface to make code better. You understand that you miss still something, solving the problems, solving them fast and efficiently, so I would buy the fabolous grokking algorhitms, did you know that all the quantistic problems quoted by janilu lacar, will never be clear if you do not understand why if you have a sorted array with ten items you will take 10 millisecond searching an item with linear search instead of the 7 of binary search, but if you have 1 billion possibilities, you will take 11 days with linear search( searching one per one), instead of 29 seconds and 7 millisecond of a binary research?

When you will think you are improving then you learn math from one of the most beautiful book: Math from programmers, thank you Campbel Ritchie for that tip, I am loving that book even more than linus torvalds.


Edit I suggest also the zen and the art of archery, then 101 zen stories, and finally the power of now from E.Tolle. A good help if you like to debug hearing bach