Materializing artifacts

Always produce artifacts. They'll offer you a platform upon which thoughts can evolve. I refer to artifacts in this context as pieces of thoughts put into writing or ideas realized in any medium of preference.

There can't be an actualization let alone an evolution of an idea that's not translated to a tangible medium. It remains a brain fart whose scent only you will momentarily enjoy

Armatures, materials

Algorithms become fairly simple when your domain and the relationships between the structures representing the domain in question is well thought out.

These structures form an armature which will hence be adorned by which ever material of your choosing. Plastics, perhaps. Materials being algorithms and how you decide to co-locate them.

Functional programming proponents will favor separating actors on data from data as opposed to keeping them within discrete enclosed object as with OOP.

Either way, you must have structure and behavior as the constituents of a working system. If the armature is not built to support the plastic, going from prototype to production becomes burdened by friction.

Molding Spaces

Although the world is an infinite conjunct of propositions, we do not aim to represent all of those in our programs. We instead carve out a niche i.e a semantic space for which we build. If we do not carve out a semantic space, our work would be endless and will undoubtedly drive us to failure. This failure hence is a symptom of unclear objectives.