husayn gokal

11 · Life Plan

← Life Plan

Tasks

All aligned with the master plan. Things I'm getting done but not necessarily everyday. Finer than the Master Plan's artifact backlog. Every item here is something you can ask me about. Each varies in difficulty and length. All published here for accountability.

Current tasks

0%

0 of 1 done·0 points this week·how scoring works

Lifetime

  1. Developer Operating Systemopensoftware

    Repo A repository containing environment setup, Git workflow, terminal notes, project templates, README templates, debugging checklists, and personal development conventions.

    Done means:

    • GitHub repo exists
    • README explains the purpose
    • environment setup checklist exists
    • Git workflow notes exist
    • reusable README template exists
    • project creation checklist exists

    Priority: Very high Status: Active early

  2. Web Foundations Portfolioopensoftware

    A collection of HTML, CSS, and JavaScript projects built without frameworks.

    Projects may include:

    • personal homepage
    • responsive landing page
    • form-heavy page
    • JavaScript quiz app
    • local-storage habit tracker
    • API dashboard

    Done means:

    • at least 5 small projects exist
    • each has README notes
    • code is pushed to GitHub
    • at least one is deployed

    Priority: High

  3. TypeScript Practice Labopensoftware

    A repository for TypeScript fundamentals, typed utilities, API clients, type modeling, form validation, and small CLI tools.

    Done means:

    • typed functions and utilities exist
    • TypeScript notes exist
    • at least one small typed project exists
    • README explains what TypeScript helped with

    Priority: High

  4. React Component Libraryopensoftware

    A small reusable component system containing buttons, inputs, cards, modals, tables, layouts, navbars, alerts, and loading states.

    Done means:

    • components are implemented
    • examples exist
    • responsive behavior works
    • accessibility basics are considered
    • README documents usage

    Priority: High

  5. Full-Stack Study Planneropensoftware

    A practical app for planning study sessions, topics, revision cycles, weak areas, and exam preparation.

    Done means:

    • frontend exists
    • backend exists
    • database exists
    • authentication exists
    • study topics can be created
    • sessions can be tracked
    • app is deployed
    • README and case study exist

    Priority: Very high Reason: It directly helps your actual life.

  6. Admin Dashboard Projectopensoftware

    A polished dashboard with tables, filters, search, pagination, charts, user roles, and settings.

    Done means:

    • dashboard UI exists
    • mock or real data is displayed
    • filters and search work
    • charts exist
    • responsive layout works
    • README explains architecture

    Priority: Medium-high

  7. Clone Project Rebuiltopensoftware

    Independently One serious clone project such as Trello, Notion, GitHub Issues, Spotify, YouTube, or Airbnb-style booking.

    Done means:

    • not just tutorial copied
    • rebuilt independently
    • modified features added
    • deployed
    • README explains differences
    • case study exists

    Priority: Medium

  8. SaaS-Style Multi-Tenant Appopensoftware

    A more serious product-style app with users, workspaces, roles, settings, audit logs, and notifications.

    Done means:

    • organizations/workspaces exist
    • users have roles
    • permissions work
    • database schema is documented
    • tests exist
    • deployment exists
    • architecture document exists

    Priority: Later high

  9. Open-Source Developer Toolopensoftware

    A useful CLI, package, template, API client, or automation tool that others could realistically use.

    Done means:

    • install/use instructions exist
    • examples exist
    • license exists
    • issues are enabled
    • tests exist if appropriate
    • release version exists

    Priority: Medium

  10. Software Case Studyopensoftware

    A long-form writeup of one serious software project.

    It should cover:

    • problem
    • user
    • architecture
    • database
    • API
    • frontend
    • testing
    • deployment
    • failures
    • lessons learned

    Done means:

    • published on website or GitHub
    • links to repo/demo
    • includes diagrams/screenshots
    • honestly explains limitations

    Priority: High once one serious project exists