<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>People on Nerdstein</title><link>https://nerdstein.net/tags/people/</link><description>Recent content in People on Nerdstein</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 22 Sep 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://nerdstein.net/tags/people/index.xml" rel="self" type="application/rss+xml"/><item><title>SimplyTest.me From The Ground Up</title><link>https://nerdstein.net/blog/simplytest-from-ground-up/</link><pubDate>Wed, 22 Sep 2021 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/simplytest-from-ground-up/</guid><description>&lt;p>When I took over as the project lead for SimplyTest.me, the previous lead shared three primary things with me:&lt;/p>
&lt;ul>
&lt;li>
&lt;p>The system had a non-trivial amount of technical debt and was rising more with time&lt;/p></description></item><item><title>Weekend Thoughts, 9/11/21: A legacy</title><link>https://nerdstein.net/blog/weekend-thoughts-6/</link><pubDate>Sat, 11 Sep 2021 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/weekend-thoughts-6/</guid><description>&lt;p>On the 20th anniversary of 9-11, it’s hard to ignore how fleeting life is. What we accomplish during our time is up to us.&lt;/p>
&lt;p>What do you want your legacy to be? Are you fulfilling it? Do you maintain awareness toward your goals and what impact you want to have?&lt;/p></description></item><item><title>Weekend Thoughts, 9/4/21: Leading through change</title><link>https://nerdstein.net/blog/weekend-thoughts-5/</link><pubDate>Sat, 11 Sep 2021 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/weekend-thoughts-5/</guid><description>&lt;p>Changes to teams, organization, structure, or process should be thoughtful and done with patience. Change can take time to materialize. Teams often don’t like change. Making changes too frequently often doesn’t allow a team to get past the storming, norming and performing phases and therefore doesn’t allow for the expected investment to be realized.&lt;/p></description></item><item><title>SimplyTest.me Welcomes Matt Glaman</title><link>https://nerdstein.net/blog/welcome-matt-glaman/</link><pubDate>Sat, 02 Jan 2021 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/welcome-matt-glaman/</guid><description>&lt;p>SimplyTest.me is a labor of love but it has been one of the most unique, satisfying contributions I&amp;rsquo;ve made to the community. Most of that labor has been dedicated toward maintaining the Drupal 7 version. Our maintenance was massively improved with the introduction of Tugboat.QA, but this year found major changes in the Drupal community with the launch of Drupal 9, the major changes to Composer workflows, and the Gitlab integration. All of these things are of high impact for Drupal and required major changes to SimplyTest. This has been especially hard to keep up with for me. Our latest incident showed the limitations of the current system, where SimplyTest.me was blocked from the Gitlab infrastructure due to updates in Drupal.org&amp;rsquo;s patching workflow. Much of this pulled my attention away from our aspirations to launch a new version. Until very recently, that is.&lt;/p></description></item><item><title>Finally! A website refresh</title><link>https://nerdstein.net/blog/new-site-2020/</link><pubDate>Mon, 28 Dec 2020 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/new-site-2020/</guid><description>&lt;p>Let me welcome you to the new nerdstein.net. I&amp;rsquo;d like to thank Ana Laura Coto for help with the design. I&amp;rsquo;d like also thank Jonathan Daggerhart for being there when I needed an assist. I am really happy to finally share this project with the world.&lt;/p></description></item><item><title>Drupal Community Care Packages</title><link>https://nerdstein.net/blog/drupal-community-care-packages/</link><pubDate>Thu, 30 Apr 2020 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/drupal-community-care-packages/</guid><description>&lt;p>Our community has always meant more than just code. These last several months have been difficult to make the same kind of connection we have come to expect from things like in-person events. And, during this time, many of us are having to juggle new challenges, may have sick loved ones, face professional or financial uncertainty, and more. I’m choosing to do something about it.&lt;/p></description></item><item><title>A DevOps Primer</title><link>https://nerdstein.net/blog/devops-primer/</link><pubDate>Mon, 29 Apr 2019 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/devops-primer/</guid><description>&lt;p>I just closed about 100 browser tabs from an early year activity. While it’s embarrassing I left those tabs open so long (going on five months), I wanted to leave them open to reflect on what I learned. And, what a better way to reflect than a blog post.&lt;/p></description></item><item><title>SimplyTest.me and Google Summer of Code 2019</title><link>https://nerdstein.net/blog/simplytestme-and-google-summer-code-2019/</link><pubDate>Thu, 07 Mar 2019 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/simplytestme-and-google-summer-code-2019/</guid><description>&lt;p>&lt;a href="https://simplytest.me/">SimplyTest.me&lt;/a> is a project I continue to lead and volunteer my time to. I’m driven to help lower the barrier to entry for people in our community to contribute, use Drupal, and be a part of our community.&lt;/p></description></item><item><title>My 2019 Aaron Winborn Award Nomination</title><link>https://nerdstein.net/blog/my-2019-aaron-winborn-award-nomination/</link><pubDate>Wed, 06 Feb 2019 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/my-2019-aaron-winborn-award-nomination/</guid><description>&lt;p>Last year, I read Jim Birch’s blog post outlining his Aaron Winborn nomination of (now) award winning Kevin Thull. As a community, we need to do our best to celebrate accomplishments and I love that this award exists. We need to tell more of our stories regardless of who gets the award. I see no reason not to share my nomination for this year’s award publicly.&lt;/p></description></item><item><title>The Season of SimplyTest</title><link>https://nerdstein.net/blog/season-simplytest/</link><pubDate>Fri, 18 Jan 2019 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/season-simplytest/</guid><description>&lt;p>Last year was spent primarily learning about SimplyTest. We did make some progress, but I think “keeping the lights on” for a system of this complexity was quite a feat after the project transfer. It’s a unique and fairly complex endeavor that bridges all elements of an open source project, a completely free service, and underlying infrastructure. I see all of the good and the bad that comes from each aspect: system maintenance, feedback from community members, customer service (Slack, Twitter, etc), system outages, and more. I recognize how valuable this service is to the community and I strive to offer the best service possible.&lt;/p></description></item><item><title>Mid-2018 Drupal Coffee Exchange Updates</title><link>https://nerdstein.net/blog/mid-2018-drupal-coffee-exchange-updates/</link><pubDate>Sat, 26 May 2018 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/mid-2018-drupal-coffee-exchange-updates/</guid><description>&lt;p>We are about to start another quarter of the Drupal Coffee Exchange. Personally this has been a lot of fun to see this start from humble beginnings and an off-the-cuff idea posted to Twitter to now have a growing membership and have been running for over a year now. We now have international participation and are looking to expand that. For me, it’s yet another reminder our community goes well-beyond the commits. Now we have a way for community members to stay caffeinated and share our favorite coffees between community enthusiasts. It’s unique, it’s fun, and it’s become a creative and complementary way to participate in our community.&lt;/p></description></item><item><title>Achieving Clarity in Component-based Best Practices</title><link>https://nerdstein.net/blog/achieving-clarity-component-based-best-practices/</link><pubDate>Mon, 02 Apr 2018 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/achieving-clarity-component-based-best-practices/</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>Here we are. It’s been over a year now that our community has explored design components (integration of design systems, pattern libraries, etc) and Drupal. The community has shared different tools and solutions, presentations from many individuals representing different companies and perspectives, and processes/workflows that enable the different teams and disciplines. I would classify the time spent to date as research, exploration, and innovation. While this is expected for something new, we need to define best practices. The purpose of this blog post is to help us start a conversation to have guidelines and principles we can use to have better discretion when developing component-based solutions.&lt;/p></description></item><item><title>2017 Conference Review</title><link>https://nerdstein.net/blog/2017-conference-review/</link><pubDate>Sun, 14 Jan 2018 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/2017-conference-review/</guid><description>&lt;p>2017 has been incredible and a year of both personal and professional growth. Events like camps and conferences are critical for me to be active in the community, as I don’t have a local group or regional meetup. In 2017, I gave more presentations than I ever expected to. I travelled to many awesome cities. I had a personal goal of giving a keynote/featured talk. I ended up giving three. I went to many places I had never seen before (both at work and through community events). I’m astonished by how much effort and care volunteers put into these events. I shared meals, craft beers, and locally roasted coffee with countless amazing individuals. I’m incredibly fortunate to have a supportive family and to work for a company that truly cares about participation and contribution to free and open source communities, like Drupal. Not only was I able to share things I’ve learned with the community, but I was able to spend time with old and new friends. I’ll have many fond memories looking back on this time and am just as excited for 2018.&lt;/p></description></item><item><title>Exploring simplicity in Drupal design components</title><link>https://nerdstein.net/blog/exploring-simplicity-drupal-design-components/</link><pubDate>Mon, 02 Oct 2017 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/exploring-simplicity-drupal-design-components/</guid><description>&lt;p>Component-based architectures have become both a popular and fairly crowded space in the Drupal community. For over a year, I have followed the progress of some tools created by those leveraging Pattern Lab as a component based design library. I can’t claim to know the full breadth of problems these individuals encountered, many of which are experienced technologists in our space. But, every solution I have seen has been complex and demonstrates some architectural red flags. I wanted to take a fresh look. I paid a designer to redesign my blog for a migration to Drupal 8. This presented the perfect opportunity to try this out. Consider the following post a simple approach you might be able to use.&lt;/p></description></item><item><title>An Analysis of Drupal Governance</title><link>https://nerdstein.net/blog/analysis-drupal-governance/</link><pubDate>Tue, 29 Aug 2017 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/analysis-drupal-governance/</guid><description>&lt;h1>&lt;/h1>
&lt;p>In my &lt;a href="https://nerdstein.net/blog/community-governance-considerations-open-source-projects">earlier blog post&lt;/a>, I researched community governance in other open source communities. While it was not exhaustive, I identified a set of trends and practices communities use to serve community members. The question remains: what can Drupal learn from other communities?&lt;/p></description></item><item><title>Promoting Community Toxicity</title><link>https://nerdstein.net/blog/promoting-community-toxicity/</link><pubDate>Tue, 18 Jul 2017 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/promoting-community-toxicity/</guid><description>&lt;p>Something has been bothering me and I haven&amp;rsquo;t been able to put my finger on it. I hesitated writing this. By doing so, I fully understand that some will choose to twist or misinterpret my words to further instill doubt into the community. While this is one&amp;rsquo;s right and often turns into a lengthy Twitter debate, many in the community have shied away from sharing their voice for fear of retribution. &lt;/p></description></item><item><title>A Drupal Contribution Non-Profit</title><link>https://nerdstein.net/blog/drupal-contribution-non-profit/</link><pubDate>Thu, 08 Jun 2017 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/drupal-contribution-non-profit/</guid><description>&lt;p>Jrockowitz&amp;rsquo;s recent blog post on crowd sourcing, found &lt;a href="http://www.jrockowitz.com/blog/crowdfunding">here&lt;/a>, sparked so many ideas for me. I wanted to discuss the most prominent idea in this blog post, the idea for a company that nurtures community contributions. Such a topic has often been on my mind and Jrockowitz post might have helped me to connect enough dots around this idea. Community members (especially maintainers) often volunteer their time and energy to community projects with little incentive aside from their will to do good. &lt;/p></description></item><item><title>Community Governance Considerations of Open Source Projects</title><link>https://nerdstein.net/blog/community-governance-considerations-open-source-projects/</link><pubDate>Mon, 05 Jun 2017 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/community-governance-considerations-open-source-projects/</guid><description>&lt;p>DrupalCon was a great way to connect with the community and gauge the pulse from recent events involving Crell. After writing blog posts, I engaged with many people to share thoughts and hear perspectives. One common question that came up: what do other communities do for governance?&lt;/p></description></item><item><title>What Gets Me Up In The Morning</title><link>https://nerdstein.net/blog/what-gets-me-morning/</link><pubDate>Thu, 25 May 2017 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/what-gets-me-morning/</guid><description>&lt;p>It is safe to say that people like talking about themselves. I&amp;rsquo;m guilty of that, but I don&amp;rsquo;t think I have actually given any real consideration or focus to the matter. That changed this morning.&lt;/p></description></item><item><title>Removing Site Building From Drupal's Vocabulary</title><link>https://nerdstein.net/blog/removing-site-building-drupals-vocabulary/</link><pubDate>Tue, 23 May 2017 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/removing-site-building-drupals-vocabulary/</guid><description>&lt;p>Drupal has a full vocabulary of Drupalisms. While I think that is fine for Drupal-specific features, it also is a sign that we seem to promote our own island when there are similar concepts that exist in the technology space. When possible, we should try to align with more conventional terms that others outside of Drupal understand. If anything, this can make Drupal more approachable and better understood in broader context. I think I identified one such term: the term &amp;ldquo;Site Building&amp;rdquo; has never sat well with me - both as an activity and as a role. &lt;/p></description></item><item><title>Communal Action in Self and Others</title><link>https://nerdstein.net/blog/communal-action-self-and-others/</link><pubDate>Mon, 17 Apr 2017 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/communal-action-self-and-others/</guid><description>&lt;p>Sometimes situations take time to resolve. This situation is complicated and the goal is to treat everyone respectfully. We&amp;rsquo;re beginning to see things play out now.  &lt;/p>
&lt;p> &lt;/p>
&lt;p>I want to offer some of my recent thoughts. By no means are they right or fully informed, but I wanted to share (please don&amp;rsquo;t shoot the messenger).&lt;/p></description></item><item><title>Civility is Community</title><link>https://nerdstein.net/blog/civility-community/</link><pubDate>Wed, 12 Apr 2017 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/civility-community/</guid><description>&lt;p>For a moment, may some of the hurt and fearful in the Drupal community take a moment to pause and reflect. Take a deep breath and slow down from the continuous retweeting, reddit posts, or the most recent Drupal Confessions. (By the way, does anyone else think &amp;ldquo;Drupal Confessions&amp;rdquo; sounds like a Saturday Night Live skit or a bad emo song?)&lt;/p></description></item><item><title>Evolving Clarity of Conduct in Technical Communities</title><link>https://nerdstein.net/blog/evolving-clarity-conduct-technical-communities/</link><pubDate>Sat, 25 Mar 2017 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/evolving-clarity-conduct-technical-communities/</guid><description>&lt;p>In my previous two blog posts [&lt;a href="https://nerdstein.net/blog/troubling-situation-indeed">one&lt;/a>] [&lt;a href="https://nerdstein.net/blog/follow-more-informed-opinion-our-community-crisis">two&lt;/a>], I shared my concerns and open questions over the recent events surrounding Crell and discussed my initial efforts to become informed even when full transparency does not and likely will not exist. I have formed the opinion that those seeking answers and specifics may never get the level of detail they desire, both for legal and privacy reasons. I continue to engage with others in conversation out of respect for those processing these events and out of my desire to form a well-rounded and bias-free stance. With the complexities involved, there is no one right answer and we most importantly need to respect the broader discourse in participation of moving this forward.&lt;/p></description></item><item><title>A Troubling Situation Indeed</title><link>https://nerdstein.net/blog/troubling-situation-indeed/</link><pubDate>Thu, 23 Mar 2017 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/troubling-situation-indeed/</guid><description>&lt;p>When I was checking Twitter last night, a prominent community member posted a &amp;ldquo;TMI&amp;rdquo; message with a link to a blog post. This was totally off-character for a man regularly promoting thought leadership in technical capacities (why I was following him on Twitter). I was quite curious and I was immediately appalled by what I read. The post can be found here: &lt;a href="https://www.garfieldtech.com/blog/tmi-outing">https://www.garfieldtech.com/blog/tmi-outing&lt;/a>&lt;/p></description></item><item><title>Follow Up: A more informed opinion on our community crisis</title><link>https://nerdstein.net/blog/follow-more-informed-opinion-our-community-crisis/</link><pubDate>Thu, 23 Mar 2017 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/follow-more-informed-opinion-our-community-crisis/</guid><description>&lt;p>As I mentioned in my previous post, I was struggling to make sense of this situation. Was Crell treated fairly? Was he being discriminated for his beliefs? How is this possible in the confines of a community that supports diversity and inclusion? I spent parts of my day participating in discussions with team members, engaging community members, researching relevant topics, and reading responses of others that had their own questions and concerns. We are all still processing this and I ask you to please respect the diverse opinions from members in the community. In my post yesterday, I made it clear that I was not informed about the details nor the subject matter being discussed. I feel better informed and feel a level of obligation to respond to some of my earlier points in the spirit of helping others to process this highly complex and sensitive issue.&lt;/p></description></item><item><title>"First" based approaches need to die</title><link>https://nerdstein.net/blog/first-based-approaches-need-die/</link><pubDate>Wed, 08 Mar 2017 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/first-based-approaches-need-die/</guid><description>&lt;p>Off the top of my head, I can name several &amp;ldquo;first&amp;rdquo;-based approaches. Do any of these ring a bell? Mobile first, content first, API first, user first, design first, experience first, modeling first, security first.&lt;/p></description></item><item><title>Commits on Drupal.org</title><link>https://nerdstein.net/blog/commits-drupalorg/</link><pubDate>Fri, 09 Dec 2016 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/commits-drupalorg/</guid><description>&lt;p>I&amp;rsquo;m a huge advocate for finding ways to encourage more Drupal participants. Due to the complexity, it&amp;rsquo;s unreasonable to expect people to initially pick up programming-heavy issues. This is the motivation behind the &amp;ldquo;novice&amp;rdquo; label, providing a means for identifying potentially low-complex tasks new contributors could safely pick up. The end result is usually one or more commits which are credited to you and/or your organization on Drupal.org.&lt;/p></description></item><item><title>Lessons Learned: The "Why" and "How" of Drupal Contributions</title><link>https://nerdstein.net/blog/lessons-learned-why-and-how-drupal-contributions/</link><pubDate>Fri, 21 Oct 2016 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/lessons-learned-why-and-how-drupal-contributions/</guid><description>&lt;h2 id="why">Why&lt;/h2>
&lt;p>I am ashamed to admit, for the longest time I used Drupal (heck, even complained about it) but contributed absolutely nothing back. It occurred to me that, not only did I learn technical and marketable skills thanks to Drupal, my Drupal experience directly corresponded to opportunities that supported my livelihood and viability for me and my family. And, all of this occurred without one line of code from me contributed back.&lt;/p></description></item><item><title>Balancing Theory and Practice</title><link>https://nerdstein.net/blog/balancing-theory-and-practice/</link><pubDate>Fri, 23 Sep 2016 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/balancing-theory-and-practice/</guid><description>&lt;p>When you are building a tool, how do you measure the success of your efforts? There are data driven approaches around adoption, like number of times your tool has been downloaded or installed. Similarly, success could be defined as how effectively you solved the problem. This could be measured by the number of issues filed, the (hopefully) lack of vulnerabilities, or the number of feature requests created. But, in any measure, success is actually defined by &lt;strong>other people&lt;/strong>. And, as an engineer, it&amp;rsquo;s such a difficult task to put yourself in their shoes. How do you deal with that?&lt;/p></description></item><item><title>The Technical Lift of Drupal 8</title><link>https://nerdstein.net/blog/technical-lift-drupal-8/</link><pubDate>Wed, 27 Jul 2016 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/technical-lift-drupal-8/</guid><description>&lt;p>Drupal 8 has been widely praised for improving the developer experience (DX). The &amp;ldquo;best of breed&amp;rdquo; adoption of tools (see: Symfony, Guzzle, PHPUnit, Composer, etc) clearly positions Drupal to mature and evolve beyond that which one community is able to do alone. But, there are many different considerations of DX that need explored. And, what lift is required for the community to grasp this new version? And, what is the impact?&lt;/p></description></item><item><title>The office is dead</title><link>https://nerdstein.net/blog/office-dead/</link><pubDate>Mon, 11 Apr 2016 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/office-dead/</guid><description>&lt;p>I recently made a pass through historic downtown Altoona and I noticed how many buildings appeared to be empty. It actually occurred to me that my definition of infrastructure has shifted radically from the conventional infrastructure companies have adopted. The &amp;ldquo;office&amp;rdquo; is hardly a requirement for a majority of jobs.&lt;/p></description></item><item><title>Our fights are not your fights</title><link>https://nerdstein.net/blog/our-fights-are-not-your-fights/</link><pubDate>Tue, 08 Mar 2016 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/our-fights-are-not-your-fights/</guid><description>&lt;p>I&amp;rsquo;m not one to really dig my heels into politics. I find it divisive and I recently had a clear example as to why.&lt;/p>
&lt;p> &lt;/p>
&lt;p>Earlier, I heard my doorbell ring. It was a Bill Shuster promoter walking door to door in my neighborhood. I have already grown tired of his campaign, seeing television commercials with scathing attacks on Democrats, his extreme views on health care, and the flashing images of Sarah Palin and other off-the-wall conservatives he self aligns with. I was handed a pamphlet of information and needed to look no further than the cover to set me off.&lt;/p></description></item><item><title>"Just Enough" Planning - An Agile Concept</title><link>https://nerdstein.net/blog/just-enough-planning-agile-concept/</link><pubDate>Wed, 02 Dec 2015 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/just-enough-planning-agile-concept/</guid><description>&lt;p>The Agile framework is all the rage. It aims to solve limitations introduced by waterfall. The framework is driven by value and priority, not fixed scope and heavy upfront planning. But, Agile and its Scrum variant is just a set of theories not intended to fully prescribe practice. There are many challenges that observing strict Agile/Scrum can present in practice, especially for agencies attempting to adopt it outside of a product development process.&lt;/p></description></item><item><title>Reliability</title><link>https://nerdstein.net/blog/reliability/</link><pubDate>Thu, 29 Oct 2015 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/reliability/</guid><description>&lt;p>Hands down, a huge pet peeve of mine is &lt;strong>a lack of reliability&lt;/strong>. &lt;/p>
&lt;p> &lt;/p>
&lt;p>Let me be clear, this is by no means to say that I am impatient. I often provide people countless opportunities to be reliable. But, I&amp;rsquo;ve learned over time that the more patient I am with something, the higher my expectations get.&lt;/p></description></item><item><title>Engineering Tenets of Agile</title><link>https://nerdstein.net/blog/engineering-tenets-agile/</link><pubDate>Wed, 21 Oct 2015 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/engineering-tenets-agile/</guid><description>&lt;h2 id="background">Background&lt;/h2>
&lt;p>I recently changed companies and am going through the process of onboarding. One of the big draws to the new company was an emphasis on people and culture. The whole balance between a for-profit business and a focus on employee needs, in my experience, can be in conflict. I have been learning more about how these goals are achieved.&lt;/p></description></item><item><title>Simple beauty of life</title><link>https://nerdstein.net/blog/simple-beauty-life/</link><pubDate>Thu, 16 Jul 2015 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/simple-beauty-life/</guid><description>&lt;p>This morning I read this &lt;a href="http://triblive.com/sports/college/duquesne/8749031-74/burt-cancer-simple#axzz3g3dL1J4B">article&lt;/a>. It&amp;rsquo;s a short phrase that stood out: &lt;strong>simple beauty of life&lt;/strong>. This reiterates a common thread from many others with severe illness or little time left. Notably former CMU Professor Randy Pausch, who died of cancer, who left a lasting impression with his &lt;a href="https://www.youtube.com/watch?v=ji5_MqicxSo">last lecture&lt;/a>. Mitch Albom wrote a popular book, &lt;a href="https://www.amazon.com/Five-People-You-Meet-Heaven/dp/1401308589/ref=asap_bc?ie=UTF8">The Five People You Meet in Heaven&lt;/a>, about a life&amp;rsquo;s reflection and purpose.  &lt;/p></description></item><item><title>My temperature is happy</title><link>https://nerdstein.net/blog/my-temperature-happy/</link><pubDate>Tue, 14 Jul 2015 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/my-temperature-happy/</guid><description>&lt;p>This evening, my daughter and I were playing doctor. I laid on the floor and she gave me a checkup. She looked at my ears. &amp;ldquo;Better&amp;rdquo;. She checked my heartbeat. She nodded her head. And, lastly, she checked my temperature. Her response was perfect and I hope I never forget it: &amp;ldquo;&lt;strong>My temperature is happy&lt;/strong>&amp;rdquo;.&lt;/p></description></item><item><title>Being present</title><link>https://nerdstein.net/blog/being-present/</link><pubDate>Tue, 14 Apr 2015 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/being-present/</guid><description>&lt;p>Generally speaking, I try to be very laid back. I do get stressed out (and continue to try to work on that). However, there is one major pet peeve of mine that I believe is worth sharing. &lt;strong>Being present.&lt;/strong>&lt;/p></description></item><item><title>Institutional knowledge</title><link>https://nerdstein.net/blog/institutional-knowledge/</link><pubDate>Sun, 11 Jan 2015 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/institutional-knowledge/</guid><description>&lt;p>No one is irreplaceable, and that is a fact. Teams often find ways to overcome the loss of staff, even creatively. Some losses hurt more than others. One key factor is institutional knowledge. This is one area that often makes employees feel irreplaceable, but should be avoided at all costs by a business.&lt;/p></description></item><item><title>A plea for patience</title><link>https://nerdstein.net/blog/plea-patience/</link><pubDate>Wed, 12 Nov 2014 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/plea-patience/</guid><description>&lt;p>I am a big fan of learning moments. In business, some learning moments come at a cost. Some mistakes are easier to forgive than others. I still believe in exercising as much patience as possible to allow people to learn.&lt;/p></description></item><item><title>Routine stifles innovation</title><link>https://nerdstein.net/blog/routine-stifles-innovation/</link><pubDate>Sun, 31 Aug 2014 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/routine-stifles-innovation/</guid><description>&lt;p>I was recently asked about what separates my company from others I have worked in the past. What immediately came to mind was the relationship with my team, the work we do, and the sheer talent. Those elements alone still make me get up in the morning. But, over a cold beer, something else struck with me. &lt;strong>My company has no routine&lt;/strong> and I love it. &lt;/p></description></item><item><title>Desirable Short Term Memory</title><link>https://nerdstein.net/blog/desirable-short-term-memory/</link><pubDate>Wed, 20 Aug 2014 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/desirable-short-term-memory/</guid><description>&lt;p>Recently, it hit me that there are actually benefits to having a short term memory. I don&amp;rsquo;t think this is broadly applicable. In fact, I think there are more instances in which you do not want to have a short term memory. Allow me to explain&amp;hellip;&lt;/p></description></item><item><title>Social Vampirism in Services</title><link>https://nerdstein.net/blog/social-vampirism-services/</link><pubDate>Sun, 10 Aug 2014 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/social-vampirism-services/</guid><description>&lt;p>Companies are very bottom line focused. Even after a high level scope of work is determined, the most appealing bids often are on the lower end. Even if &lt;strong>some&lt;/strong> form of a deliverable can be achieved in a given number of hours, it often does not yield the correct one. Smarter bids allocate more time for damage control, error correction, and proper testing. For low bids, especially really low ones, one has to wonder what part of the product suffers.&lt;/p></description></item><item><title>Serenity of thought</title><link>https://nerdstein.net/blog/serenity-thought/</link><pubDate>Thu, 24 Jul 2014 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/serenity-thought/</guid><description>&lt;p>Rands&amp;rsquo; recent blog post &lt;a href="http://randsinrepose.com/archives/busy-is-an-addiction/">B&lt;/a>&lt;a href="http://randsinrepose.com/archives/busy-is-an-addiction/">usy is an Addiction&lt;/a> struck a chord with me. It&amp;rsquo;s made me rethink many aspects of my day-to-day routine.&lt;/p>
&lt;p> &lt;/p>
&lt;h2 id="work-smarter-not-harder">Work Smarter, Not Harder&lt;/h2>
&lt;p> &lt;/p>
&lt;p>It&amp;rsquo;s so easy to say, &lt;em>I&amp;rsquo;m busy&lt;/em>. In reality, I should be &lt;strong>working smarter, not harder&lt;/strong>. Busy is as much of a state of mind, as it is the items on your plate. It&amp;rsquo;s a routine, a lifestyle, and a shitty excuse.&lt;/p></description></item><item><title>A balance of trust and quality</title><link>https://nerdstein.net/blog/balance-trust-and-quality/</link><pubDate>Tue, 01 Jan 2013 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/balance-trust-and-quality/</guid><description>&lt;p>Projects are risky. Specifications are nearly impossible to define on most projects due to technical or communication gaps. This is the age old challenge many people fight.&lt;/p>
&lt;p> &lt;/p>
&lt;p>One popular solution for unclear specs is the &lt;em>&lt;strong>fail fast&lt;/strong>&lt;/em> methodology. It&amp;rsquo;s founded on brief iterations that lack polish, frequent tests by a client and an over abundance of communication.&lt;/p></description></item><item><title>A call for simplicity</title><link>https://nerdstein.net/blog/a-call-for-simplicity/</link><pubDate>Tue, 01 Jan 2013 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/a-call-for-simplicity/</guid><description>&lt;p>You&amp;rsquo;ve heard it all before. &amp;ldquo;The old programmer did this and it&amp;rsquo;s crap&amp;rdquo; or &amp;ldquo;This person used this tool and it&amp;rsquo;s no good&amp;rdquo;. It&amp;rsquo;s the age old grudge match between the old and the new. And, it doesn&amp;rsquo;t help anyone move forward.&lt;/p></description></item><item><title>An Agile Spree</title><link>https://nerdstein.net/blog/agile-spree/</link><pubDate>Tue, 01 Jan 2013 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/agile-spree/</guid><description>&lt;p>At the heart of Agile is flexibility. This is designed into sprints that are intended to account for changes rolled into subsequent sprints.&lt;/p>
&lt;p>But, think of an overall backlog. A high level estimation will yield a given number of sprints. This structure actually is not very flexible at all. Unless, of course, each sprint has time allocated for reviewing, testing, and bug fixing. This is a slippery slope; a more substantial change can really throw off a sprint. So, how do you address the issue of quality?&lt;/p></description></item><item><title>It's not you, it's me</title><link>https://nerdstein.net/blog/its-not-you-its-me/</link><pubDate>Tue, 01 Jan 2013 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/its-not-you-its-me/</guid><description>&lt;p>Bad projects are toxic. &lt;/p>
&lt;p>While most staff within a company focus on the bottom line, the bottom line is no guarantee of project success. It&amp;rsquo;s impossible to look in your crystal ball and make this call before a project begins. Hindsight is 20/20, right? &lt;/p></description></item><item><title>Learning is giving, not just receiving</title><link>https://nerdstein.net/blog/learning-is-giving-not-just-receiving/</link><pubDate>Tue, 01 Jan 2013 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/learning-is-giving-not-just-receiving/</guid><description>&lt;p>I recently read this article: &lt;a href="http://bryanbraun.com/2013/09/21/please-stop-stewing-and-start-blogging-about-drupal">http://bryanbraun.com/2013/09/21/please-stop-stewing-and-start-blogging-about-drupal&lt;/a>&lt;/p>
&lt;p> &lt;/p>
&lt;p>You can&amp;rsquo;t ask for a better justification to throw up a blog and share some information.&lt;/p>
&lt;p> &lt;/p>
&lt;p>It made me realize a few things.&lt;/p>
&lt;p> 
&lt;strong>First&lt;/strong>: You have an opportunity to help others out because you most likely learned something someone could benefit from.
&lt;strong>Second&lt;/strong>: Don&amp;rsquo;t be shy. If anything, someone may post a comment and share information with you again.
&lt;strong>Third&lt;/strong>: Tools like Drupal were built by people who were not afraid to give back.&lt;/p></description></item><item><title>Research contributions when problems are already solved</title><link>https://nerdstein.net/blog/research-contributions-when-problems-are-already-solved/</link><pubDate>Tue, 01 Jan 2013 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/research-contributions-when-problems-are-already-solved/</guid><description>&lt;p>What happens when there are a lack of open problems? On the surface, it seems to make it more difficult to have impactful contributions. I just think it requires you to think outside of the box.&lt;/p></description></item><item><title>Risks and Unwavering Swagger</title><link>https://nerdstein.net/blog/risks-unwaivering-swagger/</link><pubDate>Tue, 01 Jan 2013 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/risks-unwaivering-swagger/</guid><description>&lt;p>Push aside the user stories, contracts, and legalities. When push comes to shove, the developer delivers the goods. In my mind, there is huge risk to a project with the role of a developer.&lt;/p></description></item><item><title>Some perspective on difficult customers</title><link>https://nerdstein.net/blog/some-perspective-on-difficult-customers/</link><pubDate>Tue, 01 Jan 2013 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/some-perspective-on-difficult-customers/</guid><description>&lt;p>We&amp;rsquo;ve all had to deal with difficult people at work. It doesn&amp;rsquo;t get easier when the difficult people are those you serve. &lt;/p>
&lt;p> &lt;/p>
&lt;p>My director once shared his thoughts on a particular audience and it has stuck with me. In higher ed, some of those served are faculty members that have made their living questioning the world around them in research. This same perspective very likely is what elevated these folks above their peers and afforded them opportunities.&lt;/p></description></item><item><title>The role of the noob</title><link>https://nerdstein.net/blog/the-noob/</link><pubDate>Tue, 01 Jan 2013 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/the-noob/</guid><description>&lt;p>Peter Nixey describes good developers as both technology proficient and hard working &lt;a href="http://peternixey.com/post/83510597580/how-to-be-a-great-software-developer">in his blog post&lt;/a>. His concept of &amp;ldquo;simplicity&amp;rdquo; is worth noting. I highly encourage developers to create code that limits complexity. But, there is an even more important aspect of complexity: &lt;em>&lt;strong>usability&lt;/strong>&lt;/em>.&lt;/p></description></item><item><title>Towards organizational efficacy</title><link>https://nerdstein.net/blog/towards-organizational-efficacy/</link><pubDate>Tue, 01 Jan 2013 00:00:00 +0000</pubDate><guid>https://nerdstein.net/blog/towards-organizational-efficacy/</guid><description>&lt;p>As organizations evolve, traditional metrics and philosophies are being thrown out the window to further organizations. Such factors include efficacy, employee satisfaction/ownership, innovation, etc.&lt;/p>
&lt;p> &lt;/p>
&lt;p>I offer no beneficial contribution to this discussion, short of agreeing in principle with these efforts. However, I point you in the direction of two things I have found to be relevant:&lt;/p></description></item></channel></rss>