The Business of Writing

Articles dedicated to writing for profit, whether it be books, courses, articles, copywriting, blogging, etc.

Follow publication

Member-only story

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

The Business of Writing
The Business of Writing

Published in The Business of Writing

Articles dedicated to writing for profit, whether it be books, courses, articles, copywriting, blogging, etc.

Adrienne C.
Adrienne C.

Written by Adrienne C.

Dominatrix of the written word. I write about writing, politics, race, money, religion, sex — hence the editor of The Third Rail

Responses (1)

Write a response

Wonderful article! I will be sharing with my engineering teams. We have a different solution that leverages HOCs to reuse logic and favors copy over abstraction. The GIST is move all logic to a HOC, reduce the component to a render function, and…

Once you’ve established a context flag in your app, it will continue to be proliferated throughout the codebase like a bad idea

For sure, it's the gateway to the wrong abstraction. I'm in a codebase now with 2^186 possible permutations due to this!

One of the nice solutions I've found to make the code look cleaner for the mentioned case is using <IF> as component