We recently had the chance to speak with Alexander Granin , who is a software architect, international speaker, researcher and active member of the C++ and Haskell communities about his upcoming book <a href="https://www.manning.com/books/functional-design-and-architecture?utm_source=workshub&utm_medium=affiliate&utm_campaign=book_granin_functional_7_22_21&a_aid=workshub&a_bid=df97db22">Functional Design and Architecture </a> and the evolution of Haskell in the past decade.

My IT career started more than 15 years ago. I was a C++ developer for most of my professional path. But my true passion was functional programming. I fell in love with Haskell 10 years ago, and it was my favorite hobby language until I moved to the position of Haskell consultant 4 years ago. I started investigating functional programming in Haskell and C++, and I found a big world of new great ideas. I was writing articles, giving talks, and my goal was to popularize functional programming among developers.

We'd like to start by learning a bit about your journey as a developer and author.

There was something that I realized quite soon. Haskell is an amazing, very influential, and even meme language that offers really breakthrough concepts. However, it turned out that we don’t have an understanding of how to build real programs, how to apply those ideas to everyday tasks, and what software engineering in Haskell looks like. I started researching this topic. I was the first with this intent in Haskell, so I decided to write a book that I knew will say its word in the industry sooner or later.

What prompted you to write a guide to software engineering using Haskell?

We know much about object-oriented programming. There are design patterns, design principles, software architectures, and ready solutions - all this forms a complete story of software design in OOP languages. But we don’t have anything equal in functional programming. There were takes on this or that for sure, but nothing that comprehensive and systematic. Authors do their best to observe separate techniques and ideas, but there is no complete story of what approaches we have in functional programming and how to apply them for real tasks

Why do you think this book is important for developers to read?

There is Object-Oriented Design (OOD) for OO languages, and in my book, I’m suggesting its counterpart for the functional world. I call it Functional Declarative Design. The importance of this topic is clear: it’s a new direction of software engineering, and learning will definitely be a good idea for everyone, not only for functional developers.

Haskell in this book is a model language, but we’re making the first two parts of the book approachable to all functional developers. A basic and intermediate Haskell will be needed in further, still, the book contains a lot of ideas universally applicable to Scala, F#, Elm, OCaml, PureScript. I believe the book will be useful to senior software engineers and software architects having a certain FP background, but maybe my book is more than that. My hope is that it becomes a must-have book for many developers from many stacks.

Who would you recommend it to?

Learning Haskell was a great idea long ago since Haskell 2010 was established. Haskell gives a completely different perspective on writing the code, and this makes you a better developer. But if this is not convincing enough, then I would say that ideas from Haskell leak into all the main languages: Scala, C++, C#, JavaScript, Java, Kotlin, Rust. Not metaphorically, but literally; for example, C++20 has concepts - a direct adoption of Haskell’s type classes.

What’s your opinion about the evolution of Haskell in the past decade and why do you think now it’s a good time to learn Haskell?

Haskell is on its slow but steady rise. In 2020, Haskell Foundation was established - an organization that aims to popularize and support Haskell in industry. We see the increasing number of job positions on the market , and even more: there is a lack of professional Haskell developers today. Manning Publications has also contributed to this growth quite much: books by Will Kurt ( Get Programming in Haskell ) and Vitaly Bragilevsky ( Haskell in Depth ) are very good and practical: a property that was in big demand in the Haskell community according to annual surveys.

I believe my book will be a great next step for Haskell and for functional programming in general, so yes, I’m very sure that Haskell is worth learning today.We would like to thank Alexander for chatting with us, we hope to have inspired our readers to start or continue their Haskell journey. You can get early access to Alexander's book Functional Design and Architecture here . Use our code nlfuncwrks21 at checkout to get 35% off.

