Coder Legion - Recent posts tagged edtech

Every Punjab Textbook, Online and Free: How I Put 251 Books in Every Student's Pocket

Mon, 19 Oct 2026 09:14:22 +0000

Every Punjab Textbook, Online and Free: How I Put 251 Books in Every Student's Pocket

This week I finished something I'd been dreaming about for years: the entire Punjab textbooks online library is now live on my website — 251 books, every class from pre-primary to 12th grade, free for every student, teacher, and parent in Pakistan to read, download, and learn from.

I'm a head teacher at a government primary school in Yazman, Punjab. For eight years I've watched kids walk to school without a single textbook in their bag — not because they're careless, but because books get lost, torn, shared between three siblings, or were never issued at all. But their parents almost always have a smartphone. So I asked myself a simple question: if the phone is already in the house, why isn't the textbook?

The answer is now my free Punjab textbooks library. Here's the full story — why raw PDFs were never enough, what I built instead, and what I learned digitizing 251 books as a teacher who codes at night.

Why Reading Punjab Textbooks Online Needed a Real Library

The official PDFs already existed. The Punjab Curriculum and Textbook Board's E&SE page (PECTAA) hosts them on Google Drive. So why did I spend weeks building a library around them?

Because "the PDF exists somewhere" and "a student can actually read it" are two very different things. Here's what raw textbook PDFs look like in practice:

No navigation. A 200-page scanned PDF has no table of contents. Finding Chapter 3 of Science means scrolling past 60 pages of blurry scans on a 6-inch screen.
Brutal file sizes. Some of these PDFs are 100MB+. On mobile data in a village, that download dies halfway — twice.
No discoverability. The board's Drive folders are organized for bureaucrats, not for a Class 7 student looking for "Waqfiyat-e-Aama."
No learning layer. A PDF is a photocopy. Nobody asks questions about a photocopy, nobody tests you on it, nobody tells you the tricky part of Chapter 4.

I didn't want a download dump. I wanted a library — the kind of page I'd send a parent on WhatsApp and know they'd figure it out in ten seconds. So that's what I built: the Punjab textbooks library at rehmanahmad.com/textbooks.

Building the Punjab Textbooks Online Library

Thirteen grade levels. 251 books. Every single book page carries more than a download button — it carries everything a student needs to actually study the book:

Real chapter tables of contents. I typed out the chapter lists for every book from the official PDFs — including scanned ones where I had to read the fehrist (table of contents) page visually. Open the Class 8 History book and you see all 5 chapters listed, clickable, in seconds.

The "Online Parho" reader. Instead of forcing a 150MB download, each book opens in a continuous-scroll reader right in the browser: lazy page rendering (a 200-page book loads like a webpage, not like a freight train), zoom for small text, go-to-page, and fullscreen mode that turns any classroom projector into a smart board.

A chapter quiz game on every book. Five multiple-choice questions, instant score, one-tap restart. I built it because my students beg to try again when they miss two — and "begging to restudy" is the closest thing to magic a teacher gets.

Teacher tips and FAQs. Every page has practical notes written from real classroom experience — which chapters trip students up, how to pace them — plus FAQs with proper search-engine markup so parents googling "Class 9 Biology chapters" actually land on the right page.

Here's the full rollout, all verified live this week:

Grade	Books
Pre-primary	4
Class 1–2	7 each
Class 3–5	7, 8, 8
Class 6–8	19, 21, 20
Class 9–10	55, 47
Class 11–12	20, 28

Class 9 alone is 55 books — core subjects plus the technical stream. For 11th and 12th, the official PECTAA page doesn't list books at all, so I sourced them from official PCTB mirrors and ran every file through the same verification pipeline: official list match, real chapter extraction, cover art, build, and a live check before it counted as done.

How to Read Punjab Textbooks Online: A 3-Step Walkthrough

Using it is deliberately boring — three taps and you're reading:

Pick your class. Open rehmanahmad.com/textbooks and tap your class. Pre-primary through 12th, all on one hub page.
Pick your book. Every class page shows each book with its cover, subject, and medium (English/Urdu). Tap one — say Class 10 Biology — and you get the full chapter list, teacher tips, and FAQs.
Read, quiz, or download. Read in the Online Parho reader (works on any phone browser, no app needed), play the chapter quiz after the lesson, or grab the official PDF download for offline study.

That's the whole pitch. No login, no paywall, no app install — because in my school, "create an account first" is where usage goes to die.

5 Lessons From Digitizing 251 Textbooks

1. The table of contents matters more than the PDF. Nobody on mobile data downloads a 150MB file to find Chapter 3. The single most-used feature of the whole library is the chapter list. Navigation is the product.

2. Mobile-first isn't a slogan — it's the only device that exists. My students don't have laptops. Every design decision assumed a cracked-screen Android phone on 4G: lazy rendering, compressed cover thumbnails, no heavy JavaScript frameworks on the reader.

3. Quizzes turn reading into a game. I added the 5-question quiz as a nice extra. It became the headline feature. Kids who would never "revise Chapter 4" will happily play "the Chapter 4 game" four times to beat their score. Gamification works when it's five minutes and zero setup.

4. Use official sources only — and say so. Every book is matched against the official board lists, with attribution. When the official page had gaps (Classes 11–12), I used official PCTB mirrors rather than random uploads, and I say that openly on the site. In education, trust is the whole currency.

5. No thin pages, ever. My rule for everything I publish: a page with a download button and nothing else helps nobody. Every book page carries real, original content — chapter lists, teacher tips, FAQs. A library of 251 stubs would have been faster to build and worthless to use.

The 5-Minute Classroom Checklist

If you're a teacher, here's exactly how to use the library in class this week:

[ ] Open your class page on the classroom tablet or projector-connected phone
[ ] Open the book's Online Parho reader in fullscreen — instant smart board
[ ] Use zoom on diagrams and maps instead of squinting at a printed copy
[ ] After the lesson, run the chapter quiz on the big screen — let the class vote on answers
[ ] Share the book's link in the parents' WhatsApp group so kids can re-read at home

And a side note for the computer-lab side of school life: for the Windows tools my lab runs on — PDF readers, document tools, classroom utilities — I grab verified free software from filecobra.com, the free-software download directory I built and run with hash-and-signature verification on every file. Same philosophy as the library: free, safe, no junk.

What's Next: Sindh, Then the Rest of the Country

Punjab was Phase 1. Phase 2 is Sindh — the STBB board's own ebook portal already hosts 194+ books from ECCE through Class 12 in Sindhi, Urdu, and English, so the groundwork exists. Balochistan comes after that. The goal is simple and, honestly, a little stubborn: every textbook in Pakistan, online, free, readable on the cheapest phone in the village.

If you're a teacher, a parent, or a student: bookmark the library and share it with one person who needs it. That's how this grows.

And a question for you: which board should I digitize next — and what's the one feature that would make your students actually open their books? I read every comment. Teacher by day, developer by night — this is what the nights are for.

Building Open-Source Education Infrastructure for African History and the African Diaspora

Wed, 26 Aug 2026 21:28:19 +0000

