<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Michael Juliano on Medium]]></title>
        <description><![CDATA[Stories by Michael Juliano on Medium]]></description>
        <link>https://medium.com/@michaelajuliano?source=rss-2a5d6d792d6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*PBOGqzuxV7eMDBQr.png</url>
            <title>Stories by Michael Juliano on Medium</title>
            <link>https://medium.com/@michaelajuliano?source=rss-2a5d6d792d6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 08:00:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@michaelajuliano/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Decision, Expectation, and The Stakeholder]]></title>
            <link>https://medium.com/@michaelajuliano/decision-expectation-and-the-stakeholder-7617d8fb0cf7?source=rss-2a5d6d792d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/7617d8fb0cf7</guid>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[projects]]></category>
            <dc:creator><![CDATA[Michael Juliano]]></dc:creator>
            <pubDate>Sun, 27 Sep 2020 00:34:08 GMT</pubDate>
            <atom:updated>2020-09-27T00:34:08.856Z</atom:updated>
            <content:encoded><![CDATA[<p>A principle is a truth considered to be fundamental in that it is a foundation upon which decisions are based. If a principle is ever shown to yield poor decisions, its truth is called into question. If a decision violates a principle, it is not based on that principle. If a decision is made in the absence of a principle, it is inherently irreproducible insomuch as it had an arbitrary basis which may change in unpredictable ways.</p><p>An expectation is an outcome in which a stakeholder is confident. Every project has one or more cornerstone expectations which can be described as the resolution of one or more problems, problems which prompted the creation of the project. These expectations are non-negotiable insomuch as they form the core reasons behind the existence of the project. If the project fails to meet any of the cornerstone expectations, the project has failed altogether.</p><p>The stakeholders of a project are the people who, as regards the project, stand either to benefit from its successful completion or to be harmed by its failure. It is not necessary for stakeholders to participate in the creation or execution of the project. The project is implicitly conducted on their behalf even without their explicit participation.</p><p>I believe every action in life can be described as a project. The majority of actions we take are simple enough that there is no benefit to the complexity of a formal project definition, but every single action can be described in terms of decisions, expectations, and stakeholders. For actions executed by individuals for their own benefit, the stakeholder and decision maker are the same person.</p><p>A project whose cornerstone expectation is to adhere to certain principles rather than to meet the needs of stakeholders is a risky project. Such projects depend on the decision makers exhibiting an outstanding sense of honor and duty to those principles, a sense which carries the risk of eventually forcing a choice between the principles and the stakeholders which could plunge the decision makers into moral identity crises. Even greater is the risk that decision makers lack the sense of honor and duty to the founding principles required to carry out their role without eventually replacing the project’s principles with their own, thereby derailing and destroying the project.</p><p>Such projects can be described as fundamentalisms which we all have witnessed result in conflicts over practically meaningless distinctions in the service of principles. Principles, themselves, are not to blame. It is the misapplication of principles as cornerstone expectations rather than tools for producing solutions to problems that causes the conflict.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7617d8fb0cf7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MVVM Makes No Sense]]></title>
            <link>https://medium.com/@michaelajuliano/mvvm-makes-no-sense-54687c753da5?source=rss-2a5d6d792d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/54687c753da5</guid>
            <category><![CDATA[mvvm]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[xamarin-forms]]></category>
            <dc:creator><![CDATA[Michael Juliano]]></dc:creator>
            <pubDate>Sun, 06 Oct 2019 06:31:27 GMT</pubDate>
            <atom:updated>2019-10-21T06:48:59.671Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been learning Xamarin.Forms to develop mobile apps, and I’ve been getting along fine in VB.NET using POCOs (real POCOs, not the JavaBean rip-offs). I’ve chosen to consciously ignore MVVM recommendations and instead am sticking to a natural decomposition of the domain into objects with coherent responsibilities that don’t adhere to the totally arbitrary decomposition recommended by MVVM. As a result, my classes are tiny, usually no more than 15 lines of actual code; focused, having a clear role to play in the larger application; and very easy to work with, requiring in many cases only one or two arguments to a constructor before being assigned to a Property from the framework.</p><p>When I design a class, my principle concern is the role the class will play in the application. For example, in the app I’m building as my learning project, I’m putting together a reporting dashboard with widgets that may be configured and added. For me, the natural points of decomposition are the dashboard page which displays the widgets, the widgets themselves which display data, a modal screen for picking a new widget to add, and a bunch of “widget choices” which provide a preview of a widget and forward users on to a modal configuration page if applicable before raising an event notifying the dashboard page that a new widget has been created and should be added. It’s simple and coherent, all the parts have clear roles, and there is very little confusion to be had about how they’re supposed to fit together.</p><p>MVVM, on the other hand, would have us introduce ambiguous, incoherent classes to this formula. First of all, every View would be stripped down to pure layout and would preferably be written in a markup language to avoid the temptation of writing code in it. I guess you could say its role is to look pretty. Then, you’d have to create a ViewModel that would be responsible for “display logic” and that would be connected to the View through “data binding.” I guess you could say its role is to violate the encapsulation of the View and the Model and to serve as a trigger point for the framework to do a ton of work to stitch together what was only separated for the sake of this pattern. Basically, this gives us a useless dummy object, and an object that carries the weight of the world on its shoulders.</p><p>Besides the obvious masochism of forcefully separating everything only to glue it all back together with a complicated framework that apparently works by magic (the class hierarchy for Xamarin.Forms is extremely complicated and basically impossible to understand), the real problem is that it wastes your time and energy by forcing you to worry about adhering to arbitrary (and therefore hard to grasp) ideals instead of about solving the problems that motivated your project.</p><p>It’s not all bad. Xamarin.Forms does actually work, and being able to write cross-platform mobile apps using a proper Object-Oriented Programming Language is a blessing, but MVVM appears to be designed to negate that benefit. Actually, MVVM appears to be designed as a way to organize your C code for writing GUI applications with yet another tacked-on, whiz bang buzzword feature requiring a heavyweight framework (data binding; it’s soooo powerful) which has somehow been elevated to the status of revolutionary (at Microsoft, at least) because it kind of sounds like a variation on something Martin Fowler wrote in a paper once.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54687c753da5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[.NET’s Initializer Syntax is Stupid]]></title>
            <link>https://medium.com/@michaelajuliano/nets-initializer-syntax-is-stupid-591541e50f2e?source=rss-2a5d6d792d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/591541e50f2e</guid>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Michael Juliano]]></dc:creator>
            <pubDate>Fri, 04 Oct 2019 22:06:30 GMT</pubDate>
            <atom:updated>2019-10-04T22:06:30.361Z</atom:updated>
            <content:encoded><![CDATA[<p>Oh, what an idiotic tale this is!</p><h3>A brief, probably inaccurate history.</h3><p>Once upon a time, there was a company called Sun Microsystems who had an Object-Oriented Programming language known as Java. This language held the promise of being able to write code once and run it anywhere. How wonderful! One day, someone had the bright idea to create a standard called JavaBeans to allow objects to be “manipulated visually in an application builder tool.” These JavaBeans should have zero-parameter constructors and should provide access to their internal state through getter and setter methods. This might leave newly instantiated objects in an invalid state and breaks encapsulation, but this was only to support the special case of using application builder tools.</p><p>Visual application builder tools of the sort that inspired JavaBeans didn’t really catch on, but what did catch on was the design for JavaBeans. Fast forward nearly a quarter of a century, and practically every (maybe literally every; I haven’t read them all) Object-Oriented Programming primer for any language written since then <em>recommends that most, if not all classes be designed this way.</em> What’s worse is that the internet is loaded with ridiculous, false, and ridiculously false Teleological arguments like “<a href="http://www.zeuscmd.com/tutorials/cplusplus/50-GettersAndSetters.php">Getters and Setters allow you to effectively protect your data</a>,” or without them, “<a href="https://stackoverflow.com/a/10407925">you cannot add any logic in [the] future to validate the data</a>,” or my favorite, “<a href="https://janedogs.com/history-of-setters/">a Setter … is suitable for fowling partridge or quail</a>.”</p><p>The fact of the matter is that the JavaBeans design was never intended to be a general recommendation for designing classes. Despite this, we not only are told to write classes this way in, like, <a href="https://www.tutorialcup.com/cplusplus/getters-setters.htm">every language,</a> but the languages themselves have features designed to facilitate this cockamamie anti-pattern like Properties in .NET, Groovy, and Dart or .NET’s initializer syntax.</p><h3>Doesn’t initializer syntax fix the problem of newly instantiated objects being in an invalid state?</h3><p>Have you heard of constructors? They’re these magical methods that let you provide data to your new objects when you create them. I honestly cannot believe anyone seriously proposed initializer syntax as a feature or that anyone took that proposal seriously. It is the most ridiculously redundant feature I’ve ever heard of. If you’ve ever found yourself asking, “when should I use a constructor vs an initializer?” then you’re a sane human being capable of rational thought because there is pretty much no difference between the two except their syntax.</p><h3>But what about muh Properties?</h3><p>They’re pretty stupid, too, but they don’t have the whole obviously-redundant thing working against them. They’re more a problem of design philosophy. There are lots of kinds of terrible code, and you probably avoid most of them, but if you can’t imagine writing classes without using Properties or Getters and Setters without just replacing them with direct access to fields, then you probably write really terrible code. The fact of the matter is that Getters and Setters that do nothing but get or set values are no different than directly accessing fields.</p><h3>Understanding Encapsulation</h3><p>For some reason, encapsulation is taught using this vague notion of security for the private members of a class. The sense people get is that as long as my private members have to check in and out at the front desk when entering or exiting my class boundary, then we’re preserving encapsulation. This is utterly and completely false. Encapsulation is the idea that a class boundary is absolute <em>because users of an object are not supposed to care about the internals of the objects their using. </em>I’m sure you’ve heard of tight coupling. Using the internals of an object rather than having the object work exclusively on its own internals is <em>how classes become tightly coupled to one another</em>.</p><p>Instead, objects should expose behavior that acts as a kind of service to other objects. Any state required for the service that shouldn’t change should be provided at construction, and any state that may change should be provided in the method call. There is no third category.</p><p>Unfortunately, this only scratches the surface. A thorough deep dive into all the corners of good Object-Oriented Design would take entirely too much time to write and read, but we’re just getting started. Ask me questions. That’ll help me know what to write about next to help you properly understand the ways in which you were victimized by educational malpractice.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=591541e50f2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lot Full]]></title>
            <link>https://medium.com/@michaelajuliano/lot-full-37ddbe624df8?source=rss-2a5d6d792d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/37ddbe624df8</guid>
            <category><![CDATA[life]]></category>
            <category><![CDATA[waiting]]></category>
            <dc:creator><![CDATA[Michael Juliano]]></dc:creator>
            <pubDate>Mon, 05 Oct 2015 05:09:47 GMT</pubDate>
            <atom:updated>2015-10-05T05:09:47.357Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine that it is 9:00 a.m. on Black Friday, and you are pulling into the parking lot at the mall.</p><p>Imagine that you just arrived at your favorite restaurant, and the host says that there is a 2-hour wait.</p><p>Imagine it is halftime or intermission at a sporting event, and you really have to poo.</p><p>Imagine you sign into Netflix, and it tells you that there are already 2 people watching videos.</p><p><a href="https://www.youtube.com/watch?v=6hPAZ5gMfsE">Get in line</a>. <a href="https://www.youtube.com/watch?v=dDWp-zek4Ic">You don’t want to wait</a>? <a href="https://www.youtube.com/watch?v=3E7_8FWqY9o">Too bad</a>.</p><p>Sorry about the Nickelback link.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37ddbe624df8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Confessions of an Internet Know-It-All]]></title>
            <link>https://medium.com/@michaelajuliano/confessions-of-an-internet-know-it-all-68f45d66c446?source=rss-2a5d6d792d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/68f45d66c446</guid>
            <category><![CDATA[arguments]]></category>
            <category><![CDATA[internet]]></category>
            <dc:creator><![CDATA[Michael Juliano]]></dc:creator>
            <pubDate>Sun, 04 Oct 2015 07:54:35 GMT</pubDate>
            <atom:updated>2015-10-04T08:05:04.259Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever had an argument with someone on the internet?</p><p>I can hear your heads nodding.</p><p>Why on earth do we do this to ourselves? What do we hope to accomplish? Are we masochists, or do we honestly believe that we can convince other people of “the truth?”</p><p>The truth is, by and large, that we want to impress strangers with our “intelligence” and “wit.”</p><p>Is anyone impressed? Probably not. I don’t remember a time where I have read a comment section and thought that either party to an argument was the least bit intelligent or witty. I am the stranger for those people, so I shouldn’t expect my strangers to feel differently about my arguments.</p><p>Maybe we should exchange that time for something more productive like <a href="https://answers.yahoo.com/question/index?qid=20070522101139AATzI4b">asking the internet what to name our pocket lint friends</a> or <a href="http://slothsbeenonmymind.blogspot.com/">blogging about sloths</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68f45d66c446" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>