What we call ourselves speaks to how we create.
But how we create isn't destiny about identity.
There is a history in every journey and how we say what we do.

Softly Engineering

Although prophesied to practice software engineering by degree, historical baggage plagues the field with an unstable past and uncertain future. Engineering assumes understanding systems and applying science to solve problems. Sparing the debate between coder, webmaster, developer, and computer scientist, the vision and anticipation behind engineering software changed with practices reinforcing it.

To each project its Role

Software is more than code, and engineering recognize complex and diverse skills to realize everything from civil society to mechanics. From analysis to quality assurance, different titles matched the demands of the times.

Quality Assurance > DevOps > Cloud Engineering

Software is malleable, with roles to reflect technical translation as much as creation. Roles that showcase their malleability within related and adjacent fields. New subsets of titles become justified through authority, marketability, and demand.

Prompt Engineer > Memory Engineer + Automation = Context Engineer
Even today’s AI age, rifts old engineering paradigms in new ways. It makes us feel like something was built.

A new experience

With the practice of building, design elements from aesthetics to function assert itself. As people popularized apps designed for them, engineers defer to research and experience. Beyond the debate to design an experience are new crafts to guide interactions. Frustrations with unpleasant, complicated software become frustration in comprehending behavior, and experiments to compliment those behaviors with usable systems.

Internalizing 'designgineer’ to recognize design and engineering as the creative foundation of our digital age. New practices birthed from integrations of how and what we produce. Offerings attributed to creative masks of UX/UI designer, design engineer, or product designer. Roles taking many shapes, but revolving around an art of listening and communicating.

Crafts don’t manage themselves

Size and scale breeds chaos. Teams march toward finality hoping the sum justifies iteratively built pieces. Rome was built neither by one person, or in one day. But understanding and empathizing with resources to responsibly realize projects is the key to outsized impact. Managing the plight of creative processes under waterfalls and iterative cycles promote flexible solutions that scrounge and scrum how teams can create with respect to time and personal well-being.

When balancing teams of designers with engineers and stakeholders, confidence evolves with practice as a product/project manager to product lead, to product officer, to demonstrating business impact. Looking beyond the current title are plans, ideas, and a roadmap towards defining a cohesive strategy along technical lines.