|
about_me
Albert Ripper
Software Engineer & Architect · Freelance
I design and build complete software systems — from architecture to deployment. Strong focus on performance, clean design and low-level understanding.
tech_stack
How I Build Systems
I work across the full software stack — from modern web interfaces to backend services and low-level systems.
My focus is not just on technologies, but on choosing the right tools for the problem.
Angular, React or Laravel for frontend applications, Quarkus for scalable backend systems, and Rust or C++ for performance-critical components.
Deployment and infrastructure are handled through containerized environments and automation.
Selected Technologies
A selection of technologies I use — chosen based on problem, performance and system requirements.
architecture
Building Systems That Last
I design systems that are scalable, maintainable and performance-driven. My focus is not just on writing code, but on creating clear structures, well-defined boundaries and long-term stability.
Principles
I choose technologies based on the problem — not trends. From modern web applications to backend services and low-level systems, the goal is always the same: build reliable and efficient solutions.
projects
Not a collection of apps — a set of systems. Each project is built around constraints, tradeoffs and control.
SYSTEM PROJECT
Firmware Analysis Toolkit
Reverse-engineering oriented system for structured binary inspection. Built to handle non-linear memory layouts, scrambled address spaces and inconsistent dumps.
Problem
Fragmented firmware with no deterministic mapping
Approach
Block clustering + heuristic pattern grouping
Outcome
Stable reconstruction without metadata
Principle → Control over abstraction
DevOps Runtime with Native Execution Layer
Problem
Opaque deployment workflows and inefficient communication between system layers
Approach
Quarkus orchestration with a Rust execution layer connected via Unix domain sockets, exposed through an Angular UI
Outcome
Transparent, reproducible deployments with low-latency execution
Separate orchestration from execution
JWT Session Model
Problem
Stateless auth lacks lifecycle control
Approach
Hybrid cookie + token orchestration
Outcome
Predictable session invalidation
State is a feature
contact
Interested in building reliable systems or discussing architecture?
Currently open for selected projects.