<?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 Peter B Smith on Medium]]></title>
        <description><![CDATA[Stories by Peter B Smith on Medium]]></description>
        <link>https://medium.com/@peterbsmyth?source=rss-b9a4bc298f3c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*iH5dIWHx4lAdZHz37MIdQw.jpeg</url>
            <title>Stories by Peter B Smith on Medium</title>
            <link>https://medium.com/@peterbsmyth?source=rss-b9a4bc298f3c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:09:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@peterbsmyth/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[7 truly stupid tips on giving software talks for anyone who has never done it before]]></title>
            <link>https://medium.com/upstate-interactive/7-truly-stupid-tips-on-giving-software-talks-for-anyone-who-has-never-done-it-before-232ca6bbc1f3?source=rss-b9a4bc298f3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/232ca6bbc1f3</guid>
            <category><![CDATA[talks]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[public-speaking]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Peter B Smith]]></dc:creator>
            <pubDate>Fri, 08 Jan 2021 20:48:32 GMT</pubDate>
            <atom:updated>2021-04-01T12:08:57.303Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*C0OJINIO_nOPAn1A.jpg" /></figure><h3>7 Tips for Talks: Software Edition</h3><h4>Take it from me, an expert software-talk-giver</h4><p>I won’t pretend to have any tips for folks who have experience with giving talks. I am not a public speaker professionally.</p><p>I have done three talks at AngularNYC, Google’s Headquarters, and CapitalOne’s headquarters in Manhattan. I have done a talk at AngularBoston. I have done a talk at jsMobileConf. I have done many talks around my home city of Syracuse, NY. I have done more Zoom talks in the last 12 months than I would have ever considered. If you’re interested and have a spare couple of hours, you can find links to all of those at the bottom of this article.</p><p>My recipe for success looks something like the outline below. These tips work for me, and maybe they will work for you.</p><ol><li><strong>Make stuff up. </strong>I don’t mean to pretend that fact is true when it’s not. I mean start off by writing out all of the possible ideas that come to mind on a topic. When I do this it looks like a markdown document with bullet points of links to lines of code, links to images, and short sentences. It helps to put it in a format that is not going to be the final. Consider this the precursor to a slide deck.</li><li><strong>Pretend you are someone else. </strong>Either in your mind or on the web, take a look at any speaker whose talk you have enjoyed. Then review step 1 and give the talk imitating that speaker. I do this to remind myself that when speaking in front of others there is a certain amount of distance from my day-to-day personality that needs to be maintained. It’s a good way to self-check that I am talking about the topic at hand, rather than being self-conscious.</li><li><strong>Assume no one will remember a word. </strong>Your words can be lengthy or short. They can be about a technology that the audience has never even used. All software talks are inherently logical. The truth is, if anyone wants to get the most out of a talk, they will need to review the talk on YouTube later. I typically go one of two directions from this assumption: either I figure out some core takeaway that I want to leave the audience with and repeat it over and over OR I go into great depth knowing that after everyone has checked out and logged into the social apps that they may revisit the topic on YouTube later.</li><li><strong>Wear whatever you want. </strong>Could there be any audience less bothered by what a presenter is wearing than a software audience? Avoid grease-stained pants and t-shirts with holes. After that, well, find your nicest t-shirt, your most leisurely sweatpants, your top-of-the-line suit, your perfectly accessorized attire. I wear suits and ties. I wear button-down shirts untucked. It doesn’t matter. I tell myself that as long as I can be as well-informed and articulated then I can just about wear anything.</li><li><strong>Don’t practice in front of your friends. </strong>Your friends may know what you are talking about. What they won’t know is what you look and sound like to a group of people who have never seen or heard you before. Friends are good for sharing an interest. Organizers are good for practicing a talk. I have been offered by organizers to preview my talk to them beforehand. I am glad that they did. I also have requested that organizers review my talks in advance. I have also given talks with friends, sharing the stage side-by-side. In those situations, we have practiced the talk in front of organizers or small audiences at local meetups before the main event. Basically, I have not ever wanted to know from a friend what they think of my software talk. More relevant audiences have always been available.</li><li><strong>Act nervous. </strong>Seriously. Act nervous. What does nervousness look like? To me, it is eyes pointed at the screen, it is a quiet voice, it is rushing through a bunch of slides. I have done all of those things. In college, at StartupWeekend events, it was my natural response to being in front of people, and it was unintentional. In all the talks below, I learned how to use it to my benefit. At the beginning of the talk, I still do all of that nervous behavior to set a starting point for the audience as a nervous speaker. Within the first minutes of the talk, as I am getting into the content I prepared, my voice naturally grows in strength, my eyes do their thing, and my pace becomes calm. What the audience sees is a progression from nervousness to confidence.</li><li><strong>Drink when it is over. </strong>Get a glass<strong> </strong>of alcohol or water or coffee. Take your drink to a group of people from the audience who are chatting away and say hello. There’s no need to ask them what they thought about your talk, they saw it, they will tell you on their own. Once you finish your drink and leave for the day, take whatever you heard and use it for your next talk. I am happy to hear any comments, I prefer the good and use the bad. I regularly go up to audience members after a talk and sometimes they come up to me.</li></ol><p>If you want to see any of the talks that I have given, check them out at <a href="https://resources.upstateinteractive.io/software-talk">Upstate Interactive Software Talk</a>.</p><figure><a href="https://upstateinteractive.io/contact/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iwSlVd3lGBS1ibN_.jpg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=232ca6bbc1f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/upstate-interactive/7-truly-stupid-tips-on-giving-software-talks-for-anyone-who-has-never-done-it-before-232ca6bbc1f3">7 truly stupid tips on giving software talks for anyone who has never done it before</a> was originally published in <a href="https://medium.com/upstate-interactive">Upstate Interactive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What are Functional Components? Your keys to the software kingdom.]]></title>
            <link>https://medium.com/upstate-interactive/what-are-functional-components-your-keys-to-the-software-kingdom-336b67b3ed1e?source=rss-b9a4bc298f3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/336b67b3ed1e</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Peter B Smith]]></dc:creator>
            <pubDate>Fri, 08 Jan 2021 17:54:41 GMT</pubDate>
            <atom:updated>2021-04-05T10:33:06.755Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>It all begins and ends with functional components.</strong></h4><figure><img alt="Flyover view of multiple functional components." src="https://cdn-images-1.medium.com/max/1024/1*klDY7NOtzjwBb3KZf2HI6w.jpeg" /></figure><p>When we start doing design in the first sprints of the project we start in the code editor. <a href="https://upstateinteractive.io/software/">Our process</a> includes white-boarding and low quality wireframes as communication tools to get the core functionality understood and our process excludes delivering high quality design mockups from static design tools like Sketch or Photoshop. Why do we exclude them? We can be as fast in the browser as we can be in Sketch, the difference is that in the browser we will have built the functional components that can form a prototype and in Sketch we will be far from a prototype.</p><h4><strong>What are functional components?</strong></h4><p>Web pages are built from documents. Web applications are built from components. Form inputs are the easiest components to recognize; a date input that has a calendar to choose the dates; a text input that makes suggestions on what to search for based on what you have started typing. These are components that can be used and reused in an application in multiple places. Another type of component is a display component; graphs and charts that take in data of a certain format and display the results; cards that show a user’s profile information that can be swiped from left to right to remove it from the screen. These components may appear in different places in the application to give users data they need to see.</p><h4><strong>Where do functional components fit in the development process?</strong></h4><p>On our development team, we have a role called “<a href="https://medium.com/upstate-interactive/what-is-a-design-technologist-an-interview-with-james-patrick-952fa020fffa">Design Technologist</a>.” This engineering role specializes in building the parts of the application that the user sees and interacts with. A Design Technologist is capable of building most of a prototype without reaching into skillsets like data management or application deployment. The components a design technologist builds are the same components as a front-end developer uses to make the application usable.</p><p>In the process of building functional components design patterns like color, spacing, and typography begin to take root in the application. With the reality that an application needs to be consistent from view to view the design technology builds consistent patterns into the application from the start. As in, when building functional components the design technologist is laying the foundation of the application’s look and feel. These are done with design tokens.</p><h4><strong>How do functional components compare to high fidelity mockups?</strong></h4><p><em>Mockups</em></p><ul><li>Still need to be turned into functional components</li><li>Are not written in the same language as web developers work in</li><li>Can be built without respect to what is achievable or implementable</li></ul><p><em>Functional Components</em></p><ul><li>When they work in the prototype they work in the usable application</li><li>Make use of the technology that is available in the web browser</li><li>Are written in the same language and therefore can be built collaboratively with developers</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bC2xiu2rLKFkpivoZUcuig.jpeg" /></figure><h4><strong>Comparing Functional Component Options</strong></h4><p><strong><em>Off the shelf</em></strong></p><p>Off the shelf components are either free or paid software libraries. Often the paid ones are not as good as the free ones, simply because the free ones are more widely used, receive more scrutiny, and are subject to more environments. Paid options can be better when specific functionality is highly complex and requires significant investment.</p><p>The best paid, off the shelf component is <a href="https://www.ag-grid.com/">ag-grid</a>. The makers know it, marketing their product as, “the best javascript grid in the world.” The grid costs over $1,000. When used in financial applications that handle the flow of billions of dollars of transactions, it makes sense. In the Angular development environment, there is no better general-purpose off the shelf set of components than Angular Material. These components are freely available for usage in any application and are developed by Google engineers as well as community contributors. They also happily meet all standards for accessibility (usable by blind and deaf people).</p><p><strong><em>Custom</em></strong></p><p>Custom components are built from nothing to serve the application they are being used in. Building custom functional components can mean duplicating functionality available from off the shelf component libraries with the customization being primarily to the styling. Custom components can also mean creating unique functionality that your application requires that off the shelf components do not provide. An example custom component that I have built is a “typeahead,” also known as an “autocomplete.” The project it is used in has complex data types that are being searched for and the autocomplete needs to display a list of that data as the user is typing. Off the shelf autocomplete components are not made to handle complex data and a custom component is necessary.</p><h4><em>Deciding between off the shelf and custom components</em></h4><p>Every project is different and every situation bears review before making a choice.</p><p><strong><em>Off the shelf components</em></strong></p><ul><li>Good for prototypes to get something in front of users as fast as possible</li><li>Good for internal enterprise projects where the return on investment is prioritized</li><li>Good for companies that do not rely on the project to represent their brand</li></ul><p><strong><em>Custom components</em></strong></p><ul><li>Good for projects that have highly individual user interaction needs</li><li>Good for companies for whom the project is a core part of their brand</li><li>Good for public-facing consumer projects where the look-and-feel is synonymous with the product</li></ul><figure><a href="https://upstateinteractive.io/contact/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qrDSrA6Iz0d7SClLQIxoHQ.jpeg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=336b67b3ed1e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/upstate-interactive/what-are-functional-components-your-keys-to-the-software-kingdom-336b67b3ed1e">What are Functional Components? Your keys to the software kingdom.</a> was originally published in <a href="https://medium.com/upstate-interactive">Upstate Interactive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Standards  of Software Quality: Prototype, Usable, and Complete]]></title>
            <link>https://medium.com/upstate-interactive/3-standards-of-software-quality-prototype-usable-and-complete-95e5d699e917?source=rss-b9a4bc298f3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/95e5d699e917</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Peter B Smith]]></dc:creator>
            <pubDate>Fri, 08 Jan 2021 17:49:39 GMT</pubDate>
            <atom:updated>2021-04-05T10:31:54.881Z</atom:updated>
            <content:encoded><![CDATA[<h3>3 Standards of Software Quality</h3><h4>Prototype, Usable, and Complete</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bSr095MK5DscNKhZBms3CQ.jpeg" /><figcaption>Software evolves forever.</figcaption></figure><h4><strong><em>Software Prototypes are built for growth.</em></strong></h4><p>Poorly built small applications and <a href="https://upstateinteractive.io/software/">software prototypes</a> are not the same. A poorly built small application can have the appearance of being close to usable and at the same time be difficult to maintain, hard to iterate on, and time-consuming to debug. A software prototype can have the appearance of being close to usable and are…</p><blockquote>built for additional functionality</blockquote><p>A prototype’s purpose is generally to experiment with design and performance without building out all of the necessary infrastructures required to make the application fully usable. This is achievable by making highly prioritized features demonstrable. In the example of a mass-market consumer application, demonstrable properties will likely include <em>look-and-feel</em> as a priority. For an internal enterprise application, demonstrable will likely contain all actions to get a business process completed.</p><p>Once the definition of demonstrable is determined, then the prototype is built to allow those benefits to be realized by extending the application. Extending the application means writing a new code to complete the functionality more than rewriting existing code to fix shortcuts.</p><blockquote>thoughtful, same as a production application</blockquote><p>A software prototype is built to grow. That’s why thoughtful development must be at the heart of the build. A commonly significant phase during the application development process is the data modeling stage. Simply, an application fundamentally relies on data to be output to the user. The model and the shape of that data informs the complexity of the final application. Data modeling during the application&#39;s prototyping gives the application a faster development velocity than starting from a prototype. This is because the functionality of the application is tightly glued to the way it works with data.</p><p>When the data model is altered, many parts of the application have to be altered to accommodate the change. Thoughtful modeling of the data is only one part of prototyping. Managing the flow of data, managing the application&#39;s state, managing the complexity of the components that the application is built from, all of these practices and more are fundamental at the earliest stages of prototyping.</p><blockquote>without many debugging needs</blockquote><p>A prototype that has a high need for debugging is most probably going to lead to a completed application that has a codebase that is near impossible to debug. Prototypes provide simple demonstrations of core functionality, and because of their simplicity, there is not much to debug. At the prototyping stage, what is seen as a bug is generally a feature that has not been implemented. That means when a user interacts with the prototype and provides comments that the login is broken, it’s likely because they have made no effort to authenticate users.</p><p>An easy-to-understand example of how developers achieve this is that when demonstrating functionality to save a comment on a post, they will use mocked (hard-coded) comment data instead of connecting to a database of comments. That decision allows them to connect to the database later and show comments in the prototype near-identical to real comments to demonstrate how commenting works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BKvmrFTOwgSOH-sQFpCfiA.jpeg" /><figcaption>Prototypes replace high fidelity mockups.</figcaption></figure><h4>Usable applications deliver user’s stories.</h4><p>Wine gets better with time. Software gets better with usage.</p><p>A delay in getting an application in front of users means a delay in completing an application. It matters that an application is ready in as many ways as possible before making it available to the entire addressable audience. For an enterprise expense management application, the application might start in the finance department for a trial period before it is made available to the sales teams incurring expenses.</p><p>Before getting the first user on an application, a development team is limited to their own intelligence and assumptions as the sources of information to make the application usable to the intended customers. Making an application usable happens by finding the users who will rely on the application whether it is complete or not, correcting code where users have falsified assumptions, and developing functionality that has been overlooked.</p><blockquote>Find the users who are going to rely on the application, whether it is complete or not.</blockquote><p>No easier place than corporate settings to find these users. The application users are going to be paid as a part of their job to use the application. Consumer applications can benefit from paying intended users to trial the application; it can be an inexpensive alternative to marketing the application as if it is completed. Under the surface, the goal is to find users who are motivated to use the application for reasons other than its intended purpose.</p><blockquote>Correcting code where users have falsified assumptions.</blockquote><p>An assumption is falsified when the application’s best-informed guess at how users will behave is proven to be false based on the response from actual users.</p><p>Making the application usable means correcting assumptions, and correcting assumptions does not mean completely re-writing the application. When the rare situation occurs that users are suggesting the entirety of what has been built is not working for them. Probably the developers are not going to be in a position to provide a usable solution. When the much more common case occurs, users suggest that interactions with the application are not perfectly delivering on their expectations, then developers can rewrite existing code to align better interactions with what the users need.</p><blockquote>Developing functionality that has been overlooked</blockquote><p>Users can point to needs that are not at all addressed by the application. When that happens, the developers and the stakeholders that organize them come together to determine the priority of those needs when weighed against already identified features that remain to be built. The options they have are either to incorporate the overlooked needs into the completed release of the application or to release the application intentionally excluding those needs and deciding to address them later or with an alternative method, such as implementing third-party integrations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e82cCtm4iLE6r7zgBtS9SQ.jpeg" /><figcaption>Complete applications are the end of the beginning.</figcaption></figure><h3>Complete applications only require maintenance.</h3><p>When an application is being used by the intended audience and meets their needs day-to-day, it is complete. There are ways of providing new features and new life to the application, often with new features and new releases. From the moment the application is complete, the option exists to move to a level of development that is maintenance-only. That means fewer developer-hours being applied to the application overall, fewer budget dollars being spent on development in any given time period, and higher levels of focus on both related and unrelated projects.</p><blockquote>Fewer Developer-Hours</blockquote><p>The application is completed to the users&#39; satisfaction, and now the developers are left without new problems to solve or enhancements to deliver. It is time to reduce the hours. Depending on the project&#39;s size, we can either fully remove developers from the application or reduce developers from full-time to part-time. The hours that are applied to the application now are almost exclusively bug fixes and keeping technology up-to-date. There will inevitably be bugs in the application that were not discovered until after a full release. They can be trivial; they can be critical; they are always present. Keeping some amount of time and attention from the developers means that they have the capacity to fix those bugs quickly. Almost as fast as the application is marked as completed, technology will improve.</p><p>Underlying dependencies will be updated, performance enhancements will be applied to the broader environment the application lives in, and more. Project Managers can then commit developer hours to maintain the application’s fitness to the technology of today. This provides the aforementioned performance enhancements, and beyond that, security is maintained. Often underlying dependencies are updated to provide fixes to newly discovered attack vulnerabilities. It is prudent to apply those updates to the application from the time it is complete until it is obsolete.</p><blockquote>Fewer Budget Dollars For Development</blockquote><p>Hand-in-hand with fewer developer-hours comes fewer budget dollars for development. As a result of application completion, budget dollars can be re-allocated to customer support, marketing, sales, and any other endeavor that complements the application. There are some caveats. When the application is complete, and there is a cost associated with each user, this causes the budget dollars to grow to accommodate the larger infrastructure needed to provide the application to more users.</p><blockquote>Focus on both related and unrelated projects</blockquote><p>A completed application can provide the basis to begin a new application. There may now be a codebase in related applications that can be applied to adjacent market segments, and use-cases are not useful to the original application. In the case of unrelated applications, you now have a team of developers that are no longer actively building your application. This frees them up for new projects. When the relationship with the developers is strong, there is an opportunity to engage them with new ideas.</p><figure><a href="https://upstateinteractive.io/contact/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wUHNDmtAJk5GEjcdLREWZg.jpeg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95e5d699e917" width="1" height="1" alt=""><hr><p><a href="https://medium.com/upstate-interactive/3-standards-of-software-quality-prototype-usable-and-complete-95e5d699e917">3 Standards  of Software Quality: Prototype, Usable, and Complete</a> was originally published in <a href="https://medium.com/upstate-interactive">Upstate Interactive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Ways to Protect Your App from Being Useless]]></title>
            <link>https://medium.com/upstate-interactive/3-ways-to-protect-your-app-from-being-useless-ef1c1c178618?source=rss-b9a4bc298f3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef1c1c178618</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[enterprise-software]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Peter B Smith]]></dc:creator>
            <pubDate>Fri, 08 Jan 2021 17:23:22 GMT</pubDate>
            <atom:updated>2021-04-05T10:30:54.099Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yoMC8SSv2wdbjB8L.jpg" /><figcaption>Any software with sufficiently numerous users eventually works.</figcaption></figure><p>There is not any particular magic to <a href="https://upstateinteractive.io/software/">developing applications</a> for others. It takes a persistent effort, getting users to use the app, combined with skilled developers to provide the foundations of its usability.</p><p><strong>1. Use it yourself. </strong>When you are seeking to build an application, and you are a potential user, then the application has its first user. That means the skilled developers you have hired to build it can ask you the outcomes you would like to achieve, and as long as a result is usable by you, it has a basis to be used by others. The key is in communicating with User Stories, not Features. The developers are the intelligent party as it comes to delivering a feature, and you are the intelligent party as it comes to knowing what the user is looking to do. And there is a difference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c-AUlrAs-J27fvTv.jpg" /></figure><p><strong>2. Pay users money.</strong> A team of developers is regularly the single largest line-item for software. It is almost tautological. Presuming there are dollars available for sales and marketing, give people some money to use your application. It could be that folks who are paid to use it from the beginning may find cause to pay you for access by the time it is completed. In enterprise scenarios, when employees are a user group, then have a panel of them ready from the first day of development until the last so that they can evaluate the product’s fitness to their needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sElg0VL78UBHJiTu.jpg" /></figure><p><strong>3. Demo non-stop. </strong>At any time, in any venue, when you are around your potential users, then show them the application. This can be done online now with any number of tools; ask your developers what the most appropriate for the type of application you are building is. At any demonstration, you might hook one or two audience members and leave with a new user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EWPZOcXZDcaROj20.jpg" /></figure><p>As for timing? As much as possible, understand your users before the development of the application by talking to them. Assuming you are the user, then it is a short conversation. For all others, you will be coming to your developer knowledgeable and articulate on the stories that need to be written in code in order to arrive at a happy ending.</p><figure><a href="https://upstateinteractive.io/contact/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3QngnUgtwpRHh4a6.jpg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef1c1c178618" width="1" height="1" alt=""><hr><p><a href="https://medium.com/upstate-interactive/3-ways-to-protect-your-app-from-being-useless-ef1c1c178618">3 Ways to Protect Your App from Being Useless</a> was originally published in <a href="https://medium.com/upstate-interactive">Upstate Interactive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Examples of First Sprint Deliverables for Enterprise Applications]]></title>
            <link>https://medium.com/upstate-interactive/5-examples-of-first-sprint-deliverables-for-enterprise-applications-76f0a948a746?source=rss-b9a4bc298f3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/76f0a948a746</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[enterprise-technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Peter B Smith]]></dc:creator>
            <pubDate>Fri, 08 Jan 2021 17:20:48 GMT</pubDate>
            <atom:updated>2021-03-14T15:17:28.510Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Flyover an app with light coming out of the screen." src="https://cdn-images-1.medium.com/max/1024/1*FMMjxrmZp7HQeqUYXzdHEg.jpeg" /></figure><p>From the moment we begin writing code, we aim to deliver code. It may take only a short amount of a single developer’s time to scaffold a project. Determining data models may be brief as well. Describing the application with <em>user stories</em> is no different. In a first Sprint, we deliver, and then every Sprint thereafter, we deliver again.</p><p><em>EXAMPLE 1: A brand new green-field project</em></p><p>Likely, this Sprint will include agreeing to data models that will be core to the application. On top of that, it will likely cover how the data models will relate to each other and a completed iteration that can be built on.</p><p>When the data models are completed, it is possible to start developing a database and API that allows data to be accessed by an application. A starter API can be delivered by the end of the Sprint.</p><p>When the data models are completed, it is possible to start mocking data that the team can use to design a prototype. It is also possible to deliver a starter application that displays the browser&#39;s data or on a mobile device.</p><p><em>EXAMPLE 2: An overhaul of an existing application</em></p><p>When an application is being overhauled, data models probably exist. In the first Sprint of the overhaul, we might decide to alter the data models to achieve new results that are desired. It might be that the data models must stay the same to maintain legacy access to the data. In both cases, the first Sprint can deliver certainty around what data models will be built in the new application.</p><p>An API and database may already exist, and that could mean there is no need for any server deliverables in the first Sprint of the overhaul. It might be that there will be necessary integrations with the existing infrastructure. In the first Sprint, it is possible to deliver successful requests and receive correct responses that the new application will be using.</p><p>Overhauling an application often means developing new views and interactions that the user will see and experience. There are potentially brand and look-and-feel considerations that need to continue in the new application. In the first Sprint, it is possible to port existing components to the new application architecture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bVyr1NOOBRXlSFb8quLlMQ.jpeg" /><figcaption>Applications use APIs to connect to each other.</figcaption></figure><p><em>EXAMPLE 3: Process to process communication</em></p><p>When making multiple processes communicate with one another, there are either minimal user interface deliverables or none at all. This is possibly the same for data modeling work, either none or only a minimal layer.</p><p>Deliverables achievable in the first Sprint can be “perfect case” demonstrations of the processes communicating. That means, given data that is input without any errors, then data can be delivered from one process to another successfully. Future Sprints can address cases that have errors or complex interactions.</p><p>Another deliverable may be creating the technical blueprints to describe how the processes are going to communicate with one another. This is often a deliverable that stems from two processes not being built in a way that they can communicate in a standards-based way. An example: when data is available from processes with APIs that follow RESTful standards then there are often straight-forward methods of making them communicate. When data is being pulled from a process that has a RESTful API into a directory on an internally hosted corporate server, then more upfront work is done to ensure that this communication can occur reliably.</p><p><em>EXAMPLE 4: Business process improvement</em></p><p>Deliverables on business process improvements achieved with software tend towards favoring substance over style. They need to work well, and looking good is not a part of the necessary outcomes.</p><p>Deliverables here can be User Stories that communicate in clear terms where the improvements need to be made to reduce wasteful activities or increase productivity. It is core to the success of the project that the results are measurable.</p><p>Deliverables can be a translation of requirements into a functional prototype that demonstrates the process an end-user will be implementing.</p><p><em>EXAMPLE 5: Skunkworks project inside the enterprise</em></p><p>Deliverables in this type of application need to be not only functional but also need to look and feel good to use.</p><p>During the first Sprint, deliverables for Skunkworks projects can be functional components that demonstrate the new controls available to application users. Functional components may be included in a scaffolded application or in isolation on standalone pages.</p><p>Data modeling matters in skunkworks applications as much as in green-field projects, and a deliverable looks similar. An iteration of data models can probably be completed in a first Sprint to communicate the fundamental inputs and outputs that will be in the application.</p><p><em>BONUS: A First Sprint Team</em></p><p>A team can grow as an application does; accordingly, there are generally fewer people working on a project at the beginning than there are at the end. It is possible that the team will stay the same size for the entire project, and more often, there are fluctuations to accommodate the various phases of development.</p><p>All enterprise applications begin with a scrum master, a product owner, and a developer team. The practical needs for all persons to be full-time are often non-existent, and because of that, the scrum master and product owner are often part-time to begin. The developer team is only made of those people who are developing the necessary deliverables to get started. In early development Sprints, it can be better to have fewer members on the team to focus on listening to user’s needs and being sure of them rather than creating discussion among developers about technical considerations that can be missing the mark on what a user will use.</p><p>A Sprint Team might include a total of a single full-time person’s time spread across three individual people for early-stage projects being created as a result of the new application. The largest representation will be from the Product Owner and the developer, while the Scrum Master is involved strictly only when necessary. When a project is further along, and now this Sprint is continuing, it is possible to have a full-time product owner, a handful of developers, and a half-time scrum master. It is possible that the scrum master not be full-time on the project, even on some of the largest applications.</p><figure><a href="https://upstateinteractive.io/contact/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YGEjBeOlAH3GCtRe9cqD6g.jpeg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76f0a948a746" width="1" height="1" alt=""><hr><p><a href="https://medium.com/upstate-interactive/5-examples-of-first-sprint-deliverables-for-enterprise-applications-76f0a948a746">5 Examples of First Sprint Deliverables for Enterprise Applications</a> was originally published in <a href="https://medium.com/upstate-interactive">Upstate Interactive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Non-technical Members of the Application Team]]></title>
            <link>https://medium.com/upstate-interactive/the-non-technical-members-of-the-application-team-5ad2791703fa?source=rss-b9a4bc298f3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ad2791703fa</guid>
            <category><![CDATA[business-intelligence]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Peter B Smith]]></dc:creator>
            <pubDate>Fri, 08 Jan 2021 17:13:35 GMT</pubDate>
            <atom:updated>2021-04-05T10:29:52.468Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F3tSJve9jqEj4TbgVr1lIw.jpeg" /><figcaption>Development is not all about developers.</figcaption></figure><p>Building <a href="https://upstateinteractive.io/software/">great software</a> takes a village. A developer is a member of the team who is contributing to the codebase. Here is a breakdown in the role of client-side: (frontend) developers, server-side (backend) developers, and <a href="https://medium.com/upstate-interactive/what-is-a-design-technologist-an-interview-with-james-patrick-952fa020fffa">design technologists</a> (designers who code). The roles of Scrum Master, Product Owner, and Stakeholder are not developers, and those roles are as much a part of the success of an application as the developer roles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hKr3C3FAO5SJbLOirn_aYA.jpeg" /><figcaption>The Scrum Master is always keeping the conversation going.</figcaption></figure><p><strong>Scrum Master</strong></p><p>As focused as a team of developers is on the code, a Scrum Master is focussed on a team of developers. People are people. They get along most times and disagree occasionally. They can see the trees and be blind to the forest. They can make it look alright on the outside when on the inside, it is all wrong. A Scrum Master looks at the people on the team with an eye towards improvement. Addressing interpersonal relations, providing perspective on the application development from a distance, and uncovering hidden issues keeps a Scrum Master active on a team. Before all that, a Scrum Master also ensures the developer team is working in the constraints of Scrum as outlined in the Scrum Guide. Are daily scrums happening? Are Sprint Reviews considering process improvements? Are Sprints keeping to their timebox? The Scrum Master ensures the answer is yes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fHROfuxQnAUapkFOuFWqJg.jpeg" /><figcaption>The Product Owner knows the goal and makes it known.</figcaption></figure><p><strong>Product Owner</strong></p><p>A Product Owner’s role evolves and morphs over time and across applications. What never changes is that they are on the team in support of the user. They write User Stories, give voice to the users when they are not present, and consider what it means to deliver an application for the user&#39;s benefit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n0awKZvXjFtLjT1id1MjbQ.jpeg" /><figcaption>The Stakeholder is a voice that needs to be heard.</figcaption></figure><p><strong>Stakeholder</strong></p><p>Stakeholders are users, accountants managing budgets, CEOs approving additional team members, and all the people who are not directly involved in developing the application who have an interest in the outcome. The Product Owner is the primary communicator between stakeholders and the developer team. The stakeholder&#39;s role is to provide background information on the context the application is being built in, inform the Product Owner of any changes to the business process the application is being applied to, and generally guide the application&#39;s development from afar. Without stakeholders, there is no purpose for the application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6N8DvEpf8mMdkr_oWGNoMQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ad2791703fa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/upstate-interactive/the-non-technical-members-of-the-application-team-5ad2791703fa">The Non-technical Members of the Application Team</a> was originally published in <a href="https://medium.com/upstate-interactive">Upstate Interactive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Kate Tsunoda]]></title>
            <link>https://medium.com/upstate-interactive/introducing-kate-tsunoda-7054afd594?source=rss-b9a4bc298f3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/7054afd594</guid>
            <category><![CDATA[software-agency]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[upstate-new-york]]></category>
            <dc:creator><![CDATA[Peter B Smith]]></dc:creator>
            <pubDate>Mon, 27 Jul 2020 14:45:23 GMT</pubDate>
            <atom:updated>2020-07-27T14:45:23.730Z</atom:updated>
            <content:encoded><![CDATA[<h4>Upstate Interactive’s First Female Advisor</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BeAyE6IEveftjgtgDTgtEA.jpeg" /></figure><p>Today Upstate Interactive is happy to announce that we are adding Kate Tsunoda, <a href="http://thoughtbot.com/">thoughtbot’s</a> San Francisco-based Managing Director, to our Advisory Board.</p><p>Ms. Tsunoda states, “As a member of the Advisory Board, I provide guidance to the company leadership on topics related to growth.”</p><p>Ms. Tsunoda has been working with Upstate Interactive informally for months, challenging us to become stronger as an agency. With her expertise and knowledge we have been able to grow our perspective on the software agency industry.</p><p>We are looking to the future to become like thoughtbot, an industry leader, loved by developers and trusted by clients. With Kate Tsunoda we are one step closer to that future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7054afd594" width="1" height="1" alt=""><hr><p><a href="https://medium.com/upstate-interactive/introducing-kate-tsunoda-7054afd594">Introducing Kate Tsunoda</a> was originally published in <a href="https://medium.com/upstate-interactive">Upstate Interactive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Love and Attraction]]></title>
            <link>https://peterbsmyth.medium.com/on-love-and-attraction-f0f8f1b2210a?source=rss-b9a4bc298f3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0f8f1b2210a</guid>
            <category><![CDATA[love]]></category>
            <category><![CDATA[attraction]]></category>
            <category><![CDATA[easter]]></category>
            <dc:creator><![CDATA[Peter B Smith]]></dc:creator>
            <pubDate>Sun, 12 Apr 2020 16:17:58 GMT</pubDate>
            <atom:updated>2020-04-12T16:35:01.600Z</atom:updated>
            <content:encoded><![CDATA[<p>Love Languages, Attractions, and Understanding</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fCioqOefwdl2_a_TqXjexg.jpeg" /><figcaption>Venus and Adonis</figcaption></figure><p>As we were walking the Springtime block of Cumberland Ave, my friend introduced me to the concept of Love Languages. It is a concept introduced and made popular in recent years by a book author. The author asserts five languages, modes of expression, of love:</p><ul><li>quality time together</li><li>spoken word</li><li>gift-giving</li><li>service to the other</li><li>physical</li></ul><p>In discussing them, we shared views on the prioritization and rankings of each of those languages. It came about from her recent realization that gift-giving is a language she enjoys. As our discourse unfolded, we agreed that quality time together is the top language. At the bottom is spoken word. The other three fill-out the middle, to us, in no particular order. I can share my reasoning on the order.</p><p>Quality time together together is on top because it is the mode of expression that provides the most opportunity for a future together. As we all search out new friends, lovers, and life-long mates we presume to spend at least the next morning together. Assuming you can inhabit the same space at the same time with another and enjoy that time, and bond in that space, and feel enraptured by the other, you have yourself a good probability of experiencing the same the next day. It is independent of the other’s skills of articulation, practical ability to care for or provide, to give material goods, or to keep their physical self fit. Yet, with the singular pleasure in being with the other, you have the basis for another day of love.</p><p>Spoken word is on bottom because language is a tool that few people dedicate themselves to the mastery of. It is rare that the other will have the articulation of love found in masterful television shows, movies, and plays of all kinds. With a world of examples of higher quality words available to everyone, the sounds of “you are beautiful,” “you are handsome,” “I like you,” and so on, can easily leave one wanting. Spoken word has its worth in love, no doubt about it. The simplicity of, “you are beautiful,” said at the right time, can make the other feel all the more love from you. More practically, the skills of communicating can mend differences in beliefs and values, construct plans and events, share jokes and thoughts, to build bonds. To focus on spoken word practicalities to the exclusion of other modes of expression would complicate love. Love can be communicated across languages, without a word, among broad populations.</p><p>What of the middle three? She and I focussed on the value of quality time, the subordinate value of spoken word, and only a few moments on physical, service, and gift-giving languages. In healthy individuals each of these three is accomplishable. Assuming relative employment then gift-giving is achievable; any pauper can afford roses. Given a minimally-able body, physical love can be made without effort. Provided the most basic of practical skills, anyone can cook a meal for a lover. In all three cases there is the presumption of a certain level of health. As a lifetime passes by the probability that one may become unable to use one of these languages increases, making these languages impermanent. Could the same be said of quality time together? Distances separate us as a matter of routine and in those times the opportunity for love to diminish increases. That’s a valid point, though unique among the languages, there is a high degree of choice in creating distance. We are free to be as near or far from each other as we choose; few forces of nature or society will separate lovers who choose to be together.</p><p>Turning the corner to Tecumseh Road, our conversation was mostly on love languages from the perspective of the giver, “how would we prefer to express love to another?” That was the essential perspective of the conversation. And the medium that made the concept popular lends itself to that. A book reader is taking action by poring through the pages of an author’s mind, in this case reading the ways one can express love. The natural result for the reader is the self-examination of one’s expression of love.</p><p>What about the opposite, to be on the receiving end? The other side of love is attraction. As one expresses their love to you, you feel attraction. You can feel no attraction when you are not receptive to the mode of expression being shared. You can feel full attraction when you are perfectly attuned to the love language being expressed. For each language, there is a corresponding attraction:</p><ul><li>durational</li><li>verbal</li><li>gestural</li><li>sacrificial</li><li>physical</li></ul><p>Explicitly, these align as follows. Assuming you feel durational attraction, the more time a friend spends with you, the more fully attracted to them you are. Assuming you feel verbal attraction, the more aligned their speech is to your speech, the more you feel attracted. Assuming gestural attraction, the ability for your partner to give you objects and materials that delight you will be attractive to you. Assuming sacrificial attraction, the services the other gives on your behalf will be a source of attraction. Assuming physical attraction, the touch of your lover will deepen your attraction.</p><p>Assuming and contemplating the perspective of the receiver is valuable, with an attempt at understanding the receiver you can plausibly discover which language they would care to “hear.” With that, you can tailor your expression to their reception. Using those Shakespearian characters, Venus and Adonis, as examples, assuming Venus’s primary love language is physical and Adonis primarily feels durational attraction then Venus would do better to spend time with Adonis on the hunt, first, then later give her physical expression of love.</p><p>When love and attraction are fully-aligned, when both prefer the same love language, when both receive attraction in the same way, then there exists a magical rarity. More commonly, love and attraction are imperfectly arranged. So there is reason for understanding. There is reason for contemplation of the other. Perfect alignment is optional for successful relationships.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0f8f1b2210a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I got drunk and wrote JavaScript for America]]></title>
            <link>https://medium.com/upstate-interactive/i-got-drunk-and-wrote-javascript-for-america-eb4f628929ae?source=rss-b9a4bc298f3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb4f628929ae</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[angular]]></category>
            <dc:creator><![CDATA[Peter B Smith]]></dc:creator>
            <pubDate>Wed, 05 Sep 2018 12:27:14 GMT</pubDate>
            <atom:updated>2018-09-05T12:30:38.120Z</atom:updated>
            <content:encoded><![CDATA[<h4>“Are you serious?“</h4><blockquote>All characters are fictional and no scotch was consumed during the making of this project.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J-oI_NIPgfOswQh6sO2K9w.jpeg" /></figure><p><a href="https://github.com/upstateinteractive/vanilla-js-application">Vanilla JS Application Example on GitHub</a></p><p>My life changed when I went into the government contractor offices of MEGA, Inc. I walked around the quiet offices that had a smell of coffee and, little did I know at the time, innovation.</p><p>It was because of a man named Michael, with a beard and flip-flops; Mr. California looked like he belonged on the same block as Instagram, not the US Military. He sat down my partner and I and asked us what we knew. We knew JavaScript — Express back-ends, AngularJS front-ends, BootStrap and jQuery were in our tool-belts — and not just those — we could make d3 visualizations from nothing. “We use a lot of vanilla.js at this office,” he said.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_3leDwVm0tKzRylwMQrWmw.png" /></figure><p>That meeting was enough for him and the rest of MEGA, Inc to get on board with Upstate Interactive as their contractors for a large project they had been working for years. There was little discussion after that about what we knew, we simply got through the standard government contractor on-boarding documents and procedures then began work. Upstate Interactive started building cyber defensive tools that would protect the infrastructure of American digital assets from Russians, North Koreans and the worst of them all, Vim users.</p><p>Our first tasks were unit testing back-end models to ensure their interactions with the databases were accurate. We used the regular tools one would use, Mocha and an assertion library. We were, however, very close to a vanilla.js front-end — just leaves away on the directory tree there were files that had no view library at all.</p><p>Maybe at this point you are scoffing at the hyperbole.</p><blockquote>Vanilla.js is a fine approach, it’s good for certain situations and I am all for it. — You</blockquote><blockquote>Of course you don’t always need a view library. — Your friend over your shoulder</blockquote><p>Bullshit. Neither of you have written any vanilla.js in five years.</p><p>The unit testing work ended for Upstate Interactive by Christmas of 2017. And Santa, in the form of Mr. California, rang in the new year with talks of more work. There would be a project that needed more engineers than they were able to staff on their own. Come February, we got a call and our ready-and-able engineering-problem-killing hoard was ready to commit a hand to them.</p><p>Then March comes. We are given the problem — there is a monolith that needs to be taken down and replace with micro-services. Monolith is an ironic understatement. Megalith is more apt to describe the application that had been built and maintained by MEGA, Inc for as long as it takes to go from middle school to college, developed originally by another team before them, and included Java.</p><p>Mr. California sat in on the first meeting to help the conversation about what tools to build this microservice with.</p><blockquote>I am familiar with Angular. The previous code appears to be in AngularJS. Moving from one to the next is natural. So we will use Angular. — Me</blockquote><p>“No Angular,” said everyone at the table.</p><p>As we were pushed to come up with something better we began to work on new HTML markup with my assigned design partner, Mark, who would be writing the application’s CSS without Bootstrap or grids or…</p><p>While working on the markup webegan looking at the world of JavaScript libraries and frameworks. Javascript is hard without the right liquor. So I opened the Glenlivet and poured liberally.</p><blockquote>Angular…</blockquote><blockquote>React...</blockquote><blockquote>Vue...</blockquote><blockquote>…</blockquote><blockquote>Mithril...</blockquote><blockquote>Cylce.js…</blockquote><blockquote>…</blockquote><blockquote>Stapes.js…</blockquote><blockquote>…</blockquote><blockquote>Where am I?</blockquote><p>We came back to the table with a one-pager on Vue.js. As good a way to get going in 2018 as any other option out there, we were confident that it also met the size and minimalism dictates of Mr. California. He was articulate in support of it as compared to Angular and after reading the information and data we collected, he shared compliments on Vue’s size. He shared back a Slack message that was the length of an essay all about using frameworks and not using frameworks, leaning towards not using frameworks.</p><p>Consensus was reached that there was merit to trying Vue for a few beginning steps of the application as well as trying a vanilla.js approach.</p><p>How would a developer who knows React, Angular and Vue work in vanilla.js?</p><p>Components build applications in hierarchal composable ways that make life so much easier than jQuery ever did. State management patterns pioneered by flux and reacted into redux and viewed in Vuex and observed in ngrx are all saviors for keeping user interfaces in-order. Manipulating the DOM is inefficient so we need to use a virtual dom.</p><pre>## JavaScript Components<br>The application uses ES6 Classes for components. They organize the front-end code.</pre><pre>...</pre><pre>**$ Convention**<br>1. Where a variable is prefixed with a $ it is a DOM element.<br>2. Where a component is prefixed with a $ it is a presentational component.</pre><pre>:README.md</pre><p>The Vue.js approach was quickly abandoned and Vanilla.js went forward.</p><p>It is hard to come up with the thought of components originally. But now that they exist, making them yourself is easy.</p><p>What is in a component? It has lifecycle hooks. It has a class structure that allows developers to write methods. It can react to events. It has a repeated pattern that can be re-used for different types of interactions and use-cases.</p><p>We had utilitarian tasks to accomplish. When the user clicked a link it needed to get data. We could do that with the fetch API. When the data came back we needed to update the DOM. Wecould do that with document.getElementById(&#39;item&#39;).innerText = . We soon realized that we could do that more generically using CSS conforming selectors with document.querySelector(&#39;#item&#39;).innerText =. We had no organization other than the list in the application was an an ES6 Class called List. The nav was an ES6 class called Nav. It worked well enough to do the DOM manipulations in methods called updateItem, deleteItem and so on, adding methods as needed.</p><p>But it was not more than a couple of days before, in reviewing the application’s requirements that it was clearly necessary to have sane state management. I poured the Glenlivet.</p><p>When I was puking in the metaphorical dumpster that is GitHub — as you do when you are drunk and looking for a way to solve your coding problem — I found the answer. In there I found <a href="https://github.com/morkro/tetrys">tetrys</a>. It was using redux without any view library.</p><pre>### What is in a component?<br>#### Constructor<br>The constructor of each component takes a [redux](redux.js.org) store.</pre><pre>#### Methods<br>##### init<br>Called when component is first created. Takes a config object with the keys `actionTypes` and `actions`. Calls `addEvents` method. Calls `store.subscribe()` with subscriber as it&#39;s argument.</pre><pre>```javascript<br>init ({ actionTypes, actions }) {<br>  this.actionTypes = actionTypes<br>  this.actions = actions<br>  this.addEvents()<br>  this.store.subscribe(this.subscriber.bind(this))<br>}<br>```</pre><pre>##### refresh<br>Called when route changes. Takes a config object with the keys `actionTypes`, `actions`.</pre><pre>```javascript<br>refresh ({ actionTypes, actions }) {<br>  this.actionTypes = actionTypes<br>  this.actions = actions<br>}<br>```</pre><pre>##### addEvents (optional)<br>Takes zero arguments. configure the event listeners for the components</pre><pre>```javascript<br>addEvents () {<br>  this.$list.addEventListener(&#39;click&#39;, this.onClick.bind(this))<br>}<br>```</pre><pre>##### subscriber (optional)<br>Listens for redux store changes. Switches over the lastAction type to determine updates to the view.</pre><pre>```javascript<br>subscriber () {<br>  const state = this.store.getState()<br>  const lastAction = state.lastAction<br>  switch (lastAction.type) {<br>    case pageActionTypes.NAVIGATE_END: {<br>      this.$input.value = select.selectSearchQuery(state)<br>      break<br>    }<br>    default: {<br>      break<br>    }<br>  }<br>}<br>```</pre><pre>:README.md</pre><p>With Tetrys as a reference point, we had our starting point for the rest of the project. We could use redux and creativity to build an application that had predictable state updates, no view library, and only the most minimal dependencies — redux and redux-thunk are two of the 3 that we used.</p><pre>## Redux<br>### Async Action Creators<br>[redux-thunk](https://github.com/reduxjs/redux-thunk) is used for async actions.</pre><pre>Example Action Creator:<br>```javascript<br>{<br>  deleteOneComplete: (payload) =&gt; ({<br>    type: actionTypes.DELETE_ONE_COMPLETE,<br>    payload<br>  }),<br>  deleteOneError: (payload) =&gt; ({<br>    type: actionTypes.DELETE_ONE_ERROR,<br>    payload<br>  }),<br>  deleteOne: function (payload) {<br>    return async (dispatch) =&gt; {<br>      try {<br>        await http.delete((`${URL}/api/space-vehicles/${payload}`))<br>        dispatch(this.deleteOneComplete(payload))<br>        return true<br>      } catch (e) {<br>        dispatch(this.deleteOneError(e.message))<br>        return false<br>      }<br>    }<br>  }<br>}<br>```</pre><pre>Dispatching from a Component Method:<br>```javascript<br>remove(uuid) {<br>  this.store.dispatch(this.actions.deleteOne(uuid))<br>}<br>```</pre><pre>:README.md</pre><p>The application shaped up with lifecycle methods after a few weeks of development and naturally re-occurring patterns. A constructor, an init, and a refresh turned out to be enough for this application. Then we also standardized non-lifecycle methods. Subscriber, addEvents, and more were used again and again to listen for changes and react to them.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1158cad7b7571b437ce3047ae92ef064/href">https://medium.com/media/1158cad7b7571b437ce3047ae92ef064/href</a></iframe><p>After months of building the application it became clear:</p><blockquote>This is working. — Everyone at the table</blockquote><p>We wrote the application as a job. It was not our creative interest to build the application. It was not going to be used by anyone other than a few Americans who are protecting our country from outside threats and internal dis-organization. It would be reviewed for it’s function and never it’s stack. It would never be open sourced and I could never discuss the details.</p><p>During the process we could not ask anyone outside of the project for input on the direction or the issues it challenged us to solve. That meant our friends in <a href="https://www.syracuse.io/">Syracuse.io</a> Slack could not weigh in. This was a challenge for us, Upstate Interactive, and the few employees of MEGA, Inc that were on working on it.</p><p>Where we went was a product of popular influences from the open source community and experienced influences from the MEGA, Inc team. Where we arrived at was a view-library-less micro-service that used redux for it’s state management.</p><p>Would we do it over again for the next project? We have a new perspective on starting projects now. We cannot take the lessons learned into every project, literally. An Appeal to Popularity is more than a <a href="https://en.wikipedia.org/wiki/Argumentum_ad_populum">logical fallacy</a>, it is a commercial imperative. Upstate Interactive gets projects in it’s doors that are already built in Angular and we need to continue using Angular that reason. Writing the logic to manipulate the DOM directly is verbose and intricate. Even though in my intoxicated states I found no hard evidence that a virtual DOM was a benefit to the project specifically, or the majority of projects generally (ENDNOTE 1), a micro-view library like <a href="https://preactjs.com/">Preact</a> would be useful for it’s brevity.</p><p>So we would continue to use the tools weneed on a project by project basis. Angular, React, or Vue are all appropriate for some projects. And vanilla.js is appropriate for others too. And that is the point. Vanilla.js is appropriate too. Now that we have done both approaches, it is more clear to us which project falls into which category.</p><p>As I finish my bottle of Glenlivet and my code transpiles I will ask myself not “Did I used the right framework?” but “Did I use the right scotch?”</p><p><a href="https://github.com/upstateinteractive/vanilla-js-application">Vanilla JS Application Example on GitHub</a></p><p>ENDNOTE 1: I could not find much of any performance benchmarking on the benefits of Virtual DOM. With that in mind, there may be some out there, and I can incorporate that if it comes up in my world. Not only that, with some applications that are not as dynamic as Facebook (which is what React was originally built to work with), a virtual DOM is more overhead than it is worth.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F682c6d%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2F682c6d%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/4dbf487062d26d986a25e2baf2031fd6/href">https://medium.com/media/4dbf487062d26d986a25e2baf2031fd6/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb4f628929ae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/upstate-interactive/i-got-drunk-and-wrote-javascript-for-america-eb4f628929ae">I got drunk and wrote JavaScript for America</a> was originally published in <a href="https://medium.com/upstate-interactive">Upstate Interactive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Blockchain Bubble? No. Blockchain Babble? Yes.]]></title>
            <link>https://medium.com/upstate-interactive/blockchain-bubble-no-blockchain-babble-yes-dc333741376d?source=rss-b9a4bc298f3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc333741376d</guid>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[ripple]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Peter B Smith]]></dc:creator>
            <pubDate>Wed, 01 Aug 2018 11:24:11 GMT</pubDate>
            <atom:updated>2018-08-01T11:24:11.692Z</atom:updated>
            <content:encoded><![CDATA[<h4>What is all the babble about?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gQONHld0KJ0PXss7ZkkUZQ.jpeg" /></figure><h4>What Is in a Word?</h4><p>Outside of the tech space, many people aren’t familiar with the word blockchain. They may have heard of bitcoin and other cryptocurrencies, but blockchain itself tends to mystify the masses.</p><p>If you spend time online, however, you’ve likely heard of both bitcoin and blockchain. Asking, “What is the underlying programming language to interact with the Ethereum blockchain?” often leads to blank stares, however. So does asking, “Where does a web developer learn to interact with the blockchain?”</p><h4>You May Not Know</h4><p>You are an Internet person, so you are not ignorant to blockchain. You may not know that Solidity is the programming language of choice for Ethereum, and you may not be aware that grabbing transactions from a blockchain ledger is possible with a web API, and you may not be aware that linking the web and blockchains is possible today, reliably.</p><h4>Let Us Babble</h4><p>We held an event to babble about the not-a-bubble. We did not discuss any cryptocurrency market prices and the hard forks that are messing with the bank accounts of teenage and retirement-age investors. We discussed the technical.</p><p>Doug Crescenzi, our in-house blockchain security engineer, shared the latest stories he has from contributing to <a href="https://openzeppelin.org/">OpenZeppelin</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F72Jh-A8do3Q%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D72Jh-A8do3Q&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F72Jh-A8do3Q%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/de9882e8c99e4032e7fe9aa12712c18c/href">https://medium.com/media/de9882e8c99e4032e7fe9aa12712c18c/href</a></iframe><p>Aaron Anderson, our friend at web3devs, went in-depth on how he and his shop builds web-enabled Ethereum interfaces by way of an overview of using <a href="https://github.com/ethereum/web3.js/">Web3</a> with React.js.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fjn4TU-gzUNo%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Djn4TU-gzUNo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fjn4TU-gzUNo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/27460331e6436c1c0154eb865b00685c/href">https://medium.com/media/27460331e6436c1c0154eb865b00685c/href</a></iframe><p><a href="https://www.cryptokitties.co/">CryptoKitties</a> took over the world of Ethereum. <a href="http://kittyhats.co/">KittyHats</a> made those pussycats kings and queens by giving them hats. Dan Viau of <a href="http://www.salinalabs.com/">Salina Labs</a> talked about what it took him and his team to make KittyHats a reality.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F3wCx_YqABBk%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D3wCx_YqABBk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F3wCx_YqABBk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0965a10783570333c4fd8386e3460141/href">https://medium.com/media/0965a10783570333c4fd8386e3460141/href</a></iframe><p>Mo Morsi of <a href="http://devnull.network/">Dev Null Productions</a> dove into the world of Ripple and XRP with a high-level understanding of the often misunderstood technology.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FgTVUk5qoJ8U%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DgTVUk5qoJ8U&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FgTVUk5qoJ8U%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b382bebd3ad2c2b514e54a6a927eacb8/href">https://medium.com/media/b382bebd3ad2c2b514e54a6a927eacb8/href</a></iframe><h4><strong>Babbling on and on and on and on and on and on and on and on…</strong></h4><p>Blockchain conversations are becoming blockchain businesses. There are now consultancies, like Upstate Interactive and Web3Devs, focusing on blockchain solutions for businesses. We are finding a lot of great conversation from the past turning in our most exciting projects. In fact, you can expect the blockchain people you know to continue babbling on about it.</p><p>Fundamental technologies are enabled by hard research. Then those technologies are commercialized. Finally, they are consumerized.</p><p>We are seeing applications now at the commercial level and there are more coming through our door every day.</p><h4>You can can call it a bubble and miss the wave or join the conversation and start building.</h4><p>We are happy to host another event focused on blockchain. Until then, you can find us at <a href="https://futuristconference.com/">The Future of Blockchains</a> in Toronto, Canada, on August 15 and 16.</p><p>Babble on!</p><p>☞ To stay up to date with <a href="http://upstate.agency/">our</a> work with smart contract development, <a href="http://blog.upstate.agency/">follow us on Medium</a> and <a href="https://twitter.com/upstateagency/">Twitter</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F682c6d%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2F682c6d%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/4dbf487062d26d986a25e2baf2031fd6/href">https://medium.com/media/4dbf487062d26d986a25e2baf2031fd6/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc333741376d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/upstate-interactive/blockchain-bubble-no-blockchain-babble-yes-dc333741376d">Blockchain Bubble? No. Blockchain Babble? Yes.</a> was originally published in <a href="https://medium.com/upstate-interactive">Upstate Interactive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>