When it comes to talking about program architecture and terms like that, it always sounds a little bit like we’re taking something a little bit more seriously than it deserves.
This is a bit of a digression of my personal opinion, but I thought it worth sharing before getting into the actual post. Skip to the next heading if you feel so inclined.
When I think of architecture, I think of buildings and vehicles and various other things that, you know, keep humans use to live, to move, to stay alive, and so on. When someone says “architecture,” computer programs are not something that comes to mind.
Secondly, in the last decade or say, there has been this cultural shift in the programming community where compiled languages are “real” programs and anything that’s interpreted or that runs on some type of virtual machine is a script or isn’t a “real” program.
But as far as “architecture” is concerned:
the complex or carefully designed structure of something.
And as far as a “program” is concerned:
provide (a computer or other machine) with coded instructions for the automatic performance of a particular task.
So talking about program architecture isn’t inaccurate at all. It can feel a little weird, I guess, and I don’t know why, but that’s my digression.
But let me bring all of this rambling back around to WordPress.
