<?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 Thomas Augustus Grice on Medium]]></title>
        <description><![CDATA[Stories by Thomas Augustus Grice on Medium]]></description>
        <link>https://medium.com/@thomasaugustusgrice?source=rss-5f723f80010e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2nnR21PcO7ckajMANKlbTg.jpeg</url>
            <title>Stories by Thomas Augustus Grice on Medium</title>
            <link>https://medium.com/@thomasaugustusgrice?source=rss-5f723f80010e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:30:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thomasaugustusgrice/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[Quick and dirty guide to code reviews]]></title>
            <link>https://medium.com/@thomasaugustusgrice/quick-and-dirty-guide-to-code-reviews-8c0b03c13b18?source=rss-5f723f80010e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c0b03c13b18</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Thomas Augustus Grice]]></dc:creator>
            <pubDate>Thu, 03 Feb 2022 08:29:55 GMT</pubDate>
            <atom:updated>2022-02-03T08:29:55.296Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PNQpA7MU0YZRtIBL73trLQ.jpeg" /></figure><p>Quick and dirty guide to doing code reviews (CRs):</p><p>1. Reviewing a CR starts with writing a good CR. You should read the description, check out any screenshots, gifs, tracked issues, and perhaps even any demo environments associated with the code.</p><p>2. One question you might ask yourself then is — am I the best person to review this code? Sometimes you might be the only person, or sometimes it might be worth picking up on context you weren’t aware of before, but sometimes it may also be best to alert someone else who can review the code more efficiently than you. For complicated changes it may make sense to “pair review” with the author, they can explain some of the more obscure parts and accelerate the pace of the review.</p><p>3. When commenting on the code, for the majority of the time you should refrain from style comments and other nitpicks — these should be addressed separately and automatically by linting mechanisms if at all possible so that they don’t take up bandwidth in a code review.</p><p>4. For critical comments, try to offer solutions if possible. If you’re holding back approval, make it clear why — don’t leave your reviewee guessing. If automated tests fail at the review stage, you can offer feedback as to what your theory is on why they failed.</p><p>5. Ultimately, shipping code is a balancing act between maintaining a quality bar and maintaining velocity on your team. Sometimes it may be more important to test a change in dev than it is to ship perfect code. Sometimes it isn’t worth getting the unit tests exactly right when you know this code is more of a “proof of concept” and is going to change soon.</p><p>6. Regarding point #1 — you can’t always trust that the code works as stated. It may be worthwhile to check out the code and set it up and test it yourself. Having a standard where code reviews come with demo environments so reviewers can test might make sense for your project (you can usually set up a CR description template that includes a section for this in your project, depending on which platform you’re using). But if one person is manually testing it, maybe communicate that with your team so that everyone isn’t spending time on that level of deep manual testing.</p><p>7. If a code review is really long or includes too many changes, you may reasonably ask the author to break it up into smaller reviews (not always reasonable, especially if there are lots of automated changes). Related to this: CRs should be as single purpose as possible, although this can be highly inconvenient, especially in the early stages of projects where many unrelated changes might need to be happening at once.</p><p>As with most things, these rules are flexible depending on your team, project, and where you are in the product lifecycle. Do you disagree with any of these points? Would love to hear from other engineers on this topic. Ultimately code reviews should be about making your team more productive.</p><p>Follow me on <a href="https://www.linkedin.com/in/thomas-grice/">LinkedIn</a>, <a href="https://twitter.com/ZodiacKodiak">Twitter</a>, or <a href="https://www.instagram.com/zodiackodiak/">Instagram</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c0b03c13b18" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Post-AmsterdamJS Thoughts: The Shape of Web To Come]]></title>
            <link>https://medium.com/@thomasaugustusgrice/post-amsterdamjs-thoughts-the-shape-of-web-to-come-7886a7e4eb06?source=rss-5f723f80010e------2</link>
            <guid isPermaLink="false">https://medium.com/p/7886a7e4eb06</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[webassembly]]></category>
            <category><![CDATA[webxr]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Thomas Augustus Grice]]></dc:creator>
            <pubDate>Sun, 10 Jun 2018 16:01:16 GMT</pubDate>
            <atom:updated>2018-06-11T16:32:01.481Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*1YX6s9Gbu5cniIDzxG9iUQ.png" /></figure><p><a href="https://amsterdamjs.com/">Amsterdam JSNation</a> was a wonderful experience that shone light on not just how the web technologies available to engineers are aiding existing day-to-day development, but how web experiences may look in 5, 10, or 15 years.</p><p>Here’s a non-exhaustive list of the topics touched on to various degrees during the conference talks: programming paradigms, PWAs, mobile, brain-computer interfaces, TypeScript/Flow/typing systems, WebXR, WebSpeech, software architecture/patterns, QA, e2e testing, IoT, isomorphic JS apps, team structure, graphics, game dev, service workers, reactive programming...</p><p>For a one day conference, AmsterdamJS had something for everyone. If you were looking for ways to improve your software practice in well-established dimensions such as end-to-end testing, <a href="https://twitter.com/VossJenn">Jenn Voss</a>’ presentation included a good breakdown and recommendation of Cypress and approaches to structuring your team with respect to QA.</p><p>But while bread-and-butter topics such as testing/QA and specific frameworks will always be helpful, what stood out to me was the number of potentially revolutionary technologies rearing their heads and being explained or demonstrated for the AmsterdamJS audience.</p><p>I thought it would be fun to go over these technologies and do the ill-advised: try and predict their impact/adoption/timeline, and the larger picture of what the future of the web is. I’m ordering these roughly in order of less unknowns/less risk to more unknowns/risk, as some of these are already further along in adoption and specification than others.</p><h4>Serverless/Static</h4><p><a href="https://martinfowler.com/articles/serverless.html">Serverless technology</a> has been underway for a while now, so it’s almost unfair to evaluate it in terms of feasibility, but it has significantly picked up steam as an idea within the dev community with the release and support of tools such as AWS Lambda and equivalents. Check the link if you’re unclear on what it is, but the tl;dr is that serverless technology frees developers from managing some of the lower-level sub-application pieces that might reside at the server level/in the DevOps bucket.</p><p>Unlike most of the other items on this list, Serverless patterns seem to affect the end UX less, moreso serving as tools to reduce development costs/increase velocity/increase simplicity. <strong>Most devs, especially back-end/full-stack devs, will know or have used a serverless pattern very soon or already have (even if they don’t call it “serverless”).</strong></p><h4>PWAs</h4><p>Progressive web apps are <a href="https://developers.google.com/web/fundamentals/codelabs/your-first-pwapp/">next-level web apps</a> that utilize design and implementation methods such as service workers, json-based manifestos, and “application shell”-based UIs to bring the user native-like behavior such as adding an icon to the phone’s home screen and a more stable experience. A web-based approach in this way can help by reducing the up-front data cost and overall investment required from users.</p><p>I expect a <strong>high rate of adoption within 2 years from many large corporations or other organizations with models that stand to benefit from increasing their mobile user-adoption rates and brand effectiveness on mobile web</strong>. To me this is an obvious, incremental push towards increasing the web’s identity as a first-class platform for applications of all kinds. <a href="https://themanifest.com/app-development/11-examples-progressive-web-apps">Examples of progressive web apps</a>.</p><h4>WebAssembly</h4><p><a href="https://webassembly.org/">WebAssembly</a> is one of the most exciting and hyped technologies to appear in recent years. It’s tough to explain succinctly, but the tl;dr is that it will allow you to compile languages like C++ and Rust into a target that will run in JavaScript environments and allow for debuggable, highly performant native-like applications.</p><p>The promise here is that WebAssembly will allow browser apps, Node, and presumably other js runtimes like <a href="https://github.com/ry/deno">Deno</a> to run compute-oriented code ranging from AAA games to image recognition and offer the developer features like threading and more direct access to memory in the js environment.</p><p>Need more proof of the power of WebAssembly? <a href="http://aws-website-webassemblyskeletalanimation-ffaza.s3-website-us-east-1.amazonaws.com/">Click here</a> and change the number of skeletal models to 100. Compare it between WebAssembly and JavaScript using the dropdown and maybe you’ll get a more intuitive sense of what is possible with this technology.</p><p>The MVP of WebAssembly is already complete <a href="https://webassembly.org/docs/future-features/">with many further features</a> in active development like threads, garbage collection, and ECMAScript module support. Currently its much easier to find proof of concepts and demos out in the wild using WebAssembly, but as <a href="https://blog.figma.com/webassembly-cut-figmas-load-time-by-3x-76f3f2395164">this article from Figma</a> details, the benefits are quite material. That being said, there are still browser implementation issues and I expect <strong>another 1–2 years before it’s easy to find high-profile production applications and highly-used libraries implemented using WebAssembly (partially or wholly)</strong>.</p><h4>WebXR / Gamepads API</h4><p>One of the most contentious topics of our time is the viability, timeline of adoption, and platforms involved in XR interface technology. At AmsterdamJS <a href="https://twitter.com/diekus">Diego Gonzalez</a> demoed how browsers like Samsung Internet are already supporting WebXR, and the complementary browser-based <a href="https://developer.mozilla.org/en-US/docs/Web/API/Gamepad_API/Using_the_Gamepad_API">Gamepads API</a>. WebXR (aka the WebXR Device API) would enable you to navigate to websites that functioned as XR apps. (Here is a video I made on the differences between VR, MR, and AR)</p><p>Although the APIs mentioned are still in flux regarding their implementation details, they’re experimentally adopted by most major browsers, and dev frameworks like <a href="https://aframe.io/">A-frame</a> are receiving plenty of open source attention. I am quite bullish on the importance of 3D in the web going forward, and WebXR helps solve one of the biggest obstacles in XR right now, which is distribution of content (by leveraging the browser and using the web as a distribution platform).</p><p>That being said, I think there are still numerous obstacles in terms of developer/designer mindshare, consumer adoption, and hardware. I would look for <strong>adoption of WebXR for specific applications within domains such as architecture/AEC, gaming, and 3D modeling/art in around 4 years</strong>.</p><h4>Final Thoughts</h4><p>I think the question we should ask ourselves is, long term, why shouldn’t <strong>everything</strong> run in the browser? That is to say — why shouldn’t every application be reachable by a URL (or browser app) and quickly executable in a portable, OS-agnostic JavaScript/WebAssembly driven virtual machine? There are and will be reasons, but the default blocker “browsers just can’t do that” is fading more every day.</p><p>I estimate in about 5 years, the limitations of the browser will be (and will be perceived to be) considerably less significant than they are today; frameworks and patterns for developing 3D, compute-heavy, and otherwise richer native-like applications will see increased adoption, especially where it makes sense to leverage the distribution pattern of the web.</p><p>Furthermore, incremental improvements to the bread-and-butter technologies that are already important to the web, such as testing frameworks (like Cypress), programming paradigms (like reactive/async programming), and PWAs will increase the dev experience, user experience, and quality of web development in general.</p><p>It is an exciting time to be writing browser software; if you are interested in leveling up your career for the future, I suggest making time to study tech that relates to the points above that you may not be using already, such as <a href="https://egghead.io/courses/get-started-using-webassembly-wasm">WebAssembly</a> or <a href="https://webglfundamentals.org/">WebGL</a>. Becoming familiar with 3D interface design patterns and interfaces may also prove useful.</p><p>What do you think, am I way off of the mark? Let me know on <a href="http://zodiackodiak.com/amsterdamjs-thoughts-the-shape-of-web-to-come/twitter.com/zodiackodiak">Twitter</a>. Or, I’ll see you at AmsterdamJS next year!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7886a7e4eb06" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Overwatch Can Teach Software Developers]]></title>
            <link>https://medium.com/@thomasaugustusgrice/what-overwatch-can-teach-software-developers-192face1f933?source=rss-5f723f80010e------2</link>
            <guid isPermaLink="false">https://medium.com/p/192face1f933</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[overwatch]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Thomas Augustus Grice]]></dc:creator>
            <pubDate>Wed, 06 Dec 2017 10:05:18 GMT</pubDate>
            <atom:updated>2017-12-06T22:18:02.434Z</atom:updated>
            <content:encoded><![CDATA[<h3>What Overwatch Can Teach Software Developers</h3><p>Overwatch is a very popular game, with plenty of polish on top of even more depth, and a masterfully crafted look and story thanks to the hard-working people at Blizzard. However, it is also known for some having some frustrating moments and unforgiving reliance on team coordination. I’ve found software development to parallel Overwatch in some regards; here are the lessons I’ve learned.</p><h4>There are ups and downs.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-2IF-U_F9-N9FCIxqrDLCA.jpeg" /><figcaption>You will be the frozen hog, sometimes.</figcaption></figure><p>There is no way to avoid losing some % of the time in Overwatch or any other competitive game I can think of. You are going to make the wrong guess based on limited information (I didn’t know that Hanzo was around the corner…) or your mechanical skills will fail you (if it happens to <em>Sinatraa</em>, it will happen to you).<br>Similarly, in software jobs and careers, you will have moments where you are at fault. You will push bugs. You may even <a href="https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-incident/">delete the database</a>.</p><p>Virtually all of the time, the correct move is to identify what you could’ve done differently; or, if it wasn’t your fault, how could you have supported your teammate? The answer is pretty much never to complain, scream, yell, or shun your teammates. Although you will undoubtedly run into much of this in Overwatch Competitive solo queue. Be the bigger person :)</p><h4>Positivity is worth more than negativity.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E0SXI8uJm-E_IGDlxL5yvQ.jpeg" /><figcaption>Be as positive as Lucio: “…we’re gonna do great!”</figcaption></figure><p>Something I’ve learned from working collaboratively with others on software projects is, although constructively negative feedback can be useful when measured (“I think there’s a better way to do this…”) and distributed mindfully, you should be giving <strong>positive feedback</strong> at least 3 times as often. The best teams I’ve worked with, in Overwatch and in software, build each other up to an almost ridiculous extent.</p><p>In Overwatch, positive feedback can build up the rapport you need to give negative feedback later on. If the first words out of your mouth are usually “can you swap off of `HANZO || TORBJORN || WIDOWMAKER`”, even if you’re right, you’re often chipping away at a foundation between your team that may not even exist yet, and this will cause you to lose more games than you win.</p><h4>You can’t always carry by yourself.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WfwxNd34ef4SWUE27RwM5Q.jpeg" /><figcaption>This genji thinks he can solo carry</figcaption></figure><p>There’s something to be said for carrying in Overwatch. If you’re a sick nasty genji playing in bronze or silver, you may be able to single handedly turn the game for your less-able teammates. However, this quickly changes as the environment begins to offer more challenges.</p><p>In software, as project ambitions and individual responsibilities grow in size, so will the pressure to perform. And perform you must — but the more you are in concert with your teammates, the higher chance of success. And there will always be a requirement of cooperation, the degree of which is dependent on the web of dependencies. But it’s unlikely you will be able to solo carry software projects once you are doing Diamond-or-above rank software development, so work with your team to capture the objective.</p><p>Thanks for reading! I stream programming, creating, and sometimes Overwatch <a href="http://twitch.tv/zodiac_sign">on twitch</a>,<br>I also <a href="http://twitter.com/zodiackodiak">tweet</a>, <a href="http://instagram.com/z0diacsign">instagram</a>, and run a <a href="https://www.youtube.com/channel/UCirwGXPsGb1-If-TGuhhR1A?view_as=subscriber">tech/XR podcast</a>. I’d love to chat about Overwatch, software engineering, or just about anything else, so hit me up.</p><p><em>All images from Overwatch’s official </em><a href="https://playoverwatch.com/en-us/media/"><em>media page.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=192face1f933" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rendering Big Ass Lists In React]]></title>
            <link>https://medium.com/@thomasaugustusgrice/rendering-big-ass-lists-in-react-b1f69aa2b8da?source=rss-5f723f80010e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1f69aa2b8da</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web]]></category>
            <category><![CDATA[redux]]></category>
            <category><![CDATA[acre]]></category>
            <dc:creator><![CDATA[Thomas Augustus Grice]]></dc:creator>
            <pubDate>Tue, 31 Oct 2017 09:35:15 GMT</pubDate>
            <atom:updated>2017-10-31T09:35:47.677Z</atom:updated>
            <content:encoded><![CDATA[<p>One problem that continuously comes up in front-end development is rendering lists of a large size N. Keep in mind that which solution you use to solve your problem is based on the structure, content, and styling of your DOM nodes, the hardware you expect to run on, and just how large you expect N to be.</p><p><strong>1. Avoid making a big ass list at all</strong></p><p>First order of business should always be making sure the thing you’re implementing _is the right thing_. Think about how you are presenting information to the user. It could be that a huge list is totally wrong, and maybe you have the time, resources, and architecture to implement a nice searching or filtering pattern, or some other capability that reduces the count of items presented to the user. Using pagination to reduce the number of items is another option.</p><p><strong>2. Reduce the number of render cycles</strong></p><p>It could be that the number of items you are presenting is fine, it’s just being unnecessarily updated (and re-rendered) too often. Fixing this could mean reducing the amount of calculations going on in the `render()` function of your component; if it is possible to store values in state instead of performing some operations to calculate or infer them, for example, that could be an improvement.</p><p>Another way to address this can be reworking your <em>shouldComponentUpdate()</em> function of your component. The boolean return value of this function determines whether a component should re-render due to a change in state or props, and by default always returns true. A stateless functional component will also always re-render. So consider making your component a class and only changing the state when particularly relevant props or state are changed, to save render cycles.</p><p><a href="https://blog.logrocket.com/make-react-fast-again-part-2-why-did-you-update-dd1faf79399f">Here’s an article that explores some tooling around this idea of discovering unnecessarily re-rendering components.</a></p><p><strong>3. Virtualize the list</strong></p><p>A cool and effective way to solve the problem is to create a virtual list that only renders rows that are visible within a given container, and creates a “fake scrolling” effect that keeps track of your scroll position and renders the appropriate items. This solution works well when you can’t use solution <strong>1</strong> or <strong>2</strong>. For example, if you have a large amount of items, but no time to implement an effective search or pagination mechanism, and reducing renders doesn’t seem to help.</p><p>Here are a few react libraries that create virtual lists. The way you use these libraries follows a basic pattern of “<em>tell the lib how big your list items are, how big you want the container to be, and finally the JSX markup of each item.</em>” It can be slightly tricky if you want to support items of different sizes, for example if one item in the list is toggled. A major downside is that a user will not be able to use the native ctrl + f in the browser to find the items that they want, so you may need to implement a rudimentary version yourself if you want to support that behavior.</p><p>* <a href="https://github.com/clauderic/react-tiny-virtual-list">React Tiny Virtual List</a> (this one worked well for me)<br>* <a href="https://github.com/developerdizzle/react-virtual-list">React Virtual List</a> (I had trouble with this one, but probably still worth a shot)</p><p>I believe these solutions _should_ allow most of y’all to continue happily developing. Given enough time and resources, you should try to eventually land on a friendly information architecture that supports your users’ searching behaviors (solution <strong>1</strong>). But did I miss anything? Feel free to reach out and let me know.</p><p>twitter: [<a href="http://twitter.com/zodiackodiak">@zodiackodiak</a>]<br>email: [<a href="/service/mailto:augustus.grice@gmail.com">augustus.grice@gmail.com</a>]<br>originally published on my website, <a href="http://augustus.tech/">augustus.tech</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1f69aa2b8da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Minimum Wage — Treating the Symptoms]]></title>
            <link>https://medium.com/@thomasaugustusgrice/minimum-wage-treating-the-symptoms-e4e37f996eb2?source=rss-5f723f80010e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4e37f996eb2</guid>
            <category><![CDATA[poverty]]></category>
            <category><![CDATA[economics]]></category>
            <category><![CDATA[minimum-wage]]></category>
            <dc:creator><![CDATA[Thomas Augustus Grice]]></dc:creator>
            <pubDate>Sat, 01 Aug 2015 20:43:58 GMT</pubDate>
            <atom:updated>2015-08-01T20:44:41.263Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Minimum Wage — Treating the Symptoms</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sR-w0nc1CjTr1u97OI_Rdg.png" /></figure><p><em>“$15 an hour? For flipping burgers?”</em></p><p>This is one of the most common memes you will encounter, in one form or another, when discussing (or reading discussion on) raising the minimum wage in the USA. There is a pervasive idea, moreso in conservative circles, that no one deserves $15 for preparing a meal, stocking shelves, or other low-skill, traditionally viewed as bottom-of-the-barrel, jobs.</p><p>T<a href="http://www.sciencedirect.com/science/article/pii/0014292195000356">here</a> <a href="http://www.cepr.net/documents/publications/min-wage-2013-02.pdf">are</a> <a href="http://www.scirp.org/journal/PaperInformation.aspx?paperID=38310#.VbcK-hNViko">many</a> resources, academic and otherwise, that suggest that an increase in the minimum wage has a neutral to positive effect on the economy. You can also find sources that <a href="http://www.washingtonpost.com/blogs/wonkblog/wp/2013/06/22/a-15-minimum-wage-is-a-terrible-idea/">argue in the opposite direction</a>.</p><p>The exact dollar amount, and whether to raise it in the first place, is debatable but it seems likely that <em>some </em>increase in the current minimum wage would be a good idea. However, that isn’t what I think should be the focus of our efforts in evaluating a minimum wage increase; we should be focusing on <em>why </em>we want to increase the minimum wage.</p><p>All the documentation I can find reinforces the idea that the fight to establish a minimum wage has always been to guarantee a certain standard of living for working individuals in our country; to quote President Roosevelt: ““By living wages, I mean more than a bare subsistence level — I mean the wages of a decent living.”<br>The question, to me, then seems to be <em>what</em> exactly we want to guarantee for working citizens of our nation — what do we consider a decent living? When I boil life down into the bare necessities for a dignified existence with significant opportunity, I come up with the following:</p><ul><li>Food (<a href="http://www.feedingamerica.org/hunger-in-america/our-research/hunger-in-america/">1 in 7 Americans uses a food bank each year</a>)</li><li>Shelter (More than 3 million people are homeless, and <a href="http://www.nationalhomeless.org/factsheets/employment.html">44% of homeless people are employed</a>)</li><li>Education (the <a href="http://www.huffingtonpost.com/howard-steven-friedman/americas-poverty-education_b_1826000.html">statistical link</a> between access to education and income levels is undeniable)</li><li>Healthcare (the <a href="http://www.nihcm.org/pdf/DataBrief3%20Final.pdf">distribution of healthcare</a> and <a href="http://247wallst.com/special-report/2014/07/07/countries-spending-the-most-on-health-care/">efficiency</a> are embarrassing)</li></ul><p>Currently, based on my experiences and simple math, you may be able to survive and even save a grand or two on minimum wage if you live in a cheap state, are very frugal, have scholarships or no educational aspirations, are debt-free and willing to take public transportation, and have no combination of interests that cost more than $1,000 a year.</p><p>That’s a lot of “ifs” and, built into those “ifs” is the assumption that you are knowledgeable and informed about how to take advantage of loopholes such as the ACA’s tax premium benefits, are okay living in a squalorous apartment complex with one or more roommates, and have a public transport system that enables your transport to-and-from your minimum wage job. If you want an education, you’d better figure out how to get a scholarship, or you’re taking on massive loans and <a href="https://studentaid.ed.gov/sa/eligibility/criminal-convictions">you’d better not have a drug charge on your record</a> (though that’s a debate for another time).</p><p>I’m personally not comfortable with the amount of qualifiers I had to use to frame a minimum wage lifestyle as decent. It seems our minimum wage is a lot closer to Roosevelt’s “bare subsistence level” than it is a living wage in the most wealthy and influential nation in the history of the known universe.</p><p>One interesting fact to consider is that we don’t, strictly speaking, <strong>need </strong>to have the federal government holding corporations’ feet to the fire to raise compensation for employees. Companies can do so voluntarily, and we need only look to the Pacific Northwestern wage-oasis of Seattle to discover Dan Price’s Gravity Payments and <a href="http://www.nytimes.com/2015/08/02/business/a-company-copes-with-backlash-against-the-raise-that-roared.html?hp&amp;action=click&amp;pgtype=Homepage&amp;module=second-column-region&amp;region=top-news&amp;WT.nav=top-news">the controversy surrounding his $70,000 minimum salary for Gravity employees</a>.</p><p>As we can see, this voluntary reassessment of the pay for Gravity’s employees has caused some conversation, much of it bitterly negative, in the direction of Mr. Price’s establishment. Regardless, Price’s cognizance of the risk he is taking by setting the example he is is laudable. He doesn’t pretend that his solution is one-size-fits-all or that it is anywhere close to failure-proof.</p><p>Moreover, examining the <a href="http://www.povertyusa.org/the-state-of-poverty/poverty-map-state/#">poverty map</a> (also the title image of this article), we can draw an interesting line from minimum wage to poverty. Southern states, almost none of which have above-federal minimum wage laws in place, comprise the most uniformly poverty-stricken region in the nation (indicated graphically by redness).</p><p>In fact, economies and businesses are complex systems and it is laughable to think that a flat number is the right wage for individuals across a nation of hundreds of millions and spanning one ocean to another. But if businesses and those leading the economy fail to adjust appropriately, they risk governmental intervention along with populist outrage.</p><p>It’s possible that raising the minimum wage to $15 is not the right solution. It’s possible that we should address these issues more directly — that by artificially raising the wage floor, we are simply treating the symptoms in too general a manner.However, in joining the chorus against the raising of the minimum wage, what solutions do you offer or support in contrast to that solution? Do you acknowledge the grim statistics and conditions that many (employed) Americans face? In the face of poverty, the rising costs of education, and the often back-breakingly expensive costs to healthcare — do you believe that the employers will choose to provide more to their employees without government intervention?</p><p>If we can become honest in our engagement of the problems of America — and realize many Americans are living well below the ideals healthy, educated, modern society — perhaps even traditionally conservative business owners can make the decision to voluntarily raise the floor for all citizens. If not, I don’t see the demand for a minimum wage going away, and the irony of free-market stubbornness forcing federal actions will likely continue.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4e37f996eb2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>