The Array Prototype Naming Convention

This article is an opinion piece about a code style for a function naming convention. This article does not intend to be a source of truth for all teams, but you yourself or your team may choose to adopt or enforce this pattern if you so desire to experiment with or document your team’s code style.

Benefits

Function names based on array prototype methods are self-documenting and encourage correct abstractions. They can be understood without prior knowledge of the overall system, because they focus on what is being done instead of how

--

--

--

Staff front end engineer | Tech lead | Architect | charlesstover.com

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Code Integrity in the Kernel

Ethanim System Architecture RSM — application nodes reach consensus efficiently

Farm Multiplier Updates — Liquidity Incentives

API Testing with Rest Assured

Building a data mesh to support an ecosystem of data products at Adevinta

Running Scalable Lightweight Session aware Python Flask application on Kubernetes

Deploying Flask App on Kubernetes

Installtion StackStorm on AWS

Obfuscating Remote SSH Command & Control

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Charles Stover

Charles Stover

Staff front end engineer | Tech lead | Architect | charlesstover.com

More from Medium

Forever Functional #13: Shuffling an Array

Typescript: Type VS Interface

The case against Non Null Assertion Operator !

TypeScript, Part 3: Working with Custom Types