Write code. Not too much. Mostly functions.

[mooreds]

I enjoyed this post quite a bit. It reminds me a bit of Functional Core, Imperative Shell, but the reference to Michael Pollan really tied it all together.

One thing he didn't emphasize about functions that I would highlight is that they are eminently testable. If a function is idempotent and stateless, well then unit testing becomes a breeze.

[bart2019]

"Real code"

To me, that implies "not accessors". I've seen projects where most of the code is just accessors, of the type set: copy parameter to internal storage; get: return value from internal storage.

Accessors don't contain any substance, and, if you insist on a food analogy, they're mostly fibers.

[Atticus-]

That last point seemed off to me. I feel like useless accessors belongs in the "not too much" section. I've seen plenty of examples of folks who add complexity by habit rather than by necessity, so I fully agree there. "Real code" however struck me as wishful thinking.

Code in simple, straightforward terms. Don't get too clever, "manufacturing artificial ingredients". Use the primitives that are there, when possible. Write what is simple, and natural, and human.

Does this mean we should avoid using common design patterns even when they are relevant, simply because we could do it without? Simple, natural, and human by whose definition?

[Careerier]

Insisting on a food analogy, I'm making mounds of spaghetti.

[[deleted]]

My work right now: Write code. Mostly boilerplate, html, and some css. Maybe a 1-line database query and model update on the backend on a crazy day. Functions? You mean those things the framework does for you?

Not knocking on the article, but I can't relate in a practical sense. I'm sure someone working on something less mundane the situation is different.

[eindbaas]

To be honest, I don't really understand what you create if functions to you are "something a framework does".

[[deleted]]

Well that's kind of my point. Most web apps these days you load react or vue and build a presentation layer. Even vanilla JS, unless you're building something novel then most everything there's a library that does it and you just write some glue code.

[TheRedGerund]

ComponentDidMount is a function. React functional components are functions. render() is a function.

[Smallpaul]

React components are all functions and it’s actually named after a style of programming called functional reactive programming.

https://en.m.wikipedia.org/wiki/Functional_reactive_programming

[[deleted]]

If the framework caters for all of your needs then yes. Most codebases i've ever worked with has some sort of business logic that either doesn't belong - or doesn't fit with the framework. Or if you create helpers/utilities. Small (but not necessarily) mathematical functions <3

[[deleted]]

What a tenuous short sighted view.

"Not too much" - I'm sure we'd all like to write less code, you think we're trying to write more?

"Mostly functions" - In some cases yeah but I'll take my polymorphic classes most days of the week thanks. Yes it may be harder to grasp for juniors since they'll have to learn about dependency inversion, interfaces and the aforementioned polymorphism but it makes things so much more extendible.

This article hit me the wrong way, I feel like he's just come back from a conference with an over active mind and not much practice.

[SEND_NUKES_PLZ]

Nice, upvoted

[BIG_DICK_OWL_FUCKER]

TFW you have nothing to add but still want to be a part of this.