A software engineer website

haskell

2024

Bowling kata as a zipper -

Haskell Legacy: Adding features -

Haskell Legacy: Pure projection -

Haskell Legacy: CQRS -

Haskell Legacy: Going event-first -

Haskell Legacy: Reversing writes -

Haskell Legacy: Creating events -

Haskell Legacy: Extracting business logic and introducing effects -

Haskell Legacy: Testing -

Haskell Legacy: Introduction -

In-depth programming language is not the point -

Haskell Ecosystem Workshop & ZuriHac 2024 -

Introduction to GHC's Generics -

Fix aeson ToJSONKey/FromJSONKey derivation -

Fizzbuzz kata: branchless version -

Types for building and types for running -

Types strengthening -

eDSLs for tests -

Type-driven development applied: librarian -

Types and Tests -

Haskell: imports vs exports -

Haskell refactorings -

Bypassing Prometheus SDK push model -

Prescriptivism and Descriptivism -

Access Control: Capabilities -

2023

Access Control: Relationship-based Access control -

Access Control: Organisation-based Access control -

Access Control: Graph-based Access control -

Access Control: Attribute-based Access control -

Access Control: Role-based Access control -

Access Control: Context-based Access control -

Access Control: ACL -

Game of Life kata: branchless Grid -

From custom Monad to Polysemy -

Implementation-oriented Monad -

Haskell Type Reflection Anti-pattern -

QuasiQuoting Smart Constructors -

Nix: optimizing Haskell build size -

Haskell contributions kick-start -

Witness functions -

Test-Driven Development Freedom -

A case against Haskell immersion -

Bloodhound redesign progress -

Haskell macros -

Nix: optimizing Haskell-based Docker-size -

New library: kill-bool -

Abaks: OpenAPI -

Abaks: Views -

Abaks: A word on testing -

Abaks: Drivers -

Abaks: Interface Adapters - API -

Abaks: Testing Use Cases -

Abaks: Use Cases -

Abaks: testing core domain -

Abaks: commands -

Abaks: events -

Abaks: initial requirements -

Polysemy: Scoped -

Polysemy: Opaque -

Polysemy: Onion architecture -

Polysemy: Design heuristics: Hiding vs Exposing -

Polysemy: Design heuristics: Dispatcher -

Plutus: Pioneers Program 4th cohort - Lecture 10 - Built with plutus -

Polysemy: Design heuristics: Hiding interpreters -

Plutus: Pioneers Program 4th cohort - Lecture 9 - Stablecoin -

Plutus: Pioneers Program 4th cohort - Lecture 8 - Staking -

Polysemy: 1.9.0.0 released! -

Plutus: Pioneers Program 4th cohort - Lecture 7 - Marlowe and hosted smart contracts -

Plutus: Pioneers Program 4th cohort - Lecture 6 - Testing -

Polysemy: Design heuristics: Grouping interpreters -

Plutus: Pioneers Program 4th cohort - Lecture 5 - Minting -

Polysemy: Design heuristics: Effects layering -

Plutus: Pioneers Program 4th cohort - Lecture 4 - On-chain/Off-chain smart contract code and indexers -

Polysemy: Design heuristics: Split by responsibility -

Plutus: Pioneers Program 4th cohort - Ouroboros -

Polysemy: Design heuristics: IO hunting -

Plutus: Pioneers Program 4th cohort - lecture 3: Tests, Times, and Dapps -

Polysemy: Async gotchas -

Plutus: Pioneers Program 4th cohort kick start -

Polysemy: Strategy internals -

Polysemy: Changing return -

Polysemy: IO -

Polysemy: NonDet -

Polysemy: AtomicState -

Polysemy: Fixpoint -

Polysemy: Bundle -

Polysemy: Higher order Effects and combined interpreters -

Polysemy: Final vs Embed -

Polysemy: Tactics binding deprecated workaround -

Polysemy: Tactics binding -

Polysemy: Strategies binding -

Polysemy: Async -

Polysemy: Higher-order effects with Final -

Polysemy: Final -

Polysemy: Higher-order effects introductions -

Polysemy: Input -

Polysemy: Embed -

2022

Polysemy: Interceptors to buffer -

Polysemy: Introduction to Interceptors -

Polysemy: Tagged effects -

Polysemy: Interpretation and effects inline injection -

Polysemy: Interpretation and effects injection -

Polysemy: Introduction to Effect interpretation -

Polysemy: Introduction to Effect definition -

Polysemy: EffectRow design -

Polysemy: EffectRow -

Polysemy: Introduction to interpreters -

Polysemy: An introduction -

TDD: optimizing for inputs vs for outputs -