Mighty QuinnConsultingMighty Quinn Consulting — home

Culture

This is MQC

How we work, what we argue about, and why the website has a blinking cursor in the logo.

Draft. Structural placeholder — replace with the real thing, ideally written by the team rather than about them.

We are nerds about this, and we are not hiding it

The solution pages give it away. Every one of them is titled with the sentence somebody actually said when the thing finally worked — "no more 'wait, when did that change?'" — rather than with a product name a branding round would have produced. So does the tier badge on every solution card, which is a rarity indicator that happens to encode real build complexity.

None of that is decoration for its own sake. A team that enjoys the work is a team that reads the changelog before the outage, and that is genuinely what you are buying.

Things we actually believe

  • The smallest thing that works. Scope is a cost, not a feature.
  • Boring where it counts. Postgres, Go, server-rendered HTML. Save the novelty for the problem, not the plumbing.
  • Own the operations. If we recommend a stack, we run it ourselves first.
  • Say what did not work. Every project has a part that went sideways. The useful consultancy is the one that tells you which part.

What we argue about

Tabs, mostly. Also whether a thing is a Smart Little Helper or has quietly become a Low-Code App — which sounds like a taxonomy dispute and is really a question of who maintains it in two years.

The cursor in this page's header blinks for the same reason. It is not decoration somebody liked the look of: it stands for somebody being about to type. We build things rather than waiting for them to appear.

Our mission statement is a script

There is no poster of corporate values in the internal portal. There is this, and it greets us at sign-in:

Write-Host 'Wir sind MQC!' -ForegroundColor Cyan

$unsereVision = 'Wir sind das coolste IT- und Beratungs-Startup in dieser und allen anderen weit, weit entfernten Galaxien.'

$unsereMission  = "Wir sind immer dazu bereit, dazuzulernen.`n"
$unsereMission += "Wir schaffen jeden Tag Mehrwerte für uns, unsere Kollegen und unsere Kunden.`n"
$unsereMission += "Wir zeigen mit unserem Wissen, unserer Art und unserer Arbeitsweise, dass IT Lösungen schafft und Spaß machen darf."

Write-Host $unsereVision  -ForegroundColor Cyan
Write-Host $unsereMission -ForegroundColor DarkCyan

for ($i = 0; $i -lt 32; $i++) { $line += '-' }
Write-Host $line -ForegroundColor Blue

Write-Host 'Fight hard! Think hard! Work smart! HAVE FUN AND ENJOY!' -ForegroundColor Cyan

It runs. That is more or less the point: anyone who writes a mission statement in PowerShell intends for somebody to execute it.

What we let ourselves do

  • Ask. We ask colleagues when we are stuck, or when somebody has more experience with a thing. That is not weakness, it is the shortest route.
  • Get it wrong. We make a mess of things. We say so, we learn from it, and we work out together what goes better next time. It is why every project file carries the column for the part that went sideways.
  • Stay fit. Technically, methodically, and in the head. All three, not just the first.