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.
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#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.
const languages = [
"Python",
"JavaScript",
"TypeScript",
"HTML",
"CSS",
"SQL",
"C"
];
console.log(languages);Frontend
├── HTML
├── CSS
├── JavaScript
├── TypeScript
├── React
└── Tailwind CSS
Backend
├── Python
├── Flask
├── Node.js
└── REST APIs
Databases
├── MongoDB
└── SQL
Tools
├── Git
├── GitHub
├── Linux
└── VS Code
fn currently_learning() -> &'static str {
"Rust"
}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 solutionA bug is not just something to remove. It is something to understand.
Projects being actively developed toward real-world use.
type ProjectStatus =
| "IN_PRODUCTION"
| "UNDER_UPDATE"
| "COMPLETED";
const productionProjects: ProjectStatus = "IN_PRODUCTION";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.
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
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
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
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
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
$ git status
modified:
EKPLUS Website
EKPLUS Management Tools
Insurance Tools
Water Management Tools
Business Automation ToolsThese projects have working foundations but are being continuously improved through:
UI improvements
↓
Feature expansion
↓
Database improvements
↓
Automation
↓
Testing
↓
Refactoring
↓
Deployment
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"
]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.
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)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
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.
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
}; ┌──────────────┐
│ LEARNING │
└──────┬───────┘
↓
┌──────────────┐
│ BUILD │
└──────┬───────┘
↓
┌──────────────┐
│ TEST │
└──────┬───────┘
↓
┌──────────────┐
│ DEPLOY │
└──────┬───────┘
↓
┌──────────────┐
│ IMPROVE │
└──────┬───────┘
↓
┌──────────────┐
│ LEAD │
└──────────────┘
- 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
$ whoami
b1gg13
$ echo $MISSION
"Build with precision. Learn with purpose."
$ echo $STATUS
"Still building."
$ echo $NEXT
"Build something better."Hungry to learn.
Curious enough to break things.
Persistent enough to rebuild them.
BUILD.
BREAK.
UNDERSTAND.
IMPROVE.
REPEAT.
