Not so long ago, I wrote an article about OWASP ASVS 5.0 (a comprehensive security checklist aiming for web applications). I mentioned there that AI security was intentionally left outside of its scope. There is now a brand new OWASP document specifically for filling this gap: AISVS. I've looked at this standard. Is it actually helpful when building an AI-enabled system?
Large financial institutions use the public Canton Network in live systems that process hundreds of billions of dollars every day. Here are 8 distinct production use cases from financial markets — covering short-term lending, securities lending, trading, payments, and digital ownership records.
Canton is Digital Asset's privacy-preserving ledger protocol. Unlike public blockchains, it limits transaction visibility from the start – each participant only sees what they're authorized to see. This article breaks down how Canton handles consistent state, historical integrity, and issuer trust.
Daml is a functional language for writing smart contracts on Canton Network — a distributed ledger built for regulated, multi-party workflows. This guide covers Daml syntax, templates, choices, testing with Daml Script, and local debugging tools.
Depending on the team and project, developers may work from well-defined requirements or help shape solutions from the ground up. In developer tooling, the latter tends to happen particularly often. We spoke with Karol Skóra about what surprised him most after moving from backend development into tooling and why communication may be just as important as technical expertise.
JEP-538 introduces the third preview of the PEM API. This API provides native support for decoding and encoding cryptographic objects in the Privacy-Enhanced-Mail (PEM) format, which is kind of an industry standard.
Interview with Krzysztof Romanowski, Head of Development Productivity at VirtusLab Software engineering loves process, structure, best practices, and architectural purity. Tooling engineering often lives somewhere else entirely - in edge cases, uncomfortable tradeoffs, and systems that only work because somebody deeply understands how they break. We sat down with Krzysztof Romanowski to talk about why tooling engineers often think very differently from the rest of the industry.
Interview with Jerzy Muller, Scala Evangelist & Dev Tooling Expert at VirtusLab Sometimes Google returns zero results. That’s usually where tooling engineers begin their work. In large-scale engineering organizations, their job is to make impossible systems work together and keep thousands of developers unblocked when everything starts breaking at scale. We sat down with Jerzy Müller, Scala Evangelist and Dev Tooling Expert at VirtusLab, to talk about what this work actually looks like behind the scenes.
After seven years in Java, I joined a Kotlin project and got curious about the native ecosystem. To learn it, I built a small Trading Accountability App — a tool that logs trades, enforces trading rules, and flags violations when discipline slips — from scratch using only Kotlin-native libraries, and this article walks you through doing the same.
Concurrency in Scala has come a long way from the humble beginnings of scala.concurrent.Future. What started as a minimal abstraction over callbacks that allowed easy sequencing of operations, thanks to the monadic composition has since evolved into a rich ecosystem of effect systems, each trying to solve real-world problems around type and resource safety, composability, and performance.
The Cats library and the related Cats Effect were inspired by scalaz and scalaz-concurrent libraries (and, more broadly, by Haskell and its ecosystem). They represent the most widely adopted effect system in the Scala ecosystem. In this context, effects are values representing descriptions of computations that can be composed using typeclass-based abstractions like Functor, Monad, or Sync, as provided by Cats and Cats Effect. This approach promotes the use of pure functions and referential transparency - the principle that any expression can be replaced by its evaluated result without changing the program's behavior.
Kyo is one of the younger kids on the block - at the time of writing of this blogpost it has only reached its first release candidate for version 1.0. It is the brainchild of Flavio Brasil, a tenured Scala open source author and contributor who, in the past, created Quill, an SQL library based on Scala’s metaprogramming facilities and contributed to Twitter’s Finagle stack. Kyo attempts to take the idea of fused effects introduced in the ZIO monad and generalise it to provide a complete algebraic effects runtime and solve the “monads do not compose” problem at the same time. In practice, Kyo is also a purely functional, monadic solution but it’s built for the future and uses a lot of new features of Scala 3 to aggressively avoid allocations and inline common operations.
