@thorstenball@adamwathan@awesomekling I’ve always found the standard 5/3/1 templates to probably be easier (read: better laid out) if you upped the frequency a bit - doing a deadlift variation after the main squat work and a squat variation after the main deadlift work would likely help keep things moving
I just published my first paper review of 2024 - "Blueprint: A Toolchain for Highly-Reconfigurable Microservice Applications": https://t.co/vAKlaU8YXC
The paper from SOSP proposes a framework intended to simplify iterating on different technical designs for a system.
This framework, called Blueprint, splits up application business logic, framework-level components (e.g. RPC functionality, distributed tracing libraries, storage backends), and instantiating the application with configuration.
The paper discusses several examples of iterating on a system design after onboarding to Blueprint, including evaluating the performance impact of deploying with microservices vs monolith and choosing a distributed tracing library.
Authors of the paper are
@vaastav05, Deepak Garg,@AntoineKau, and
@mpi_jcmace
@Neurisko @davidfowl Do you think this is a social problem? Writing OCaml and working on Hack, I regularly see requests for NEW language features. The idea a language adds new, more expressive constructs feels positive.
@davidfowl My daily driver languages are OCaml and Rust but what I love about Rust is expressive by default, performance by choice. C# seems to evolve with the same ethos. Having worked in companies with other server languages, I don’t think that flexibility is captured as effectively.
@kwuchu My last cleaning lady put me onto the Shark upright models - I think they’re under 300 bucks and they’re great for pet fur and whatever crap collects on my kitchen floor
@charliermarsh@hd_nvim You could always create a new enum of three elements to represent Success<T>, NotFound, and Failure(String) or whatever your model needs.