Database-guy, Typo-maker, Voyager. phd in I told you so, knighthood in.. also, the sky is blue... https://xitter.cf/t.co/CRtkMGGMkb

Rotterdam or Anywhere...
Joined July 2009
Also seen a lot of Storks. Must be a Lucky Day.
15
Had to smile... (Will try not to repeat certain jokes though... sensitive matters there)
Sorry this is fucking hillarious
49
Yep. Good Advice there.
It would be cool if there was a coding language you could run *really* close to the database #iykyk
1
106
The debate on use of AI runs... Here are some things to take into consideration.
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.
1
1
820
Interesting
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.
106
Piet de Visser (Не надо было трогать Мрию!) retweeted
Difference between Developer & Tester
15
389
44
4,073
1,374,728
Should I broadcast this....? (Want to keep for later reference)
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
1
380
Many of the answers make sense. And has anyone seen Murphy around?
Can I ask a dumb question: If a UUID is "practically impossible" to duplicate, why do we still check for duplicates?
139
Piet de Visser (Не надо было трогать Мрию!) retweeted
Pro tip: If the LLM generates code that you cannot understand, it means you need to upskill. Use AI to explain what was generated and provide more resources to help you keep up with the model. Being able to review the code that AI generates will become a mandatory requirement for software engineers.
12
22
2
159
10,354
BOFH level.
The HR department rolled out a massive corporate wellness initiative last month. They gave every department head a $15K budget to improve team mental health and workplace ergonomics. The sales director bought standing desks and ergonomic chairs for his entire floor. I took my $15K and purchased a commercial-grade sensory deprivation tank. I had it installed in the sub-basement next to the primary fiber optic line. When the head of HR asked how a saltwater isolation pod benefited the IT team, I had my answer ready. I told her that managing high-level network topology requires immense cognitive bandwidth. I explained that to visualize complex firewall configurations, my engineers need to achieve a state of 0 sensory input. I called it an "algorithmic meditation chamber." She wrote down the phrase and thanked me for prioritizing mental neuro-plasticity. We don't have any IT engineers. I'm the only person in the department, and my workload is entirely automated by a shell script I wrote during the Obama administration. I spend 3 hours every afternoon floating in body-temperature saltwater in absolute darkness. It's the most peaceful part of my workday. Nobody ever comes down to the sub-basement because I put a sign on the door warning of severe electromagnetic radiation. Yesterday, the CEO sent me an urgent email about a massive spike in dropped packets across our VPN. I was entirely submerged in Epsom salt at the time. I replied 2 hours later saying I had successfully rerouted the traffic while in a deep state of tactical visualization. He replied saying I was the absolute backbone of the company. Corporate wellness isn't about physical health. It's about isolating yourself from the people who sign your paychecks.
1
225
Relevant !
A BBC interviewer asked a Nobel physicist the simplest question in the world: why do two magnets push each other apart. He refused to answer it. What he did instead is the best seven minutes on thinking ever filmed. The man is Richard Feynman, at home in 1983, no blackboard, no notes, sitting in an armchair. He does not dodge because he cannot answer. He dodges because he wants you to see what the question is actually asking. So he takes an ordinary sentence, that a woman slipped on the ice and broke her hip, and starts asking why, and every answer opens another why, until the ground gives way. Then he turns it around on the interviewer with a question about ice that sounds trivial and is not. The point he arrives at is the uncomfortable one. Every explanation is only a translation into something you already accept without explanation. Magnets have no such translation. There is nothing more familiar than magnetism to reduce magnetism to, which is why every answer you were given at school was a picture, not a reason. It matters more now than it did in 1983. Any tool will hand you a fluent answer in a second. Knowing which questions actually have a bottom is the part that is still yours. One question. Seven minutes. It is in the video.
110
Cloud Architect...
Our data center costs have spiked by 400% in the last 6 months. The board hired an external auditor to figure out why we're consuming the energy equivalent of a small European nation. The auditor asked me what exactly is running on the isolated quantum mainframe. I looked at him with disdain and said it was our localized disaster recovery matrix. It isn't. I'm using our enterprise cloud infrastructure to simulate a 1:1 scale digital replica of the Roman Empire. I have 14 million AI citizens currently fighting a civil war inside our AWS architecture. When the marketing department tries to upload a video file, it takes 40 minutes because Emperor Tiberius is actively sieging Gaul on the same processor thread. The auditor pointed out that the data flow was completely unstructured and erratic. I told him he was looking at an asymmetrical neural mesh designed to confuse foreign ransomware protocols. I asked him if he wanted to be the guy who disabled our only defense against international cyber terrorism. He immediately closed his laptop and approved the budget increase. Tomorrow I'm diverting 50 terabytes of RAM to invent gunpowder early.
2
168
Clever!
i can’t believe someone solved recipe design decades ago and everyone just decided to ignore it
2
129
Piet de Visser (Не надо было трогать Мрию!) retweeted
You can create enums in Oracle AI Database 26ai with CREATE DOMAIN color_e AS ENUM ( red, orange, ... ) This maps the names to values from 1 (red = 1, orange = 2, ...) @pdevisser shows how you can use these as Table columns Readable constants in SQL simpleoracledba.blogspot.com…
5
13
1,175
Try stopping that...
The officer who ordered an IFV over a Mariupol barricade now commands Ukraine’s Armed Forces. ㅤ President Volodymyr Zelenskyy has dismissed Gen. Oleksandr Syrskyi and appointed 43-year-old Maj. Gen. Mykhailo Drapatyi as Commander-in-Chief. ㅤ The video is Mariupol, May 9, 2014. Pro-Russian militants had seized the city police headquarters. Drapatyi, then a major commanding a battalion of the 72nd Mechanized Brigade, rode in the first BMP-2 of the relief column. When a barricade blocked the road, he ordered the driver forward. The vehicle used it as a ramp and kept going. ㅤ He later led around 260 troops and more than 30 vehicles out of encirclement near Izvaryne, commanded on the southern and eastern fronts, and helped stop Russia’s 2024 offensive in northern Kharkiv Oblast. ㅤ Ukraine’s new commander-in-chief did not become a symbol because of a speech. He became one because, when the road was blocked, he went first. ㅤ
85
Yes. But some of the on-call weeks are Good Memories now. They were less fun at the time, but now just nice memories.
77
Piet de Visser (Не надо было трогать Мрию!) retweeted
I think AI coding hype follows roughly four stages: 1. Amazement You try it and can’t believe how much code it generates from a few prompts. 2. Expansion You start more and more projects because shipping suddenly feels cheap and fast. This is also the phase where people start convincing everyone around them: - coworkers - management - friends in other companies because nobody wants to “fall behind” in 6–12 months. That creates a massive snowball/FOMO effect. 3. The grind phase You realize the generated code has architectural issues, sloppy mistakes, weird abstractions, duplicated logic, broken edge cases, etc. So you start: - re-prompting - switching models - increasing reasoning effort - reviewing fixes - generating fixes for previous fixes And suddenly you spend your days reviewing AI-generated pull requests instead of building software. 4. Realization You realize AI coding increases output much faster than it increases certainty. The code still needs: - review - testing - ownership - architectural understanding - long-term maintenance Usually by expensive senior engineers. And the interesting thing is: this whole cycle can take many months or even more than a year because people become socially and professionally invested in the narrative themselves. Once teams, managers, and entire companies have been convinced that this is the future, it becomes psychologically and politically very hard to later say: “Actually, the ROI is much lower than we expected.”
🤖 Made with AI
This is what we've been seeing with every company we work with. Try justifying spending 100k on token spend when only 18k even makes it to a stable prod feature. In the rush to maximize AI token spend, companies are wasting over 44% on bug fixes
147
388
63
2,026
202,318