Skip to content
Book discovery call
Our Philosophy & Standard

The PyCentric Operating Code

Seven non-negotiable principles that govern how we architect software, make tough trade-offs, treat our clients, and evaluate talent across every role.

Where We Are Going

Our Vision

To be the premier software engineering and applied AI studio across South Africa and the African continent, empowering forward-thinking enterprises globally with uncompromised architectural excellence, pragmatic innovation, and high-velocity digital infrastructure.

What We Do

Our Mission

To engineer resilient, cost-effective software architectures, mobile ecosystems, and applied AI solutions through Spec-Driven Development (SDD) and end-to-end SDLC ownership, backed by rigorous automated testing, transparent fixed-price models, and a 3-month comprehensive warranty.

Why We Exist

Our Core Purpose

Democratizing institutional enterprise engineering pedigree (AWS, BMW IT Hub, FNB Fintech) to solve mission-critical business problems deterministically and affordably.

01

Ground Truth & Spec-Driven Rigor

Formal specifications, working software, and empirical data beat theoretical debates, 'vibe coding', and AI buzzwords.

In Practice

Locking machine-verifiable specifications (ADRs, OpenAPI schemas, SOW acceptance gates) before writing code, then managing the full SDLC from TDD and load testing through production SRE.

Anti-Pattern

Unstructured 'vibe coding' from vague tickets, choosing shiny tools to look smart on the client's dime, or abandoning a codebase at launch without CI/CD and observability.

02

The Rule of Three

Never prematurely abstract: solve once to ship fast, solve twice to observe patterns, extract into a reusable library on the 3rd time.

In Practice

Solving a problem natively for two clients, and on the third repetition, extracting the battle-tested logic into a documented, reusable internal package or CLI tool.

Anti-Pattern

Spending 3 weeks building a generic 'universal framework' on day one, or copy-pasting the same boilerplate across five projects without ever extracting a shared library.

03

Sovereign Craftsmanship

Standardize on Golden Paths, prioritize OSI-compliant open source, and ensure 100% clean IP ownership with zero copyleft risk.

In Practice

Standardizing on FastAPI, Flutter, Redis, and Mongo/Postgres with Taskfile automation; using permissive FOSS (MIT/Apache 2.0/BSD) so clients retain unencumbered ownership of their IP.

Anti-Pattern

Introducing unvetted AGPL libraries into proprietary client repos, or writing undocumented, tangled spaghetti code to create artificial vendor lock-in.

04

Relentless Problem Empathy

Start with the customer's operational bottleneck, measure success in hours and rands saved, and manage scope via collaborative swapping.

In Practice

Practicing collaborative scope swapping: 'We can gladly add Feature B, but to protect your fixed deadline and budget, let us swap out Feature A.' Verifying ROI with real telemetry.

Anti-Pattern

Saying yes to every out-of-scope request without discussing trade-offs, leading to missed deadlines, burned-out teams, and surprise change-order disputes.

05

Frictionless Candor

Fixed pricing, plain language, early risk escalation, and blameless 5-Whys post-mortems with mandatory regression tests.

In Practice

Quoting 30-day fixed prices in clear language. When a production bug occurs, authoring a blameless 5-Whys post-mortem and adding an automated test in CI within 24 hours.

Anti-Pattern

Hiding bad news or timeline slips until the deadline, finger-pointing during outages, or hotfixing a bug in production without automated regression test coverage.

06

Harsh-Reality Resilience

Engineer for South African and emerging market conditions: offline networks, load spikes, data costs, and strict POPIA compliance.

In Practice

Building offline-first Flutter synchronization, idempotent background retry queues, sub-150ms p95 API response times, and bank-grade POPIA data encryption.

Anti-Pattern

Building fragile web apps that crash during momentary connectivity drops or routing sensitive customer financial data through unvetted public AI APIs.

07

Elevate the Room

High standards are contagious. Leave every codebase, documentation page, and teammate better than you found them.

In Practice

Providing thorough, educational PR reviews that explain architectural mental models; pair-programming to unblock peers; maintaining zero tolerance for ego.

Anti-Pattern

Knowledge hoarding, gatekeeping codebase access, talking down to non-technical stakeholders, or tolerating high-performing jerks who damage team trust.

