Speaking the Same Language: Mocks, e2e, and Good Code

A lot of discussions this week on X and on LinkedIn about mocks, e2e, Go vs C#, and good vs badly written code. Watched the threads from afar, and if you squint, most in the thread have different definitions for those words.

I find it difficult to participate because 2 people talking about 2 completely different things, and debating some point of view doesn’t make any sense when the point of view isn’t viewed correctly or the same by people in the thread.

I can help with the Mock and Stub. I can help a little with the e2e. I can’t help much with “good code”. I can’t help you at all comparing language ecosystems. So I’ll just cover the first 3.

Continue reading “Speaking the Same Language: Mocks, e2e, and Good Code”

We Hire React Developers

“We hire React developers”. Sadly, that doesn’t really hold up; you’ll need to be wayyyyyy more specific. What does “React developer” mean?

Some write JavaScript, some write TypeScript.

Some use classes, some use Hooks.

Some use imperative/procedural style components, some create pure ones, some use higher order components, some use Mediators, some utilize functional core/imperative shell, some practice a variety utilize a combination thereof, and others have no idea and just inject hooks until they’re “done”.

Continue reading “We Hire React Developers”