Developer in Development™
Developer tools · AI-assisted systems · Questionable experiments
Building things that usually begin with “let me just try this.”
Sometimes they even survive. 🫠
FarhaanOS v0.1 / profile edition — decorative version; still figuring out the release cycle.
Processes · Projects · The lab · Stack · Telemetry
> initializing developer...
> loading profile.................. [OK]
> attaching Claude Code............ [OK]
> attaching Codex.................. [OK]
> initializing questionable ideas.. [OK]
> sanity check..................... [SKIPPED]
> ready.
A decorative boot log. The only thing running here is the joke.
| Process | State |
|---|---|
| Think Before Code | 🟢 ACTIVE |
| Co-Dude | 🟣 EXPERIMENTAL |
| DSA | 📖 LEARNING |
| System design | 📖 LEARNING |
| Backend engineering | 🔎 EXPLORING |
| Sleep | 💤 SUSPENDED |
Exploring developer and agent tooling, with an ongoing interest in secure backend engineering. Process states are editorial, not live monitoring. Sleep has filed an appeal.
|
A better question beats a borrowed answer. Socratic agent skills for DSA practice, starring Quackrates. Guided questions and incremental hints protect productive struggle instead of handing over the finished solution.
|
Watch the code think out loud. A C-like execution visualizer: a lexer, recursive-descent parser, AST, and tree-walking interpreter turn source code into a step-by-step trace with live variable tracking. Runs as a browser simulation, without a native compiler.
|
|
From “here's the folder tree” to actual folders. Parses typed/ASCII directory trees into a structured representation and interactive view, then generates downloadable React or Node project scaffolds with real files.
|
Experiment in progress. An experimental local-first CLI that coordinates Codex as implementer and Claude Code as reviewer in isolated Git worktrees, then hands the diff, test results, and review findings to a human for the final call.
|
AI-assisted development is part of my workflow. These descriptions cover what the projects do; their repositories carry the implementation details.
Things produced after somebody said: let me just try this.
| Experiment | What escaped the notebook |
|---|---|
| English Terminal | Deterministic English-language CLI for filesystem operations and read-only GitHub API queries. |
| PromptRouter | Chrome extension that recommends an AI model based on your prompt. |
| VoyagerPulse | Deep-space telemetry simulation with error correction and bit-error-rate visualization. |
| Regex Playground | A small tool for experimenting with regex patterns. |
| Password Strength & Crack-Time Estimator | Password analysis and entropy-based brute-force time estimates; an educational experiment. |
| DevTool | JSON formatting and API request testing in one utility. |
Across projects and practice; proficiency is still under construction.
| Layer | Working set |
|---|---|
| Languages | JavaScript · Python · C++ · Java |
| Frameworks | React · FastAPI · Tailwind CSS |
| Infrastructure & tools | Git · GitHub · GitHub Actions · Vite · Monaco Editor · JSZip |
| AI-assisted development | ChatGPT · Claude Code · Codex · GitHub Copilot |
An illustrative workflow: I choose the tools, carry context between steps, and decide what goes into the repository. Tool roles vary by task.
Human / intent + decisions
|
v
Planning
ChatGPT / Claude Code / Codex
|
v
Implementation
Claude Code / Codex / Copilot
|
v
Review
Human + tests + AI feedback
|
v
Git repository
|
v
Software
|
+--> feedback --> Human
Manual handoffs, human judgment. The orchestration layer is mostly me switching tabs.
Contribution history & activity · Repositories · Public pull requests
Live records stay on GitHub, so this dashboard doesn't freeze a flattering number in time.
Expand optional contribution visualization
Generated by this repository's existing scheduled workflow; it may lag behind GitHub. Colors follow the generated asset's palette.
View contribution history directly on GitHub → · Check the generation workflow
[WARN] Still learning.
[WARN] Occasionally solves bugs by
creating different bugs.
[WARN] Small side projects may exceed
original scope.
[INFO] Stack Overflow remains part
of the architecture.
[INFO] Most systems eventually compile.
farhaan@github:~$ exit
Session closed. Curiosity persists.
I debug code with hope, snacks, and occasional emotional damage.