When people hear "education platform," they usually think about another Learning Management System.

EchoEd isn't trying to become another LMS.

It's an attempt to build open-source educational infrastructure centered on teaching African history and the histories of the African diaspora—built transparently, collaboratively, and alongside the communities it hopes to serve.

Today, I'm opening EchoEd for early community review, and I wanted to share why I'm building it, what exists today, and where I'd love help from educators and developers.

Why EchoEd Exists

History shapes identity.

It influences how we see ourselves, how we understand the world, and how future generations understand the people who came before them.

While there are many excellent educators and historians doing incredible work, access to high-quality, culturally grounded educational resources is still uneven. Many schools, homeschool families, and community organizations are looking for engaging, trustworthy ways to teach African history and the histories of the African diaspora.

I believe open source can help.

Open-source software has transformed how we build technology. It enables collaboration across organizations, countries, and backgrounds. It allows communities to improve systems together instead of relying on a single vendor or institution.

I believe educational infrastructure deserves the same approach.

Instead of building behind closed doors and asking educators to adapt later, I want EchoEd to be shaped by educators, historians, developers, accessibility advocates, and community organizations from the beginning.

Because trust should come before scale.

What Exists Today

EchoEd is still early, but it's no longer just an idea.

Today the project includes a working K–5 demonstration with:

Student learning experiences
Teacher workflows
Administrative experiences
Public documentation
Contributor onboarding documentation
Open-source contribution guidance

The goal wasn't to build every feature before inviting people in.

The goal was to build enough that meaningful conversations could begin.

What Phase 1 Prepared

Before inviting contributors, I wanted to make sure the project felt welcoming and transparent.

Phase 1 focused on preparing EchoEd for open-source collaboration rather than adding new product features.

That work included:

A significantly improved README
Contributor documentation
A Code of Conduct
Architecture documentation
Security guidance
Public demo documentation
Community trust documentation
Outreach readiness guidance
GitHub issue templates
Pull request templates
A public roadmap

These aren't the most exciting features to build.

But they're some of the most important if you want people to feel confident contributing to a project.

Good open-source communities don't happen by accident. They require intentional documentation, clear expectations, and respectful collaboration.

What Phase 2 Needs

Now the focus shifts from preparation to learning.

EchoEd doesn't need hundreds of contributors tomorrow.

It needs thoughtful feedback from people with different expertise.

Right now, the project would benefit most from:

Educator feedback

I'd love educators to walk through a learning experience and answer questions like:

Does this feel intuitive?
Would students understand the flow?
What's missing?
What classroom realities aren't being considered?

Developer contributors

There are opportunities across the stack, including:

Documentation improvements
Frontend development
Backend enhancements
Testing
Demo reliability
Accessibility improvements
Developer experience

Whether you've contributed to open source for years or you're looking for your first contribution, there's room to help.

Accessibility review

Educational software should be usable by everyone.

Improving keyboard navigation, screen reader support, semantic HTML, color contrast, and overall usability is an area where community expertise can make a real difference.

Historical review

Perhaps the most important area of all.

I'm looking for historians, educators, and community members who can help strengthen:

historical framing
source quality
representation
accuracy
balance of perspectives

Technology can accelerate learning.

But it should never replace careful historical scholarship.

How Developers Can Help

Not every contribution requires writing thousands of lines of code.

You could help by:

Improving documentation
Fixing UI issues
Building frontend features
Improving backend services
Writing tests
Improving demo reliability
Reviewing accessibility
Improving developer onboarding
Refining the architecture

Some of the highest-impact contributions to open source aren't glamorous—they simply make it easier for the next person to contribute.

How Educators Can Help

If you're an educator, I'm not asking you to volunteer countless hours.

Even reviewing one lesson or one learner journey can provide insights that fundamentally improve the project.

Helpful feedback might include:

Classroom usability
Age appropriateness
Instructional flow
Historical framing
Source recommendations
Topics that deserve greater attention

Your expertise is valuable, and I want EchoEd to reflect that by listening first.

Looking Ahead

This project has no marketing budget.

There isn't a large team behind it.

Right now, EchoEd is growing through conversations, thoughtful feedback, and people who believe education can be built more openly.

My hope is that over time, EchoEd becomes more than a software project.

I hope it becomes a community of educators, historians, developers, students, and organizations working together to expand access to meaningful, evidence-based learning about African history and the histories of the African diaspora.

If You're Interested

If any part of this resonates with you, I'd love for you to get involved in whatever way feels appropriate.

You can:

Explore the demo
Read through the documentation
Open a GitHub issue
Suggest improvements
Contribute code
Review historical framing
Share the project with someone who might have helpful expertise

Every thoughtful conversation makes the project stronger.

Because building educational technology isn't just about writing software.

It's about building trust.

And I believe the best way to build trust is to build together.

Lean AI Architecture: SymPy Verification & Vector Search

Tue, 25 Aug 2026 03:02:42 +0000

I'm a Mechatronics Engineering student who just shipped an AI academic platform for Nigerian university students. This is the technical breakdown of how it's built.

THE ARCHITECTURE DECISIONS

When you're building for Nigeria with zero funding, you can't make the same architectural decisions as well-funded startups. Every choice matters because every API call costs money you don't have.

Here's how I built this.

SEMANTIC SEARCH WITHOUT BREAKING THE BANK

The core problem: A student uploads 500MB of course materials. They ask a question. I need to find the relevant sections instantly without:

Calling the entire corpus through Claude/GPT-4 (prohibitively expensive)
Using expensive vector search services (Pinecone costs $$)
Processing the same documents repeatedly (waste)

The solution: Local vector embeddings + Qdrant (self-hosted).

Architecture:

Student uploads materials
    ↓
Convert to chunks (1024 tokens, 200-token overlap)
    ↓
Generate embeddings (using nomic-embed-text, free via Ollama on a cheap VPS)
    ↓
Store in Qdrant (lightweight, self-hosted, ~2GB RAM for millions of vectors)
    ↓
On query: embed the question, cosine-similarity search, retrieve top-K chunks
    ↓
Pass only relevant chunks to Claude (not the entire corpus)
    ↓
Response generated with context

Why this works:

Embeddings are done once, offline
Queries are lightning-fast (Qdrant is optimized for this)
I'm not paying per-token for irrelevant material processing
Running Ollama on a cheap VPS (₦15k/month) is infinitely cheaper than Pinecone's subscription

Real numbers:

Average query: 50 tokens → Claude call
Without vector search: 5000 tokens → 100x more expensive
Annual saving: enough to sustain the infrastructure

VERIFICATION PIPELINE: NEVER TRUST THE MODEL

Math hallucinations will make students fail exams. This can't happen.

Here's the verification flow:

