~ / about
Shady Nathan Tawfik
About Me ( Full-Stack · Data Science · ML/AI · Cybersecurity · Design · Open Source )
Get in Touch
About Me
In a technology landscape increasingly split into narrow specializations, Shady Tawfik represents a rare profile: that of an interdisciplinary architect at the intersection of technological complexity and visualized semantics. With over eleven years of professional experience in software engineering and communication design, he operates confidently across a spectrum spanning systems-level development, machine learning and distributed web architectures to typographic precision, information design and brand identity. Tawfik's philosophy is rooted in the belief that outstanding software is not created solely through bug-free code or mathematical performance, but through a deep understanding of human interaction. For him, design is not a superficial layer applied to the user interface after technical implementation, but a structural foundation. Likewise, code is not an end in itself, but a tool for making complex logical structures tangible, accessible and functional. This hybrid identity as both designer and engineer, combined with over a decade of practical experience, enables Tawfik to conceptualize, implement and scale projects independently—from the first algorithmic idea and system architecture through UX design and strategic communication.
Work Experience
Founder & Chief Architect
2026 - PresentBewertiq • Germany
Public data forensics & review integrity platform. Y Combinator portfolio. Geospatial 3D visualization, ad-risk detection, scalable data pipelines. bewertiq.org
www.bewertiq.orgLead / Staff Data Scientist - L3
2025 - PresentOpencode • United States
Development of data-driven solutions and fullstack applications.
Software Developer
2023 - 2025u + I interact • Germany
Software development for interactive media projects.
Software Developer
2023epunks • Germany
Software development and system architecture.
Web Developer
2022Hardlait Paris • Paris
Web development for international client.
Software Developer (Education)
2021neue fische • Cologne
Software development bootcamp and certification.
Developer
2021Humboldt-Universität • Berlin
Academic research and development projects.
Bachelor Grafik und Kommunikation
2020FH Bielefeld • Bielefeld
Bachelor's degree in Graphic Design and Communication.
Web Developer
2020Zahnarzt Helden • Germany
Web development for dental practice website.
Software Developer
2020bagzz Berlin • Berlin
Software development for private projects.
Full-Stack Developer
2020tva-studio • Cologne
Full-stack web development for clients.
UI/UX Web Developer
2020Watergate Berlin • Berlin
UI/UX development for private projects.
Cybersecurity Intern
2020RTL Group • Cologne
Cybersecurity internship and training.
Web Development Internship
2018Clark • Germany
Web development internship.
Web Development Internship
2017Alasco GmbH • Germany
Web development internship.
Full-Stack Developer (Education)
2017Ironhack Berlin • Berlin
Full-stack development bootcamp.
Bachelor Physik
2017Uni Bielefeld • Bielefeld
Bachelor's degree in Physics.
Abitur
2012Max-Planck Gymnasium • Germany
High school diploma.
WordPress, TYPO3, and the reality of both
I live and work in Germany, which means a CMS is never just a CMS. Clients ask about data processing agreements, accessibility, update windows and who is still around in five years. I build and maintain WordPress and TYPO3 in that reality — not as a page-builder operator, but as a developer who reads the source, writes the plugins and extensions, and owns the result in production.
WordPress is where most of my CMS work lives. I know the hook system, the REST API, custom post types and taxonomies, Gutenberg and the block editor, multisite, WP-CLI, the autoloaded-options problem, object caching — and the unglamorous parts: nonces, capabilities, escaping, prepared SQL, uninstall routines and database migrations. I write plugins like any other software: namespaced, i18n-ready, with an update path and an uninstall that leaves no debris.
The trials are real. WordPress gives you freedom and hands you the bill: a plugin ecosystem of wildly different quality, themes that ship their own jQuery, page builders that lock content into shortcodes, and an update treadmill where a minor release can break a site nobody touched in two years. Security is not a plugin you install; it is the discipline of every line you ship. Performance is rarely a caching plugin — it is the query you didn't need, the option you didn't autoload, the image you didn't resize.
TYPO3 is the other side of the German coin: more structure, more upfront cost, less chaos. TypoScript, Fluid, Extbase, TCA, FlexForms, site sets, Composer, DDEV, workspaces and the scheduler are not a weekend, but once the architecture is in place it stays legible for years. Upgrades are planned projects instead of surprises — exactly what public-sector and mid-sized clients need. I develop for both: WordPress plugins with hooks, REST endpoints, admin screens and uninstall logic; TYPO3 extensions with Extbase, Fluid, TCA, TypoScript and PSR-14 events.
Which one is better? The honest answer is: the one the client's team can still maintain in five years. I choose on organisation, budget, editorial workflow and update culture — not on what is fashionable this quarter.
My philosophy: simple stacks, boring choices, sharp tools
I belong to the generation that started with HTML tables, moved to CSS when tables stopped being layout, and then watched JavaScript grow from a few lines of form validation into an ecosystem with its own build system, package manager and release cycle. I have shipped jQuery, SPAs and Laravel, and I have maintained the aftermath. Every abstraction buys you something and charges rent. My job is to know the interest rate.
I love a simple stack. A server, a database, HTML, CSS and a bit of JavaScript will outlive most frameworks — and whoever inherits it can still read it. I reach for React and Next.js when the product genuinely needs them, not because the CV looks better with them. Laravel is the same story: a good framework with a lot of batteries, sometimes exactly right, sometimes a few PHP files and a well-written query are the more honest answer.
And yes, I still use node_modules. I am not going to pretend I can remove it — modern tooling, bundling, linting, testing and a handful of modules that genuinely save weeks live there. But I keep the tree small, pin what I can, read what I add, and prefer the platform when the platform already does the job. A dependency you don't need is not free: it is a future upgrade, a future CVE and a future explanation.
Two things I refuse to treat as optional: SQL and Python. SQL because data outlives the application — if you cannot read a query plan, write a window function and explain why an index exists, you are guessing. Python because it is the shortest path from an idea to a working analysis: scraping, cleaning, statistics, machine learning, automation, a small FastAPI service. TypeScript pays the bills in the browser; SQL and Python are where I think.
This is not an anti-framework position. It is an anti-accident one: choose the tool you can explain, operate and replace.