gabby

@fullmoon.id

Author of haskellforall.com, dhall-lang.org and @trygrace.dev, professional doggirl and endurance hunter I'm a midwife to the hidden beauty in everything she/her 🏳️‍⚧️ coworkers DNI https://linktr.ee/gabriella439 💖 @ember.pet

me: why is it pacific standard time? we’re not in the pacific. it should be western standard time gabby: yeah, and EST isn’t atlantic standard time. hm. i’ve never thought about that before gabby: central time isn’t even central, it’s actually a bit right of center me: just like all centrists

I wrote this years ago about domain-specific languages but you could replace domain-specific languages with agentic coding and it's the exact same story today, except on an even larger scale

This tradeoff can still tempt businesses because it’s appealing to replace skilled labor with unskilled labor. The reasoning goes that a small investment of more skilled labor (the authors of the domain-specific language) can enable a larger pool of less skilled labor (the less technical users) to do most of the work. However, what you will often find in practice is that this larger group of less technical users is frequently blocked without continuous assistance from the engineers who created the language.

So in practice you’re not actually replacing skilled labor with unskilled labor. Rather, you’re merely “laundering” skilled labor as unskilled labor and creating more work for your engineers to make them seem more replaceable than they actually are.