I'm eagerly looking forward to this book.

I wish it were structured backwards, though.

If I'm reading it, it's because I want to learn about software architecture in Haskell.

Give me the "Large Applications in Haskell" chapter up front. Tell me what I'm going to learn, tell me where I'm going to find it, then teach it to me.

Maybe I'm a little bit jaded by Haskell resources which promise I'll know Haskell, teach some basics, then tell me about monad burritos. (Holy shit y'all are overcomplicating the fuck out of monads. "It's a workflow. You can use functions within a workflow easily because of do-notation. If you want to make your own workflow you should define: how to change a value within the workflow to another value within your workflow using some function; how to do that using a function that came from your workflow; how to apply your workflow to a value that's not in your workflow. That's it. If you're doing something super fucking weird we might yell at you for "breaking the law" but unless you're doing weird shit you won't hear from us again."