Alex Martsinovich

Alex Martsinovich

@distantprovince.bsky.social

#ElixirLang Developer 🇨🇦 Tech side: https://distantprovince.by/ Less tech side: https://distantprovince.substack.com/

94 followers120 following233 posts

Pinned

Agentic coding is undeniably very useful. It's also very bad. I compiled a list of what I think is wrong with it: four problems with no solution in sight. Or, as I call them, the four horsemen of agentic coding. ⬇️

Alex Martsinovich reposted

Agentic coding is undeniably very useful. It's also very bad. I compiled a list of what I think is wrong with it: four problems with no solution in sight. Or, as I call them, the four horsemen of agentic coding. ⬇️

View full thread

4. Team Fallout Agents weaken the social fabric of engineering teams by reducing interpersonal communication, increasing self-reliance, and hindering skill expression. We're all too busy prompting Claude. And prompting is an intimate process.

Agentic coding is undeniably very useful. It's also very bad. I compiled a list of what I think is wrong with it: four problems with no solution in sight. Or, as I call them, the four horsemen of agentic coding. ⬇️

View full thread

2. Alienation Engineers become alienated from code and, as a result, care less. Meat proxy, Claude condom – there's no shortage of colourful analogies. AI widens the distance between code and its creator, inevitably leading to a declining sense of ownership.

3. Deskilling AI erodes existing skills, impedes learning, and doesn't offer any meaningful skill progression. We can talk all we want about being architects and high-level thinkers, but the way we acquired those skills is going away, and it's unclear if there's a new one.

Agentic coding is undeniably very useful. It's also very bad. I compiled a list of what I think is wrong with it: four problems with no solution in sight. Or, as I call them, the four horsemen of agentic coding. ⬇️

1. Slop LLM-generated code has a strong smell that makes codebases repulsive to humans. Bigger and better models don't seem to help. The big bet here is that we'll never have to read code again, but so far, that hasn't happened, and we're having a very bad time.

Forgot to mention but Chatting Alone got an honorable mention in Adam Mastroianni's annual blog competition! Adam is brilliant and his own writing is outrageously good, so you can imagine how huge this is for me ❤️

Alex Martsinovich@distantprovince.bsky.social

I wrote about model permanence - a very natural but false idea that models exist between conversation turns. distantprovince.substack.com/p/chatting-a...

We should just add new Unicode characters for Claudisms

mr. TIM@timkellogg.me

Apparently in the next version of Fable, Anthropic changed their tokenizer based on real world usage and made “Let me check rather than answer from memory” into a single token, reportedly saving 43% of all token generation very interesting tinyurl.com/58zf9d3c

We really need to tone down the "developers feel their identity threatened" argument. This is very condescending and borderline bad faith. LLMs have a laundry list of negative effects, we can talk about them for years and won't get even close to identity issues.

It's amazing how LLM driven development is both good and bad at the same time. I don't see any extreme stance on it winning. We'll have to learn how to use this goddamn tool properly: without frying our brains or slopifying software.

I once again have some extra free time on my hands, so I'm going to dig into why DBConnectionErrors are seemingly never grouped correctly and see how many yaks require shaving. Our first stop is naive `Logger.error` calls. We need to figure out what to do with them!

github.comUse reports for logging errors by martosaur · Pull Request #768 · elixir-ecto/postgrexThis PR proposes to log error using report format instead of simple string. The change should be transparent, except for those who potentially relied on log message structure. More Context One of t...

🎉 InstructorLite has passed 50k downloads on Hex! It started as a fork almost 2 years ago and quickly transformed into a full rewrite. I'm very happy that there are people (and companies!) out there who find it useful! #ElixirLang #MyElixirStatus

Spot on. I personally employ 2 tricks to ease the pain: 1. Draft PRs. As soon as you're more or less set on the path, push it and request a review. Once there is something tangible on the table, it's much easier to get feedback. This also forces you into iterative approach.

2. Internalizing the fact that full rewrite is almost always not as bad as it seems. That's just the painful truth of life. First draft is hard, final pass is easy and yields much better result. Kill your darlings!

Looking for an #ElixirLang dev? I'm officially on the market! 4+ years of Elixir in production. Natural affinity to testing, o11y and DX. My most used OS libraries are InstructorLite and PostHog SDK. Remote from 🇨🇦, PDT, links in bio. RTs appreciated 🙏 #MyElixirStatus

View full thread