<?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 Clifton Craig on Medium]]></title>
        <description><![CDATA[Stories by Clifton Craig on Medium]]></description>
        <link>https://medium.com/@cliftoncraig?source=rss-19f99e48a228------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*TMUG6mmEUHVRwWxx.jpg</url>
            <title>Stories by Clifton Craig on Medium</title>
            <link>https://medium.com/@cliftoncraig?source=rss-19f99e48a228------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:18:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cliftoncraig/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[Too much to swallow]]></title>
            <link>https://cliftoncraig.medium.com/too-much-to-swallow-2295537f3f54?source=rss-19f99e48a228------2</link>
            <guid isPermaLink="false">https://medium.com/p/2295537f3f54</guid>
            <category><![CDATA[choices-matter]]></category>
            <category><![CDATA[dmx]]></category>
            <category><![CDATA[pain]]></category>
            <dc:creator><![CDATA[Clifton Craig]]></dc:creator>
            <pubDate>Fri, 09 Apr 2021 20:00:50 GMT</pubDate>
            <atom:updated>2021-04-09T20:00:50.650Z</atom:updated>
            <content:encoded><![CDATA[<p>Life has changed for everyone since 2020. Some of us went from bad to worse. some went from worse to better, and others stayed pretty much the same. Regardless of how the world has changed around you, each one of us faces a decision every morning. I am writing this morning because I was reminded about that decision through a series of random events that happened since last night. I think I’m just now making the connection between these seemingly unrelated events.</p><p>First there was a personal situation which happened last night. I had an almost-encounter with someone I have been trying to avoid. This individual, who shall remain nameless, has been popping up from time to time in my mind and I’ve been tempted to… let’s just say engage with the person in ways that are counter productive. In the middle of the almost-encounter I was somehow redirected to a more positive situation. It’s personal and I won’t share much beyond the fact that I made a conscious choice not to engage. (I’ll leave it to your imagination whether the engagement would have been something as chaotic as a physical fight, as mundane as an annoying phone call, or as harmless as a walk in the park.)</p><p>Then there was the <a href="https://news.yahoo.com/grammy-nominated-rapper-dmx-dead-at-age-50-161809834.html">news about DMX</a> trending on social media. I never really knew much about his back story, but the man suffered a lifetime of pain and drug addiction. It was reported that he was abused by his mother and her boyfriends and he was in and out of rehab. Usually these stories roll through my social media timeline without my giving much thought because they’re so common that they’ve been almost normalized. This time I had to dig in because… c’mon! It’s DMX!!! I read some articles, listened to some old songs and mourned.</p><p>This morning I woke up and chose to brush up on VS Code and tinker with extensions. I was pre-empted by my typical goofing on Twitter. Then I got hit by 2 tweets that connected all of the dots for me. Dr. Amber <a href="https://twitter.com/iCallMeRUDY/status/1380585802430873603?s=20">reminded me to choose fun</a> and Scott Hanselman shared a bit about <a href="https://www.hanselman.com/blog/how-to-deal-with-extreme-physical-pain">his current chronic issue</a>. It reminded me of a chronic issue I endured for decades.</p><p>I suffer from a condition <a href="https://www.mayoclinic.org/diseases-conditions/achalasia/symptoms-causes/syc-20352850">called achalasia</a>. It’s a totally embarrassing problem where I suffer internal choking every time I eat or drink anything. It makes it difficult for me to enjoy any food or drinks. I have always been a slim guy, but since a botched surgery in the early 2000’s I’ve been unable to gain more than 20 pounds on top of my already emaciated 160lbs frame. It’s also humiliating because I constantly have to explain my condition (which I often forget I have) immediately after eating. Imagine having to explain verbally why you’re having trouble speaking in the middle of a choking episode! It’s also frustrating because the people I explain myself to have no idea what or why I suffer. I’m usually blamed for my current dilemma as if I somehow brought this on by my own ignorance. The truth is my choking episodes happen at randomly/spontaneously and can be triggered by anything as innocent as a glass of water.</p><p>I’ve had scenarios where it comes hours after eating while driving back home on the highway. There are moments where I have to pull off the road gagging, dry-heaving and gasping for air. I was once spotted by a police officer while doing this on a busy interstate. He pulled up behind my vehicle to ask if I was okay or needed help.</p><p>Then there are people who try to fix me externally. “Why don’t you just go to the doctor and get it fixed?”, goes the suggestion. Without having walked in my shoes (this is not the only botched surgery I’ve had) you would have no idea how terrifying it is to hear a doctor inform you that the only way to even begin to address your current problem is to remove more of your internal organs, which also leads to uncertain results. Over the years I’ve had dozens of doctors visits and humiliating/intrusive evaluations (week long testing with externally worn devices that have tubes run through my nose down my esophagus to measure swallowing and stomach acid or whatever) and none of it gives anything definitive. My condition is chronic which means I have to live with it.</p><p>This brings me back to my opening point about decisions. Every one of us faces temptations and adversity on a daily basis. How we respond to these events determines who we are as a person. I am so imperfect as I often give into my demons. DMX fought his demons as well and ultimately succumbed to them. There was a silver lining in the middle of the interviews of him whichI watched since last night. I saw how he went from his struggle to healthy back <a href="https://youtu.be/fZEXbyK-9wc">to struggling</a> and then back <a href="https://youtu.be/EzaFvOOHX00?t=91">to healthy</a>. I picked up on his many successes from Rap to film/movie roles to exploding on <a href="https://youtu.be/RG4TRTbENnE">#Verzuz with Snoop Dogg</a>. Finally I saw one clip where he claimed that if he dropped dead right then he would feel he lived a good life.</p><p>This man fought his demons. He faced a choice (like we all do) every day. Some days he gave in, and others he won. I realized that life is not about the the problems we face or the mistakes we make along the way. Life is all about how we respond to these events.</p><p>Do you own your mistakes or do you make excuses for your behavior? Does your presence in the room add value to the people around you or are you constantly looking for recognition or a favor from other people in the room?</p><p>DMX reminded me that you could be a complete mess, a drug addict hooked on crack but still add value by being authentic.</p><p>Scott Hanselman reminded me that you can live with chronic issues (plural here) and still continue to have a fruitful life… one that others envy without knowing your actual struggle.</p><p>Dr. Amber reminded me that you can have a PHD and still choose fun.</p><p>It really comes down to that last subtle but significant point. When life gets too tough and becomes too much to swallow we can remember that we each have a choice every day. Today I think I’ll choose fun!</p><p>(Now if I can just choose which store to buy my paper from I might be able to finally learn how to do stuff in VS Code!)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2295537f3f54" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hurt People, Hurt People]]></title>
            <link>https://cliftoncraig.medium.com/hurt-people-hurt-people-78585cccf46c?source=rss-19f99e48a228------2</link>
            <guid isPermaLink="false">https://medium.com/p/78585cccf46c</guid>
            <category><![CDATA[people-skills]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Clifton Craig]]></dc:creator>
            <pubDate>Mon, 15 Mar 2021 00:47:01 GMT</pubDate>
            <atom:updated>2021-03-15T00:47:01.332Z</atom:updated>
            <content:encoded><![CDATA[<p>There is something unique about being a software engineer who comes from a spirit of empathy. You learn a perspective that lets you see code clearly. You also learn a point of view that lets you see people clearly. Seeing people is the big blind spot of many software engineers. No matter how hard we try our vision is obscured by code. We tend to see the world in algorithms and patterns that should be optimized. We see our primary job as coding and correcting these broken algorithms not understanding that some of these broken things in our lives are intentional. Sometimes it’s not practical or even correct to remove something that looks/feels broken. I have always felt that understanding the necessity of certain broken algorithm, pattern, or person is essential to moving passed your biases. I want to discuss a technique I’ve learned that helps me deal with difficult people in my life. Some I’ve been hurt by, and others I’ve been inspired by.</p><p>I titled this article after a concept my pastor speaks about from time to time. It is one of the most insightful messages I’ve ever come to understand. Putting engineering aside for a moment, consider how people tend to despise broken things. Whether it’s your microwave, the app on your phone, or the the handle on your toilet bowl… we resent it. We do what we can to either correct, destroy or remove broken things from our lives. An engineer, on the other hand, tends to inquire about the root cause of the breakage. Unscrewing the back from the microwave, reverse engineering the source code behind the app, or pulling the lid off of the toilet. Engineers are extremely efficient with things but not normally efficient with people. Can we apply these same engineering passions to people?</p><p>We internally label those that hurt us as “bad people”. (Some people might use slightly more colorful labels but the meaning is at least similar.) If we change our label from “bad” to “broken” we might tend to see our situation a little differently.</p><p>What if, instead of retaliating/removing/destroying the broken person, we opened the person up and tried to understand the breakage? Restating the title with our new label we might find that many broken people are broken by other broken people. Now if you’ve ever written any computer logic in the past you will immediately see a pattern! It’s called recursion, and you’ll know that it is critical for any recursive algorithm to have a terminating condition or else you suffer from stack overflow. Now we have a choice. We can continue the recursive pattern of hate, hurt, retaliation or we can terminate our loop.</p><p>The above analogy is pulling in a subtle and different direction than where this writing is heading, however, but we can restate a few things. A “bad” (or whatever label you typically use) person is actually a broken person. We can examine the source of what makes a person broken. Sometimes we might learn that the breakage is by design.</p><p>Let’s consider some examples. A person who has the propensity of always needing to tell the truth even in awkward situations can be considered harsh, insensitive or outright stupid. However, if you open them up, you might realize this person has suffered a history of being ravaged by lies and actually empathizes more than anyone else in the room.</p><p>You might deal with somebody who has a habit of not participating in group activities, has a narrow view, extremely opinionated, and doesn’t get along with others. If you unscrew their back and peer into their heart you could find a broken marriage/family where that person’s only escape hatch is doing the one thing they know so well.</p><p>In the first example we have a person who will refuse to let anyone spread inaccurate information or fail for illogical reasons. This can be an invaluable personality trait in that the person is bold enough to say what other people feel. It is can also be a totally destructive personality trait when the truth is not tempered with love, care, or consideration.</p><p>In the second example we have someone who can be incredibly focused and effective at getting things done. This is also someone who can be very time consuming because their effectiveness is predicated on having the stars aligned in their favor.</p><p>Confusing these examples with analogies we can say that a screwdriver isn’t the best tool to drive a nail nor is a hammer the most practical instrument for twisting a screw. The point is that we want to appreciate people for their uniqueness and gifts rather than loathe them for what we determine as broken. Sometimes the breakage can be leveraged to drive just that one crooked nail or turn that awkward screw. The intent of this article is to give engineers a fresh perspective of the people they encounter. Dealing with widely varied people and personalities is a valuable, yet seemingly impossible skill for an engineer to learn. If you apply a bit of what you are already passionate about, it can help you along.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78585cccf46c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TDD Is Not Easy, and neither is coding…]]></title>
            <link>https://cliftoncraig.medium.com/tdd-is-not-easy-and-neither-is-coding-d7a9222110c1?source=rss-19f99e48a228------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7a9222110c1</guid>
            <category><![CDATA[test-driven-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[test-driven-design]]></category>
            <dc:creator><![CDATA[Clifton Craig]]></dc:creator>
            <pubDate>Mon, 15 Feb 2021 00:13:23 GMT</pubDate>
            <atom:updated>2021-02-15T00:13:23.185Z</atom:updated>
            <content:encoded><![CDATA[<p>TDD Is Not Easy, and neither is coding…</p><p>There is an interesting discussion I participated in regarding Test Driven Design (TDD), a popular programming practice. The topic alleges this practice is easy and i want to elaborate my experience and history in this article. My intention is not to shame anyone who either found success or failure with the methodology but to highlight one of the biggest misunderstandings which is wide spread in the industry.</p><p>Let me begin by reminding everybody that programming is not easy. While many of us find joy and satisfaction from this career, there is a reason salaries in the Bay area (and other areas) are so high. Writing code takes a certain discipline and mindset that is not present in many people. If you are patient and methodical you can, indeed, reason your way through the most complex design. However, if you are not familiar or comfortable with logical reasoning then you will be met with frustration and have a high likelihood of giving up. That doesn’t mean you are incapable, shortsighted or incompetent. It only speaks to your familiarity, and particular way of thinking. Some people or logical, some are artistic, and others have sprinklings of artistic creativity and logic.</p><p>Now let’s talk about Test Driven Design. I spent a large part of my 22+ year career preaching and trying to get different teams on board with TDD. I’ve seen it succeed on projects and I’ve seen it fail. In just about every scenario where it has failed I’ve noticed a particular pattern. It is never a failure from lack of effort, aptitude or cognitive ability. Rather it has been a failure for an engineer (or an entire team) to switch mindsets. Herein lies the BIG misunderstanding.</p><p>You actually need a non-developer mindset to succeed at TDD. In other words you have to STOP thinking like a developer to be successful with this development concept! Let that sink in for a moment. I want to come back to this point but first I will digress a bit.</p><p>As an engineer we are born and raised as problem solvers! We pride ourselves with how quickly and brilliantly we can rattle off a technical solution to any problem and we obsess over the details! Our entire nature is to provide answers! We are so good at it that we provide answers before the question is even asked! We provide answers to questions that were never asked! Got a pile of data you wanna crunch? No problem, throw it in a NoSQL SQL DB! Wait, is that read heavy or write mostly? We have a configuration for both! Let me shard that DB for you! You need to distribute HD video and multiplexed audio to a wide audience in real time with zero latency! There is a guy right now with a custom cooked UDP service and a brand new protocol waiting by the phone! This is how most developers live and breathe!</p><p>So what does it mean to practice Test Driven Design? I won’t get into the weeds on this topic, but at a high level it means one thing. We focus on the requirements and leave the technical details for later. Test Driven Design, done properly, is an “Outside In” practice which focuses on the question. (I want to emphasize <em>done properly</em>, because I still fight with some devs who claim to be advocates but don’t understand why you can’t do it from the inside out.) TDD is about obsessing over the question rather than the answer! “What are we building? Why are we building it? Who is using it?” The entire premise of TDD is actually not about testing at all. This is why you will have a large population claiming it is easy. The misconception here is that it’s easy to write tests.</p><p>Let me state it this way. Writing tests can be fairly easy, however this is not the same discussion. If you are <em>testing</em> your code then you are probably not doing TDD. You can have 90–100% test coverage and <strong>NOT</strong> be doing TDD. I’ve seen this in practice and it’s a really easy oversight to have. If we de-emphasize testing then the focus and misconception is a littler easier to see.</p><p>I’ll write it this way, “tdD”. The last “D” in the acronym refers to “Design” and is the most significant. The entire point of TDD is to drive the <em>design</em> of your code by <em>coincidentally</em> using a test framework. That’s right, I said coincidentally! Some smart folks learned a while ago that you don’t even need to use a test framework to do this. They reasoned that you can use something that is frequently missing at most companies: a requirements document or formal user specification! (Does your project have an up to date version of one of these?) This idea gave rise to tools like FitNesse, R-spec and a new acronym, BDD. The principle is the same. We want to go from the requirements, or the specification to the code and back again. I won’t elaborate too much on the details behind TDD and BDD. Instead I’ll leave that for another article.</p><p>If <em>testing</em> your code is not actually part of TDD it’s no wonder so many people are having a hard time! I am really trying to drive a subtle point here. There are so many different ideas and principles around TDD that it can easily cut a nerve. Indeed there are large populations of developers and TDD advocates that miss the point of TDD and are actually arguing in favor of writing tests. This population is not technically wrong when they reason that writing tests and testing code is easy. This is the same population of the community that has not yet embraced the most difficult part of TDD. They are married to the technical details of tooling and have not done the mental gymnastics required to conceptualize the actual practice. I gotta say it, testing is cool and we have some really solid tooling for it. It’s challenging to point this out because it’s like telling the emperor he has no clothes on. I’ve had several spirited discussions around this topic and it never goes anywhere.</p><p>This brings me back to my original point. You have to STOP thinking like a developer to be even understand or be successful with TDD! Telling a developer to not think about testing and start thinking about product specs as part of TDD is like teaching a fish to fly or teaching a bird to swim! This is a terrible/awesome analogy because there are some flying fish and many birds swim. The point is that the majority of birds stay mostly out of the water while most fish avoid the skies. So while it may be easy to show someone how to write a test, have you ever tried to tell a developer to close her/his editor, delete code, or start from the outside first? If so, then you’ll understand how unique and difficult learning TDD really is! You have to teach a developer to not think like a developer!</p><p>I want to end on a very controversial note. I honestly don’t think many projects should use TDD. Don’t get me wrong! I love the practice and always promote testing more than most people! Yet I feel there really isn’t anything wrong with developers/teams that don’t practice true TDD. The philosophy is challenging enough where the associated costs often outweigh the benefits. I’ve been on plenty of successful projects and teams. Some of these use it while many of these don’t. While I feel most (if not every) project I’ve been on could benefit from TDD, the investment and effort to get it right on a medium to large team is rather significant because of everything I’ve outlined above. As an engineer I always think TDD is the best approach, but as a manager I would always weigh the costs and potential of failure against the theoretical benefits. As a person who has played on both sides of the fence I can’t ignore the reality that many projects should probably avoid it.</p><p>(I recently gave a talk where I encouraged my entire team to learn Test Driven Design so we can begin embracing it!)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7a9222110c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why don’t you value my code?]]></title>
            <link>https://cliftoncraig.medium.com/why-dont-you-value-my-code-e36aedbe6f6c?source=rss-19f99e48a228------2</link>
            <guid isPermaLink="false">https://medium.com/p/e36aedbe6f6c</guid>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Clifton Craig]]></dc:creator>
            <pubDate>Sun, 12 Jul 2020 21:16:01 GMT</pubDate>
            <atom:updated>2020-07-12T21:16:01.273Z</atom:updated>
            <content:encoded><![CDATA[<p>“The Lord looked with favor on Abel and his offering, but on Cain and his offering he did not look with favor. So Cain was very angry, and his face was downcast.</p><p>Then the Lord said to Cain, “Why are you angry? Why is your face downcast? If you do what is right, will you not be accepted?” — Genesis 4:4–6</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B-dHRrz7NZpxuwa7eO0YNQ.jpeg" /></figure><p>Have you ever felt like the code you spent weeks obsessing over was kicked to the curb? Has your month long project just been overwritten by some other hot-shot dev who hated your normalized DB and thinks you shouldn’t use mutable variables? Have you devoted an entire weekend learning a framework only to be told it is being deprecated and pulled from the project?</p><p>In my 21+ years of software development I’ve noticed many corollaries between what I see on the job and what I’ve learned through my faith. Please bear with me, this is not a scriptural lesson or Bible study. It’s about doing the right thing for the right reason.</p><p>I used to be that developer who spent weeks/months obsessing over code and later fighting mercilessly to have it included in the project… considered in my manager reviews. I used to wonder, “why don’t they care about my code?” In the story above Cain was bitter because his gift was not accepted. In my story I grew bitter because my contributions were not valued. How and why does this happen?</p><p>I, like many developers, was focusing on writing code that I thought was important. I even went as far as creating user stories to support the use cases of my code at times. In every scenario I anticipated and assumed a technical need and in every scenario those technical needs were not tied to any business need. I was clever enough to create use cases but never successful enough to connect those use cases to business value because there was none. This was incredibly dangerous but let me try to use an analogy to explain why.</p><p>Imagine being in the Army and seeing a fallen comrade who is bleeding from the chest. Rather than address the chest wound you begin wrapping bandaging around the leg. Now you may get upset because your comrade is screaming at you and not appreciative of your tight tourniquet skills. You may even begin to explain, “once you get your leg blowed off my work here will immediately prevent you from bleeding to death!” You would be technically correctly but ethically moronic.</p><p>The Army story is an extreme analog to what many of us do in the industry. We fail to address the immediate business need in favor of what we spent most of our time on. It’s actually very easy to mix and prioritize technical needs over true business needs because we are solution providers who treasure code-based solutions! We know the code better than the business and we can’t stand when business folks tell us what truly matters! The truth is we don’t speak the same language as the business people. So how do we bridge the gap between what we treasure and what the business actually values? How do we line up our passions with the core business?</p><p>The trick is to do the opposite of what makes sense in most scenarios! In other words, let broken code remain broken until the business complains about it. This is the most difficult skill for any developer to master, because it requires saying “no” to the very itch that is core to who you are. It’s like telling a body builder to build muscle by not lifting weights. (This actually makes sense because in the ephemeral world of programming most things tend to work out optimally when done backward.) If you can master this feat, which most developers struggle with, then you will immediately move from a novice into the league of code assassins. How does this work?</p><p>Pretend Louis is working on a Ruby/Rails project and notices he can add simplify and speed to the user update function by wrapping a bunch of updates in an actual transaction that currently performs home-grown transaction logic with a slew of queries and manual undo operations. It makes sense because the logic is obviously complicated and it could use a ton of spring cleaning. Meanwhile Sarah, the product owner, has the task of making sure the multi-million dollar deal with a client doesn’t fall to pieces because of constant glitches in the batch data import process for the client.</p><p>Louis can walk away from this obvious eye-sore of Ruby Rails code and address the gaping chest wound of data import glitches or he can spend his Saturday trying to bandage the leg of the user transaction problem. Louis might call Sarah stupid because she obviously doesn’t care how ridiculously slow the user update screen runs. Sarah would be completely justified in retorting that Louis is throwing millions of dollars in the trash to chase a ghost in the user update when all of the same users have been set in the system for 2 years. The update is hardly used.</p><p>I almost want to call this Error Driven Development because it forces you to wait for an actual business error to drive your development. It also allows the team and the business as a whole to use the most effective solution to the immediate needs. Louis has to wait for enough user data input to happen where a complaint (or error) about sluggishness surfaces to justify any action here.</p><p>In the Louis/Sarah story Louis’ idea and obsession is technically correct but irrelevant in the practical sense. Because there is no business need to improve user data input it is wasteful. Sarah’s business needs drive actual revenue that fills both Louis’ bank account and refrigerator.</p><p>In the end Louis needs to do what is right rather than blindly perform optimizations for the sake of writing code. I opened this article with a quote from Genesis where we have one guy providing an offering for the sake of providing an offering. (There’s more to that story where the offering was not from the heart, not what was asked for, and did not represent the better part, etc.) I want to end by posing some questions like, “have you played the role of Louis?”</p><p>Have you grown frustrated because you are working on things YOU feel are important but have not been accepted? Have you been in touch with your product owner or the the core business owners to fully understand where the true business needs are?</p><p>If our fictional character Louis does what is right then and entire Saturday could be devoted to the data import where that itched could be scratched to total satisfaction. There are likely tons of rails validation errors and home grown transaction management blocks there… plenty for Louis to feed off of. The business need would then properly be addresses filling the refrigerator where there would be even more for Louis to feed off of.</p><p>If this article resonates with you consider sharing it and coming back the next time I have a moment of inspiration. My writings are sporadic and occasionally there is a point buried somewhere deep in them. If you’ve read this sentence then you have a ton of patience for my rambling, for that I thank you sincerely.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e36aedbe6f6c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AfroTech 2019]]></title>
            <link>https://cliftoncraig.medium.com/afrotech-2019-e9b14636d7aa?source=rss-19f99e48a228------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9b14636d7aa</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[afrotech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[black-people]]></category>
            <dc:creator><![CDATA[Clifton Craig]]></dc:creator>
            <pubDate>Sun, 10 Nov 2019 18:01:03 GMT</pubDate>
            <atom:updated>2019-11-11T02:51:23.155Z</atom:updated>
            <content:encoded><![CDATA[<p>I initially planned to sleep in this weekend. I’m traditionally afraid of spending large amounts of money and I’ve been fighting this bad habit of chilling at home over the weekends in my PJs so this commitment was pretty major. I’m also extremely shy/introverted. You might not get that impression from seeing me online or meeting me in person, but it’s true. I have this tendency to avoid social interactions, which I constantly combat. So again, it underscores the significance of my commitment to attend AfroTech this year. I wanted to put it off until next year, or find something unnecessarily important and prioritize it. I am so glad I made a different choice.</p><p>If you’re black and you’re in tech or even curious about tech then you owe it to yourself to attend one of these events. Do what you can, beg/borrow/bribe your way there. The experience is unlike any other tech conference. You don’t want to miss out on the sessions. You don’t want to short-change yourself the opportunity to network and connect with folks, and you won’t believe your eyes when you get there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6m7ewLYXCThCOwJleUw4kw.jpeg" /><figcaption>Celebrity Appearances</figcaption></figure><p>Over seven thousand people showed up this year. Let’s talk about that number because I could end my writing on that sentence alone. When was the last time you’ve seen ever seven thousand of anything in one place? Seven thousand+ servings of fried eggs? Seven thousand+ rolls of toilet paper?? Seven thousand+ little boxes of tic-tacs??? Over seven thousand people from all over came together this weekend in the name of black tech excellence.</p><p>Everyone would have a unique experience, and attending any conference is all about what you make out of it. You have to take the good with the bad so I’m going to explain how my experience went.</p><p>Beginning with the good, the event started with a kickoff in the main ballroom. The MC walked through the crowd interviewing guests. He pulled one lady from Africa and gave her 20 seconds to summarize her oxtail recipe. Homegirl dropped the ingredients and my mouth was watering well before the first 15 seconds expired.</p><p>Then there was the bad, the obvious issues which were related to the swell of participants. Long lines (which would be familiar to anyone who has attended a WWDC or similar conference), limited access to certain sessions and activities, almost non-existent network connectivity and expensive food which takes hours to arrive. These issues would make even the most die-hard conference attendee want to leave, but hold on. I said earlier, “attending any conference is all about what you make out of it.” I made up my mind to be empathetic to the event organizers having organized events of my own in the past. I just rolled with the irritations. After all, how can you accommodate what is likely the population of a small city in one concentrated central area? These organizers did their thing and I’m STILL surprised the earth didn’t cave under the mass of people.</p><p>Moving beyond the population pains, I got to the significance of what was actually happening before my very eyes! I saw my people thriving in ways that had been hidden for most of my career. Through my entire career I can count, almost on one hand, the amount of black people I’ve actually encountered in tech. Things improved slightly when I moved to the bay area, but I still don’t need to remove my shoes to count.</p><p>I saw and had discussions with some of the most amazing people each with unique back stories that all had a similarly themed origin. If I had a nickel (prepare for cliché) for every person there who had a “I never knew there were black folk in tech” beginning I could probably make my next two car payments… without setting up auto-pay. Let that sink in.</p><p>Going to different sessions were more opportunities to network and learn from each other. I sat next to a guy who was working on nano-tech to fight breast cancer! These are little micro-machines that attach themselves to cancer cells. They then do the Street Fighter II Chun-Li kick until the cancer cell hollers, “eeeyyyahhhh” all echoey. He happened to be so fascinated by my Tonka-toy robot I brought along that I was embarrassed! I spoke with designers, and hardware engineers and electrical engineers and doctors. This is all before the speaker even takes the stage. The amount of raw talent and passion from everyone in the room was mind-blowing. It helps to carry along a robot so that you feel like you fit in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/506/1*086XM-pHSlVuGoaST2fnxQ.jpeg" /><figcaption>Bluebot’s first AfroTech</figcaption></figure><p>While the event was attended primarily by black people there were some white people, hispanic, and other ethnicities. Waiting in line for food, I spoke to one white guy with an interesting story. He said he also attended a woman’s conference prior. He explained how he likes to attend conferences where *he* is the minority because it gives him a unique perspective. While he spoke I wondered why all white people wouldn’t trip and fall into whatever magical mayonnaise that resulted in this man’s “flawless-victory” attitude.</p><p>Then there were the speakers. Every session I attended ended with a standing ovation for the presenter. That‘s not just a measure of talent it also speaks to the level of support we all have for one another. There was a common theme throughout most sessions which centered on three major issues; lack of diversity, its impact on A.I., and biases. Each speaker presented with their own unique style and brought different perspectives to the room. Most topics touched on this obvious pink elephant in the board room of all major tech companies.</p><p>I really need to spotlight the black women speakers that I heard. They were outright phenomenal! Never, have I ever seen people present with as much passion, insight, and completeness. I should have been taking notes. The fellas were also amazing, but the women really did their thing. (I’m not hating, and I think my lack of sleep impacted my appreciation for some of the sessions.) The two talks that stuck out the most were the presentation by Dr. Nashlie Sephus on A.I. and discussion on automation by Brianna McCullough. definitely suggest you watch/follow/pay-attention to these amazing women</p><p>Inside the ballroom area there were plenty of vendor tables from most of the widely recognized companies and stations with swag, and recruiters offering opportunities. The vendors I spoke to were transparent about hiring bias as well as what I call the major problem in tech recruiting. (I’ll speak more on that in a follow-up article.) I didn’t spend too much time at the vendor tables as I am spoken for and merrily employed.</p><p>As I wandered clumsily between events and stations I was constantly bumping into people I knew from online only. It was my not-so-secret mission to grab each one for a photo op however my amazement at the whole experience distracted me on at least two occasions. I walked right up to these people, each who I deeply admire, with casual conversation while masquerading my anxieties behind my overly-joking antics. My recently purchased Galaxy Active2 watch was secretly ratting on me as I never disabled the heart monitor display. “Hey, what going on?”, I would mouth while the heart-shaped icon on my wrist glowed bright red pushing over 80bpm. I only realized how obvious this must have been on the drive home, but what can I say? I’m the kinda guy who always wears his heart on his sleeve.</p><p>The after-parties which occurred before, after and during all of the sessions and breakouts are amazing. The music was bumping, people danced in the streets and there was just an overall sense of family present the whole time. It is like “the cookout” played through a <a href="http://jmeter.apache.org/">Jmeter</a> load-test config and replicated on hundreds of hosts. A <a href="https://www.oracle.com/technetwork/java/index-138747.html">Java-programming-based</a> load testing tool is the best and only way to describe what had seriously been played out in several areas of Oakland simultaneously. Imagine the sent of barbecue cooking with the sound of reggae, and hip-hop, complimented by a kick-back setting.</p><p>I attended one after-party which drew me out of my comfort zone into a position of “get down” on Friday night. Because I have two almost-grown kids and I’m literally pushing my mid-forties with a broom the size and shape of Ned <a href="https://media.giphy.com/media/zt917vqOwZBLO/giphy.gif">Flander’s mustache</a>, I sometimes feel too out of touch to party. I had the help of some dope people to pull me out of that shell and literally onto the dance floor where I awkwardly demonstrated why I <em>probably</em> should stay behind the equipment table at any party where I can detangle cables and diagnose connectivity problems. “Yes, I do believe this mono plug is incorrectly connected into a stereo jack and that cable is partly frayed costing a bit of fidelity loss.” I danced, then stumbled, then did something that could loosely be described as either dance, or swim. I didn’t care. People didn’t care.</p><p>You should definitely be prepared going into one of these tech conferences. All of the usual rules apply. Order business cards. Book your hotel in advance. Check the agenda days prior. Plan your route. Bring backup batteries for your devices. Arrive early. Download the accompanying app. Brush your teeth. Book your hotel in advance. Don’t stay out too late or drink too much. Look both ways before asking a question. Anticipate heavy traffic on the way to and during the conference. Book your hotel in advance. Communicate rendezvous locations to friends in advance. I was surprised how the LinkedIn QR code scanning feature is used by almost everyone for sharing contact info.</p><p>In summary, you just need to get there. If next year’s event is anywhere remotely similar to this year’s event then it’s worth every dime you can dig out of your couch. Tell a friend and bring a friend. Get your company to sponsor, if possible. I may try my hand at speaking at the next one assuming they’ll accept my CFP.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9b14636d7aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can’t see nothing but the source…]]></title>
            <link>https://cliftoncraig.medium.com/cant-see-nothing-but-the-source-3961fbbf5c59?source=rss-19f99e48a228------2</link>
            <guid isPermaLink="false">https://medium.com/p/3961fbbf5c59</guid>
            <category><![CDATA[life]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Clifton Craig]]></dc:creator>
            <pubDate>Tue, 29 Oct 2019 22:09:13 GMT</pubDate>
            <atom:updated>2019-10-29T22:09:13.497Z</atom:updated>
            <content:encoded><![CDATA[<p>Early in life I was affected, infected with a passion for tech. Around the age of 5 or 6 I started to take my toys apart to see how they worked, and I played video games heavily. I told my mom I wanted to be a dentist not because I was at all interested in teeth, but because of all the cool equipment I saw at the dentists office. In my youngest years I had several encounters with lights that blinked, toys and gadgets that would move electronically, and starship-like noises. However, nothing piqued my interests more than one product in particular. I drew a very special connection with one extremely fascinating toy called the IntelliVision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/474/1*DCSoUuXc_6gFHp8ZVZFvJA.jpeg" /></figure><p>The IntelliVision was a game console that came in several iterations. We initially owned the Sears model and later my dad bought the IntelliVision II as a Christmas gift. This beast had an optional computer keyboard attachment (sold separately) which allowed you to write programs in the BASIC programming language. You could grab graphics/sprites from your favorite game, display them and animate them across the screen! A couple years later the IntelliVoice module was released. This module gave your games the ability to talk! I was bitten.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*l-tLaa4XomXFbdhIGDrInQ.jpeg" /></figure><p>Today I work as a software engineer doing all the things I dreamed of as a child. I have a deep passion for voice technology and artificial intelligence, although I, myself, am artificially unintelligent! My passion is rooted deep in my childhood and my childish antics influence everything I do from the way I dress, to the way I code, to the way I write. I’ve maintained a blog for several years elsewhere on the internet where my goofiness has run rampant. On this blog I only talk tech. In my life I mostly talk tech. These days I can’t see nothing but the source code, I’m tripping! I invite you to trip out with me as I write about the things I know as well as the things I don’t know so that we can collectively come to know those things we wished we’d always known, y’know?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3961fbbf5c59" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>