Free applicatives, the handle pattern, and remote systems
Comments
via exploring-better-ways.bellroy.com by jackdk
Comments
via exploring-better-ways.bellroy.com by jackdk
Exploring Better Ways - Bellroy
Free applicatives, the handle pattern, and remote systems
Using free applicatives and the handle pattern to batch, optimise and test interactions with remote systems
QNX Resource Manager in Rust: Message Passing and Resource Managers
Comments
via membarrier.wordpress.com via raymii
Comments
via membarrier.wordpress.com via raymii
Memory Barrier
QNX Resource Manager in Rust: Message Passing and Resource Managers
Welcome to the first part of a series of posts on how to write a QNX resource manager in Rust. This post will, in fact, not discuss Rust at all, but rather provide some background information on re…
No Silver Bullets: Why Understanding Software Cycle Time is Messy, Not Magic
Comments
via arxiv.org via cyplo
Comments
via arxiv.org via cyplo
arXiv.org
No Silver Bullets: Why Understanding Software Cycle Time is Messy,...
Understanding factors that influence software development velocity is crucial for engineering teams and organizations, yet empirical evidence at scale remains limited. A more robust understanding...
cl-tuition: a Common Lisp library for building TUIs inspired by Charm
Comments
via github.com via vindarel
Comments
via github.com via vindarel
GitHub
GitHub - atgreen/cl-tuition: A Common Lisp library for building TUIs
A Common Lisp library for building TUIs. Contribute to atgreen/cl-tuition development by creating an account on GitHub.
What’s your go-to strategy for giving engineers access to production?
I’ve been in this field for almost 15 years, and I don’t think I’ve ever seen two companies handle this the same waySome other places just hand out just-in-time database access with short-lived credentials, others rely on rigid role-based permission, and others go all in on anonymized data dumps or shadow environments to avoid prod access altogetherWhat's your go-to when it comes to giving access to engineers to access production applications and such? How do you balance velocity with security/compliance/
via by txxnano
I’ve been in this field for almost 15 years, and I don’t think I’ve ever seen two companies handle this the same waySome other places just hand out just-in-time database access with short-lived credentials, others rely on rigid role-based permission, and others go all in on anonymized data dumps or shadow environments to avoid prod access altogetherWhat's your go-to when it comes to giving access to engineers to access production applications and such? How do you balance velocity with security/compliance/
via by txxnano
lobste.rs
What’s your go-to strategy for giving engineers access to production?
0 comments