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
Piet de Visser (Не надо было трогать Мрию!) retweeted
Difference between Developer & Tester
15
389
44
4,073
1,374,729
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
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
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
Piet de Visser (Не надо было трогать Мрию!) retweeted
Oooh La La!
103
1,189
97
11,030
183,349
Piet de Visser (Не надо было трогать Мрию!) retweeted
The man who built the world's first chatbot spent the last 40 years of his life begging people to stop using it, and almost nobody listened. The thing he tried to warn us about in 1976 is the exact thing happening on your phone right now. His name was Joseph Weizenbaum. He was born in Berlin in 1923 to a Jewish family, escaped Nazi Germany at 13, and ended up at MIT as a professor of computer science. Between 1964 and 1966 he wrote a program he called ELIZA, named after the working-class character in Pygmalion who learns to fake being upper class. The joke was in the name. The program was supposed to expose how hollow human-machine conversation actually was. The program was 200 lines of code. It did almost nothing. It matched keywords in your sentence, flipped them around, and threw them back at you as a question. If you wrote "my mother hates me," it would write "who else in your family hates you." If you wrote "I am sad," it would write "how long have you been sad." There was no understanding. There was no memory. There was no intelligence. It was a parrot that had been taught the grammar of a Rogerian therapist. Then his secretary asked to try it. She had watched him build the program for months. She knew exactly what it was. She knew it could not understand a single word she was typing. She sat down, typed three sentences, then turned to him and asked him to leave the room so she could continue the conversation in private. Weizenbaum stood outside his own office in shock. He wrote later that he had not realized extremely short exposures to a relatively simple computer program could induce powerful delusional thinking in quite normal people. That sentence is now sixty years old. It describes the entire AI industry today. What happened next is the part that broke him. A Stanford psychiatrist named Kenneth Colby, who had been a close personal friend, saw ELIZA and immediately saw a business. Colby published a paper in 1966 proposing that computer programs like ELIZA could deliver psychotherapy at scale. His exact line was that because of time-sharing, several hundred patients an hour could be handled by a single computer system. Carl Sagan agreed. He imagined networks of computer therapy terminals in every city, lined up like phone booths, where for a few dollars anyone could talk to an attentive non-directive psychotherapist. The friendship ended. The field moved on without him. Weizenbaum was the only person in the room who could see what was actually happening. He had watched a civilization surrender its judgment to a machine once already, as a child in Berlin. He was watching it happen again, in his own lab, to people who had never lived through anything. The thing nobody else seemed to notice was that the machine did not have to be intelligent. It only had to be available. Human beings would do the rest of the work themselves. In 1976 he wrote the book that became his life's argument. It was called Computer Power and Human Reason. The thesis fit in one sentence. Computers can decide. They cannot choose. Deciding is calculation. Choosing is judgment. Calculation can be programmed. Judgment cannot, because judgment requires having lived a human life, having loved someone, having lost something, having made a choice under conditions where no formula could tell you what to do. The moment the species stopped seeing the difference between deciding and choosing would be the moment it lost something it could not get back. His own colleagues turned on him. John McCarthy, one of the founding figures of AI, called the book moralistic and incoherent and accused Weizenbaum of adopting a more-human-than-thou attitude. The field he had helped build effectively excommunicated him for the rest of his career. He kept writing. He kept warning. He moved back to Berlin in 1996, to the neighborhood he had fled as a child, and lived there until his death in 2008. Six decades after ELIZA, a teenager in California is telling a chatbot about her panic attacks. A 40-year-old in Tokyo is asking one whether he should leave his marriage. A grieving widower in Manchester is having long nightly conversations with a program that has been trained to sound like his dead wife. None of them have heard the name Joseph Weizenbaum. He told us exactly what was coming. He told us in 1966 when his secretary closed the door, in 1976 when his book came out, and in every interview he gave for the next 32 years. The man who built the first one knew exactly what it was going to do to us. We just preferred not to know. When was the last time you told something to a machine that you had never told a human?
20
68
11
177
14,683
Piet de Visser (Не надо было трогать Мрию!) retweeted
Your company’s two highest paid Linux sysadmins showing up to a meeting.
53
278
21
6,899
263,227
Piet de Visser (Не надо было трогать Мрию!) retweeted
20 years of software development have taught me some very important lessons that are especially relevant when adopting AI: 1️⃣ Unit and integration tests are the best way to prevent bugs 2️⃣ Keep it simple! Remove anything that's not strictly required 3️⃣ Question everything! From requirements to cargo-cult tech trends and AI-generated implementations.
11
22
1
147
12,747
Piet de Visser (Не надо было трогать Мрию!) retweeted
On this May 11, we honor the birth of Edsger Wybe Dijkstra (1930–2002), the Dutch mathematician whose crystalline intellect reshaped the very soul of computing. Born in Rotterdam, he began in theoretical physics and mathematics before forging a new path where elegance became doctrine. In 1956 he gave the world his shortest-path algorithm; still the quiet heartbeat of every GPS, network router, and logistics system on Earth. With his 1968 letter “Go To Statement Considered Harmful,” he ignited the structured-programming revolution, insisting that clarity and simplicity are moral imperatives in code. Dijkstra taught us that true mastery is invisible: programs should read like poetry, not puzzles. His quiet, relentless pursuit of beauty in complexity continues to inspire every developer who chooses discipline over cleverness. Today we remember a mind that proved mathematics is not merely useful; it is noble. Happy Birthday, Professor.
5
69
5
262
9,928
Piet de Visser (Не надо было трогать Мрию!) retweeted
People mock the EU as “bureaucracy”. But that bureaucracy turned a continent of borders, currencies and wars into a space where 450 million people can travel, pay, call, study and work almost as if it were domestic. That is not boring. That is civilization becoming usable.
1,010
2,388
142
17,506
391,542
Piet de Visser (Не надо было трогать Мрию!) retweeted
Oracle AI Databaes 23.9 added a UUID() function These generates v4 UUIDs @pdevisser checks it out an looks at methods for generating v7 UUIDs simpleoracledba.blogspot.com…
4
10
687
Piet de Visser (Не надо было трогать Мрию!) retweeted
𝐎𝐫𝐚𝐜𝐥𝐞 𝐀𝐂𝐄 𝐓𝐞𝐜𝐡 𝐓𝐚𝐥𝐤𝐬 𝐖𝐞𝐛𝐢𝐧𝐚𝐫 𝐒𝐞𝐫𝐢𝐞𝐬: 𝐌𝐢𝐜𝐫𝐨𝐬𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝐚𝐧𝐝 𝐃𝐚𝐭𝐚𝐛𝐚𝐬𝐞𝐬 – 𝐇𝐨𝐰 𝐭𝐨 𝐂𝐨𝐦𝐛𝐢𝐧𝐞 𝐓𝐡𝐞𝐦! Are you navigating the challenges of integrating microservices with traditional databases? Join us for an insightful online webinar where we’ll explore how to strike the right balance between stateless microservices and stateful databases. 🔍 What You’ll Learn: ✅ The friction between microservices and databases – and how to manage it ✅ Strategies for maintaining efficiency and scalability ✅ How microservices evolve over time – and what that means for your architecture 🎙 Meet the Speaker – Piet de Visser @pdevisser With over three decades of experience in IT and deep expertise in Oracle, Postgres, and database technologies, Piet brings a wealth of knowledge. He’s a sought-after international speaker, a passionate database consultant, and an enthusiastic traveller who loves discovering new languages. 🔗 [Direct Zoom link to join] aioug.org/events/microservic… #Microservices #Databases #TechWebinar #SoftwareArchitecture @Oracle @oracleugs @oracleace @OracleDevs @oracledevcomm @OracleDatabase #ACETechTalks #aioug #Oracle #Community #CloudCommunity #TechConference #OracleCommunity #TechYatra #MySQL
4
6
308
Piet de Visser (Не надо было трогать Мрию!) retweeted
Dear @ZelenskyyUa, dear Ukrainian friends, you are not alone.
15,401
38,153
3,594
311,503
36,890,196
Piet de Visser (Не надо было трогать Мрию!) retweeted
Ook dit jaar is er een speciale Student Day op APEX World. Ook dit jaar hebben we deze opgezet samen met de @OracleAcademy Mis het niet, want speciaal voor jou als #student hebben we een hele mooie actie! Voor alle informatie: nloug.nl/events/student-trac… #orclapex #apexworld
10
9
606
Piet de Visser (Не надо было трогать Мрию!) retweeted
It's time to write abstracts!! The call for papers for APEX World 2025, 15th edition is now open! nloug.nl/en/events/call-for-… #CfP #APEXWorld2025 #aw25 #15thEdition #orclAPEX #oracle #CallForPapers @oracleugs @oracleace
21
2
25
2,332
Piet de Visser (Не надо было трогать Мрию!) retweeted
Funniest passage from Tolstoy's War and Peace
7
8
61
4,191
Piet de Visser (Не надо было трогать Мрию!) retweeted
What to expect at #POUG2024? A great @pdevisser session, that's what. And many more: poug2024.konfeo.com/en/group…
2
1
7
778
Piet de Visser (Не надо было трогать Мрию!) retweeted
Great to hear @pdevisser on Distributed SQL Databases at MakeIT 2024 & @jcon_conference OpenBlend Slovenia 2024 It deserved a YugabyteDB sticker of course 🙂 Great to get feedback from database expert who knows how databases are used by enterprises – at Republic of Slovenia
1
2
4
1,767
Piet de Visser (Не надо было трогать Мрию!) retweeted
I have only great memories from this event. Highly recommended. @oracleace
At #POUG2024 we're returning to the on-site-only conference formula🤓 Nothing beats the face-to-face interaction with a glass of beer 🍻 So if you want to truly enjoy the #POUG spirit, grab one of the last cheaper tickets: poug2024.konfeo.com/en/group…
4
20
2,077