florian25686

PHP-Developer working with Symfony and Pimcore. Blogging to keep a personal Wiki

[Тsфdiиg @tsoding]

You used to be able to just create a Native GUI App in 10 seconds. No Electron, no Game Engines, no Web frameworks. Just a lean fast .EXE produced in seconds. Works on any Windows machine WITHOUT Internet connection. Software Development is actually going backwards.

[florian25686 @florian25686]

Latest addition to my techkit? @KeychronMK Lemokey P1 Pro. It comes with RGB-lights and a feature I never knew I've missed: typed heatmap 😄

[florian25686 @florian25686]

one just starts to write anywhere whatever they want without the need to understand what they are doing.
What a mess! #rant

[florian25686 @florian25686]

Honestly: #JavaScript is a real mess. An event can be overwritten anywhere in the codebase and there is no easy way (not painfully looking through all your existing js-files incl. js-frameworks etc) to find that code. I understand now why it is popular: 1/2🧵

[Laravel News @laravelnews]

Hetzner SDK for Laravel https://t.co/RKnQc7O1Up posted by @paulredmond

[Smaïne - ApiPlatformCon 17/18 Sept. @SmaineDev]

This is crazy !!
#ApiPlatformCon

[florian25686 @florian25686]

@ApiPlatform RIP. I‘ll remember all the hours I‘ve spent learning with you

[florian25686 @florian25686]

Current project, not highly complex so it is good for learning new skills. #FrontendDev #CSS

[Cal Evans @CalEvans]

I’m working on my 3rd “vibe coded” project. This one is about done. All of them have been non-trivial web applications.

I am getting better at it. The first one I threw away 3 version and then just gave up.

The second one I threw away 3 versions. #3 made it into production. (It’s still there but I’m not ready to announce it. It needs some cleanup)

This one I threw away 1 but the second one is about ready for production. Production is a very lose term here because it’s not something I’ll ever let anyone else see other than the lovely and talented @kateva. It’s a tool for us to use. (Ping me and ask, I’ll explain)

So here are my main takeaways from vibe coding.

- You can’t just keep clicking the continue button. I ended up with a truncated database at one point by doing that.

- My indicator that it has overrun its context window is PHP unit. If it tries to use —verbose, I know it’s overrun the window. Most days I have to tell it 10-15 times to use —debug. If you do it long enough, you’ll learn to tell when it’s overrun its context windows and that’s when you have to be careful.

- Gemini Pro is so verbose when coding that a lot of the important things it says like “I did x.” is lost in its apologies for bad code or corrupting a file.

- Save early, save often. Setup a git repo and commit every time things are working. I can’t count the times the agent will corrupt a file or just delete it because it thinks it’s corrupt. If you see it doing that, stop it, check the file out from git and tell it to try again.

Biggest takeaway.

I love coding. Vibe coding is like watching someone else code and then saying “no wait, do this instead”. It’s nowhere near the same rush as bending a computer to your will with bespoke code.

[florian25686 @florian25686]

Read my latest blog about testing nested static-classes https://t.co/uSNK5fqHJH