Ben Bachem

Ben Bachem

@bezbac.dev

Digital generalist working in startups • Based in Berlin, Germany

354 followers356 following224 posts

Had a conversation about this yesterday and I find it crazy how little is actually happening to improve code readability and audibility. Sure, there is A LOT going on and things like x.com/rough__sea/s... are interesting but I feel the topic is dwarfed in comparison to just generating more code.

x.comRyan Dahl (@rough__sea) on XExperimenting with celld in increasingly pathological situations. After merging the replicated write-behind log, this experiment had 4 instances of celld, each on its own machine, and round-robin kill...

Ben Bachem reposted

LLMs are good at making things work when they're broken. I've yet to find a model that will step back and look for ways to avoid similar problems in the future.

I think shadcn's / Radix's trigger elements are a *really* bad design, especially with agentic coding. Agents will gladly create Frankenstein components that render 4 visually unique trigger buttons conditionally to reuse a dialog instead of creating a HOC and wrapping the callsites.

One thing I think the zellij repo could benefit a lot from though is some community management. The original issue existed for more than 2 years with no official acknowledgment & multiple community PRs. I'm pretty sure many of the 1.5k issues are outdated or duplicates.

I'm constantly amazed by how difficult it is to get coding agents to write good React code. I have to constantly fight codex to not add useEffect and refs everywhere.

Ben Bachem reposted

As someone who is contributing to both local-first and atproto I am delighted to see these communities moving closer together. We have a lot of principles and values in common

Local-First Conf@localfirstconf.com

@pfrazee.com is the CTO at @bsky.app and one of the codesigners of the AT Protocol. He's going to talk about the Atmosphere's ideals about open computing, and how the team views tackling scale as core to the mission.

I started a new job this week and so far the experience has been great! The experience of diving into a _huge_ unknown React codebase, that does a lot of things differently from how I am used to, is a bit of a challenge though.

After 5 1/2 years and ~5,000 commits, today is my last day at @ superchat.com. I joined when we had 0 customers and an empty office. We grew to 9,000+ and became the DACH market leader. Incredibly proud of what we built. Excited for what's next — more on that soon. 🎢

Since ESLint 10 is out, I decided to finally reserve some time to migrate from ESLint 8 to 9 @work. This definitely is a whole lot of work...

Just finished the audiobook. Really enjoyed it, especially the earlier chapters.

Ben Bachem@bezbac.dev

I started listening to the audiobook version of „Proto“ a few days ago and both the content and narration is absolutely enchanting www.audible.com/pd/Proto-Aud...

It sounds to polished to me to be AI, but maybe I'm just not aware of the current state of the art. Most of the artists in the playlist have a generic name, no bio except a mention of mention neorecordings@gmail.com and only a single released song. They also all share a similar style of logo

Ben Bachem reposted

Replying to @meredithmeredith.bsky.social

Engaging in mental gymnastics to justify what's convenient but unevidenced, unjust but personally beneficial, 'rewires your neural map' in ways that degrade your overall ability to understand and analyze the world around you, which is a precondition for intelligence and creativity.

Ben Bachem reposted

Replying to @erlend.sh

Capitalism to me implies antitrust and strong regulators. It also does not imply anti labor rights, but equity for employees and workers. I am however strongly against dividing employers and employees in groups that should fight against each other. Nothing good comes from that.

I spent way to much time yesterday fighting the borrow checker over something I _knew_ shouldn’t work. Safe so say, it won.

Copilot one-shotted a custom ESLint rule for me a few days ago and then one-shotted the fix command with a second prompt, I just had to write the test cases. IMO lowering the effort / cost of custom ESLint functions could lead to much more consistent code, so I'm very exited about it!

I feel stupid for only realizing yesterday that you can run git clone and git push against any machine addressable via SSH without any custom software running on it 🤯

Just wrote a parameterized test in Kotlin for the first time. Being able to simply reference a method to generate all the test cases is quite handy 👌