where have i seen this before? redux iirc?

wait this is a bit, right?

scheduled maintenance uncovers weak links in the system or something?

wait is this real or @foone.bsky.social doing a bit

well it’s been 15 years and the time has only moved like 4 years

(or something idk i don’t remember the last season i watched)

this looks fake

7 friends? in this economy?

bsky.app/profile/kaba...

now i understand the “opinions not of employer” disclaimers

what’s the working drier count of the house at the end of this exercise?

not with that attitude

350/500 🙂‍↔️

relatable. certain words trigger in me a fight or flight response to this day, should probably work on it.

cw: spoilers

ooo big barrister needs saving? from what? big bad mobsters?
stuck prosecuting, or the canon she walks away (presumably the start her own defense practice), they’re still stuck facing the same people

also no you cannot redeem micky joy with 2 episodes sorry

wtf was silk s3 finale

and the hundred thousand employees groan as they get yet another “media policy” update email

and no! i don't want you to get sold on wide events / observability 2.0 or whatever from the above article

just, give your logs a little bit more thought

(ALSO MAKE SURE YOUR LOG LEVELS ARE DYNAMICALLY RUNTIME RECONFIGURABLE OK BYE)

this is something you can start with _today_ while you figure out structured logging libraries for your project..

a. most of the new log lines i introduce are of the above format
b. some places where structured logging is supported, use them

(don't get me started on json output lines)

bad

"user=$userId created order $orderId with total $cost"

probably better

"order created user=$userId order=$orderId total=$cost"