Rapid Consulting

We are AI-enabled technologists

Every step—from whiteboard to deployment—is handled with rigor, precision, and expertise.

We design and deliver systems that are technically excellent, robust, future-proof and practical to operate.

We translate complex opportunities into elegant, production-grade solutions.

We build with precision, scalability, and a clear understanding of the business context.

car
Built for impact

Confidence through thoughtful engineering, continuous innovation, and uncompromising craftsmanship.

cube
Beyond Code

Strategy, maintainbility & cost-effectiveness. Accurate analysis and balanced decisions.

glasses
Measurable advantage

Our work is defined by outcomes: faster operations, smarter decisions, and capabilities that compound over time.

Application Layer Expert Developers

Transforming Ideas into Intelligent Solutions

Software consultants specializing in ruby, javascript, php and python. 

Empowering our clients with AI/ML integration, custom model development, and intelligent automation for forward-thinking businesses.

hand of god

"We use AI but 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.

.

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] 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.