Projekte

Ausgewählte Arbeiten

Eine Auswahl von Projekten, die meinen technischen Schwerpunkt zeigen: Full-Stack-Anwendungen, Backend-Dienste und Entwicklertools.

k6boost

CLI tool for API performance testing that simplifies Grafana k6 workflows.

Case Study GitHub

k6boost is a Node.js CLI tool that wraps Grafana k6 and provides a developer-friendly interface for API performance testing. Configure endpoints through an interactive menu or CLI commands, run tests using predefined profiles (Smoke, Load, Stress, Spike, Soak, Breakpoint), and automatically save reports for comparison. Designed to make performance testing accessible without needing to write k6 scripts.

Das Problem

Performance testing is critical for backend reliability, but writing and maintaining k6 scripts requires scripting knowledge and adds overhead. Teams need a simpler way to configure endpoints and run tests without becoming k6 experts. k6boost abstracts the scripting layer behind a simple interface, making performance testing accessible to developers and QA engineers.

Meine Rolle

Designed and built k6boost from the ground up. Implemented the interactive CLI menu, endpoint management system, all test profiles with configurable parameters, report generation and comparison logic, and security features for handling environment variables. Published to npm.

Architektur

1Node.js CLI entry point with interactive menu system
2Endpoint configuration storage in k6boost.json
3Command-line interface for scripting and CI/CD integration
4Grafana k6 integration layer (subprocess execution)
5Report generation and structured JSON output
6Configuration management with environment variable substitution

Technische Entscheidungen

Built an interactive menu as the primary interface because developers new to performance testing should not face a blank CLI.
Stored configuration in k6boost.json (git-tracked) while keeping reports in .k6boost/ (gitignored) to support baseline comparisons.
Wrapped k6 rather than reimplementing the engine because k6 is proven; the value is in making it accessible.
Supported both interactive and command-line modes so k6boost works for ad-hoc testing and CI/CD pipelines.
Required --allow-remote flag for non-localhost targets to prevent accidental load on production.

TypeScriptNode.jsGrafana k6npm CLIJSONEnvironment Variables

Financial Dashboard

Full-stack financial dashboard with a Spring Boot backend and Next.js frontend.

Case Study GitHub

Started from a Next.js learning project and extended it into a full-stack application by building a custom Spring Boot REST API backend. The frontend uses React and TypeScript with Tailwind CSS. The backend uses Spring Boot 3 with Spring Data JPA, Hibernate, and PostgreSQL (via Supabase). Backend deployed on Azure App Service.

Das Problem

The original Next.js course project communicated directly with a database from the frontend. The goal was to replace that with a proper API layer — a Spring Boot backend — to practice real-world full-stack architecture where the frontend and backend are separated services.

Meine Rolle

Built the entire Spring Boot backend independently. Refactored the Next.js frontend to consume the new API instead of direct database access. Handled API design, data modelling, JPA entity mapping, and Azure deployment.

Architektur

1Next.js + React frontend (TypeScript, Tailwind CSS)
2REST API layer — JSON over HTTP
3Spring Boot 3 backend (Java 17, Maven)
4Spring Data JPA + Hibernate ORM layer
5PostgreSQL database (Supabase)
6Azure App Service deployment

Technische Entscheidungen

Used Spring Boot for the backend to practice the full Spring ecosystem — dependency injection, JPA integration, REST controller patterns, and exception handling.
Chose PostgreSQL on Supabase for development convenience while keeping a standard relational database.
Deployed the backend on Azure App Service to gain experience with cloud deployment outside of Vercel.
Used DTOs to separate the API contract from internal JPA entity structure.

JavaSpring BootSpring Data JPAHibernatePostgreSQLSupabaseAzureNext.jsReactTypeScriptTailwind CSS

file-case-converter

CLI tool that renames files and automatically updates all import paths using AST parsing.

Case Study GitHub

A Node.js CLI tool that converts file names across an entire codebase (kebab-case, camelCase, snake_case, PascalCase) and automatically updates all import statements by parsing the source files with an AST — not regex. Supports dry-run mode, ignores node_modules, and works on large projects.

Das Problem

Renaming files in a JavaScript/TypeScript project manually breaks imports. Regex-based find-and-replace is fragile and error-prone on large codebases. This tool solves the problem by using AST-based import analysis to safely rename and update everything in one command.

Meine Rolle

Designed and built the tool from scratch. Implemented the AST-based import resolver, file renaming logic, case conversion functions, CLI argument parsing, and dry-run preview mode. Published to npm.

Architektur

1Node.js CLI entry point
2Case conversion module (kebab, snake, camel, pascal)
3File system traversal (recursive, ignores node_modules)
4AST parser for import path extraction and replacement
5Dry-run mode to preview changes before applying them

Technische Entscheidungen

Chose AST parsing over regex to make import updates safe and accurate across different import syntax styles.
Added dry-run mode as a first-class feature — developers should always be able to preview destructive changes.
Published as an npx-compatible package so users can run it without installing.

JavaScriptNode.jsASTnpm CLI

Ebenfalls erwähnenswert

TechStack Lab

Personal learning lab — hands-on projects, code notes, and technology experiments.

A public repository where I document technical learning through code. Topics include Java fundamentals, JVM architecture, Spring Boot integration, JWT authentication, async programming patterns, and more. Organised as individual focused experiments rather than one large project.

JavaSpring BootSupabaseJavaScriptReact

Case Study GitHub

GitHub

Mehr auf GitHub

Ich nutze GitHub zum Experimentieren, für Notizen, Algorithmusübungen und Lerndokumentation. Nicht alles hier ist ein fertiges Projekt, aber die Commit-Historie zeigt, woran ich arbeite.

github.com/sabeerwaqas Kontakt aufnehmen

Wird geladen …

k6boost

CLI tool for API performance testing that simplifies Grafana k6 workflows.

Case Study GitHub

Das Problem

Meine Rolle

Architektur

1Node.js CLI entry point with interactive menu system
2Endpoint configuration storage in k6boost.json
3Command-line interface for scripting and CI/CD integration
4Grafana k6 integration layer (subprocess execution)
5Report generation and structured JSON output
6Configuration management with environment variable substitution

Technische Entscheidungen

Built an interactive menu as the primary interface because developers new to performance testing should not face a blank CLI.
Stored configuration in k6boost.json (git-tracked) while keeping reports in .k6boost/ (gitignored) to support baseline comparisons.
Wrapped k6 rather than reimplementing the engine because k6 is proven; the value is in making it accessible.
Supported both interactive and command-line modes so k6boost works for ad-hoc testing and CI/CD pipelines.
Required --allow-remote flag for non-localhost targets to prevent accidental load on production.

TypeScriptNode.jsGrafana k6npm CLIJSONEnvironment Variables

Ebenfalls erwähnenswert

TechStack Lab

Personal learning lab — hands-on projects, code notes, and technology experiments.

JavaSpring BootSupabaseJavaScriptReact

Case Study GitHub

Ausgewählte Projekte

k6boost

Financial Dashboard

file-case-converter

Ebenfalls erwähnenswert

TechStack Lab

Mehr auf GitHub

Ausgewählte Projekte

k6boost

Financial Dashboard

file-case-converter

Ebenfalls erwähnenswert

TechStack Lab

Mehr auf GitHub