We are AI-enabled software consultants
Every detail—from architecture to deployment—is handled with rigor, ensuring clarity, performance, and long-term maintainability.
We design and deliver systems that are technically rigorous and commercially impactful.
We embed AI into core workflows, decision-making, and product architecture to create durable advantage.
We translate complex opportunities into elegant, production-ready solutions.
We build with precision, scalability, and a clear understanding of business context.
Built for impact
We combine deep engineering expertise with AI to deliver solutions that are practical, scalable, and grounded in real business outcomes.
AI that actually ships
We don’t just prototype—we design and deploy production-ready AI systems that integrate with your existing stack.
Measurable advantage
Our work is defined by outcomes: faster operations, smarter decisions, and capabilities that compound over time.
Transforming Ideas into Intelligent Solutions
Software consultant specializing in AI/ML integration, custom model development, and intelligent automation for forward-thinking businesses.
"We are better than AI. We are human."
Real thinking.
Real people.
Crafted, not generated.
Invented, not imitated.
The future needs
more humanity.
Not less.
AI can replicate patterns.
Humans create meaning.
e9e
Latest Articles
All Articles
How to mock fetch and a state change in jest, react
tl;dr: I decided not to do it.
Since Enzyme is obsolete as of React 18, you would use <render /> and not <mount />. Therefore, you don't have a wrapper to manipulate and observe the state of the component being tested.
Furthermore, I'm really only testing the component because it's a best practice, and because of the expectation of future complexity. The state change itself is trivial:
[FIXED] Cannot find module babel-preset-react-app/ node_modules/@babel/runtime/ helpers/interopRequireDefault.js
The solution for me was to clear Jest cache:
./node_modules/jest/bin/jest.js --clearCache
[FIXED] Uncaught PHP Exception EntityStorageException: Invalid address: (to): at SqlContentEntityStorage.php line 815
Seeing this ^ error and currently don't know how to fix it. It happens only on some of my (presumably identically configured) websites. This is happening when a user attempts to post any comment.
Turns out, this was due to a workflow rule that attempted to email the author of a parent-comment and notify them that their comment has been replied to. Since there is no parent comment, there is no email to send a message to, which was causing the error.