<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data-Oriented Programming on Professional developer</title><link>https://www.professionaldev.dev/tags/data-oriented-programming/</link><description>Recent content in Data-Oriented Programming on Professional developer</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 16 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.professionaldev.dev/tags/data-oriented-programming/index.xml" rel="self" type="application/rss+xml"/><item><title>Data-Oriented Programming in Java: Move Data to Functions</title><link>https://www.professionaldev.dev/post/java/data_to_functions/</link><pubDate>Fri, 16 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.professionaldev.dev/post/java/data_to_functions/</guid><description>
&lt;p&gt;Your &lt;code&gt;Car&lt;/code&gt; class has twelve methods now. Washing, waxing, polishing, billing — everything that ever needed the car's fields got bolted onto it. Nobody remembers which ones mutate state, and testing &lt;code&gt;scrub&lt;/code&gt; means constructing half the object graph first.&lt;/p&gt;
&lt;p&gt;It's the equivalent of welding the car wash onto the car: the object hauls its machinery everywhere it goes.&lt;/p&gt;
&lt;p&gt;But don't overcorrect — some methods &lt;em&gt;do&lt;/em&gt; belong on a &lt;code&gt;Car&lt;/code&gt;. &lt;code&gt;car.start()&lt;/code&gt;, &lt;code&gt;car.lockDoors()&lt;/code&gt;, &lt;code&gt;car.unlockDoors()&lt;/code&gt; are intrinsic to what a car &lt;em&gt;is&lt;/em&gt;: every car needs them forever, and they touch its own mechanical state. The absurdity isn't methods on objects — it's variable services welded into data.&lt;/p&gt;</description></item></channel></rss>