def generate_and_verify_answer(question, context):
    for attempt in range(3):
        answer = generate_answer_with_claude(question, context)
        
        if contains_math(answer):
            # Extract LaTeX expressions
            expressions = extract_latex(answer)
            
            # Verify each with SymPy
            for expr in expressions:
                try:
                    symbolic_result = sympy.simplify(expr)
                    # Also numerically evaluate
                    numeric_check = float(symbolic_result)
                    
                    # If this passes, mark as verified
                    answer = mark_as_verified(answer, expr)
                    
                except Exception as e:
                    # Math is wrong, log it, try again
                    log_verification_failure(expr, e)
                    answer = None
                    break
        
        if answer and answer_passes_quality_check(answer):
            return answer
        
        # If we got here, answer failed verification
        # Regenerate with explicit instruction to fix it
        add_to_context("Previous attempt was mathematically incorrect. Recalculate.")
    
    # After 3 failures, flag for human review
    return flag_for_human_review(question, context)

The workflow:

Generate answer with Claude (using system prompt emphasizing accuracy)
Extract all mathematical expressions
Verify with SymPy (both symbolic and numeric evaluation)
If verification fails, regenerate with error context
Retry up to 3 times
If still failing, queue for human review

Cost optimization:

Only math-heavy courses run full verification
Lightweight semantic similarity checks for straight recall questions
Caching verified answers (if Question A and Question B are semantically similar, reuse the verified response)

This prevents hallucinations without tripling my API costs.

OFFLINE-FIRST PWA: WORKING ON ₦40K PHONES

Nigeria's internet is unreliable. Many students use cheap Android phones. I can't require:

Constant connectivity
Large app downloads (uses data they have to pay for)
Installation from Play Store (requires Google Play account verification that many students lack)

Solution: Progressive Web App (PWA) with service workers and IndexedDB.

Tech stack:

