Skip to content
View nooby6's full-sized avatar

Block or report nooby6

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
nooby6/README.md

Audrine Whrite

Backend-focused software engineer building scalable services, APIs, distributed systems, and data-intensive applications.

I work across Go, Java/Kotlin, Python, TypeScript/Node.js, and SQL, with a strong focus on backend architecture, PostgreSQL, concurrency, testing, reliability, and production engineering.

What I build

  • Scalable services and APIs — backend services, REST APIs, queues, workers, webhooks, and event-driven workflows.
  • Reliable systems — transactions, concurrency control, idempotency, failure recovery, validation, and database constraints.
  • Performance and debugging — query optimisation, profiling, benchmarking, bottleneck analysis, and systematic debugging.
  • Engineering quality — automated testing, code review, maintainable architecture, clear interfaces, and pragmatic design decisions.

Languages

Go · Java · Kotlin · Python · TypeScript / Node.js · SQL

I use different languages where they make engineering sense, including concurrent Go services, JVM backends, Python APIs, TypeScript applications, and PostgreSQL-backed systems.

Selected work

A distributed job and workflow engine built from first principles in Go. It focuses on durable job state, PostgreSQL-backed queueing, concurrent workers, execution leases, ownership, and failure recovery.

Engineering focus: concurrency · distributed systems · PostgreSQL · API design · testing · reliability

Stack: Go, PostgreSQL, pgx, net/http, Docker, GitHub Actions

An enterprise workforce scheduling backend built with Kotlin and Spring Boot. It models employees, shifts, leave, scheduling conflicts, transactional updates, and database-level consistency.

Engineering focus: domain modelling · transactions · PostgreSQL · API design · concurrency safety · automated testing

Stack: Kotlin, Java 21, Spring Boot, PostgreSQL, Flyway, Docker, GitHub Actions

A real-world sales and logistics platform covering orders, inventory, delivery tracking, role-based access, reporting, and operational workflows.

Engineering focus: business rules · relational data modelling · APIs · authentication · operational software

Stack: TypeScript, React, Vite, Supabase, PostgreSQL

SokoSauti

A commerce and marketing platform for African SMEs involving merchant messaging, automation, payments, and data-driven workflows.

Engineering focus: backend architecture · APIs · messaging · payments · asynchronous workflows

Engineering Practices

Backend

  • Go
  • Java / Kotlin / Spring Boot
  • Python / FastAPI
  • Node.js / TypeScript

Systems

  • REST APIs
  • PostgreSQL
  • Distributed systems
  • Queues and workers
  • Concurrent processing
  • Event-driven architecture
  • Background jobs
  • Webhooks
  • Authentication and authorization

Reliability & Performance

  • Automated and integration testing
  • Concurrency testing
  • Database transactions
  • Query optimisation
  • Profiling and benchmarking
  • Failure recovery
  • Idempotency
  • Observability
  • CI/CD

Code Review & Engineering Quality

  • Reviewing API contracts and service boundaries
  • Finding concurrency and race-condition risks
  • Checking transaction and database consistency
  • Identifying inefficient queries and avoidable work
  • Evaluating error handling and failure modes
  • Assessing test coverage and testability
  • Refactoring for clarity and maintainability
  • Using ADRs and review notes to document engineering decisions

How I Approach Engineering

I care about more than getting an endpoint to return 200.

When building or reviewing backend systems, I look at correctness under failure, concurrency behaviour, transaction boundaries, database performance, API contracts, testability, observability, and operational failure modes.

I prefer small, understandable interfaces, explicit business rules, strong automated tests, and designs that remain predictable as traffic and system complexity increase.

I also treat code review as an engineering activity rather than a style check: understand the change, challenge its assumptions, look for correctness and performance risks, verify the tests, and leave the code easier to operate and maintain.

Current Direction

Deepening my work in backend engineering, distributed systems, algorithms, system design, performance engineering, code review, and production software practices.


Based in Kenya · Backend-focused · Open to software engineering opportunities

Pinned Loading

  1. forgequeue forgequeue Public

    Go

  2. opsgrid opsgrid Public

    Kotlin

  3. nsqio/nsq nsqio/nsq Public

    A realtime distributed messaging platform

    Go 25.8k 2.9k