First of all, thank you, Ben for introducing this book.
Just finished the book and it was indeed "a good read overall".
The experience shared in the eyes of a software engineer was a fresh one. I especially liked the parts where Ken was able to analyze what he did, what he did wrong, and how he worked with others.
I give it ππ
I hope others can have fun reading it and also get much out of Ken's experience π
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.
Let me know what you think!
Sure thing there, Ben.
Thank you for the book recommendation π
First of all, thank you, Ben for introducing this book.
Just finished the book and it was indeed "a good read overall".
The experience shared in the eyes of a software engineer was a fresh one. I especially liked the parts where Ken was able to analyze what he did, what he did wrong, and how he worked with others.
I give it ππ
I hope others can have fun reading it and also get much out of Ken's experience π