Riad Eita

The same content as text – or everything as one page:

• Riad Eita: Software & AI engineer in Berlin, at Siemens (via Eviden). Most of my work happens between systems – interfaces, contracts, pipelines, identity – in Java and TypeScript, in Python services, on container platforms.
• Two ways of reading a system:
• The scope keeps widening:
• Systems are never only technical: Every architecture encodes decisions: who can see what, who decides, who is left out. Studying political science and sociology next to engineering is my way of looking at the same systems from the other side.
• Politics & institutions: Who decides – and how that gets built into institutions.
• Philosophy: What technology should do is not a technical question.
• Society: Structures outlast the people inside them – until they don't.
• Selected work: Four systems, four seams. Connect them to see how they are built.
• Embedded AI Assistant: An assistant that answers with the project's own context and carries out approved operations in the platform – without asking engineers to leave the tool they already work in.
• Follow a request through it:
• Extension delivery across a server landscape: Enterprise extensions have to reach a large landscape of servers in compatible versions – without manual steps that drift apart over time. Rollouts that are repeatable and traceable instead of hand-made.
• Token exchange for single sign-on: Internal tools each authenticate on their own; people should not have to sign in to every one of them. Moving between integrated tools without signing in again.
• Dependency & metadata services: Which extension depends on what – and which version runs where – is scattered across repositories and servers. One place to ask instead of many places to look.
• One stack, read top to bottom:
• Project Hub: Project work – time, trips, expenses, appointments – ends up in five apps, and none of them produces the document needed at the end. In TestFlight testing on iOS; the web version runs at projecthub.fs223.de.