agilob

joined 2 years ago
sorted by: new top controversial old
1
Cyber Security: A Pre-War Reality Check - Bert Hubert's writings (berthub.eu)
1
JIT vs AOT compilation (bell-sw.com)
1
No Restarts, No Disruptions: Seamless Pod Resource updates with In-Place Resizing (engineering.doit.com)
1
Using CRaC to reduce Java startup times on Amazon EKS | Amazon Web Services (aws.amazon.com)
1
JDK 21 G1/Parallel/Serial GC changes (tschatzl.github.io)
1
Defcon: Preventing Overload with Graceful Feature Degradation (www.micahlerner.com)
1
UUID Benchmark War (ardentperf.com)
1
Merge then review (programming.dev)
submitted 2 years ago* (last edited 2 years ago) by agilob@programming.dev to c/programmer_humor@programming.dev
0 comments fedilink
 

Move fast and break things.
Merge vulnerabilities.
Double the work.
Merge code without tests.
Anything, but don't let code become stale.

1
Configure multidimensional Pod autoscaling | Google Kubernetes Engine (GKE) | Google Cloud (cloud.google.com)
1
Grafana 10.2 release: All the latest features to know (grafana.com)
1
Introducing Grafana OnCall shift swaps: A simpler way to exchange on-call shifts with teammates | Grafana Labs (grafana.com)
1
What benefits do you get for being on-call? (programming.dev)
 
  1. How much extra do you get paid for being on an call rotation?
  2. Is the salary/benefits the same for inconvenience of being on call and working on an incident?
  3. What other rules do you have? Eg. max time working on an incident, rota for highly unsociable hours?
  4. How many people are on the same schedule with you?
  5. Where are you based, EU/US/UK/Canada?
view more: ‹ prev next ›