<div>Mihaela Popa</div><div>9 September, 2021 | 3 min read</div>We recently had the chance to speak with Alexander Granin, who is a software architect, international speaker, researcher and active member of the C++ and Haskell communities about his upcoming book <a href="https://www.manning.com/books/functional-design-and-architecture?utm_source=workshub&amp;utm_medium=affiliate&amp;utm_campaign=book_granin_functional_7_22_21&amp;a_aid=workshub&amp;a_bid=df97db22" rel="noopener noreferrer nofollow" dir="ltr">Functional Design and Architecture</a> and the evolution of Haskell in the past decade. <h3>We'd like to start by learning a bit about your journey as a developer and author.</h3>My IT career started more than 15 years ago. I was a C++ developer for most of my professional path. But my true passion was functional programming. I fell in love with Haskell 10 years ago, and it was my favorite hobby language until I moved to the position of Haskell consultant 4 years ago. I started investigating functional programming in Haskell and C++, and I found a big world of new great ideas. I was writing articles, giving talks, and my goal was to popularize functional programming among developers. <h3>What prompted you to write a guide to software engineering using Haskell?</h3>There was something that I realized quite soon. Haskell is an amazing, very influential, and even meme language that offers really breakthrough concepts. However, it turned out that we don’t have an understanding of how to build real programs, how to apply those ideas to everyday tasks, and what software engineering in Haskell looks like. I started researching this topic. I was the first with this intent in Haskell, so I decided to write a book that I knew will say its word in the industry sooner or later. <h3>Why do you think this book is important for developers to read?</h3>We know much about object-oriented programming. There are design patterns, design principles, software architectures, and ready solutions - all this forms a complete story of software design in OOP languages. But we don’t have anything equal in functional programming. There were takes on this or that for sure, but nothing that comprehensive and systematic. Authors do their best to observe separate techniques and ideas, but there is no complete story of what approaches we have in functional programming and how to apply them for real tasks. There is Object-Oriented Design (OOD) for OO languages, and in my book, I’m suggesting its counterpart for the functional world. I call it Functional Declarative Design. The importance of this topic is clear: it’s a new direction of software engineering, and learning will definitely be a good idea for everyone, not only for functional developers. <h3>Who would you recommend it to?</h3>Haskell in this book is a model language, but we’re making the first two parts of the book approachable to all functional developers. A basic and intermediate Haskell will be needed in further, still, the book contains a lot of ideas universally applicable to Scala, F#, Elm, OCaml, PureScript. I believe the book will be useful to senior software engineers and software architects having a certain FP background, but maybe my book is more than that. My hope is that it becomes a must-have book for many developers from many stacks. <h3>What’s your opinion about the evolution of Haskell in the past decade and why do you think now it’s a good time to learn Haskell?</h3>Learning Haskell was a great idea long ago since Haskell 2010 was established. Haskell gives a completely different perspective on writing the code, and this makes you a better developer. But if this is not convincing enough, then I would say that ideas from Haskell leak into all the main languages: Scala, C++, C#, JavaScript, Java, Kotlin, Rust. Not metaphorically, but literally; for example, C++20 has concepts - a direct adoption of Haskell’s type classes.Haskell is on its slow but steady rise. In 2020, Haskell Foundation was established - an organization that aims to popularize and support Haskell in industry. We see the increasing number of <a href="https://functional.works-hub.com/jobs/?tags=haskell" dir="ltr">job positions on the market</a>, and even more: there is a lack of professional Haskell developers today. Manning Publications has also contributed to this growth quite much: books by Will Kurt ( <a href="https://www.manning.com/books/get-programming-with-haskell?utm_source=workshub&amp;utm_medium=affiliate&amp;utm_campaign=book_kurt_get_3_16_18&amp;a_aid=workshub&amp;a_bid=766c7388" rel="noopener noreferrer nofollow" dir="ltr">Get Programming in Haskell</a> ) and Vitaly Bragilevsky ( <a href="https://www.manning.com/books/haskell-in-depth?utm_source=workshub&amp;utm_medium=affiliate&amp;utm_campaign=book_bragilevsky_haskell_6_28_18&amp;a_aid=workshub&amp;a_bid=3f69e5d2" rel="noopener noreferrer nofollow" dir="ltr">Haskell in Depth</a> ) are very good and practical: a property that was in big demand in the Haskell community according to annual surveys. I believe my book will be a great next step for Haskell and for functional programming in general, so yes, I’m very sure that Haskell is worth learning today. We would like to thank Alexander for chatting with us, we hope to have inspired our readers to start or continue their Haskell journey. You can get early access to Alexander's book Functional Design and Architecture <a href="https://www.manning.com/books/functional-design-and-architecture?utm_source=workshub&amp;utm_medium=affiliate&amp;utm_campaign=book_granin_functional_7_22_21&amp;a_aid=workshub&amp;a_bid=df97db22" rel="noopener noreferrer nofollow" dir="ltr">here</a>. Use our code <code dir="ltr">nlfuncwrks21</code> at checkout to get 35% off. If you would like to read more interviews like these, be sure to <a href="https://functional.works-hub.com/register?utm_source=organic&amp;utm_medium=blog&amp;utm_campaign=m.popa" dir="ltr">sign up</a> to Functional Works!<img src="https://functionalworks-backend--prod.s3.amazonaws.com/logos/9310e838e99de86eb2c8d6320391975f" alt="Author's avatar" width="89" height="89">

