Book Image

Learning Functional Programming in Go

By : Lex Sheehan
Book Image

Learning Functional Programming in Go

By: Lex Sheehan

Overview of this book

Lex Sheehan begins slowly, using easy-to-understand illustrations and working Go code to teach core functional programming (FP) principles such as referential transparency, laziness, recursion, currying, and chaining continuations. This book is a tutorial for programmers looking to learn FP and apply it to write better code. Lex guides readers from basic techniques to advanced topics in a logical, concise, and clear progression. The book is divided into four modules. The first module explains the functional style of programming: pure functional programming, manipulating collections, and using higher-order functions. In the second module, you will learn design patterns that you can use to build FP-style applications. In the next module, you will learn FP techniques that you can use to improve your API signatures, increase performance, and build better cloud-native applications. The last module covers Category Theory, Functors, Monoids, Monads, Type classes and Generics. By the end of the book, you will be adept at building applications the FP way.
Table of Contents (21 chapters)
Title Page
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Index

Software design methodology


Software design is where we:

  • Gather requirements
  • Create specifications from requirements
  • Implement a solution based on the specifications
  • Review results and iterate to improve the solution

Traditional waterfall development depends on a perfect understanding of the product requirements at the outset and minimal errors being executed in each phase. Source: http://scrumreferencecard.com/scrum-reference-card/

Scrum blends all the development activities into each iteration, adapting to discovered realities at fixed intervals:

 Source: http://scrumreferencecard.com/scrum-reference-card/

In the process of creating specifications, artifacts such as Unified Markup Language (UML) diagrams are often created to help us think about the problem and craft a viable solution.

Analysis is where we model real-world operations, breaking apart pieces into components. Design is where we craft a software solution based on the analysis work, our IT environment, and the frameworks/technology stacks...