Piet de Visser (Не надо было трогать Мрию!)

Database-guy, Typo-maker, Voyager.
phd in I told you so, knighthood in..

also, the sky is blue...

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

Also seen a lot of Storks.
Must be a Lucky Day.

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

/* todo: more...*/
That could be me.
(I m still mostly human)

[Programmer Humor @PR0GRAMMERHUM0R]

Human-written code has a signature, and it's a stale README nobody planned to fix.

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

@postgresql_007 @PostgresSupport Enjoy.
Conferences are Great excuses for Road Trips.
I m slowly making my way back from #hroug2026.

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

Had to smile...

(Will try not to repeat certain jokes though... sensitive matters there)

[Asa Hidmark @Nymne]

Sorry this is fucking hillarious

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

@vodafoneNL Als iemand iets achter de schermen heeft gedaan: Dank. Telefoon doet het weer... Ouf.

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

@vodafoneNL : connectie problemen vanuit Austria en Slovenia? is er iets gaande of doe ik wat fout? (zie PM).

Data werkt prima, maar telefonie lijkt niet te werken?

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

@vlad_mihalcea @JavaCro @Hroug_Croatia The party alone is worth it.

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

Yep.
Good Advice there.

[Connor on SQL and Database @connor_mc_d]

It would be cool if there was a coding language you could run *really* close to the database #iykyk

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

The debate on use of AI runs...
Here are some things to take into consideration.

[Vlad Mihalcea @vlad_mihalcea]

Key ideas I got from DevTalksRomania:

- While AI can boost productivity on some specific tasks, great teamwork improves productivity on even more activities. This is like setting up an orchestra, where everyone needs to be tuned and work in synergy.

- Writing tests manually can help you add determinism to your project. Generating both the app code and the test with AI may lead to AI writing tests on hallucinations. This is similar to OSS, where we'd write tests for a bug before implementing the fix.

- When LLMs regress towards the mean, and everyone uses LLMs, the output would be of average quality, but clients don't want to pay for average, so expertise will be very valuable to differentiate from the rest.

- When prototyping with a new tech, do it on an app that's unrelated to your business so that management doesn't promote the prototype to production-ready.

- You can use the Maven daemon, parallel tests, and caching to speed up your build significantly.

- Use linters and verifiers (e.g., ArchUnit) to speed up reviews, especially now that AI can easily generate lots of changes

- Set up a rule in your team so that a PR cannot exceed a threshold of changes (e.g., at most 400 lines of changes), so that it's easier to review and approve one PR at a time.

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

I know a few of those companies...

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

You know who you are...

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

Interesting

[Superman @thesupermannx]

China published the most uncomfortable paper on vibe coding.

ETH Zurich tested 100 developers in a controlled, commercial-grade vibe coding environment to see who actually succeeds.

The findings are brutal.

The researchers tracked computer science achievement, written communication skills, and general cognitive reasoning.

They wanted to see what actually predicts vibe coding proficiency when you never touch a line of source code yourself.

Two major predictors emerged.

Written communication proficiency mattered. The ability to structure thoughts and articulate intent unambiguously in text directly impacts what the AI builds.

But that wasn't even the main takeaway.

Computer science achievement was a massive, dominant predictor of success.

Even when researchers controlled for general intelligence and reasoning skills, CS background still heavily dictated who built working software and who completely crashed.

In fact, CS knowledge contributed roughly twice the unique predictive variance of writing skills alone.

Why? Because vibe coding isn't about writing code. It’s about debugging logic.

When an AI agent builds a complex application and quietly breaks an edge case under the hood, a non-technical user looks at the glowing UI and assumes it works.

They don't know what questions to ask. They don't know what logic to challenge. They lack the mental models to recognize architectural catastrophe.

You can prompt your way past syntax.

You cannot prompt your way past a fundamental lack of engineering intuition.

The hype told us that learning to code is dead because language is all you need.

The data just proved the opposite.

To truly master the vibe, you still need to understand how the machine thinks.

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

@timpastoor @LadyRed_6 BTDT.
Intuition?
Or a tendancy for funny places?

I did consider it Lucky Coincidence, still do.

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

This will turn out Prediction (sans blague)

[Error 404: Humor Found😉 @expensiveaccide]

Difference between Developer & Tester

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

@oelma__ remote

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

@kmcnam1 I'm sure there will be a Black Mirror episode on that (or maybe already is)

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

Should I broadcast this....?
(Want to keep for later reference)

[Sniper Barbie @LadyRed_6]

Nicknames for lazy coworkers:

Cordless - only works for 2 hrs

E.T. - always wants to go home

KitKat - always taking a break

Muffler - always exhausted

Seaweed - just floats around all day

Sensor light - only works if someone walks by

Wheelbarrow - only works when pushed

—expect a visit from HR

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

Many of the answers make sense.

And has anyone seen Murphy around?

[yash.jsx @yashmp2004]

Can I ask a dumb question:

If a UUID is "practically impossible" to duplicate, why do we still check for duplicates?

[Piet de Visser (Не надо было трогать Мрию!) @pdevisser]

@lazy_IT_guy It is true: we pay our software- and SaaS providers to test their products for bugs.

And we pay Extra when we find one, extra time, extra cost, extra workarounds...

Clever vendors.