We recently had the chance to speak with Alexander Granin, who is a software architect, international speaker, researcher and active member of the C and Haskell commun...

Classic

We recently had the chance to speak with Alexander Granin , who is a software architect, international speaker, researcher and active member of the C++ and Haskell communities about his upcoming book <a dir="ltr" href="https://www.manning.com/books/functional-design-and-architecture?utm_source=workshub&amp;utm_medium=affiliate&amp;utm_campaign=book_granin_functional_7_22_21&amp;a_aid=workshub&amp;a_bid=df97db22" rel="noopener noreferrer nofollow">Functional Design and Architecture </a> and the evolution of Haskell in the past decade.

We know much about object-oriented programming. There are design patterns, design principles, software architectures, and ready solutions - all this forms a complete story of software design in OOP languages. But we don’t have anything equal in functional programming. There were takes on this or that for sure, but nothing that comprehensive and systematic. Authors do their best to observe separate techniques and ideas, but there is no complete story of what approaches we have in functional programming and how to apply them for real tasks.

There is Object-Oriented Design (OOD) for OO languages, and in my book, I’m suggesting its counterpart for the functional world. I call it Functional Declarative Design. The importance of this topic is clear: it’s a new direction of software engineering, and learning will definitely be a good idea for everyone, not only for functional developers.

Learning Haskell was a great idea long ago since Haskell 2010 was established. Haskell gives a completely different perspective on writing the code, and this makes you a better developer. But if this is not convincing enough, then I would say that ideas from Haskell leak into all the main languages: Scala, C++, C#, JavaScript, Java, Kotlin, Rust. Not metaphorically, but literally; for example, C++20 has concepts - a direct adoption of Haskell’s type classes.

Haskell is on its slow but steady rise. In 2020, Haskell Foundation was established - an organization that aims to popularize and support Haskell in industry. We see the increasing number of <a dir="ltr" href="https://functional.works-hub.com/jobs/?tags=haskell">job positions on the market </a>, and even more: there is a lack of professional Haskell developers today. Manning Publications has also contributed to this growth quite much: books by Will Kurt ( <a dir="ltr" href="https://www.manning.com/books/get-programming-with-haskell?utm_source=workshub&amp;utm_medium=affiliate&amp;utm_campaign=book_kurt_get_3_16_18&amp;a_aid=workshub&amp;a_bid=766c7388" rel="noopener noreferrer nofollow">Get Programming in Haskell </a>) and Vitaly Bragilevsky ( <a dir="ltr" href="https://www.manning.com/books/haskell-in-depth?utm_source=workshub&amp;utm_medium=affiliate&amp;utm_campaign=book_bragilevsky_haskell_6_28_18&amp;a_aid=workshub&amp;a_bid=3f69e5d2" rel="noopener noreferrer nofollow">Haskell in Depth </a>) are very good and practical: a property that was in big demand in the Haskell community according to annual surveys. I believe my book will be a great next step for Haskell and for functional programming in general, so yes, I’m very sure that Haskell is worth learning today.

We would like to thank Alexander for chatting with us, we hope to have inspired our readers to start or continue their Haskell journey. You can get early access to Alexander's book Functional Design and Architecture <a dir="ltr" href="https://www.manning.com/books/functional-design-and-architecture?utm_source=workshub&amp;utm_medium=affiliate&amp;utm_campaign=book_granin_functional_7_22_21&amp;a_aid=workshub&amp;a_bid=df97db22" rel="noopener noreferrer nofollow">here </a>. Use our code <code dir="ltr">nlfuncwrks21 </code>at checkout to get 35% off.

If you would like to read more interviews like these, be sure to <a dir="ltr" href="https://functional.works-hub.com/register?utm_source=organic&amp;utm_medium=blog&amp;utm_campaign=m.popa">sign up </a>to Functional Works!

Functional Design and Architecture: Interview with Alexander Granin

We'd like to start by learning a bit about your journey as a developer and author.

What prompted you to write a guide to software engineering using Haskell?

Why do you think this book is important for developers to read?

Who would you recommend it to?

What’s your opinion about the evolution of Haskell in the past decade and why do you think now it’s a good time to learn Haskell?

10 Interview Questions Every JavaScript Developer Should Know

The way we teach coding is all wrong. Here's how it needs to change

Learn these 5 Highest-Paying Programming Languages to Get a Hike