> I believe avoiding unnecessary temporary variables in a very valuable thing for the reasonability of code I’m not convinced temp vars are avoidable in produc

> I believe avoiding unnecessary temporary variables in a very valuable thing for the reasonability of code I’m not convinced temp vars are avoidable in production code, since usually you end up needing error checking/handling on intermediate results anyway. Teams I’ve worked on generally try to avoid dense nested and/or chained expressions for this reason, but also because too much density or conciseness also limits the readability/reasonability of code. I like that pipes turn nested expressions right-side out like the article points out, but temp vars already do this too. The other thing that temp vars help with is making it easier to change functions in the middle of a sequence. If you have a nested expression, sometimes having to refactor something in the middle leads to a bigger avalanche of changes than necessary. Using temp vars might be somewhat less churn in some cases due to already haven broken down the expression into pieces. Maybe this pipes design will allow that too, it’s hard to say without using it for a while.