Skip to content
View b1gg13's full-sized avatar
♠️
KODE
♠️
KODE

Block or report b1gg13

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

b1gg13.deb

Oduor Brian Ogutu

developer = {
    "name": "Oduor Brian Ogutu",
    "alias": "b1gg13",
    "mission": "Build with precision. Learn what I build.",
    "status": "always_learning",
    "coffee": True,
}

Where hunger never dies, creativity feeds.


MISSION

interface Mission {
    write: "with precision";
    learn: "with understanding";
    build: "with purpose";
    improve: "continuously";
}

const mission: Mission = {
    write: "with precision",
    learn: "with understanding",
    build: "with purpose",
    improve: "continuously"
};

My goal is not simply to make code work.

I want to understand why it works, why it breaks, what happens underneath, and how it can be improved.

Change is part of development.

BUILD → TEST → BREAK → DEBUG → UNDERSTAND → REFACTOR → DEPLOY

VISION

#include <stdio.h>

int main(void)
{
    printf("Build understanding.\n");
    printf("Create products worth using.\n");
    printf("Create a portfolio worth seeing.\n");
    printf("Learn enough to lead others.\n");

    return 0;
}

I am working toward becoming a developer who can move from:

Idea → Architecture → Code → Product → Deployment → Maintenance

while understanding the reasoning behind every stage.


LANGUAGES

const languages = [
    "Python",
    "JavaScript",
    "TypeScript",
    "HTML",
    "CSS",
    "SQL",
    "C"
];

console.log(languages);

Current Stack

Frontend
├── HTML
├── CSS
├── JavaScript
├── TypeScript
├── React
└── Tailwind CSS

Backend
├── Python
├── Flask
├── Node.js
└── REST APIs

Databases
├── MongoDB
└── SQL

Tools
├── Git
├── GitHub
├── Linux
└── VS Code

Exploring

fn currently_learning() -> &'static str {
    "Rust"
}

HOW I THINK

def solve(problem):

    understand(problem)

    pieces = break_into_smaller_parts(problem)

    solution = build(pieces)

    while not solution.is_good_enough():

        test(solution)

        if solution.breaks():
            understand_why(solution)
            fix(solution)

        refactor(solution)

    return solution

A bug is not just something to remove. It is something to understand.


🚀 PROJECTS.IN_PRODUCTION

Projects being actively developed toward real-world use.

type ProjectStatus =
    | "IN_PRODUCTION"
    | "UNDER_UPDATE"
    | "COMPLETED";

const productionProjects: ProjectStatus = "IN_PRODUCTION";

EKPLUS Business Management System

project = {
    "name": "EKPLUS Business Management System",
    "purpose": [
        "Sales",
        "Employee Management",
        "Commissions",
        "Client Bills",
        "Payroll",
        "Reporting"
    ],
    "stack": ["Python", "Flask", "MongoDB", "SQL"],
    "status": "IN_PRODUCTION"
}

A business-management platform designed around real operational workflows.


EKOMARK Insurance CRM

CREATE TABLE clients (
    client_id INTEGER PRIMARY KEY,
    name TEXT,
    phone TEXT,
    policy_status TEXT
);

Planned capabilities include:

  • Client management
  • Motor insurance
  • Health insurance
  • Quotations
  • Renewals
  • Claims
  • Policy records
  • Reporting

Stack: Python · Flask · MongoDB · SQL

STATUS: IN_PRODUCTION


Water Delivery Management System

const delivery = {
    customer: "Customer ID",
    capacity: [5000, 10000],
    billing: ["Daily", "Weekly", "Fortnightly", "Monthly"],
    payment: ["Cash", "M-Pesa", "Invoice"],
    status: "IN_PRODUCTION"
};

Designed for water-delivery operations including:

  • Customer records
  • Tank capacity
  • Delivery tracking
  • Billing
  • Payments
  • Invoices
  • Customer history
  • Reporting

Property Management System

class Property:

    def __init__(self, tenant, rent):
        self.tenant = tenant
        self.rent = rent
        self.status = "ACTIVE"

    def collect_rent(self):
        return "RECORD PAYMENT"

Focused on:

  • Properties
  • Tenants
  • Rent
  • Arrears
  • Utilities
  • Maintenance
  • Payment records
  • Reporting

STATUS: IN_PRODUCTION


Big Bites Meal Prep

type Order = {
    customer: string;
    meals: string[];
    delivery: boolean;
    paymentConfirmed: boolean;
};

function confirmOrder(order: Order) {
    return order.paymentConfirmed
        ? "ORDER CONFIRMED"
        : "AWAITING PAYMENT";
}

