Ferdinand Kramer

👨‍💻 Senior Developer @ui_interact | 🎱 1. Snooker & Billard Club Bielefeld e.V. | ⚽ Kickerfeld Kickern in Bielefeld

[Ferdinand Kramer @fk41n_]

Zum Beispiel wie bei Fentanyl in den USA. Blöd, dass das in Deutschland so reglementiert wird.

[Antoine Richard @AntoineRichard]

Sie kann seit 10 Jahren weder aufstehen, noch gehen! Innovation und Technik rettet und verbessert Leben! Sie kann nur in einem freien Markt gedeihen! Je freier die Märkte sind, desto mehr medizinischer Fortschritt!

[Ferdinand Kramer @fk41n_]

@DieSkeptikerin Dieter N.?

[Ferdinand Kramer @fk41n_]

@IchHabeFragen73 @PeterSinse @SoerenLorensen Leberkäse

[Ferdinand Kramer @fk41n_]

This is because it doesn't understand.

[Tom Johnson @tomjohndesign]

This is how I feel about vibe coding.

Any project I try that has any kind of complication has this immediate burst of progress. Things are amazing and it feels like a superpower. Then... as I add more complexity, things crash to a halt.

The only projects that I think I can create are ones that fall in this "vibe zone". Prototypes, UIs, products—anything that's simple and has low complexity fits right in that zone. Proof of concepts, interactions, stuff like that. The tools are able to make things that fit in that slot.

But.

Everything falls to pieces as that complexity curve increases. And the problem is that any good product design process has increasing complexity. A basic prototype turns into a good prototype as soon as it has layered interactions, transitions, good affordances, hover states, 1000 tiny little details that make something feel correct and real.

The benefit of vibe coding is supposed to be that you move fast and you can whip things out—letting AI do all the work for you. The problem is it loses steam as soon as the necessary complexity is added. It keeps redoing itself, rewriting code, affecting things that are unrelated and then causing other issues.

But if you add that complexity, every vibe coding session quickly turns into a whack-a-mole bug-bashing session.

I'm not sure the solution to this. With traditional prototyping the solution is to duplicate, add more complexity, create more frames/scenes, tweak, fork, etc.

However with vibe coding, one little prompt can destroy literally everything. There's a stage where I end up walking on prompt eggshells-- trying not to give it too much or too little context so that it doesn't go rogue and break everything.

There's only a few exceptions to this. @cursor and @framer.

I can make great progress with Cursor, give it narrow context, and I have to approve the edits that it makes. This feels like a correct workflow. The problem is, I can't see the thing that it's making because it's an IDE, not a visual environment. Yes, I can create local builds and refresh my browser and all that kind of stuff. But the visual aspect is totally lost from the coding experience. It's a developer tool.

Framer gets this right because it only allows narrow updates within a single component on the page. Yes, it's limiting because it can only do a single thing at once, but at least it's not trying to create the entire page from scratch and manage it all through a prompt interface.

These seem like the right approach.

@Cursor: Allow the AI to edit anything but allow the user to approve those edits and see them in context.

@Framer: Allow the AI to only narrowly edit a single file or component to keep the complexity down to a minimum and reduce catastrophic edits.

I'm optimistic that tools like @Figma, @Lovable, @Bolt, and @V0 can make cool prototypes, but I just keep running into walls when it comes to doing anything more than just a basic interaction prototype. They need to do less IMO.

Hopeful that those tools add more controls that are in the same line as Cursor and Framer. I'll also add that this is similar to how we do it with @Basedash chart generation as well. But we're not a vibe tool in the normal sense so the parallels are a little bit harder to draw.

[Ferdinand Kramer @fk41n_]

@grok gibt es viele flugzeugtypen die mit erneuerbaren Treibstoff betankt werden können?

[Hubert Aiwanger @HubertAiwanger]

Die Klimakleberzeit ist zu Ende, wir bauen wieder Flugzeuge in Deutschland! Vorstellung der neuen D328eco in Oberpfaffenhofen/Bayern. Entwicklung in Bayern, Fertigung in Leipzig/Sachsen. 40% weniger Treibstoffbedarf, kann mit erneuerbaren Treibstoffen betankt werden, 43 Passagiere, Markteinführung 2026/27. Gut Flug!

[Ferdinand Kramer @fk41n_]

@marcfriedrich Quetscher

[Ferdinand Kramer @fk41n_]

@jenny_nass26 Wenn man Fahrradwege baut hagelt es?

[Ferdinand Kramer @fk41n_]

@Jensin520 @MarcoFoster_ @joesantarlasci @liberal_party Half of you voted for him?

[Ferdinand Kramer @fk41n_]

@MiRo_SPD Kann ich den Globus haben?

[Josef NATO @JosefBrato]

guckt mal was eine lächerliche Show sie abgezogen haben um zu zeigen, dass sie die Stromverbindung nach Russland abstellen hahahahahahaha

[Ferdinand Kramer @fk41n_]

@system76 Suse 2003

[Ferdinand Kramer @fk41n_]

@DFurneaux Nothing has happened

[Aes🇺🇸 @AesPolitics1]

Taken to the cleaners.💀

[Ferdinand Kramer @fk41n_]

@BGatesIsaPyscho https://t.co/jNlaCOuDlF

[Ferdinand Kramer @fk41n_]

@DFurneaux @remindmetweets in 10 days

[Ferdinand Kramer @fk41n_]

@DFurneaux @RemindMeOfThis 01.01.2025

[Grant Slatton @GrantSlatton]

The junior dev asked the senior dev “why are you pushing this code with no abstraction? What if you want to change it in the future?”

The senior dev responded “then I will change it in the future”

In that moment the junior dev was enlightened

[Ferdinand Kramer @fk41n_]

@animeeagel Chili con carne

[Wes Bos @wesbos]

CSS can FINALLY animate height: auto!

[Ferdinand Kramer @fk41n_]

Deutscher Alex Jones

[Matthias Hauer 🇩🇪🇪🇺 @MatthiasHauer]

Nein, @jreichelt, ARD und ZDF rufen NICHT zum Mord an Menschen auf.

Natürlich waren die Aussagen von @elhotzo mehr als daneben (und auch gefährlich) - aber #Hotz vertritt weder ARD noch ZDF. #NIUS ist und bleibt eine Fake-Schleuder mit Dauer-Agitation.