Sascha Block

@SaschaBlock@devhub.social
12 Followers
37 Following
54 Posts
Sascha Block is an IT Architect based in Hamburg and the founder of Rock the Prototype. Passionate about making prototyping accessible and tangible, I created Rock the Prototype to bring ideas and software to life through prototypical approaches. My mission is to share knowledge about software development, prototyping, and IT architecture, inspiring others to explore and innovate.
Websitehttps://rock-the-prototype.com
YouTubehttps://youtube.com/@Rock-the-Prototype
Spotify 🇩🇪spoti.fi/3NJwdLJ
Apple Podcast 🇩🇪apple.co/3CpdfTs
Sascha BlockJan 7

Digital identity folks on Mastodon: do you listen to English #podcasts? 👋

I just published an RTP (EN) episode on #digitalIdentities + #IAM — #ITsecurity & #trust at the core.

Reply with: Apple / Spotify / YouTube / you preferred delivery / (or “no podcasts”) ✅

🍎 Enjoy on Apple Podcasts: 👉 https://qrco.de/bgXoxH 
🎧 Listen on Spotify: 👉 https://qrco.de/bgXouD

Podcast on YouTube: 👉 qrco.de/bgXour

Show threadSascha BlockJan 5

@jmax My native language is german. Hopefully my english isn’t that bad. So, I’m glad about your honest feedback.

My english podcast series is a little bit behind, but topic up to date:

🍎 Enjoy on Apple Podcasts: 👉 https://qrco.de/bgXoxH 
🎧 Listen on Spotify: 👉 https://qrco.de/bgXouD

Podcast on YouTube: 👉 qrco.de/bgXour

https://youtu.be/UycveezW19A

Episode 13 - Digital identities and identity access management

Podcast Episode · Rock the Prototype - Software development & Prototyping · 01/01/2026 · 32m

Apple Podcasts
Show threadSascha BlockJan 5
@jmax From my practical experience it is the biggest pain point and an elementary loss that requirements are not regularly tested. Even more in regulated invironments and due to black box code hidden… it’s an endless story and that’s my main motivation to let change happen.
Show threadSascha BlockJan 5

@Lyle My take: automate the first pass (signal + evidence: “majority / minority / none”), then keep a human-in-the-loop decision for edge cases and risk acceptance.

What would be your minimum required outputs (fields) for that automated check?

Beside: In what particular function and role do you perform these checks? What’s the ultimate goal?

Show threadSascha BlockJan 5
@Lyle Yes, there’s a relevant connection within - thanks. A “policy compliance ruleset” (e.g., restricted vendors/apps/links) might be a strong use case in some domains. If you have a short example requirement set from your context I can think about how to model it as a DSL ruleset and show how validation output would look like.
Show threadSascha BlockJan 5
@jmax Guess you mean #Cucumber/ #Gherkin (#BDD)? If yes: that’s an interesting direction — mapping requirements to Given/When/Then and validating quality before tests. Curious what you’d expect from such an integration.
Show threadSascha BlockJan 5

I’m looking for 2 people to sanity-check the approach (10 minutes).

If you work with #requirements, #compliance, or #audits: what would you need to try this on a real spec?
Boost welcome 🤗

#DSL #opensource #itsecurity #requirementsengineering #infosec

Sascha BlockJan 5

Fediverse check: who can actually see this? 👋

I’m building dsl-core: an open-source #DSL that makes requirements machine-readable and verifiable (ambiguity / atomicity / consistency).

❓ What would be the first meaningful use case for you?
Repo: https://github.com/rock-the-prototype/dsl-core
(Boost welcome 🙏)

#opensource #itsecurity #requirementsengineering #infosec

GitHub - rock-the-prototype/dsl-core: Core Specification for the Audit-by-Design DSL - Human- and machine-readable domain-specific language (DSL) for defining, validating, and auditing atomic requirements (AFOs) in regulated software environments. Open specification, free to use and extend.

Core Specification for the Audit-by-Design DSL - Human- and machine-readable domain-specific language (DSL) for defining, validating, and auditing atomic requirements (AFOs) in regulated software e...

GitHub
Show threadSascha BlockJan 29, 2025

@toxi Avram Joel Spolsky has certainly not coined the term architecture astronaut without good reason.

No astronaut (we should also include cosmonauts) should ever run out of oxygen 😅

In this respect, it certainly always makes sense not to be at home in just one world. Although, at the moment we only have this one damn planet and its standards.

Show threadSascha BlockJan 29, 2025

@toxi …before huge sums of taxpayers' money are wasted.

So in a way, my perspective is that of an architectural astronaut. However, I think it's worth taking a look around the engine room and including “Scotty”.

That much pragmatism is a must.

In this respect, yes, I find exotics quite exciting, but simply not relevant. FHIR - as it is currently defined and, above all, validated (black hole) - is also an exotic, but that's another story.