Miikka Koskinen

Aspiring documenter of things. Software engineering, resiliency, Clojure. Hiking, kayaking, outdoors. He/him. @[email protected]

[Miikka Koskinen @arcatan]

By the way, I'm mostly posting on Fediverse now (handle in bio) - I'm still lurking here though.

[Pekka Enberg @penberg]

Inspired by @gabe_guerra_ launching DC systems, I went ahead and registered https://t.co/0cWTELU8U2. If you're interested in attending or speaking, fill out the form there. If there are enough crazy systems people around here, we'll have ourselves a meetup!

[Miikka Koskinen @arcatan]

@metaLulie right, i reconize that. makes sense

[Miikka Koskinen @arcatan]

@metaLulie Huh, why are rationalists big on covert aggression?

[Miikka Koskinen @arcatan]

@penberg @ManningBooks Cool! Looking forward to reading it

[ilmo raunio @ilmo_r]

Just released 0.1.0 version of oksa, a library for generating GraphQL queries using Clojure data structures. New version introduces a way to construct queries using an API.

https://t.co/GrTm6qtX1Z

[Miikka Koskinen @arcatan]

@penberg How do you measure the vector similarity by the way? Cosine similarity?

[neoltitude @ctrlcreep]

We regret to inform you that the wugs have speciated. There are now bouba wugs and kiki wugs

[Emery Robin @emwrobin]

spent my lunch break today coming up with ways that the Kate Middleton story would turn out if it were being investigated by various fictional detectives

[@norootcause.surfingcomplexity.com on Bluesky @norootcause]

Two of the biggest source of incidents I’ve seen are:
1. Legacy code
2. Migrating away from legacy code

The conclusion is clear: you should only write non-legacy code

[Miikka Koskinen @arcatan]

@mkpaa Sataisipa vettä niin sitten olisi ehkä luonnonjäät luistelukunnossa 🤔

[🎭 @deepfates]

I love USING PYTHON i want to FUCKING MANAGE DEPENDENCIES BY HAND

[Miikka Koskinen @arcatan]

@defnotbeka It does help with binding! Since it has a different effect on the texture than egg, it doesn't suit every recipe, so it needs a bit of experimenting

[Charity Majors @mipsytipsy]

So, we lost the battle to define observability. You know it, I know it. Observability was supposed to *mean* something, and in the early days, it did.

"Observability" once meant the kind of exploratory, open ended investigation our systems increasingly demand.

[Miikka Koskinen @arcatan]

@eatonphil Seriously speaking I think it's a good idea though, esp. for the ecosystems like npm where the dep trees really go deep

[Miikka Koskinen @arcatan]

@eatonphil Shallow metrics can't stop me - I will vendor the universe

[frog @monofrogue]

Heard joke once: man goes to doctor. Says he's depressed. Says life seems harsh and cruel. Says he feels all alone in a threatening world where what lies ahead is vague and uncertain. Doctor says, "Treatment is simple. Great clown Pagliacci is in town tonight. Go and see him."

[Miikka Koskinen @arcatan]

@Stefferi Tässä on muuten suht. tuore artikkeli libertarismin historiasta Suomessa käyttäjältä @IKarryla. Siinäkin on samansuuntaisia havaintoja, että vaikka libertaari liike on ollut pieni, sen ideat ovat päässeet vahvasti esille. https://t.co/yJW576yYRM

[Miikka Koskinen @arcatan]

@tekknolagi Good stuff. I tried to use Ninja for something and it was almost great but using file mtimes to detect changes wasn't a good fit - but looks like Turtle addresses that issue by using content hashing instead

[Kent Beck 🌻 @KentBeck]

Given the cost of blocking, asynchronous code reviews, I'm surprised more teams haven't experimented with eliminating them.

What bad things would happen if you just integrated changes? Are those bad things happening already? What else could you do to avoid those problems?