Siemens Communications / Telecom
Making switch failures readable
A grammar-driven analyzer turned telecom switch error symptoms into information engineers could inspect.
Explore story & flowSystems Engineering & Integration
Make complexitylegible. Then useful.
Parse a switch failure. Define a customer record. Find the next urgent case. An engineering thread built around helping people and systems understand what comes next.
4 stories · Business context first · Engineering one layer deeper
The Error Symptom Data Analyzer, simplified
Follow the flow. Select a stage to look inside.
Symptom File (StackTrace)
Error symptom files and stack traces were produced by programs written in CHILL.
Read the full diagram explanation
Switch programs written in CHILL produced error symptom files. A Lex/Yacc grammar parsed and analyzed them; engineers inspected results in a C++/Unix application. No production trace or sample output is shown.
A REPEATING PATTERN
Complex information→A usable system→A clearer decision
Files, transactions and queues become structures engineers and operators can act on.
THE BOUNDARIES BETWEEN SYSTEMS
At the system boundary.
Start with the problem.
Then look under the hood.
Capgemini / Telecom
Java objects ↔ XML: the MetaSolv–Cygent integration
A utility using the Java Reflection API translated Java objects to XML and XML back into Java objects at the boundary between telecom CRM and order-management systems.
Explore story & flowGTE (later Verizon) / Telecom
Defining a shared customer record
Backend CRM engineering at the boundary between customer interactions and activation or provisioning systems.
Explore story & flowCapgemini / Telecom
Getting the next case right
Workflow integration for wireless number portability, followed by a way to put the most pressing case in front of an agent.
Explore story & flowTHE ENGINEERING TOOLKIT
From code to connected systems.
Languages, integration tools, platforms, databases and AI systems across my work.
Languages
From systems code to application logic.
- C++
- Java
- Python
- PL/SQL
Integration & tools
Middleware, workflows, internal tools and analytics.
- WebLogic
- MQSeries
- Vitria
- TIBCO
- Lex
- Yacc
- Retool
- Looker
- Power BI
Technologies
The contracts between applications.
- Object-oriented programming
- RMI
- CORBA
- XML
- DTD
- Java Reflection
Cloud & hosting
Platforms across the broader toolkit.
- AWS
- Azure
- Render
- Vercel
- Railway
- Lovable
Databases
Relational data and query systems.
- Oracle
- SQL Server
- PostgreSQL
AI & LLM
Retrieval, model context and AI coding tools.
- RAG
- Vector databases
- Claude Code
- Codex
- Antigravity harness
This is a career-wide toolkit, not the stack of every project. Individual stories identify their own technologies. RMI was explored in the GTE work; production use in that project is not asserted.
FOLLOW YOUR CURIOSITY
Find your thread.
Browse this collection or connect the dots across all three.
Refine by company, period, capability, technology or domain
4 stories
Making switch failures readable
A grammar-driven analyzer turned telecom switch error symptoms into information engineers could inspect.
Defining a shared customer record
Backend CRM engineering at the boundary between customer interactions and activation or provisioning systems.
Java objects ↔ XML: the MetaSolv–Cygent integration
A utility using the Java Reflection API translated Java objects to XML and XML back into Java objects at the boundary between telecom CRM and order-management systems.
Getting the next case right
Workflow integration for wireless number portability, followed by a way to put the most pressing case in front of an agent.
LET’S CONNECT THE DOTS
What’s the complex problem
on your desk?
Explore how engineering depth and commercial judgment can work together.
Start a conversationThese are personal accounts of professional work. Company and client names identify context and do not imply endorsement. Conceptual diagrams explain relationships; they are not production screenshots.