<?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 Automator on Medium]]></title>
        <description><![CDATA[Stories by Automator on Medium]]></description>
        <link>https://medium.com/@ben-the-automator?source=rss-d7f919a53c74------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*o9S1AQntcychrTVJD-Qmbg.png</url>
            <title>Stories by Automator on Medium</title>
            <link>https://medium.com/@ben-the-automator?source=rss-d7f919a53c74------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:02:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ben-the-automator/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[Story Time: The Most Vulnerability Tickets Ever? — Ep 3]]></title>
            <link>https://ben-the-automator.medium.com/story-time-the-most-vulnerability-tickets-ever-ep-3-f81ef2baa806?source=rss-d7f919a53c74------2</link>
            <guid isPermaLink="false">https://medium.com/p/f81ef2baa806</guid>
            <category><![CDATA[trial-and-error]]></category>
            <category><![CDATA[automation-solution]]></category>
            <category><![CDATA[vulnerability-management]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Automator]]></dc:creator>
            <pubDate>Sat, 12 Nov 2022 12:56:46 GMT</pubDate>
            <atom:updated>2022-11-12T12:56:46.221Z</atom:updated>
            <content:encoded><![CDATA[<h2>Story Time: The Most Vulnerability Tickets Ever? — Ep 3</h2><p>Once upon a time I worked for a company that had the typical approach to vulnerability management — Spreadsheets…. I had to change this!</p><blockquote>I really hate spreadsheets</blockquote><p>The thought of copy and pasting data really didn’t appeal to me and I wasn’t allowed to run macros etc due to security policy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/326/1*2YCsRiL2PlI14qKPfxqopw@2x.jpeg" /></figure><h3>There had to be a better way!</h3><p>I had this idea early on in my career to take a Nexpose API and then integrate it with Jira and using Jenkins as my orchestrator.</p><p>There was a problem, I didn’t know Ruby at the time and I wasn’t a seasoned developer.</p><p>Still, I gave it a shot after teaching myself how to be a wannabe Rubyist and created one of the first closed loop vulnerability management systems.</p><p>Some of the goals of the project</p><ul><li>Provide a complete timeline of events</li><li>Allow for no duplication of data</li><li>Self service close of tickets</li><li>Allow for near immediate result validation</li><li>Even added in the ability to submit a false positive using a Jira transition</li></ul><h3>What could go wrong?</h3><p>Let’s enumerate it shall we:</p><ul><li>Well, I <strong><em>monkey-patched</em></strong> the code. Meaning code was written directly into the library or gem file and I didn’t have access to anything like Git…</li><li>Resource limitations meant I had to run the “production” code on my computer</li><li>There was no test environment…</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/215/1*y_DG4sm2UeKea3OGX-j_bw@2x.jpeg" /></figure><ul><li>Resistance was sooo high! Here’s this thing that will make life easier. How could you not like it!?</li><li>Estimation… is hard. I estimated something like 40k tickets.</li></ul><blockquote>Instead it made <strong><em>1.2 MILLION tickets! </em></strong>It <strong>crashed</strong> the on-prem JIRA!</blockquote><h3>What’s the silver lining?</h3><ul><li>It worked! For the first time ever, this company could see the risk level it had and could actually do something about it! Oh, and no duplicate tickets.</li><li>Even though there was so many tickets, I built in a bulk close feature in JIRA to allow Patch Tuesdays to be as simple as close it and check later to see if the vulnerability was fixed.</li><li>I contributed and collaborated on the code that allowed for the API to kick off multi-threaded remediation scans. That was pretty neat!</li><li>The completion of this project sparked a whole new possibility of work in my career and really stoked my passion fire.</li><li>No more spreadsheets!</li></ul><h3>Some of the sauce</h3><p>My idea was later adopted into Insight VM. But, not completely.</p><p>To make 1.2 million tickets, I choose the single vulnerability per system model (<a href="https://ben-the-automator.medium.com/automator-chronicles-a-brief-guide-to-vulnerability-automation-ep-2-15ff2fbdb286">see my previous publication for more information</a>).</p><blockquote>I know what you are thinking… this is obviously the reason the estimate was off? Unfortunately, no it wasn’t. There was a change in the level of cvss to report on… from 7.0 now down to 3.0 on launch day (can you say <strong>holy informational vulnerabilities Batman!?</strong>)</blockquote><p>To ensure tickets didn’t collide, I created an encrypted version of the <strong>ip:hostname:vuln_id</strong>. This value was then added to a custom field and code queried open tickets to make sure there wasn’t a match prior to creating the ticket. Other values like the cvss were added to drop downs (for easy dashboarding) along with other text values like hostname and IP address. Lastly, the owner was created as a field (before labels were popular).</p><p>Using JIRA, I designed a workflow that allowed for a quick transition using my service account only using conditions and such. The workflow also allowed for restricted functionality manual close of a ticket for false positives/accepted risks, but only after they were added to Nexpose and the risk register.</p><h3>Logic Flow</h3><p>The workflow overall was fairly rudimentary.</p><p><strong>Opening tickets:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*xkoixDQocWWbh5vMsSXAUw.png" /></figure><p><strong>Closing tickets:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ND7Olx6JQ2TYWD_kwFygAA.png" /><figcaption>User in Jira (bulk transition) &gt; Jenkins scheduled query for tickets in “pending” status &gt; decrypt value &gt; Nexpose adhoc scan &gt; interpret results &gt; return to open with comment OR close with proof of remediation</figcaption></figure><p><strong>Reporting</strong>: Most of the reports were actually done in JIRA. Dashboards per team with pie charts and things. An overall dash for full visibility and most importantly identifying systems no one “owned.”</p><blockquote>You can’t lower your risk without knowing who is the owner of the system. Iteratively, we were able to detect when owner values were changed to better create accurate team tickets.</blockquote><h3>Lessons Learned</h3><p>I always feel it’s valuable to learn about my mistakes and figure out what can be done in the future to provide a better experience for myself and the company.</p><ol><li>After nearly DDoSing some servers because Nexpose was kicking off n scans against the same system… I would likely use Redis or something along with a threshold of how many scans per system at the same time.</li><li>Estimation — I should have had some better figures available prior to real launch (even if that meant disappointing a whole floor of people) and things like proper test environments would have been ideal.</li><li>Git er done — Git with version control is a big part of my career. I really wish I could have submitted PR’s for the company to review instead of just having code on my machine…. When we needed to upgrade the version of the gem, we couldn’t because my diff wasn’t version controlled and I made sooo many edits… the whole project had to be rebuilt.</li><li>Webhooks and things- I have done things in Jenkins that even the most seasoned users have made a Tim Allen “aeuhhh?”…. A webhook would be more graceful, easier to troubleshoot and control rather than cron jobs with crazy API calls pulling back payloads that are rediculously large.</li><li>I wish I had a better author relationship with Nexpose on this project.</li></ol><h4>Thanks for coming to my Ted talk!</h4><p><strong><em>Please comment and follow for more.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f81ef2baa806" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automator Chronicles: A brief guide to Vulnerability Automation — Ep 2]]></title>
            <link>https://ben-the-automator.medium.com/automator-chronicles-a-brief-guide-to-vulnerability-automation-ep-2-15ff2fbdb286?source=rss-d7f919a53c74------2</link>
            <guid isPermaLink="false">https://medium.com/p/15ff2fbdb286</guid>
            <category><![CDATA[vulnerability-management]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Automator]]></dc:creator>
            <pubDate>Fri, 28 Oct 2022 04:12:27 GMT</pubDate>
            <atom:updated>2022-10-28T04:17:43.872Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*lUlhrdot0zeDuFefDYJ2qw@2x.jpeg" /></figure><p>On this episode of Automator Chronicles, we will dive into some vulnerability(vuln) automation. This isn’t a complete beginners guide, but I will cover some ground level things.</p><p>However, your feedback will drive my next article. Please let me know what you want to know and its depth.</p><h3>Define: Vulnerability Automation</h3><p>At a high level, vulnerability automation means to automate the handling of vulnerabilities for things like visibility, reportability and actionability.</p><blockquote><strong>Visibility</strong>: How bad is it actually? Graphs and such. Make people see the bad and hopefully remediate it.</blockquote><blockquote><strong>Reportability:</strong> How bad is it in a report format. But more importantly, an excel (:barf) file thing that people can report on and filter and such.</blockquote><blockquote><strong>Actionability: </strong>What can we actually action? I don’t mean alerts for the sake of … alerts. Someone needs to be able to do something with this. Can we kick off any kind of automated things like a chef recipe?</blockquote><h3>1. The Great Debate — How to do things?</h3><p>So when you go to automate the vulns, how should you proceed? Everyone has their opinion and has “read all the things” in xyz.</p><p>Sometimes, your experience will win. Sometimes, you end up crying on the inside as the project you are in charge of is knowingly headed for a cliff and utter disaster. But, decisions above your pay can only be contended for so long :sigh.</p><p>I’d say that there are a couple common ways to approach this at over a dozen companies I have solved this for. Let’s compare them, shall we.</p><h4>Option 1 — As much information in one ticket as possible</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/249/1*DynDday8w9MQKZAtGJggKA@2x.jpeg" /></figure><p>Let’s throw all the vulns for a single system in one ticket. After all, this is how people work tickets, right?</p><p><strong>Pros:</strong></p><ul><li>You have identified all the issues for a single system in a single ticket (easy right)</li></ul><p><strong>Cons:</strong></p><ul><li>All the info… in one ticket?!</li></ul><p><strong>Common questions and problems:</strong></p><ul><li>How will you maintain state? — What is the definition of done? Is it best effort, until you delete the ticket and start over (yes, this has happened at multiple companies…), or do you just say it’s “DONE” and then mark the rest as false positives…?</li><li>What happens if the issues spread across multiple tiers? — (people do actually run a web, db, and app on the same server (with multiple teams touching the same server) :sad_noises )</li><li>How long will this ticket live? — You wanted a semi-annual (no wait), monthly ( or was it weekly (<strong><em>this will change often and without warning</em></strong>)) timeframe representation of tickets. If the ticket lives for a year, is that ok?</li></ul><h3>Option 2 — One ticket with all the systems with the same vulnerability</h3><p>Brilliant! It’s the same issue above with <strong><em>even more tickets</em></strong>! Now you have definitely guaranteed the need for more teams to touch the same ticket!</p><h3>Option 3 — One ticket per system per vulnerability</h3><p>We have reached critical mass in the ticket world!</p><p>Pros</p><ul><li>You can identify how many vulns per system exist</li><li>You can identify how many systems have the same vuln</li></ul><blockquote>Get ready for this —<strong> *easy way to determine a definition of done AND timeline!</strong></blockquote><ul><li>Easiest to automate deduplication! Yes — Really!</li><li>You get to test the max ticket capacity of your ticket system! — Please make sure your ticket system admins are aligned with this approach!</li></ul><p>Cons</p><blockquote>EVERYONE WILL COMPLAIN — Be ready but stand your ground!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*wqf4UJ2AM0SX29-6E1n13w@2x.jpeg" /></figure><ul><li>Anyone who doesn’t like change will surely go ballistic. “You expect me to close n tickets for a single system! OR Do you know how much time I will need to add to do all these crazy things?”</li></ul><p>* Definition of Done — How to know when a ticket can be closed without wondering if you should have done more.</p><p>** Timelines for tickets are really important for auditability. If you can’t definitively determine that a ticket was closed correctly and the work was completed… you can’t really stand by it during an audit.</p><h3>2. Pre-Work</h3><p>Once you determine a strategy for moving forward, it’s time to prepare for launch (OR explosion)! Now, is a great time to get as much leadership support as you can. At least setup meetings and be prepared to present your findings.</p><p>Next, gather metrics and estimates about performance. Also, I would strongly recommend a small test launch before the real thing.</p><p>If you can, setup a test instance for your ticketing system. Licensing issues and resource constraints have been a thing in the past. However, most vendors will happily give you a development license if you ask. This to a vendor means likely continuity with the product.</p><h4>Metrics and Estimates</h4><p>To gather metrics, use my rule of estimation for uncertainty: Take whatever you think you know and an estimate of length and <strong><em>add 25% to it for meetings, add another 10% for hoops and 5% for errors and documentation.</em></strong></p><h4>Charts and Slide Decks</h4><p>The business speaks these words (in my experience). If you truly want a successful project, leaders must support you and be able to speak intelligently about your project to others.</p><ul><li>Keep slides brief with a couple bullet points (bonus points for transitioning them in one at a time— help maintain focus).</li><li>Use the company branding profile for your deck. Show camaraderie and being a team player.</li><li>Schedule time for questions — Try to not over explain a point to let questions flow naturally.</li><li>Note: It may take some time after the meeting for questions to flow as well (especially if it’s a new subject). This is normal, don’t get discouraged.</li></ul><h3>3. Time to launch!</h3><blockquote>You’ve made it this far! Keep going!</blockquote><p>Come implementation day, everyone will be on edge. Leaders will be anxious. Builders will be drinking be drinking (coffee) heavily.</p><blockquote>Try to calm both groups by using a PowerPoint to show… just kidding!</blockquote><p>The key to implementation is to have a plan for roll out and good estimates. If you are confident in your estimates and have communicated your roll out plan, you’ll do fine.</p><h3>4. Next Steps</h3><p>You have rolled out the automation. How did it go?</p><blockquote>If it went good:</blockquote><ul><li>Great job!</li></ul><p>Congratulations on your success!</p><ul><li>Do you have enough documentation to allow the process to continue long after you have left?</li></ul><p>Not advocating for only documenting positive things. Document your decisions and your methods.</p><p>Failed documentation level is the easiest burn it down and start again initiator!</p><blockquote>If it went bad:</blockquote><ul><li>What could you have done differently.</li></ul><p>Always learn and iterate from your mistakes. My first roll out was technically both a success and disaster. Even by the 3rd one it wasn’t a clear success. These things take time and experience!</p><ul><li>Was the failure something you could/should have controlled?</li></ul><p>Don’t beat yourself up on things you couldn’t control!</p><ol><li>You can’t make anyone faster.</li><li>You can’t make an arduous approval process less so (without being involved with the redesign).</li><li>Lastly, could haves are a one time reflection — Yes, you could have built a queue instead of storing in memory etc. Don’t obsess over what COULD have happened. Strive to make sure you don’t repeat the lesson.</li></ol><h3>Thank you!</h3><p>I hope you found this useful and valuable.</p><p>If you would like to hear more on a topic or different topic, please comment and let me know!</p><p>Please show support by following to hear more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15ff2fbdb286" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automator Chronicles: You can automate almost any* process — Ep 1]]></title>
            <link>https://ben-the-automator.medium.com/automator-chronicles-you-can-automate-almost-any-process-ep-1-15e8404cc9be?source=rss-d7f919a53c74------2</link>
            <guid isPermaLink="false">https://medium.com/p/15e8404cc9be</guid>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Automator]]></dc:creator>
            <pubDate>Mon, 24 Oct 2022 14:00:37 GMT</pubDate>
            <atom:updated>2022-10-28T04:13:04.904Z</atom:updated>
            <content:encoded><![CDATA[<h3>Automator Chronicles: You can automate almost any* process — Ep 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TneHy1adXnZpO1pkQFIfWQ.png" /></figure><p>I wanted to try my hand at writing an article and coming up with some Automator Chronicles based on my lengthy career in Automation. You can find some cool tips, tricks and experience based expertise here. You may also find some cool Story Time moments…. which I hope you will enjoy!</p><p>These are my views and experiences. These do not represent my employer etc.</p><p>Let’s just jump into it:</p><p>This is my MANTRA:</p><h3>Any* process with definable inputs, repeatable steps and determinable outputs CAN be automated!</h3><h3>/* Reaction</h3><p>This is usually where the client goes,</p><blockquote><em>“Wait — What are you talking about!. My process CANNOT be automated! How are you going to do x, y, z? (Visible Confusion; Concern sets in)”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/0*OO55Izi99Bqr2o93" /></figure><p>*/</p><h3>Pre-Requisites</h3><ul><li>Can you solve problems? I don’t mean like you can YouTube or Stack Overflow, but you can apply <a href="https://fs.blog/second-order-thinking/">Second Order Thinking</a> and are ok with thinking outside the box.</li></ul><blockquote><em>Box. What box?</em></blockquote><ul><li>I use a lot of code to solve problems — You don’t have to, but it certainly helps.</li><li>Be confident in drawing diagrams — They don’t have to be perfect, but you should always understand them and be able to explain them easily to others.</li><li>Be resilient. It can take time, frustration and a whole bunch of iteration.</li></ul><h3>TLDR Step by Step</h3><ol><li>Gather requirements</li><li>Discussions (whole lotta discussions)</li><li>Diagrams, Discussions, Coffee (Oh My!)</li><li>Prototyping and iteration</li><li>Acceptance?</li></ol><h3>Step by Step (Kinda)</h3><p>Not definitive (ask me if you want elucidation :P )</p><h3>1. Requirements Gathering</h3><ul><li>What do we have to work with? Just take down a list of all the ingredients for this process. Specifics are great, but don’t get into the weeds. Look for high level stuff.</li></ul><blockquote><em>Raw materials such as: Ticket, document, alert, email etc are common answers here</em></blockquote><ul><li>Do we have repeatable steps?</li></ul><blockquote><em>It doesn’t matter if it’s even written down (right now) as long as the entire process can be followed with no ambiguity or non-evidence based decisions.</em></blockquote><blockquote><em>Even complex decision trees are OK! Just make sure that it is repeatable….. otherwise that part/section/branch CANNOT currently be automated using a programs GUT FEELING.</em></blockquote><ul><li>What’s the expected outcome(s)? Are we baking a soufflé or a mud pie? Need to know what the finished product is…. so I have one or more deliverables for you!</li></ul><blockquote><em>Maybe we need MOAR tickets (hopefully with context!) or to send a text, create a log, fire another process (maybe that process doesn’t exist yet! (my favorite!)).</em></blockquote><blockquote><em>Just make sure we can arrive at some outcome (per step conclusion) … “it depends” won’t work here!</em></blockquote><ul><li>What’s your moral fiber? Does the process compromise business integrity, violate compliance/contractual requirements or otherwise make me feel like a bad human for doing it? I said Any* multiple times and this is a big thing for me.</li></ul><blockquote><em>I won’t compromise on my values and ethical responsibilities to myself, the business etc. Sorry — Find another person.</em></blockquote><h3>2. Discussion</h3><ul><li>Can it be done?!</li></ul><blockquote><em>I haven’t found a scenario that met the above questions that I couldn’t automate!</em></blockquote><ul><li>How long will this thing take?!</li></ul><p>You’ll likely want an LOE (level of effort) for X thing. I can estimate this like we can estimate when we have flying cars… IT DEPENDS.</p><blockquote><em>If it is something I have done before such as Automating Vulnerability Management, Active Directory Compliance as Code or a provisioning process involving 8 languages…. I might have an idea.</em></blockquote><ul><li>LOE will depend on multiple things — How many stakeholders are there? Are there multiple people involved? Who’s doing the work? Do you have a Jenkins (I ❤ Jenkins!) Do we have to jump through hoops to get libraries approved (Story Time coming for this!) and more…</li><li>Srly I need a LOE for this…..Ok fine — Somewhere between 2 weeks and a year! J/K… but not really.</li><li>Estimation for me starts with how long to arrive from A-Z (I’ll figure out the rest along the way!). Can I take raw material and produce a deliverable?</li><li>Next, Take your estimate for completing the code/solution and add something like 25% to it for meetings, add another 10% for hoops and 5% for errors and documentation.</li></ul><blockquote><em>Always strive to under promise and over deliver!</em></blockquote><h3>3. Diagrams, Discussions, Coffee (Oh My!)</h3><ul><li>Obviously, I cannot solve the problem right away…. now we have to start diagramming….</li></ul><blockquote><em>Hopefully you have a whiteboard, lots of napkins or don’t mind me writing on your walls?</em></blockquote><ul><li>Lots MOAR discussion. Not meetings for the sake of meetings….</li></ul><blockquote><em>Make me know the process better than you!</em></blockquote><ul><li>A lot of coffee! I have a sign by my desk that describes this perfectly!</li></ul><blockquote><em>I run on COFFEE, CHAOS &amp; Cuss Words</em></blockquote><ul><li>Research into available libraries, api’s etc will allow you to refine the process timeline. But, you may have to get dirty and create your own library (Please DON’T roll your own Crypto or Auth!).</li></ul><h3>4. Prototyping and iteration</h3><blockquote><em>Watch out for scope creep!</em></blockquote><p>Be prepared to repeat steps a lot.</p><ul><li>You are going to come up with some winners out of the gate and some traaaash ideas.</li><li>Be kind to yourself. Iterate on your thoughts and feedback until you have something that can be shipped.</li></ul><h3>5. Acceptance?!</h3><ul><li>If you have done all the above, it’s safe to say that you can probably ship something.</li><li>MVP (Minimum Viable Product) has always been a very hard concept for me to work on because it involves building weak pillars and foundation. When I know that “here be dragons” and bigger ones if I don’t plan ahead, I tend to fight them head on in the moment.</li></ul><h3>6. Lessons Learned</h3><p>When you complete a project or phase or milestone, analyze it. Think about how it could have gone better (and worse). Think about what you will do differently and measure the above steps.</p><blockquote><em>Yes. You may have come out of this experience with a little bit of bruising.</em></blockquote><ol><li>Did you gather enough requirements?</li></ol><p>This is a tricky concept to grasp. Too many and you will never finish… too few and your project might not prove useful in any form. If there’s value in hearing how requirements gathering has worked (and not worked) in the past, let me know please.</p><p>2. Did you get your estimate right?</p><p>Probably not. You will refine this over time and get better about it. Problems can happen at any stage of the project, unexpectedly and without warning. A “simple” concept can turn into debugging the memory, network or code (yours and others).</p><blockquote><em>Next thing you know, you are hearing color from the amount of espresso you inhaled to solve this “simple” thing.</em></blockquote><p>3. Did it work the first time?</p><p>Most definitely not. This is ok and expected! I can come up with a concept to automate something within minutes of hearing the process at a high level. That idea almost always, always changes when we dive in to the nitty gritty.</p><blockquote><em>The more information you can get, the better your solution will be.</em></blockquote><p>4. What can you do better/different?</p><p>Think about it. There’s always something to improve on. Maybe work on diagramming clearer, your Power Point (yes, I know) skills, your presentation/communication skills… etc</p><blockquote><em>Always be improving!</em></blockquote><h3>You made it. The end of my article!</h3><p>Comments are appreciated!</p><ul><li>How do you feel? Did I help (even a little is ok)</li><li>Am I off my rocker?</li><li>What do you want to see?</li></ul><h3>Thanks for coming to my TED talk!</h3><p>Credits — If you have a better idea to provide credit, I am all ears :)</p><ul><li><a href="https://theconversation.com/what-happens-to-your-body-when-youre-stressed-81789">https://theconversation.com/what-happens-to-your-body-when-youre-stressed-81789</a></li><li><a href="https://timcalkins.com/2019/07/confusion-as-a-defensive-strategy/">https://timcalkins.com/2019/07/confusion-as-a-defensive-strategy/</a></li><li><a href="https://www.attorneyatwork.com/infinitive-and-beyond/">https://www.attorneyatwork.com/infinitive-and-beyond/</a></li><li><a href="https://www.practicalpainmanagement.com/resources/clinical-practice-guidelines/editorial-practicality-pain-acceptance">https://www.practicalpainmanagement.com/resources/clinical-practice-guidelines/editorial-practicality-pain-acceptance</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15e8404cc9be" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>