My view of software
Key design work often starts before code: what should someone be able to do, which data are needed, and what happens after a missed deadline or missing record? A clear workflow guides technology choice and later testing.
Schulmittag and Schulnavi illustrate different tasks. School meals require roles and recurring processes to work together. School choice requires data that people can compare meaningfully. Both interfaces must explain what the data actually say.
Operations add questions: who notices errors, which version runs, how is data restored? For me, a technical decision is fully described only when its recurring costs, limits and possible exit are understandable.
Three questions to go further
- What distinguishes a prototype from a product?
- A prototype tests an assumption. A product performs a recurring task for others, requiring responsibility, failure handling, access protection, maintenance and data handover. The transition depends on actual use.
- When does a dedicated instance help?
- A separate application or database can simplify separation between institutions. It does not replace access control and adds operational work. The choice depends on data, contracts, change frequency and support.
- What makes open data useful?
- Traceable sources, visible data dates and understandable limits. Missing information must appear as missing; an interface must not turn a technical gap into an apparently certain judgment.
Articles & practical guides
Hashing, encryption and digital signatures: the difference
Checksums, confidentiality and verifiable origin serve different purposes. A decision guide for files, backups and software protocols.
Checking files with PowerShell: SHA-256 and the right bytes
A reproducible PowerShell exercise: create a test file, calculate SHA-256, compare line endings and interpret results correctly. With a PDF edition.
Understanding SHA-256: from bytes to a hash
Why a SHA-256 hash has 64 hexadecimal characters, how bytes matter and what a checksum actually establishes. With examples, a browser demo and PDF.
From prototype to operation: what to clarify before real use
An application runs. But who maintains it, notices errors and restores data? Six questions for the transition from demonstration to daily use.
A book that renews itself
The free book from christlichdenken.at is regenerated with every release. What happens when you treat a book like software — and why.
Tools that hold up
nerve supports software development, fleetdeck handles deployment. Why I build my own tools, explain them and state their limits.
One instance per institution
Why Schulmittag uses separate instances, the responsibility this creates and why isolation alone does not guarantee security.
Software for municipalities: what digitisation really needs
School meals on paper, spoken registrations, manual billing. What building Schulmittag taught me about municipal digitisation.
Projects as a starting point
Farleda
Farleda is the flagship project of Raphael Lugmayr and Stoicera: European rail journey planning, traceable emissions comparisons and joint pilots.
Wachsam
Wachsam by Stoicera: learn to recognise fraud and phishing through short cases. For families, schools and businesses, available in the browser.
Stoicera Atlas
Stoicera Atlas: structure data, design views and connect workflows. Closed demo on request through Raphael Lugmayr and Stoicera.
MealTime (Schulmittag)
Schulmittag / MealTime: school meal software, from parent registration to billing. Product development and operations with Raphael Lugmayr as CTO.
Schulnavi
Schulnavi uses open school data to help find and compare schools in Austria. A project by Raphael Lugmayr and Stoicera.