Frontend: React + Vite (small bundle size is critical)
State management: Zustand (lighter than Redux)
Offline storage: IndexedDB + Dexie.js wrapper
Sync: Custom sync engine (similar to Firestore's approach, but local-first)
Service Workers: Cache-first for static assets, network-first for API calls

How it works:

// Service worker: cache static assets aggressively
self.addEventListener('install', (event) => {
  event.waitUntil(
    caches.open('v1').then((cache) => {
      return cache.addAll([
        '/',
        '/index.html',
        '/styles.css',
        '/app.js',
        // Core UI assets only
      ]);
    })
  );
});

// On fetch: serve from cache first, update in background
self.addEventListener('fetch', (event) => {
  if (event.request.method === 'GET') {
    event.respondWith(
      caches.open('v1').then((cache) => {
        return cache.match(event.request).then((response) => {
          // Return cached version immediately
          const fetchPromise = fetch(event.request).then((networkResponse) => {
            // But also fetch fresh version and cache it
            cache.put(event.request, networkResponse.clone());
            return networkResponse;
          });
          
          return response || fetchPromise;
        });
      })
    );
  }
});

For data:

// IndexedDB for course materials and past answers
const db = new Dexie('UniUI');
db.version(1).stores({
  courses: '++id, userId',
  courseContent: '++id, courseId', // Stores embeddings locally
  answers: '++id, courseId, timestamp',
  syncQueue: '++id' // Queue API calls when offline
});

// When offline, queue the request
async function askQuestion(question, courseId) {
  if (!navigator.onLine) {
    // Store in sync queue
    await db.syncQueue.add({
      type: 'ask_question',
      question,
      courseId,
      timestamp: Date.now()
    });
    
    // Show locally cached similar answers
    return db.answers
      .where('courseId').equals(courseId)
      .toArray();
  }
  
  // Online: fetch new answer
  return callAPI('/api/ask', { question, courseId });
}

// Sync when connection returns
window.addEventListener('online', async () => {
  const queue = await db.syncQueue.toArray();
  for (const item of queue) {
    await processQueueItem(item);
    await db.syncQueue.delete(item.id);
  }
});

Results:

Initial load: ~2.5MB (heavily gzipped)
Works completely offline after first visit
Syncs automatically when connection returns
Runs on phones with 512MB RAM (real Android phones in Nigeria)
Zero dependency on Play Store

PAYMENT INTEGRATION: LOCAL METHODS FIRST

International payment processors (Stripe, PayPal) don't serve Nigeria well. Most students don't have international cards.

Solution: Paystack (Nigerian payment processor).

Integration:

from paystack import Paystack

paystack = Paystack(secret_key=settings.PAYSTACK_SECRET)

# Plan-based billing
@app.post('/api/subscribe')
async def subscribe(user_id: str, plan: str, email: str):
    plan_amount_kobo = {
        'basic': 50000,      # ₦500
        'pro': 200000,       # ₦2,000
        'premium': 500000    # ₦5,000
    }[plan]
    
    # Initialize payment
    response = paystack.transaction.initialize(
        email=email,
        amount=plan_amount_kobo,
        metadata={
            'user_id': user_id,
            'plan': plan,
            'usage_type': 'subscription'
        }
    )
    
    # Store pending transaction
    db.pending_transactions.insert({
        'user_id': user_id,
        'reference': response['data']['reference'],
        'plan': plan,
        'status': 'pending'
    })
    
    return {'auth_url': response['data']['authorization_url']}

# Webhook for payment confirmation
@app.post('/webhooks/paystack')
async def verify_payment(request: Request):
    signature = request.headers.get('x-paystack-signature')
    
    # Verify webhook is from Paystack
    body = await request.body()
    computed_sig = hmac.new(
        settings.PAYSTACK_SECRET.encode(),
        body,
        hashlib.sha512
    ).hexdigest()
    
    if signature != computed_sig:
        return {'error': 'invalid signature'}, 401
    
    data = await request.json()
    
    if data['event'] == 'charge.success':
        reference = data['data']['reference']
        
        # Verify transaction with Paystack
        payment = paystack.transaction.verify(reference)
        
        if payment['data']['status'] == 'success':
            # Activate subscription
            transaction = db.pending_transactions.find_one(
                {'reference': reference}
            )
            
            user_id = transaction['user_id']
            plan = transaction['plan']
            
            db.subscriptions.insert({
                'user_id': user_id,
                'plan': plan,
                'started': datetime.now(),
                'expires': datetime.now() + timedelta(days=30),
                'paystack_customer_code': payment['data']['customer']['customer_code']
            })
            
            # Clean up
            db.pending_transactions.delete_one({'reference': reference})
    
    return {'status': 'ok'}

Features:

Bank transfer support (for students without cards)
Card payments (Visa, Mastercard, Verve)
Recurring billing for subscriptions
Chargebacks handled by Paystack
No international payment complexity

INFRASTRUCTURE: BUILDING LEAN

Since I have zero funding, every infrastructure decision is about cost.

Stack:

Backend: FastAPI on Railway or Render (free tier, then ₦5k/month)
Database: PostgreSQL (free tier Render or DigitalOcean)
Vector DB: Qdrant (self-hosted on same server as backend)
Embeddings: Ollama running locally (one-time setup, no recurring cost)
LLM: Claude API (pay per token, ~₦0.003 per response)
File storage: Cloudflare R2 (₦0.015/GB, rivals S3)
Frontend hosting: Vercel (free tier)
Monitoring: Datadog free tier or custom dashboards

Monthly cost breakdown:

Server: ₦5,000-₦10,000
Database: ₦0-₦5,000 (free tier covers 5GB, very few large DBs)
LLM API: ₦50,000-₦100,000 (depends on usage)
Storage: ₦1,000-₦5,000
Domain + SSL: ₦0 (free Let's Encrypt)

Total: ₦56,000-₦120,000 per month

At ₦500 per user, I break even after 112-240 paying users. I have over 1,000 early signups.

AI BOTS: AUTOMATION TO SCALE SOLO

I can't hire a team. So I built AI bots to handle operations.

Tessy (Infrastructure bot):

Monitors server health every 5 minutes
Alerts via Telegram if CPU > 80%, RAM > 90%, disk > 85%
Auto-generates daily infrastructure reports
Logs analysis with Claude (detects patterns in failures)

import anthropic

async def analyze_logs(logs: str):
    client = anthropic.Anthropic()
    
    response = client.messages.create(
        model="claude-opus-4-1",
        max_tokens=1024,
        messages=[
            {
                "role": "user",
                "content": f"""Analyze these logs for patterns, anomalies, or issues:
                
{logs}

Specifically look for:
1. Error spikes
2. Unusual patterns
3. Performance degradation
4. Security concerns
5. Recommendations

Be concise."""
            }
        ]
    )
    
    return response.content[0].text

Treasure (Support bot):

Responds to support emails with Sendgrid
Categorizes issues (bug, feature request, billing, etc.)
Generates responses for 70% of common issues
Escalates complex issues to me with context

Three others:

Content generator (creates study materials)
Analytics (generates daily growth reports)
Morning briefing bot (sends me a 2-minute summary every morning)

This costs me: $0. They run on the same server.

WHAT'S NEXT (TECHNICALLY)

Wolfram Alpha integration – For advanced math/science
Multimodal support – Accept handwritten notes, images, videos
Real-time collaboration – Study with classmates simultaneously
Model fine-tuning – Train Claude on top 1000 FUTO courses for better specificity
Podcasts – Auto-generate audio summaries of materials

THE PHILOSOPHY

Every technical decision serves one goal: make quality education accessible to a student on a ₦40,000 phone with ₦500/month.

That constraint forces good engineering:

Caching instead of recomputing
Local-first instead of cloud-first
Verification instead of hope
Free tools instead of premium services
Boring, reliable tech instead of shiny new frameworks

This is infrastructure engineering. It should be invisible.

Uni UI is live at app.uniui.com.ng.

If you're building for Africa, building lean, or wrestling with verification in AI systems, let's chat.

The future of Nigerian edtech is being built right now. And it's built on pragmatic engineering.

Uni UI – Your Semester, Supercharged.

Naija Learn-AI

Tue, 07 Jul 2026 17:36:45 +0000

🎓 An AI tutor that speaks different languages.
Most AI tutoring tools are built as if every student learns in English and thinks in English. That's not the reality for a huge number of Nigerian university and STEM students, so I built NaijaLearn-AI to close that gap.

It's a powered multilingual AI tutor supporting five languages, a combination I haven't seen any other tutoring app fully address. The idea is simple: meet students in the language they think in, and the concepts land faster.
This one comes from a simple observation, and I think simple observations, taken seriously, are where a lot of the best products come from.
🔗 Try it: https://naijalearn-ai.netlify.app

It's open source too. 👇
🔗 https://github.com/JulietChinenyeDuru/NaijaLearn-AI
Feel free to fork it and build on it, and if you find it useful, a star ⭐ on the repo goes a long way in helping others discover it.

The Time-Reclamation Engine: How Two Students Are Building an Agentic Learning Incubator for Africa

Sat, 25 Apr 2026 07:43:28 +0000

We Just Watched the Future Get Announced. Now We're Building It.
Honestly? Watching the announcements coming out of Google Cloud Next '26 felt like someone finally put words to the thing we've been trying to build for months.
Agentic technology is revolutionizing how we work and the transformation is accelerating. Google And sitting here as two second-year students in Kenya, we aren't just watching that transformation happen from the sidelines. We are trying to bring it somewhere it hasn't fully arrived yet: the university student's daily life.
The conversation at Next '26 isn't about whether AI can do things anymore. It's about building systems where AI actively works, decomposing goals, coordinating tasks, delivering real outcomes. When we heard that framing, we looked at each other and thought, that's exactly what students need. Not another chatbot. Not another content platform. An agentic system that works for you while you're busy being a student.
That's Octal Foundry.

The Hidden Hours Problem
Here's something nobody really talks about.
The average university student has somewhere between 2 and 4 hours of fragmented free time every single day. Time between lectures. The gap before your next class. The hour after dinner before you convince yourself to sleep. It's not a long stretch of focused time. It's scattered, unpredictable, and easy to lose to your phone.
But here's the thing: those hidden hours, added up across a semester, represent an enormous amount of untapped potential. That time could be career capital. It could be real, progressive skill-building toward a specific goal. Instead, for most students, it just disappears.
That's not a laziness problem. It's a structure problem.
When you have 45 minutes between classes and you want to learn something useful, the barrier isn't motivation. The barrier is that opening YouTube or Google means facing an ocean of content with no clear starting point. By the time you've figured out what to watch next, your 45 minutes is gone. Tutorial hell doesn't just trap people in long sessions. It kills the small windows too.
Octal Foundry is built specifically for those hidden hours. We call it what it is: a time-reclamation engine.

What We're Actually Building
Octal Foundry is an Agentic Learning Incubator. And the feature that sits at the heart of the MVP is something we think changes everything.
A student uploads their semester timetable.
That's the starting point. Not a quiz. Not a lengthy onboarding form. Just the timetable they already have. Our AI analyzes it, reads the existing structure of their academic week, and identifies the white spaces. The gaps between lectures. The free periods. The windows that currently exist but aren't being used for anything intentional.
That's where the work begins.
Once the white spaces are identified, the student describes their future. Where they want to go. What kind of career they're building toward. What they want to be capable of doing that they can't do yet. From that input, Octal Foundry's agents generate a personalized roadmap and do something we think is genuinely exciting: they give the student back an updated timetable.
Not a replacement timetable. A hybrid one.
The original academic schedule stays exactly as it is. But now the white spaces are filled. Every gap has a purpose. Every free hour has a lesson. The student gets a single document that shows them their full week, their university commitments and their personal learning journey, sitting side by side, already calibrated to fit together.
This is what it looks like in practice.
A Computer Science student wants to learn data science. They upload their timetable. Octal Foundry finds a one-hour gap on Tuesday afternoon and slots in a focused lesson on Python variables. Not a playlist. Not a course to browse through. One concept, one hour, structured to be completable in exactly the time available. The next gap gets the next concept. The roadmap moves forward one white space at a time.
Now think about a medical student who wants to align their career with AI. Maybe they've been reading about what's happening in healthcare and they want to understand where they fit in that future. They upload their timetable, they describe that vision, and Octal Foundry finds their available windows and builds toward it. A one-hour gap becomes a focused session on AI ethics in medicine. Not a vague suggestion to "look into it." A structured, scoped lesson designed to fit the time they actually have and move them meaningfully forward on a topic that matters for the career they want.
In the agentic era, a single intent triggers a chain reaction where a primary agent decomposes goals into tasks for specialised sub-agents that collaborate to deliver real outcomes. Google Cloud That is the architecture Google is scaling across enterprise workflows right now. Octal Foundry takes that same logic and points it at the student's week, filling it with purpose, one white space at a time.

No More Searching. The Right Video Finds You.
Here is one of the things we are most excited about in the MVP.
We are integrating YouTube as our primary content source, powered by LangChain. This is a deliberate choice and it matters more than it might sound.
Every student already knows YouTube exists. The problem has never been the content. The problem is the search. The decision fatigue of typing a query, scanning thumbnails, reading descriptions, clicking the wrong video, going back, trying again, and losing 20 minutes before a single minute of actual learning happens. That process is exhausting and it eats the hidden hours before the student even starts.
Octal Foundry removes that entirely.
When a student opens their hybrid timetable and sees that Tuesday's free hour is dedicated to Python variables, the platform doesn't point them toward a search bar. It surfaces the specific YouTube video that matches that lesson, calibrated to the duration of the window they have. LangChain enables us to intelligently match the concept being learned to the most relevant, appropriately scoped video available. The student opens the app, sees what they're learning, sees the video, and starts. That's it.
No searching. No second-guessing. No wasted time deciding.
The content was always out there. Octal Foundry makes sure the right piece of it is waiting for the student at exactly the right moment.

Learning That Has to Be Earned
Watching a video is not the same as learning something. We know this because we've done it ourselves, nodded along to a tutorial, felt like we understood, and then sat down to build something and realized we had retained almost nothing.
That's why Octal Foundry builds accountability directly into the structure.
Every week comes with a task. Not a suggestion. A task. For tech students, this might be a Python challenge, a small project, a function to write and test. When the student is ready to submit, they paste their GitHub URL. The platform receives it, verifies the submission, and unlocks Week 2. No submission, no progression. The learning path stays locked until the work is done.
This isn't about being harsh. It's about being honest. Real learning requires doing, and a system that lets students passively move through content without demonstrating understanding isn't actually helping them. Octal Foundry is designed to produce students who can actually build things, not students who have watched a lot of videos about building things.
The weekly task structure also means that by the time a student reaches the end of the semester, they haven't just followed a roadmap. They have a body of work. Real submissions. Real projects. Things they built during the hidden hours that used to disappear.
And at the end of it all, there is a capstone project. A final challenge that brings together everything the student has learned across the semester. Complete it and earn a certificate. Not a participation certificate. A certificate that represents a working project, submitted evidence, and a full semester of structured, intentional learning.
The holidays are not a break from this. They are dedicated project time, a longer runway for deeper work that the semester's fragmented hours couldn't fully accommodate.
The Future of Octal Foundry
What we are building for the MVP is the foundation. But the vision goes further and we want to be honest about where we intend to take this.
The long-term future of Octal Foundry has three pillars that we are genuinely excited about.
The first is an African-based AI model. Right now we are building on top of existing infrastructure, which is the right call for an MVP. But our vision is to eventually build and train our own model, one that is rooted in the African context, understands the realities of students in emerging markets, and reflects the problems and opportunities that are most relevant to this continent. This isn't a distant dream. It's a deliberate direction.
The second is African-based projects. The tasks and capstone projects that students complete should not just be technically rigorous. They should be contextually relevant. We want the projects given to students to be grounded in African problems, African datasets, African realities. A student building a solution on Octal Foundry should be building something that connects to the world they actually live in and want to improve.
The third is smart contracts for verified achievement. This is where things get really interesting. We are exploring the integration of smart contracts into the submission and certification layer of Octal Foundry. The idea is that a student must submit a genuinely working solution to unlock the next week's content and earn their weekly badge. Not a placeholder. Not a half-finished attempt. A working solution, verified on-chain, that cannot be faked or skipped. The weekly badge becomes a piece of verifiable proof. The semester certificate becomes something with real, tamper-proof credibility. In a world where credentials are increasingly easy to inflate, we want Octal Foundry certificates to mean something concrete and provable.
The agentic logic at the core of this is intentionally domain-agnostic. We are starting with Computer Science and Mathematics students because they are our beta group and they give us sharp, immediate technical feedback. But the infrastructure doesn't stop there. The medical student example isn't hypothetical. Any high-rigor field where structured, progressive knowledge acquisition matters and where students are currently left to figure it out alone is a candidate for this system.
We aren't building an app. We are building infrastructure for structured knowledge. And the more we build it, the more convinced we become that this is genuinely a revolution.

How It Started: An Idea That Found Its People.
I started Octal Foundry as a personal initiative. As a 2nd-year Mathematics and Computer Science student at Maseno University, personally stuck in tutorial hell and watching the same happen to peers, the question became impossible to ignore: why doesn't an intelligent system exist that can just take all of this content and turn it into a structured path tailored to me?
The idea existed. What it needed was the right environment to grow.
That environment was the Guild Code Community.
Guild Code is not just another online group. It is a space where talented developers find each other, where real mentorship actually happens, and where people hold each other accountable to ship things that matter. The community is led by Mr. Kelvin Obote, a product designer, AI and ML researcher, developer and enthusiast who has built Guild Code into something genuinely rare: a place where ambition meets direction. Keeping the community alive and making everyone feel genuinely supported is Madam Ivy, the community manager whose presence has made a real difference to this team at every step.
Joining Guild Code didn't just give us a space. It accelerated everything.
It was inside that community that I met Grace Karume, a 2nd-year Mathematics and Computer Science student from JKUAT. When Grace heard the idea, she didn't just understand it. She immediately started thinking about how to build it. She joined as co-founder and Lead Developer, and from that moment the initiative stopped being a personal frustration and started becoming a real product.
The support from Mr. Kelvin Obote and Madam Ivy has been consistent, practical and genuinely encouraging. Having mentors who push you, believe in what you're building and show up when it matters is something a lot of student builders never get. We don't take that lightly.

The Team
Danson Githuka leads research and agentic architecture, focused on the logic layer: how a student's goal gets decomposed, how content gets mapped to skills, how white spaces get matched to the right lesson, how YouTube videos get surfaced through LangChain, and how the entire learning path gets sequenced into something a real person can actually follow in the time they have.
Grace Karume leads technical development, owning the architecture, the build process, and making sure everything the team ships is robust and scalable.
Together, Danson and Grace lead a distributed team of developers from both Maseno University and JKUAT. Two campuses. One team. All building the tools they wish they'd had when they started.

Why the Agentic Era Belongs to Students Too
Here's what strikes us about everything coming out of Next '26.
Nearly 75% of Google Cloud customers are now using AI products to power their businesses, and the agentic enterprise transformation is accelerating across every industry. Google The infrastructure for autonomous, goal-driven AI systems is being built at extraordinary scale. And almost all of the conversation is pointed at enterprises.
We think that's only half the story.
The same principles that make agentic systems powerful for businesses, breaking down complex goals, coordinating specialised agents, delivering structured outcomes, are exactly what students in emerging markets need. The student with ambition and internet access but no mentorship, no structured curriculum, and only 45 minutes between classes is not a niche use case. That student is everywhere. That student is us.
The pace of technological change since last year's Cloud Next has never been faster. Google That's as true for two second-year students in Kenya as it is for any enterprise customer. The tools that make this buildable now simply didn't exist two years ago. We are building Octal Foundry at exactly the right moment.
The Agentic Era isn't just a corporate trend. It's an infrastructure shift. And we intend to route some of that infrastructure toward the people who need it most.
Three Months to MVP
That's the target. Three months to put something real into the hands of real students.
Every decision the team makes comes back to one question: does this help a student convert their hidden hours into career capital faster? If yes, we build it. If not, we cut it.
We are those students. We know what it feels like to have the drive and not the structure. That's not a sad story. It's the clearest possible brief for a product.
Follow the Journey
If you're a student developer who has lost hours to tutorial hell and scattered content, this is being built for you.
If you're a medical student who wants to understand where AI fits in your future but doesn't know where to start, this is being built for you too.
If you believe the Agentic Era should reach further than the enterprise, follow what Octal Foundry is building.
We are two second-year students, a talented distributed team, a community that believed in us before we had anything to show, and a vision we are completely serious about.
The hidden hours are waiting. The white spaces are there. The right video is already on YouTube. The task is already written. The roadmap is already built.
All that's left is for the student to begin.
Let's build.

LearnOptima

Sun, 22 Feb 2026 00:50:46 +0000

The Story

I had 8 unfinished courses on my laptop.

I tried fixing this with AI. Spent 3-4 hours crafting the perfect prompt.

Got back a mountain of text.

Half hallucinated. Practice problems all wrong difficulty. I could read it, but couldn't apply it.

I was spending more time prompt engineering than learning.

Then I searched Twitter: "want to learn" "don't know where to start"

Found 50+ people saying the same thing.

Not "I quit courses." They couldn't even start.

Three patterns:

Decision paralysis - too many resources, no clear path
Tutorial hell - watch tutorials, can't build anything real
Knowledge gap - tutorials too basic OR too advanced, never just right

I asked them: "What do you want to BUILD?"

Suddenly clear:

"Build a portfolio website" (not "learn coding")
"Analyze sales data" (not "learn data analytics")

Specific output = clear path.

What LearnOptima Does

Asks three questions:

What do you want to ACHIEVE?
What do you already KNOW?
How much TIME do you have?

Builds a 30-day roadmap for YOUR situation.

Step-by-step. Not a text mountain.

Key Features

Any skill - coding, marketing, design, piano, languages, anything
Skips what you know - starts exactly where your gap is
Goal-oriented - "build X in 30 days" not "learn Y"
Adapts - performs well? Moves faster. Struggling? Slows down.
Spaced repetition - auto-schedules reviews based on memory science

How It Works

Step 1: Tell us your specific goal
Step 2: Quick knowledge assessment
Step 3: Set daily time commitment
Step 4: Get your personalized 30-day roadmap

Daily lessons. Clear next steps. No guessing.

Early Results

60 testers across programming, languages, business, creative skills.

Feedback: "I didn't realize how much time I wasted on basics I already knew. This just tells me where to start for MY situation."

First learning program I finished in 2 years.

Try It

Free tier: Create one 30-day roadmap for any skill. No credit card.

Test it with a real goal. See if it works for you.

Wait-list for early access to Mastery tier with special surprise discount for early birds.

Get Involved

Looking for early testers who:

Have unfinished courses
Know some stuff but not everything
Want to learn a specific skill

Try the free tier. Tell me what works and what doesn't.

Honest feedback > nice feedback.

I Analyzed 50+ "Where Do I Start" Posts on Twitter. Here's Why People Can't Even Begin Learning.

Tue, 17 Feb 2026 21:45:19 +0000

I searched Twitter for people talking about wanting to learn new skills. Not to sell them anything. Just to understand what's actually stopping them.

Here's what I found.

The Search

I typed these exact phrases into Twitter:

"want to learn" "don't know where to start"
"learning" "overwhelmed"
"tutorial hell"

Filtered for posts from the last month. English only.

Found 50+ posts from real people expressing the same frustration.

Not "I started a course and quit."

They couldn't even start.

Pattern 1: Decision Paralysis

Anonymous User 1: "I want to learn data analytics. I don't know where to start."

Anonymous User 2: "I want to take courses this year but honestly don't know what to learn or where to start."

Anonymous User 3: "So much I want to learn this year and I don't know where to start."

Same words. Different people. Over and over.

"I want to learn [skill]. I don't know where to start."

Not laziness. Paralysis.

Here's why it happens:

You decide you want to learn data analytics.

You Google it.

Results:

47,000 YouTube videos
500+ Udemy courses
200+ Reddit threads debating Python vs R
Blog posts saying "just start"
Other blog posts saying "don't start without a plan"

You spend 2 weeks researching which resource is "best."

Never actually start learning.

This is called choice overload. Too many options = no decision.

Barry Schwartz wrote a whole book about it in 2004 (The Paradox of Choice). The internet has made it 100x worse.

Pattern 2: Tutorial Hell

Anonymous User 4: "I want to learn coding but every time I try, I get lost. I never know where to start so I just look up YouTube tutorials. That always leads me to be even more confused and burnt out before I even started."

Anonymous User 5: "Tutorial hell is the biggest setback in a programmer's journey."

Anonymous User 6: "There's a huge difference between reading about code and shipping a product. Most get stuck in tutorial hell, watching endless videos."

Tutorial hell is a specific phenomenon:

Watch tutorial
Feel like you understand
Try to build something
Realize you have no idea what to do
Go back to watching tutorials

Repeat indefinitely.

Why it happens:

YouTube tutorials are designed for watch time, not learning outcomes.

You search "learn React."

Results:

15-hour complete course (starts from absolute zero)
30-minute crash course (assumes you're already advanced)
"Build a project" tutorial (assumes you know React basics)

You pick one. Watch for 2 hours. Realize it's the wrong level for you. Start over with a different one.

After 3 cycles: you're burnt out before any real learning happened.

Pattern 3: The Gap Between Knowing and Doing

This one was the most interesting.

Anonymous User 7: "I actually try to do that. But when I start building, I feel like I have no idea what to do. And when I watch a tutorial, it feels like 'I already know this.' That's the confusing part."

This person is stuck in no man's land.

When they watch tutorials: "I already know this." (Boring)
When they try to build: "I have no idea what to do." (Lost)

This is the gap most courses never address.

Courses assume you're either:

Complete beginner (need "What is a variable?")
Expert (can skip to advanced topics)

Nobody designs for the middle: "I understand the concept but can't apply it."

This is where most people actually are.

What Actually Works

I started replying to people asking: "What do you want to BUILD with [skill]?"

Every single time, they'd reply with clarity.

Anonymous User 8: "I want to build websites." (Previously: "want to learn coding")

Anonymous User 9: "I want to analyze customer data for my job." (Previously: "want to learn data analytics")

Anonymous User 10: "I want to play songs I love on piano." (Previously: "want to learn piano")

The shift from skill-oriented to output-oriented changes everything.

Vague: "Learn coding" = infinite resources, no direction

Specific: "Learn enough JavaScript to build a portfolio website" = clear 30-day path

Vague: "Learn data analytics" = paralysis

Specific: "Learn SQL and Excel to analyze my company's sales data" = obvious starting point

The Three Questions

After analyzing all 50+ posts, I realized successful learners answer three questions before starting:

1. What do I already know?

This eliminates wasting time on basics. If you already know JavaScript fundamentals, you don't need to watch "What is a variable?" for the 5th time.

2. What do I want to achieve?

Not "learn React." But "build a working e-commerce site."

This defines the endpoint. You know when you're done.

3. How much time do I have?

20 minutes/day requires different content structure than 2 hours/day.

Most platforms never ask these questions. They assume:

Everyone starts from zero
Everyone wants comprehensive mastery
Everyone has unlimited time

This is why 87% of online courses never get finished (Jordan, 2015).

Why I Built LearnOptima

After seeing this pattern 50+ times, I realized something.

People don't need another course platform.

They need a system that:

Asks what they already know (skips that)
Asks what they want to achieve (builds toward that)
Asks how much time they have (structures content accordingly)
Generates a roadmap for THAT specific situation

Not generic. Personalized.

So I built it.

Multiple AI models working together. Not just one ChatGPT prompt. One for assessment. One for content generation. One for quality control. One for spaced repetition scheduling.

Early Results

Testing with 60 people now across: programming, languages, business skills, creative fields. Someone's using it for guitar theory.

The common feedback: "I didn't realize how much time I was wasting trying to pick the perfect resource. I just needed someone to tell me where to start for MY situation."

Average completion rate so far: 73%.

Industry standard: 10-15%.

The Lesson

The internet has too much information, not too little.

The bottleneck in 2026 isn't access to knowledge.

It's knowing which knowledge matches YOUR:

Current level
Specific goal
Available time

People aren't failing because they lack discipline.

They're failing because they're using one-size-fits-all systems in a world where personalization is possible.

References:

Jordan, K. (2015). Massive open online course completion rates revisited. International Review of Research in Open and Distributed Learning, 16(3).

Teachfloor (2024). 100+ Mind-Blowing eLearning Statistics for 2025.

Schwartz, B. (2004). The Paradox of Choice: Why More Is Less. New York: Ecco.

If you've got unfinished courses on your laptop or you're stuck at "where do I start," I built LearnOptima for you.

Free tier: Create a 30-day roadmap for any skill. Test it with a real goal.

https://learnoptima.online

efIQo - Study more efficiently

Fri, 13 Feb 2026 16:17:39 +0000

As a student and learner that has been frustrated in time past for lacking a proper study technique, I wanted to build something that would help me study the way I want to study. I wanted to make my study sessions more engaging and practical, not just staring for minutes and hours into the abyss of a book or scribbling endlessly into a note.

I wanted to understand what I study and also retain as much as I can by the time I am done studying.

I built efIQo, a tool that learners can actively interact with while they study, with the first version of efIQo, learners can create flashcards and quizzes while they study.

What more? learners have access to a repository of flashcards and quizzes created by other learners on the platform. Apart from actively studying, there is an indirect form of peer learning where learners can learn and teach one another.

I integrated AI into the product, allowing learners to spin up flashcards from any topic and subject or from an uploaded document.

Join a vibrant community of learners today.

Confetto AI

Fri, 26 Dec 2025 12:09:54 +0000

Confetto is an AI interview simulator built for medical school admissions.

It lets applicants practice MMIs and traditional interviews in a realistic way. You choose the school and interview format, answer scenarios, get follow-up questions, and see feedback on how you did.

It’s useful when you don’t have access to coaches or want more reps between real interviews.

Get started: https://confetto.ai

Building Specialized AI Simulator for Healthcare Admissions

Fri, 26 Dec 2025 10:18:58 +0000

Most general-purpose AI tools for interview practice focus on broad conversation. They are great for getting comfortable with speaking aloud, but they often lack the specific evaluative frameworks required for high-stakes fields like medical or dental school admissions.

When we looked at the existing landscape for students, we noticed a common limitation: the feedback is often too general. For a student facing a Multiple Mini Interview (MMI) or a panel board, knowing they "spoke clearly" isn't enough. They need to know how their response aligns with the specific ethical and professional benchmarks that admissions committees actually use.

We built Confetto.ai to bridge this gap by focusing on a "simulator" model rather than a standard chat interface.

The System Logic

The goal was to move from simple Q&A to a structured assessment. Here is how the process works for the student:

Institutional Context: The platform allows students to select their target schools, such as UCSF, Mayo Clinic, or the University of Toronto. This is important because the "correct" approach to an interview can change based on a school’s specific mission and values.

Probing for Depth: In a real medical interview, the evaluator often asks follow-up questions to see how deep your reasoning goes. We’ve designed the AI to recognize when an answer is superficial and to ask adaptive follow-ups that challenge the student to expand on their ethical or critical thinking.

Linguistic Tracking: Beyond the content of the answer, the system monitors delivery metrics that are hard for a student to self-assess, specifically filler word frequency and pacing.

The Assessment Layer

The feedback is structured around the same rubrics used in professional admissions:

Score Benchmarking: Students receive a 100-point score across categories like Empathy, Ethical Reasoning, and Professionalism.

Actionable Refinement: Instead of just a summary, the system highlights where the logic in an answer might be weak and suggests ways to better incorporate personal experiences or clinical context.

The Bigger Picture

We see a lot of potential in moving away from broad AI assistants toward these highly vertical simulators. By focusing strictly on the nuances of healthcare admissions, we can provide the kind of specialized feedback that usually requires expensive, one-on-one human coaching.

The Two Problems Holding EdTech Back (and How We Can Fix Them)

Wed, 13 Aug 2025 11:17:28 +0000

AI is everywhere. It's in your phone, in your fridge, probably even in your toaster if you look hard enough. Unless you’re a monk meditating in the Himalayas (in which case, congratulations, you’ve achieved inner peace—skip this post), this tidal wave of change is heading straight for you.

And yet… in education, we’ve got a couple of problems that make me want to slam my head on the desk. Let’s talk about them.

The “Teaching About AI” Problem
Schools and EdTech companies love talking about AI. Oh, they’ll host webinars, write think-pieces, and even run expensive “AI literacy” courses. But are they actually using AI to teach? Nope. It’s like watching a cooking show where the chef just lectures you on salt while the stove stays cold.

And here’s the real kicker: surveys show around 58–74% of school teachers and 72% of EdTech trainers have never been trained to use AI. College faculty? Often the same story—training is patchy and inconsistent. That’s like hiring a swim coach who’s never been in the water.

Until teachers and platforms start using AI as a tool instead of treating it like an abstract theory, students are going to stay stuck in the slow lane.

The “We’ve Always Done It This Way” Problem
Even when educators do get AI training, resistance to change is sky-high—especially in schools, EdTech companies, and universities. Students can be hesitant too, usually for privacy or ethical reasons. The only group that seems less stubborn? Self-learners, who tend to be more open to new tools and ideas.

And honestly, I get the hesitation… but also, I don’t. If AI can help you master a topic in 30 minutes instead of three hours, why wouldn’t you take that deal?

The uncomfortable truth is that many EdTech platforms make money by keeping you on their site longer. A faster, better learning tool? That’s a business risk. No wonder some founders can’t stop pointing out AI’s flaws—it’s less about “protecting education” and more about “protecting revenue.”

The Solution? Self-Learning
You know who doesn’t resist change? Self-learners. They don’t care about “how it’s always been done.” They care about finding the fastest, smartest way to master a skill—and they’ll switch tools in a heartbeat if something better comes along.

That’s why we built GritWise—a personalised AI learning platform that doesn’t just dump content on you. It actually guides you, helping you learn with AI instead of just about it.

If you’re tired of slow, outdated learning and ready to take control, maybe it’s time to stop waiting for the system to change… and start changing your own approach.

Learn smarter, not longer.

Take back control of your learning:https://gritwise.in/

Introducing YAP: Speak. Earn. Repeat.

Sat, 09 Aug 2025 12:35:00 +0000

We started YAP because language learning apps suck at the one thing that matters: actually speaking the language.

If you've ever opened Duolingo for 100+ days straight but still froze during a real conversation, you're not alone. Flashcards and strange dialogues don’t prepare you for real-world speaking or even conversations.

YAP flips the model.

It’s the first learn-to-earn language app where users practice building conversational fluency and get rewarded with a token for speaking. We reward fluency for your effort and progress, not passive learning.

We’re a small team of four. If you’re learning a new language, interested in being rewarded with a token, or want something different than Duolingo or others, we’ll be sharing our journey: from design sprints to smart contract fails, and everything in between.

Follow along. Or better, yap with us.

— Team YAP
www.goyap.ai

The Digital Classroom: What We’ve Gained—and What We’ve Lost

Fri, 11 Jul 2025 03:45:30 +0000

"Technology didn’t replace teachers—it redefined the classroom."
The pandemic fast-forwarded education’s digital transformation. In a matter of weeks, traditional chalk-and-talk classrooms turned into Zoom calls, virtual blackboards, and breakout rooms.

Now, years later, as hybrid learning becomes the new norm, it's time to ask: What did we truly gain—and what did we lose—in the process?

✅ What We Gained from the Digital Shift

Learning on Your Own Terms
Remote learning brought unmatched flexibility. No commute. Self-paced learning. Replayable lectures. According to a Harvard study, many students reported better time management and increased autonomy.
Increased Accessibility
EdTech opened doors for many who were left out of traditional systems. For example:

Neurodivergent learners could control sensory input.
Students with chronic illnesses could attend class remotely.
Working professionals could reskill after hours.

Global Classrooms
With platforms like Khan Academy, edX, and Coursera, anyone with an internet connection could learn from top universities. Education became borderless.

❌ What We Lost in the Process

Human Connection
Education is more than information—it's conversation, collaboration, and community. A Brookings report highlighted the emotional disconnect students felt during online learning.
The Digital Divide
While some gained access, many were left behind. Over 500 million students lacked devices or stable internet, according to UNESCO.
Teacher Burnout
Teachers wore multiple hats: educator, tech support, digital content creator. A McKinsey study revealed record burnout levels, leading to early retirements and attrition.

New Skills for a New Era

Digital Literacy: How to use LMS, troubleshoot tech, collaborate online.
Self-Regulation: Managing distractions and time in a remote world.
Blended Pedagogy: Teachers became content creators overnight—learning platforms, interactive tools, and even video editing!
Welcome to the Hybrid Era

Post-pandemic, many schools adopted hybrid models—a mix of in-person and digital learning.

Tools like:
Flipped Classrooms: Watch lessons at home, do activities in class.
AI Tutors: Tools like ChatGPT and Socratic offer instant assistance.
Collaborative Platforms: Notion, Miro, Google Classroom... the list keeps growing.
But hybrid learning must be intentional—not just digital band-aids on broken systems.

Summary: What to Keep & What to Fix

Keep ThisFix That
Flexible learning modesTeacher burnout
Personalized AI toolsLack of social learning
Access to global contentThe digital divide
Coming Soon: Daily JavaScript Coding Questions!

Starting next week, I’ll be launching a new daily series:
JavaScript Coding Questions for Interviews

Each post will feature:

A fresh coding challenge
Real-world interview relevance
Clean, optimized JavaScript solutions
Time/space complexity breakdowns
Bonus: DSA concepts made simple
Perfect for:
New grads | Job switchers | Self-taught devs

Stay tuned and hit Follow to get each challenge in your feed.

From side project to working product - the story behind efIQo

Wed, 02 Jul 2025 06:58:57 +0000

June 2, 2025.

Just a random Monday for most people, but not for me. It was a day I launched efIQo - a product I have been working on since the 1st of December, 2024.

efIQo is a study tool that allows users to create, share and learn with personalized flashcards and quizzes, it also doubles as a peer-learning platform where you can learn with flashcards and quizzes created by other learners.

I have launched a number of "side projects" in the past but efIQo felt so different, from the ideation to development to the beta version and the stable version. Every line of code, every thought process, every logic and everything between.

The whole idea for me on efIQo started as far back as 2022/2023, a bit before chatGPT burst on to the scene, as a freshman in uni, I wanted to build something that I could use as a study tool. Yeah, efIQo was born out of my personal need.

I had majority of the logic down already, some of the code I wrote back then in my friend's room still exists in the codebase to this day, but I could not transform it into a working product at the time. why? not only because I did not have enough skills but I was waiting for everything to be perfect, I wanted it to be the next big thing on the internet. poor me.

I suspended development for a while after that, I honed my craft and built a few more personal projects and with the little experience I had, I realized that learning is not just by tutorials, reading docs, and taking courses but by building real-world projects.

I went back to "ace it" (what efIQo was before rebranding), dusted the cobwebs, reviewed the existing code and got back to building. I used X (Twitter) as an accountability partner, sharing my progress along the way, building in public, such a thing.

I launched the beta version of efIQo, that version only had the flashcard creation feature, I later integrated the quiz feature, then the authentication feature, then the storage feature. I also shared my progress on peerlist, with my accountability partners, I just kept building bits and bobs, feature by feature, code by code.

With those features, I launched the efIQo 1.0, what could not be achieved about a year or two ago was done in 6 months. How? A change of mindset - I was waiting to build the next big thing that would shake the internet, rather, I just built something born out of my personal need because I could.

At the moment, I am currently working on integrating AI into efIQo, users will be able to create flashcards and quizzes by providing the course/subject and specific topic.

Some journey it has been.

The only way is up from here, till then, let us keep building.

want to level up your study game? sign up at https://efiqo-app.web.app