Universal Standards

How The Code Applies Across Every Role

The PyCentric Operating Code is not an engineering handbook: it is our company-wide operating system.

Engineering & Architecture

Software, Data & Cloud

  • Ground Truth: Working code beats slide decks; never push AI where SQL/scripting works.
  • Rule of Three: Extract shared libraries on the 3rd repetition to compound velocity.
  • Craftsmanship: Test coverage $\ge 90\%$, sub-150ms p95 latency, zero copyleft risk.
Commercial & Solutions

Sales, RevOps & Pre-Sales

  • Ground Truth: Deep customer problem discovery over pushing vanity AI demos.
  • Rule of Three: Build standardized demo environments & battlecards from repeated wins.
  • Empathy & Scope: Practice collaborative scope swapping to protect fixed client budgets.
Growth & Storytelling

Marketing & Content

  • Ground Truth: Case studies with real rands/hours saved over generic clickbait.
  • Candor: Kill underperforming campaigns quickly based on transparent CAC data.
  • Empathy: Speak directly to operational bottlenecks keeping business leaders awake.
People & Governance

HR, Legal & Operations

  • Elevate the Room: Structured STAR interview scorecards to hire people above our 50th percentile.
  • Candor & Hardening: Radical coaching, clear compensation bands, and blameless operational retros.
  • Resilience: Airtight POPIA compliance, clear IP assignment, and lean operational overhead.
Cognitive Decision Architecture

The Epistemic Knowledge Matrix

At PyCentric, unexamined assumptions are liabilities. We use the four quadrants of knowledge to eliminate blind spots, celebrate intellectual humility, and fuel continuous, deliberate upskilling across every engineering team.

Q1 Conscious • What We Know
Verified Mastery

Known Knowns

The Realm of Proven Execution

Validated competencies and non-negotiable standards: Python 3.12, FastAPI, uv, Flutter, PostGIS, Docker, Taskfile automation, and minimum 90% TDD domain logic coverage.

Operational Mandate: Codify & Automate

Author Architectural Decision Records (ADRs), automate CI linting gates, and mentor peers to compound company-wide velocity.

Q2 Conscious • What We Do Not Know
Targeted Curiosity

Known Unknowns

The Realm of Deliberate Upskilling

Conscious capability gaps and frontiers: high-concurrency spatial GiST tuning, gRPC bidirectional streaming, B-BBEE QSE scorecard planning, or SARS Section 11D R&D incentives.

Operational Mandate: Directed Spikes & Practice

De-weaponize ignorance with Carol Dweck's Growth Mindset ("we do not know this yet"), funded by a dedicated 25% R&D sprint capacity allocation.

Q3 Latent • What We Know
Tacit Wisdom

Unknown Knowns

The Realm of Unarticulated Superpowers

Internalized domain intuition, rapid incident triage heuristics, unwritten patterns, and competencies high-performers undervalue in themselves due to imposter syndrome.

Operational Mandate: Externalize & Celebrate

Use Signal 360 reviews to reflect superpowers back with code evidence; convert intuitive triage instincts into documented runbooks.

Q4 Latent • What We Do Not Know
Radical Humility

Unknown Unknowns

The Realm of Blind Spots & Black Swans

Latent system failure modes, unexpected regional telecom drops during Eskom Stage 6 load shedding, unmodeled regulatory traps (SARB Section 743), or Dunning-Kruger hubris.

Operational Mandate: Stress-Test & Pre-Mortem

Enforce blameless 5-Whys post-mortems with mandatory 24h regression tests, run chaos engineering drills, and conduct pre-mortems to surface weak signals.

Performance & Hiring

Measured in 'PyCentric Signal'

We evaluate ourselves twice a year using PyCentric Signal, our strengths-anchored 360 review process. Guided by the Epistemic Knowledge Matrix, we identify each contributor's Top 2 Superpowers (Quadrants I and III) and their 1 Highest-Leverage Growth Edge (Quadrant II) based on verified code evidence.

In our hiring loop, every candidate is evaluated on these principles using the STAR behavioral framework, signed off by an independent Bar Raiser.

Work With Our Team Join PyCentric