hm https://github.com/bluesky-social/social-app/blob/main/CLAUDE.md

[eramdam@social.erambert.me]

@cwebber yeah, least surprising Bluesky thing to do

[fay@lingo.lol]

@erincandescent
@res260 @cwebber we have tools for that tho? templates and libraries and bootstrapping and automation tools. they don't have to be, as @olivia so said a couple month ago "made from shit and blood"

[erincandescent@akko.erincandescent.net]

@fay @res260 @cwebber there's lots of code for which no reusable template could be created that is nonetheless rote

[erincandescent@akko.erincandescent.net]

@fay @cwebber @res260 is this a failure of ours? Perhaps. But it's the sum product of millions of small failures, not something easily corrected

[theesm@social.tchncs.de]

@cwebber oof, always wonder what review processes are in place at places where a large portion of changes have been vibecoded. I tend to discuss why a certain implementation has been picked, what pitfalls have been considered, if a solution is adequate to a problem etc. when reviewing major changes with engineers whose code I review, "claude did that" wouldn't really stand as an answer in my book. Makes me wonder if that kind of discussion just isn't common anymore? this whole agent stuff just seems like a big footgun to me that will inevitably lead to hard to comprehend and more difficult to navigate/to maintain codebases

[fay@lingo.lol]

@erincandescent @res260 @cwebber respectfully, that's not my experience If the task is specific enough to require human intervention, then it shouldn't be left to a stochastic code generator either

[fay@lingo.lol]

@erincandescent @res260 @cwebber with the hundreds of billions of dollars burned to make stochastic code generators that only sort of work (and at horrific ethical costs), i dare say that we could have developed adequate tooling instead, and we still can

[erincandescent@akko.erincandescent.net]

@fay @res260 @cwebber it's a coordination problem, not an effort problem. If everyone agreed to use the one serialisation format with the one schema language, with the one runtime environment, ...

[fay@lingo.lol]

@erincandescent @res260 @cwebber i mean a lot of people are agreeing to use the one llm right now, it seems

[aslakr@mastodon.social]

@cwebber Is there something funky going on? bsky seems to be down, at least in Europe.

And the post seems blocked by a labeler in blacksky https://blacksky.community/profile/did:plc:ragtjsm2j2vknwkz3zp4oxrd/post/3meogr22l3k2d

[cwebber@social.coop]

Welp, there we go https://bsky.app/profile/why.bsky.team/post/3mgaqaaisfs2e

> Oh interesting, people who don’t know how to build software are getting mad at my post about building software. Cute.
>
> Let me be clear, over the next year, the job of software engineer will shift dramatically to no longer have typing syntax into an editor as its primary time sink.

[fay@lingo.lol]

@cwebber yeah he's still his insufferable arrogant idiot self

[kats@chaosfem.tw]

@cwebber Typing is their primary timesink while developing? Not thinking?

[itamarst@hachyderm.io]

@cwebber The idea that the primary timesink of a software engineer is typing is bizarre.

[brad@m.toad.host]

@cwebber I'm really not a huge fan of how ready people seem to be to just completely relinquish their ability to code. It does not take long for your brain to wallpaper over entire skillsets.

[faoluin@chitter.xyz]

@cwebber LLMs write better code* until the investors come knocking for their payouts, then the price goes up and LLMs aren't writing any code.

* they don't

[brad@m.toad.host]

@cwebber also, I can see this type of situation very, very easily spiraling into a classic "death by convenience."
How long until the primary engineers no longer understand the how their program is built or what motivated ostensibly insignificant decisions that eventually add up