“Composition” means putting things together.
I compose when I write. I’ll write a sentence. I’ll write a second sentence. I’ll maybe add a third. Soon, I have a paragraph.
I make choices when I compose. A new sentence might belong in a new paragraph.
Maybe a sentence demands its own paragraph.
(Maybe a thought isn’t that important but I can’t help but include it. I might wrap such a thought in parentheses.)
I’ll compose sentences into paragraphs, and then the paragraphs often get composed into something, too. A blog post, maybe. An essay or an article. An email. A cover letter. Perhaps a chapter — one of many that get composed themselves, into a book.
I compose when I write code, too. I’ll write a line of code. I’ll write another line. Maybe I’ll add a third. Soon, I might start thinking about taking a few lines and extracting them into a function.
So I make choices when I compose code. New functionality might belong in a new function, a new class, a new module.
I’ll compose functions into classes and/or modules, then compose modules into libraries and/or applications.
