why F#’s pipes operator is so awesome In his talk at Build Stuff 2014, described the lack of in code such as these: “Seven Ineffective Coding Habits of Many Programmers” Kevlin Henney visual honesty public int howNotToLayoutMethodHeader(int firstArgument,string secondArgument) and on what visual honesty means, he presented a number of quotes from Daniel Higginbotham’s excellent website: Clean Up Your Mess To answer the question “What is clean design?” most succinctly: a clean design is one that supports visual thinking so people can meet their information needs with a minimum of conscious effort … You convey information by the way you arrange a design’s elements in relation to each other. This information is understood immediately, if not consciously, by the people viewing your design… This is great if the visual relationships are obvious and accurate, but if they’re not, your audience is going to get confused. They’ll have to examine your work carefully, going back and forth between the different parts to make sure they understand. The quotes talk about laying out information so that their visual relationships are obvious and accurate. So if you layout your method arguments in such a way that their visual relationships are not accurate and you do that purposefully, then you’re in fact being dishonest. As I sat there, I finally understood why are so awesome. I always knew it makes cleaner and more readable code, it’s intuitive, but I haven’t been able to find the words to explain why — the trouble with being able to understand something with minimum conscious effort is that your conscious mind can’t explain how it understood it. F# pipes Not anymore, now I finally understand it. When we’re reading a piece of regular English text, we’re reading from left-to-right, then top-to-bottom. This convention controls the flow of information we receive as we read, so when we’re laying out information for people to consume, we lay them out in the order of left-to-right, then top-to-bottom. But what about code? When it comes to writing nested function calls, somehow this flow of information has been reversed! With F#’s pipes (which has been adopted in both Elm and Elixir by the way), we have finally managed to restore some sanity and present sequence of function calls in a way that matches the way we consume any other textual information. Visual honesty right before your eyes! Links Clean Up Your Mess — A guide to Visual Design for everyone NDC Oslo 2014 — Takeaways from keynote “it’s a write/read web” NDC Oslo 2014 — Takeaways from “career reboot for the developer mind” Takeaways from Theo Schlossnagle’s talk on Scalable Internet Architecture Takeaways from Hewitt, Meijer and Szyperski’s talk on the Actor model Takeaways from Gael Fraiteur’s multithreading talk

Flow

Twitter

Understanding homoiconicity through Clojure macros

Smallest .Net ref type is 12 bytes

Ask me for help about serverless

Read My Stories

Too Long; Didn't Read

Make resilience your competitive advantage

Being visually honest with F#

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

Modeling Hierarchical Access With AppSync In 3 Simple Steps

104 Stories To Learn About Go

105 Stories To Learn About Functional Programming

100+ Free Pluralsight Courses to learn Python, Java, and Spring Boot

10 Websites to Learn JavaScript for Beginners

Modeling Hierarchical Access With AppSync In 3 Simple Steps

104 Stories To Learn About Go

105 Stories To Learn About Functional Programming

100+ Free Pluralsight Courses to learn Python, Java, and Spring Boot

10 Websites to Learn JavaScript for Beginners

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps