- Mastering React Test:Driven Development
- Daniel Irvine
- 800字
- 2021-06-24 14:44:57
About the author
Daniel Irvine is a software consultant based in London. He is a member of the European software craft community and works with a variety of languages including C#, Clojure, JavaScript, and Ruby. He’s a mentor and coach for junior developers and runs TDD and XP workshops and courses. When he’s not working, he spends time cooking and practicing yoga. He co-founded and runs the Queer Code London meetup.
This book would not be what it is without the input of my technical reviewer, Raimo Radczewski, who is also the author of the expect-redux package that is used in this book. I met Raimo a few years ago through the European software craft community. We bonded at a SoCraTes conference and found that we shared many of the same driving forces. Through many conversations, I learned to respect his thoughtfulness, kindness, and, of course, his deep knowledge of JavaScript and the React ecosystem. So, when I first took on this project, I immediately asked Raimo to come on board. Thankfully, he said yes. In the following eight months, he had a difficult job of reading though many drafts of—shall we say—variable quality. Those who have worked with me know that I can be lazy, careless, brazen, and inconsistent. Well, Raimo has seen it all and more, so firstly, I must thank him for continuing with the project in spite of the early drafts. I must also thank him for teaching me about many of JavaScript’s nuances, of which I simply wasn’t aware. He also guided me back toward idiomatic React code, because until I wrote this book I had really been writing JavaScript “out in the wilderness,” with my own style. He brought me back in from the cold. He suggested some simplifications to my implementations; for example, the undo/redo reducer in Section 3, which would have been a great deal more complicated without his critical eye. I blamed my terrible code on burn-out, but actually, Raimo is a fantastic programmer and I look forward to the next occasion that we get to work together.
My editor, Keagan Carneiro, has been constantly positive and supportive, not once ever judging me for missing my self-imposed deadlines, which toward the end I missed consistently. We got through it in the end. Of all the wonderful things he did for me, perhaps the most powerful was the push to embrace hooks. When I first informed him in November 2018 that the React team had announced this weird thing called hooks that looked horrendous and that I couldn’t ever imagine taking off, but that we might have to consider doing a chapter on, he turned around and suggested that I rewrite the entire text entirely to use hooks. Bearing in mind we were halfway through at this point, it was a pretty big ask. Of course, I knew he was right and I trusted his assessment, so I had to go through the five stages of grief of denial, anger, bargaining, depression, and acceptance in super-quick time, before getting on with it. (I believe Raimo is still hovering somewhere around the bargaining stage.) In the end, we were only delayed by a month, so I have to thank Keagan for ensuring that the book wasn’t out of date before it was even published.
Sachin Sunilkumar, my technical editor, was wonderfully patient with me as I was reworking code snippets right until the last moment. He went on a journey of discovery with me as we built and tested against alpha releases of React. That was fun and stressful in equal amounts!
There are a number of other friends who stepped in at the last moment to review content when I was rushing with the final draft. Their assistance was invaluable. The text is much better for their efforts. Charlotte Payne, Dan Pelensky, Isidro López, Makis Otman, Sam Szreter, Zach Shaw: thank you. I hope you enjoy seeing your suggested improvements in print.
To the development team at Idean—in particular, Brendan Murphy, Lucy Monie Hall, and Zach Shaw—thank you for listening to me bang on about “my book” at least once a week.
I cannot finish without thanking my partner, Phillipe, who has suffered as I embarked on this project, my first book. Staying on track while still having a day job was a mammoth effort for me. It really took it out of me. Phillipe put up with me as I was tired, distracted, creatively drained, emotionally distraught, unavailable, and—toward the end—burned out, monosyllabic, and not much fun. He supported me through the project from start to finish. Thank you.
My editor, Keagan Carneiro, has been constantly positive and supportive, not once ever judging me for missing my self-imposed deadlines, which toward the end I missed consistently. We got through it in the end. Of all the wonderful things he did for me, perhaps the most powerful was the push to embrace hooks. When I first informed him in November 2018 that the React team had announced this weird thing called hooks that looked horrendous and that I couldn’t ever imagine taking off, but that we might have to consider doing a chapter on, he turned around and suggested that I rewrite the entire text entirely to use hooks. Bearing in mind we were halfway through at this point, it was a pretty big ask. Of course, I knew he was right and I trusted his assessment, so I had to go through the five stages of grief of denial, anger, bargaining, depression, and acceptance in super-quick time, before getting on with it. (I believe Raimo is still hovering somewhere around the bargaining stage.) In the end, we were only delayed by a month, so I have to thank Keagan for ensuring that the book wasn’t out of date before it was even published.
Sachin Sunilkumar, my technical editor, was wonderfully patient with me as I was reworking code snippets right until the last moment. He went on a journey of discovery with me as we built and tested against alpha releases of React. That was fun and stressful in equal amounts!
There are a number of other friends who stepped in at the last moment to review content when I was rushing with the final draft. Their assistance was invaluable. The text is much better for their efforts. Charlotte Payne, Dan Pelensky, Isidro López, Makis Otman, Sam Szreter, Zach Shaw: thank you. I hope you enjoy seeing your suggested improvements in print.
To the development team at Idean—in particular, Brendan Murphy, Lucy Monie Hall, and Zach Shaw—thank you for listening to me bang on about “my book” at least once a week.
I cannot finish without thanking my partner, Phillipe, who has suffered as I embarked on this project, my first book. Staying on track while still having a day job was a mammoth effort for me. It really took it out of me. Phillipe put up with me as I was tired, distracted, creatively drained, emotionally distraught, unavailable, and—toward the end—burned out, monosyllabic, and not much fun. He supported me through the project from start to finish. Thank you.
推薦閱讀
- C# 7 and .NET Core Cookbook
- 我的第一本算法書
- ASP.NET 3.5程序設(shè)計(jì)與項(xiàng)目實(shí)踐
- 單片機(jī)應(yīng)用與調(diào)試項(xiàng)目教程(C語言版)
- OpenGL Data Visualization Cookbook
- Getting Started with Eclipse Juno
- MySQL入門很輕松(微課超值版)
- Python+Tableau數(shù)據(jù)可視化之美
- FPGA嵌入式項(xiàng)目開發(fā)實(shí)戰(zhàn)
- 一步一步跟我學(xué)Scratch3.0案例
- Android Sensor Programming By Example
- C# 7.1 and .NET Core 2.0:Modern Cross-Platform Development(Third Edition)
- Instant Pygame for Python Game Development How-to
- Hands-On ROS for Robotics Programming
- MySQL從入門到精通