Back Loathe to Love You Save as PDF
Contents ( 53)
  1. Praise for Ali Hazelwood
  2. TITLES BY ALI HAZELWOOD
  3. LOATHE TO LOVE YOU
  4. Contents
  5. Under
  6. One Roof
  7. Prologue
  8. One
  9. Two
  10. Three
  11. Four
  12. Five
  13. Six
  14. Seven
  15. Eight
  16. Nine
  17. Ten
  18. Eleven
  19. Twelve
  20. Thirteen
  21. Epilogue
  22. Stuck
  23. with You
  24. One
  25. Two
  26. Three
  27. Four
  28. Five
  29. Six
  30. Seven
  31. Eight
  32. Nine
  33. Ten
  34. Eleven
  35. Twelve
  36. Epilogue
  37. Below
  38. Zero
  39. Prologue
  40. One
  41. Two
  42. Three
  43. Four
  44. Five
  45. Six
  46. Seven
  47. Eight
  48. Nine
  49. Epilogue
  50. Bonus
  51. Chapter
  52. Acknowledgments
  53. What’s next on your reading list?

“What . . . Why are you doing that?”

He looks at me, not one ounce of his previous exasperation in his expression. “You’re right.”

“About?”

“It was me. It was my fault you didn’t get the client. But not for the reason you think.”

“What?”

“The day after we . . .” He runs a tired hand down his face. “That morning I had a meeting with one of the engineering managers I supervise. He told me that he was refining a pitch for a project that had specifically asked for sustainability features. He didn’t go into detail and I didn’t ask, but since it’s not our forte he wanted to know if I had any resources. I sent him an academic article.” His throat bobs. “It was the one you wrote.”

I’m dizzy. I’m sitting down, but I think I might fall over. “My article? My peer-reviewed article on frameworks for sustainable engineering?”

He nods slowly. Helplessly. “I also sent your thesis out in a company-wide email and highly encouraged all team leaders to read it. Though that was a few days later, after I’d read it myself.”

“My thesis?” I must have misheard him. Surely I’m in the thick of a cerebrovascular event. “My doctoral dissertation?”

He nods, looking apologetic. I . . . I don’t think I’m even mad anymore. Or maybe I am, but it’s diluted in the total, utter shock of hearing that . . . “How did you get my thesis? And my article?”

“The article was on Google Scholar. For the thesis . . .” He presses his lips together. “I had a librarian from Caltech send me a download link.”

“You had a librarian send you a download link,” I repeat slowly. I’m inhabiting a parallel dimension. Where atoms are made of chaos. “When?”

“The morning after. When I got to my office.”

“Why?”

“Because I wanted to read it.”

“But . . . why?”

He looks at me like I’m a bit slow. “Because you wrote it.”

Maybe I am a bit slow. “So you were trying to . . . figure out GreenFrame’s pitch based on my published work?”

“No.” His tone drops some of the guilt and is back to three parts firm, one part indignant. “I wanted to read what you wrote because I’m interested in the topic, because at dinner it was very obvious that you’re a better engineer than most people at ProBld—including myself—and because about five minutes into my workday I realized that if I wasn’t going to stop thinking about you, I might as well be productive about it. And as I read, I realized that your work is above good, and sharing it with everyone else seemed like a no-brainer. I didn’t think that I was handing your pitch to my entire company, and . . . Fuck. I just didn’t think.” He rubs the back of his hand against his mouth. “It was my fault. It wasn’t on purpose, but I take full responsibility. I’m going to talk with my engineering manager and with the client and . . . I’ll figure this out. We’ll find you a way to make sure you get the credit you deserve.”