More Things Developers Say and What They Mean

Photo by NESA by Makers on Unsplash

Last Month, I published a post called Things Developers Say and What They Mean. It was very fun and we had a great discussion on these things. Since that post, I have received even more bits of jargon that developers say and decided it was a good time to do a second post.

Just to recap the last post: there are a lot of bits of jargon and buzzwords that developers say that are not taught in courses and tutorials but are important to know. As a self-conscience developer, you tend to not want to stop and ask what these buzzwords are (even though you should) and so I decided to post these definitions in these posts so that you quietly and safely learn these definitions and your imposter syndrome can stay our little secret(#sarcasm).

Currying: The first time I heard this, I couldn’t help but think of my favorite Thai dishes. Given the context, I was pretty sure that currying a function did not have much to do with my favorite food, but still had no idea how curry fit into what people were talking about. I quickly learned that currying is a functional programming technique of separating parameters into multiple function calls. For example, we can take this:

const add = ( a, b ) => a + b;
const result = add(1,2);
// result === 3;