A food and meal-preparation concept focused on:

Meal Prep · Recurring Orders · Events · Delivery · Customer Management

STATUS: IN_PRODUCTION


Merchant Business Management Platform

FINANCE
   │
   ├── Sales
   ├── Expenses
   ├── Statements
   ├── Tax Reports
   │
DOCUMENTS
   │
   ├── Procurement
   ├── Receipts
   ├── OCR
   └── Records
   │
REPORTING
   │
   └── Business Intelligence

A broader platform concept for small-business financial and operational management.

STATUS: ACTIVE DEVELOPMENT


🔧 PROJECTS.UNDER_UPDATE

$ git status

modified:
    EKPLUS Website
    EKPLUS Management Tools
    Insurance Tools
    Water Management Tools
    Business Automation Tools

These projects have working foundations but are being continuously improved through:

UI improvements
        ↓
Feature expansion
        ↓
Database improvements
        ↓
Automation
        ↓
Testing
        ↓
Refactoring
        ↓
Deployment

✅ COMPLETED

completed = [
    "EKPLUS Website",
    "Business Administration Tools",
    "Initial Insurance Management Tools",
    "Initial Water Delivery System",
    "Initial Property Management Tools",
    "Frontend Web Projects",
    "Python Automation Projects",
    "HTML/CSS/JavaScript Projects"
]

But...

const finished = false;

if (project.isUseful()) {
    project.continueImproving();
}

A completed version does not necessarily mean the end of development.

Some projects become foundations for the next version.


🧪 LAB

Not every repository is intended to become a product.

Some exist because I wanted to answer a question:

questions = [
    "How does this work?",
    "Why did this break?",
    "What happens if I change this?",
    "Can I automate this?",
    "Can I make it faster?",
    "Can I make it simpler?"
]

for question in questions:
    experiment(question)

Current Areas of Exploration

Python
├── Automation
├── Data Structures
├── APIs
├── Web Applications
└── Business Systems

JavaScript / TypeScript
├── DOM
├── React
├── Next.js
├── Node.js
└── API Integration

Backend
├── Flask
├── MongoDB
├── SQL
└── REST APIs

Engineering
├── Git
├── Linux
├── Testing
├── Debugging
└── Deployment

📚 LEARNING_PROTOCOL

fn learn(concept: Concept) -> Knowledge {

    study(concept);

    build_with(concept);

    break_it();

    debug();

    explain_it();

    rebuild();

    return understanding;
}

My preferred learning cycle:

LEARN
  ↓
BUILD
  ↓
BREAK
  ↓
DEBUG
  ↓
UNDERSTAND
  ↓
REBUILD
  ↓
DOCUMENT
  ↓
TEACH

The objective is not to memorize syntax.

The objective is to understand the system behind the syntax.


🧠 DEVELOPER_STATE

type DeveloperState = {
    curiosity: boolean;
    persistence: boolean;
    creativity: boolean;
    discipline: boolean;
    willingnessToBreakThings: boolean;
};

const brian: DeveloperState = {
    curiosity: true,
    persistence: true,
    creativity: true,
    discipline: true,
    willingnessToBreakThings: true
};

ROADMAP

                 ┌──────────────┐
                 │   LEARNING   │
                 └──────┬───────┘
                        ↓
                 ┌──────────────┐
                 │    BUILD     │
                 └──────┬───────┘
                        ↓
                 ┌──────────────┐
                 │    TEST      │
                 └──────┬───────┘
                        ↓
                 ┌──────────────┐
                 │   DEPLOY     │
                 └──────┬───────┘
                        ↓
                 ┌──────────────┐
                 │   IMPROVE    │
                 └──────┬───────┘
                        ↓
                 ┌──────────────┐
                 │    LEAD      │
                 └──────────────┘

Direction

  • Full-stack development
  • Business process automation
  • Data-driven applications
  • AI-assisted business systems
  • API development
  • Database architecture
  • Software engineering
  • Deployment & DevOps
  • Open-source contribution
  • Technical leadership

README.version

$ whoami

b1gg13

$ echo $MISSION

"Build with precision. Learn with purpose."

$ echo $STATUS

"Still building."

$ echo $NEXT

"Build something better."

b1gg13

Hungry to learn.
Curious enough to break things.
Persistent enough to rebuild them.

BUILD.
BREAK.
UNDERSTAND.
IMPROVE.
REPEAT.

📊 GitHub

Pinned Loading

  1. 100_daysOfGini 100_daysOfGini Public

    #100DaysOfCode

    Python

  2. data-python data-python Public

    Python

  3. wierdpoet wierdpoet Public

    my poetry site..