Consulting · Engineering · Research

Practical engineering for complicated systems.

I’m Ed. Abdiel Rodriguez — a consultant, computer-science academic, and software engineer working across risk analysis, automation, AI, process improvement, reliability, and vulnerability engineering. ProgreTech is both the home of my independent practice—where people can reach me for consulting, development, and technical services—and a public workshop where I share selected projects, experiments, and lessons as they develop.

Risk & Impact AnalysisAutomationApplied AISRE & ReliabilityVulnerability EngineeringProcess Improvement
ProgreTech banner
ProgreTech

Practical software for everyday technical problems.

I use ProgreTech to share tools, experiments, and reusable pieces of software that have been useful in my work or personal projects. The subjects vary—automation, reliability, learning tools, document processing, risk analysis, and AI—but the goal is usually simple: make a difficult or repetitive task a little easier.

Areas I often work in

Software engineering · process automation · applied AI · SRE and reliability · risk and impact analysis · enterprise integration · document/OCR workflows · data interfaces

Some projects are complete products, some are internal patterns, and some are simply useful experiments worth documenting.

How the work is useful

Functionality that can travel between projects.

A feature built for one application often solves a more general problem. I try to document those pieces so the project can be useful as an example, not only as a finished application.

OCR & document processingTurn images and documents into structured information that can be reviewed, searched, translated, or passed into another workflow.
Guided workflowsBreak complicated tasks into understandable steps, with contextual help and sensible defaults.
AutomationRemove repetitive interaction while keeping the workflow inspectable and maintainable.
Risk & dependency analysisConnect technical signals and relationships so people can focus on changes that need attention.
Local-first & lightweight appsKeep applications simple to deploy and, where useful, keep state close to the user.

Examples of reusable building blocks

FunctionExamplesCan also help with
OCR + structured reviewManabi Kōbō, document workflowsIntake, archiving, searchable documents, data entry
Guided help / tutorialsLearning tools, engineering workbenchesOnboarding, internal tools, self-service processes
Dependency analysisNAVI, change-assurance utilitiesRegression planning, release readiness, technical risk
Event/history trackingCodeSealAudit trails, provenance, controlled historical review
Local-first stateSpecklet, NexoTori conceptsPersonal tools, offline workflows, privacy-sensitive apps
Projects & case studies

A few places where these ideas are being used.

A few current projects are shown below. The featured-projects page includes the engineering context, reusable techniques, and public links where they are available.

Learning tools

Manabi Kōbō

Manabi Kōbō is a Japanese-learning workshop I built for developers and other learners who want practical ways to read, practice, and work with Japanese material.

Manabi Kōbō interface
Guided Japanese learning, reading, and developer-focused practice.

Alongside the learning material, it has become a useful place to apply technologies that solve common content problems: OCR for extracting text from images, Sudachi-based Japanese text processing, furigana generation, multilingual presentation, PWA behavior, guided tutorials, printable study material, QR generation, and local/AI-assisted workflows.

RapidOCR / OCRSudachiFuriganaPWAMultilingual UIGuided tutorialsReportLab / printable output
Software provenance

CodeSeal

CodeSeal is a technical provenance registry for recording code-signing history and checking whether registered source has appeared in earlier registry events.

CodeSeal interface
Source provenance, history, and verification workflow.

The project uses registry history, match detection, provenance notifications, privacy-aware access to detailed records, and auditable report inspection. Those patterns are also useful anywhere historical evidence needs to be retained without making sensitive details broadly visible.

FlaskRegistry historyProvenanceAccess loggingPrivacy-aware reports
Enterprise reliability

NAVI & SAP engineering utilities

NAVI and a collection of smaller SAP/Python tools help with change analysis, operational visibility, reporting, RFC/API data access, and release-readiness work.

The common pieces include RFC/API integration, dependency relationships, report generation, interactive data views, job monitoring, and change-risk context. Many started as small utilities around a specific operational task and remain useful examples for connecting enterprise systems to lightweight Python tooling.

PythonRFC / APIsFlaskBokehRisk analysisOperational reporting
Local-first workflows

Specklet & NexoTori

These projects explore small, focused workflows where application state and useful next actions matter more than a large backend or dashboard.

They provide examples of PWA patterns, local state, task/case modeling, mobile-friendly interfaces, and OCR-assisted intake concepts. The same approaches can fit personal utilities, field workflows, and applications where keeping data on-device is useful.

PWALocal storageWorkflow stateResponsive UIOCR concepts
Older work & experiments

Small tools are still useful references.

The GitHub archive includes SAP automation, RFC data feeds, reporting tools, PDF utilities, hardware projects, game preservation work, and other experiments. I keep them available because sometimes a small implementation detail is exactly what someone else is looking for.

Have a question?

The site assistant can help point you toward a project or topic. For a real conversation, the contact page has the best ways to reach me.