The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Deep Thought of the "3-6-9 Manifesto" established as an Automation Architect who understands the bridge between ancient efficiency principles and 2026 agentic technology.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Challenges
View all
Related posts
Code is a map of the problem it solves.
Good software is not defined by how much code exists, how complex the stack looks, or how many technologies were involved.
It is defined by whether the system solves the right problem clearly, reliably and with as little unnecessary complexity as possible.
At HERODOT, software engineering is where strategy becomes infrastructure.
Architecture, automation, interfaces, integrations, security, maintainability and performance all have to work together. The goal is not simply to ship code. The goal is to build systems that remain understandable, adaptable and useful after launch.
Because code is temporary.
The problem it solves is what matters.
The framing turns a fairly abstract engineering message into something visually legible—the red-on-black system and oversized type create a strong technical voice. The line about solving the right problem also gives the composition a clear point of view.
🚀 Recently launched a Webflow build for Toronto-based intellectual property (IP) software startup. The team at Clerq and Overline were brilliant to work with, and had incredible vision to make this one stand out.
Clerq, rebranded from NL Patent, is an agentic AI platform that automates patent workflows. Overline led the rebrand and designed the site, then handed it over to me to build in Webflow.
Really grateful to be chosen to work on this one, and deliver a solid site for Clerq to move forward with.
Check out the full case study in my Profile
Most people don’t avoid automation because they lack ideas.
They avoid it because turning “when this happens, do that” into a working system can swallow an afternoon.
n8n has just introduced an assistant that can take a plain-English request, build the workflow, run it, and help fix what breaks.
That makes the first step easier. But there’s still one thing the tool can’t decide for you: what should happen when reality doesn’t follow the happy path.
Before automating a task, write down:
What starts it?
What should happen?
When should a person step in?
If you could automate one annoying task this week, what would it be?
