Skip to content
View einnor's full-sized avatar

Organizations

@golclinics

Block or report einnor

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. 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
einnor/README.md

Ronnie Nyaga

APIs, asynchronous workflows, and thoughtful interfaces.

I build software with a focus on correctness, reliability, and clear trade-offs. My public projects explore the path from an interactive client to an API, persistent state, and background work.

Start here

Project Engineering focus Explore
GraphQL Forum API Authorization boundaries, request-scoped batching, transactional answer selection, database migrations and subscription events. Schema · Integration scenarios
Uptime A dependency-free Node.js monitoring API: sessions, background probes, timeouts, atomic file replacement and status-change alerts. API walkthrough · Failure-path tests
Serverless Reminders Scheduled Lambda workflows, SES integration, scoped IAM and offline email-template verification. Design and operational boundaries

Interfaces and state

Project What to look for
Song-Hop React 19 discovery UI, resilient device-local favorites, responsive layouts and user-initiated synthetic audio. An account-free demo with fictional content.
Todoey Flutter/Provider state flow, input validation, widget interaction tests and a runnable web build.
React Tetris Collision rules, immutable movement, timer lifecycle and regression-tested line-clear scoring.

Song-Hop's running discovery interface

Also: Ruyo Client, a legacy TypeScript order-management frontend with documented API contracts and browser screenshots using clearly labeled simulated services.

How I approach engineering

  • Make behavior inspectable. Executable examples and tests should explain an API better than a feature checklist alone.
  • Exercise failure paths. Expired sessions, missing data, interrupted requests and unavailable services are part of the design.
  • State the consistency boundary. Atomic file writes, database transactions and at-least-once delivery solve different problems.
  • Keep demonstrations honest. Local fixtures, external integrations and production-readiness gaps are explicitly identified in each README.

These are hands-on portfolio and learning projects. Each README includes reproducible setup, architectural decisions, and clear boundaries around what has been verified.

Pinned Loading

  1. uptime uptime Public

    Dependency-free Node.js monitoring API with background probes, status-change alerts, atomic file storage, and real HTTP regression tests.

    JavaScript 1

  2. flutter-todoey flutter-todoey Public

    Flutter 3.50 task-list app exploring Provider state, validated input and widget tests, with Android/iOS scaffolds and a runnable web build.

    Dart

  3. serverless-reminders serverless-reminders Public

    TypeScript scheduled email workflows using Lambda, EventBridge and SES SDK v3, with scoped IAM and credential-free template previews.

    CSS 1

  4. react-tetris react-tetris Public

    React 19 falling-block game with custom hooks, collision detection, immutable movement, tested scoring, and Vite tooling.

    JavaScript 2 2

  5. song-hop song-hop Public

    Strict TypeScript + React music-discovery demo with resilient local favorites, cross-tab state, accessible keyboard navigation and tested Web Audio.

    TypeScript

  6. graphql-forum-api graphql-forum-api Public

    Forum GraphQL API: Apollo 5, request-scoped batching, transactional answer selection, subscriptions, and SQLite/MySQL integration tests.

    JavaScript