<?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 Chris Hennighan on Medium]]></title>
        <description><![CDATA[Stories by Chris Hennighan on Medium]]></description>
        <link>https://medium.com/@chennighan?source=rss-5873c3612248------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BrU_FwidCIzNf-e6tZaeiw.jpeg</url>
            <title>Stories by Chris Hennighan on Medium</title>
            <link>https://medium.com/@chennighan?source=rss-5873c3612248------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:22:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chennighan/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[Unleashing the Power of AI in Jira Ticket Creation with AutoStory]]></title>
            <link>https://medium.com/@chennighan/unleashing-the-power-of-ai-in-jira-ticket-creation-with-autostory-bf85e142aa81?source=rss-5873c3612248------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf85e142aa81</guid>
            <category><![CDATA[atlassian]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[openai]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[jira]]></category>
            <dc:creator><![CDATA[Chris Hennighan]]></dc:creator>
            <pubDate>Wed, 29 Mar 2023 01:52:26 GMT</pubDate>
            <atom:updated>2023-03-29T01:54:10.892Z</atom:updated>
            <content:encoded><![CDATA[<p>Discover how <a href="https://autostory.io/">AutoStory</a> is revolutionizing project management by streamlining the Jira ticket creation process with AI-generated user stories and bug tickets.</p><p>In today’s fast-paced business environment, project management efficiency is crucial for success. One key aspect of project management is effective ticket creation, which ensures that development teams have the information they need to work on tasks without delays. AutoStory, an AI-powered Jira Forge app, is transforming the ticket creation process, enabling teams to save time, reduce manual work, and increase productivity.</p><p>In this blog post, we’ll explore the value AutoStory provides by automating the ticket creation process in Jira with AI-generated user stories and bug tickets.</p><h3>Streamline Ticket Creation with AI:</h3><p>AutoStory uses ChatGPT (more specifically and accurately the openai API), a powerful AI developed by OpenAI, to automatically generate comprehensive user stories and bug tickets. By providing a descriptive title for your ticket, the AI creates a detailed story or bug ticket in a matter of seconds. This eliminates the need for manual ticket creation, saving your team valuable time and effort.</p><h3>Boost Productivity with Consistent, High-Quality Tickets:</h3><p>One of the main benefits of using AutoStory is the consistent quality of the generated tickets. The AI ensures that each ticket includes relevant acceptance criteria and testing details, reducing the chance of errors and miscommunications while also generating a substantial description to summarize the ticket. This results in improved efficiency, better collaboration, and fewer project delays.</p><h3>Save Time and Resources:</h3><p>The traditional ticket creation process can take anywhere from 10 to 20 minutes per ticket. With AutoStory, you can generate a ticket in as little as 15 seconds. This translates to significant time savings for your team, allowing them to focus on more important tasks and ultimately increasing overall productivity.</p><h3>Customizable Tickets:</h3><p>While the AI-generated tickets provide a solid foundation, AutoStory also allows users to easily edit and customize tickets to suit their specific needs. This flexibility ensures that your team can tailor the information in each ticket, maintaining the unique context and requirements of your projects.</p><h3>Seamless Integration with Jira:</h3><p>AutoStory integrates effortlessly with Jira’s built-in ticket creation flow, allowing your team to enjoy a seamless user experience. By making the transition to AI-powered ticketing as smooth as possible, AutoStory ensures that your team can quickly adapt to and benefit from this innovative technology.</p><h3>Conclusion:</h3><p>AutoStory is a game-changing Jira Forge app that harnesses the power of AI to revolutionize the ticket creation process. By automating user stories and bug tickets, AutoStory enables teams to save time, increase productivity, and maintain consistent quality across all tickets. Experience the future of Jira ticketing with AutoStory and unlock the true potential of your development team.</p><p>Start your free 30-day trial of AutoStory today and witness firsthand the impact it can have on your project management process.</p><p><a href="https://marketplace.atlassian.com/apps/1230488/autostory-ai-powered-ticket-creation-for-jira?hosting=cloud&amp;tab=overview">AutoStory: AI-Powered Ticket Creation for Jira | Atlassian Marketplace</a></p><p>#jira #atlassian #chatgpt #openai #ai #jiraforge #forgeapps #AutoStory #JiraPlugin #UserStories #Productivity #AgileTeams #openaichatgpt</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf85e142aa81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[View and View Model Modularization in a Large ASP.NET Core Application]]></title>
            <link>https://medium.com/@chennighan/view-and-view-model-modularization-in-a-large-asp-net-core-application-842097e52c1a?source=rss-5873c3612248------2</link>
            <guid isPermaLink="false">https://medium.com/p/842097e52c1a</guid>
            <category><![CDATA[partial-views]]></category>
            <category><![CDATA[viewmodel]]></category>
            <category><![CDATA[razor]]></category>
            <category><![CDATA[mvvm]]></category>
            <category><![CDATA[aspnetcore]]></category>
            <dc:creator><![CDATA[Chris Hennighan]]></dc:creator>
            <pubDate>Mon, 11 Feb 2019 15:11:02 GMT</pubDate>
            <atom:updated>2019-02-11T15:11:02.464Z</atom:updated>
            <content:encoded><![CDATA[<p>It can be overwhelming to tackle building an entire V* (view, view model | controller) layer for an enterprise application, or even just a large web application in general. If you aren’t careful, you can easily end up with a monolithic view layer that is impossible to maintain. We are all familiar with this monster, one with rampant logic in templates and inline scripting and styling. We are going to leave those discussions for another time and base the article off of a few working assumptions/goals:</p><ul><li>Separate business logic from the view</li><li>Strongly type each partial view</li><li>Separate inline static files (JavaScript and CSS, I’m looking at you)</li><li>No full Razor implementation (No Razor Page with built in actions, we’ll be using controllers)</li><li>Razor templating engine (we’ll use some of the syntax provided by Razor)</li></ul><blockquote><strong>Quick Disclaimer</strong>: This implementation approach may not be beneficial to everyone, and it’s dependent upon the technology you’re implementing. This is just the approach that I took to make my application more modular, in a clean and concise way that is easy to maintain and scale. With that being said, let’s continue!</blockquote><h3>The Approach</h3><p>Directory Structure and organization are very important parts of making your V* architecture more modular. For this approach, I break down the views into 2 main categories:</p><ul><li>Top level views</li><li>Partial Views</li></ul><p>You can think of the top level view as the driver for your view; It handles including everything it needs to display one full section of your site. We’ll use the example of a Music Streaming Application Dashboard. I’ve created a simple mockup visual you can see below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jfeH9avVzpn8He3GDE3FUw.png" /><figcaption>Music Streaming Dashboard Mockup</figcaption></figure><p>The above graphic shows a Music Streaming Dashboard View. The top level view acts as a driver to include all the partials it needs to display correctly. If we break this graphic up, we can see pretty clearly the different partials we’d need to make this work. Here’s how I have this view broken down:</p><pre>- Dashboard<br>- - - Playlist<br>- - - - - Song (a list of songs inside the Playlist view)<br>- - - PlaybackControls</pre><p>When we break it down in this way, we start to see how we can make the Dashboard more modular, as all the dashboard really does is provide the container in which the other partial views live (the driver-like analogy we used earlier).</p><h3>Strongly Typed View Models</h3><p>Strongly typing each view and partial view is the next step.</p><h4>Why do this?</h4><p>You want to strongly type your views and partial views because it provides a few specific advantages:</p><ul><li>Compile time type checking</li><li>Data organization <br>- exactly what data is supposed to accessible in each strongly typed view is known. This allows you to build your views and view models in parallel, making it easier to deconstruct what data is actually needed.</li><li>Maintainability<br>- strongly typed views become inherently modular because they are split into logical chunks of common display items that are described by view models that describe exactly what data they need.</li><li>Modularity<br>- When a section of an application is broken down, a hierarchy emerges and you’re able to deconstruct it into a top level view which includes partial views to drive the functionality as described by the figure above. <br>- When you have modules separated like this, they become reusable elsewhere in your application if you ever need to recycle the functionality of a module.</li></ul><h4>How do we do this?</h4><p>To do this, we need to back each View and Partial View with a proper ViewModel. Structurally, the ViewModels will look very similar to the organization of the Views. For example, to recycle a graphic from above:</p><pre>- DashboardViewModel<br>- - - PlaylistViewModel<br>- - - - - SongViewModel<br>- - - PlaybackControlsViewModel</pre><pre>- DashboardView<br>- - - Playlist PartialView<br>- - - - - Song Partial View<br>- - - PlaybackControls Partial View</pre><p>We can see that organizationally, they are basically mirror matches. This can help make logical sense of where everything lives in your application when modifying/adding data for new views you create and current views you’re working with.</p><blockquote><strong>Quick Disclaimer</strong>: We are going to be operating under the assumption that we are already inheriting a parent Layout for our top level Views.</blockquote><p>Your <strong><em>Layout.cshtml</em></strong> file might look something like this:</p><pre>&lt;!DOCTYPE html&gt;<br>&lt;html&gt;<br> &lt;head&gt;<br>  &lt;!-- top level styles for all inherited views to use --&gt;<br>  &lt;link rel=&quot;stylesheet&quot; href=&quot;~/path/to/useful/styles/useful.min.css&quot; /&gt;<br>  <br>  &lt;!-- additional view level styles --&gt;<br>  <a href="http://twitter.com/RenderSection">@RenderSection</a>(&quot;styles&quot;, required: false)<br> &lt;/head&gt;<br> &lt;body class=&quot;insert-your-useful-body-class&quot;&gt;<br>  &lt;div class=&quot;insert-your-useful-container-class&quot;&gt;<br>   <a href="http://twitter.com/await">@await</a> Component.InvokeAsync(&quot;Header&quot;)<br>   <a href="http://twitter.com/await">@await</a> Component.InvokeAsync(&quot;Sidebar&quot;)<br>   <br>   &lt;div class=&quot;insert-your-useful-content-wrapper-class&quot;&gt;       <br>    &lt;section class=&quot;insert-your-useful-content-class&quot;&gt;<br>     &lt;!-- Your Page Content Here --&gt;<br>     <a href="http://twitter.com/RenderBody">@RenderBody</a>()<br>    &lt;/section&gt;<br>   &lt;/div&gt;<br>   <br>   <a href="http://twitter.com/await">@await</a> Component.InvokeAsync(&quot;Footer&quot;)<br>   <a href="http://twitter.com/await">@await</a> Component.InvokeAsync(&quot;ControlSidebar&quot;)<br>  &lt;/div&gt;<br>  <br>  &lt;!-- top level scripts for all inherited views to use --&gt;<br>  &lt;script src=&quot;~/path/to/useful/scripts/useful.min.js&quot;&gt;&lt;/script&gt;<br>  &lt;!-- additional view level scripts --&gt;<br>  <a href="http://twitter.com/RenderSection">@RenderSection</a>(&quot;scripts&quot;, required: false)<br> &lt;/body&gt;<br>&lt;/html&gt;</pre><p>With this extendable layout being setup, you can now set up your top level view. I mentioned earlier that the top level View should act as a driver for all the partials required for the section of the application to function properly. For this, I recommend setting up the parent container in your top level view, in this example the <strong><em>DashBoardView.cshtml</em></strong> file:</p><pre><a href="http://twitter.com/model">@model</a> MusicStreamingApplication.Models.DashboardViewModel<br>@{<br>    // the overall layout to inherit<br>    Layout = &quot;_Layout&quot;;<br>}<br><a href="http://twitter.com/section">@section</a> styles {<br>    &lt;!-- any additional styles for Dashboard --&gt;<br>}</pre><pre>&lt;!-- all the partials Dashboard requires --&gt;<br>&lt;partial name=&quot;~/Views/Dashboard/Playlist.cshtml&quot; for=&quot;Playlist&quot; /&gt;<br>&lt;partial name=&quot;~/Views/Dashboard/PlaybackControls.cshtml&quot; for=&quot;PlaybackControls&quot; /&gt;</pre><pre><a href="http://twitter.com/section">@section</a> scripts {<br>    &lt;!-- any additional scripts for Dashboard --&gt;<br>}</pre><p>Notice above how we’re passing the partial view exactly what view model it needs to work and display the correct data with the for attribute. for is shorthand for @Model. so the result of using for would map to @Model.Playlist for the first partial.</p><p>Moving on to the model example, your <strong><em>DashboardViewModel.cs</em></strong> would look something like this:</p><pre>using MusicStreamingApplication.Models.PlaylistViewModel;<br>using MusicStreamingApplication.Models.PlaybackControlsViewModel;</pre><pre>namespace MusicStreamingApplication.Models.DashboardViewModel<br>{<br>    public class DashboardViewModel<br>    {<br>        public RequestViewModel(){}<br>        <br>        public PlaylistViewModel Playlist { get; set; }<br>        public PlaybackControlsViewModel PlaybackControls { get; set; }<br>    }<br>}</pre><p>Furthermore, you can start to see how we are drilling down to the exact granularity each partial view needs. The <strong>PlaylistViewModel </strong>would then have a <strong>SongViewModel<em> </em></strong>and so on.</p><h3>Conclusion</h3><p>Creating scalable and modular applications can be tough, but if you commit yourself to a specific approach it becomes much easier. Strongly typing your views allows you to mirror your data needed inside the view with the view model for each specific view and partial view respectively; Doing this makes your application more organized, modular, scalable, and provides additional compile time type checking benefits. Now, having said all of that, get back to work!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=842097e52c1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reservoir — an XRP Escrow Application]]></title>
            <link>https://medium.com/@chennighan/reservoir-an-xrp-escrow-application-8d40fb60fb0b?source=rss-5873c3612248------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d40fb60fb0b</guid>
            <category><![CDATA[escrow]]></category>
            <category><![CDATA[xrp]]></category>
            <category><![CDATA[reservoir]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ripple]]></category>
            <dc:creator><![CDATA[Chris Hennighan]]></dc:creator>
            <pubDate>Sat, 02 Dec 2017 01:19:53 GMT</pubDate>
            <atom:updated>2017-12-02T01:19:53.027Z</atom:updated>
            <content:encoded><![CDATA[<p>There were a few questions we asked ourselves before we started the Reservoir project, such as:</p><ul><li>What is the point of escrowing XRP?</li><li>Why would anyone be interested in this?</li><li>Is there room for innovation in this space?</li></ul><p>We should give a little background as to what escrow is in the traditional sense in layman terms. Escrow came about out of the unpopular notion that parties had to trust each other to finalize a transaction. If party A was selling goods and party B wanted to buy those goods with cash, then one of the parties would ultimately have to trust the other in order for the transaction to take place; Not to mention if there was something improper going on with one side such as bad goods, or even fake currency to give an oversimplified example. From this unappealing process arose the concept of escrow, wherein both parties place their trust in a common third party, holding payments until services have been rendered or goods have been received. The third party usually takes a small fee from the transaction, and in return transacting parties gain peace of mind as well as whatever security the third party is able to provide.</p><p><a href="https://ripple.com/build/escrow/#use-case-time-based-lockup">Time based lockup escrow</a>, in terms of XRP can be thought of in much the same way if you think of the transaction as between two parties: the XRP Ledger Address issuing the escrow, and the XRP Ledger Address<strong> </strong>that is designated as the destination address; The XRP Ledger<strong> </strong>itself, in this case, is the trusted third party who handles all the security etc. This minimizes risk in trusting a third party also, because you’re putting your trust in the XRP Ledger which comes with all the security benefits of the RCL (<a href="https://ripple.com/build/xrp-ledger-consensus-process/">Ripple Consensus Ledger</a>). This can also be used in a number of different ways, but here is the implementation case from <a href="https://www.secureblockchains.com/reservoir/about">Reservoir</a>:</p><ul><li>Securely storing XRP for a predefined period of time which removes it from the circulating supply and nobody has access to it. It remains an object on the XRP Ledger. You are the holder of both the XRP Ledger Address the XRP is being sent from as well as the XRP Address the XRP is released to once the escrow object has matured (i.e fulfilled the date set when the escrow object was created); The XRP Ledger itself remains the trusted third party.</li></ul><p>Reservoir intends to start with the time based lockup escrow functionality and expand into more conditional and cryptographic implementations. Starting with time based lockup makes sense because it brings the community the ability to lock their XRP up securely in the same manner that Ripple themselves plan to <a href="https://ripple.com/insights/ripple-to-place-55-billion-xrp-in-escrow-to-ensure-certainty-into-total-xrp-supply/">lock their 55 billion</a>. There is definitely room for innovation and improvement in the XRP escrow space and we see the opportunity to not only build applications in many different industries, but build tools that other developers can also use which will ultimately empower the entire XRP community. Thanks for joining us on this journey, and we hope you’ll visit our site at <a href="https://www.secureblockchains.com/reservoir">https://www.secureblockchains.com/reservoir</a> and give us some feedback, we’d love to hear from you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d40fb60fb0b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simplifying the XRP Purchase Process]]></title>
            <link>https://medium.com/@chennighan/ripple-exchange-simplifying-the-xrp-purchase-process-9a0cfde558a9?source=rss-5873c3612248------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a0cfde558a9</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[xrp]]></category>
            <category><![CDATA[ripple]]></category>
            <dc:creator><![CDATA[Chris Hennighan]]></dc:creator>
            <pubDate>Mon, 02 Oct 2017 17:03:11 GMT</pubDate>
            <atom:updated>2017-10-04T16:22:16.968Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine you pitch someone the idea of a cryptocurrency that can outperform the market leaders by a magnitude of over 100 times the transactions per second measurement and that the technology is currently being widely tested in banks around the world. Now you have their attention so you go on, explaining how the cryptocurrency will revolutionize not only the financial industry, but virtually every industry that accepts payments. At this point, they are genuinely interested and want to know how they can acquire such a cryptocurrency, and what exchange they can put their hard earned <strong>USD </strong>into to get <strong>Ripple </strong>(<strong>XRP</strong>).</p><p>Almost everyone unfamiliar with cryptocurrency exchanges and the process of buying and selling just assumes that you can make the easy transaction of <strong>$ → XRP</strong>, but that is not the case at all. The process is actually much more complex and to demystify this process I’ll explain what actually happens in the current state of affairs of purchasing XRP and the processes that you have to go through in acquiring it. To purchase XRP you have to go through the following steps:</p><ul><li>Start with the amount of <strong>XRP </strong>you want to purchase in <strong>USD</strong></li><li>Choose an exchange (I have used Coinbase the most) that offers a direct exchange of <strong>USD → Bitcoin (BTC) or Ethereum (ETH)</strong></li><li>Based on the exchange you are using, once you exchange your <strong>USD → BTC or ETH</strong> (which could in many cases take up to 2 weeks) you have to either send your newly acquired currency to another exchange that offers the exchange of this currency for <strong>XRP</strong>, or if the exchange you’re using already offers exchanging your <strong>BTC or ETH → XRP </strong>you can keep it on this exchange (there aren’t many exchanges that offer this feature, if any at the date this article is written).</li><li>Exchange your <strong>BTC or ETH → XRP </strong>and now you officially own your cryptocurrency, but it doesn’t end there.</li><li>Having acquired your <strong>XRP </strong>you need to create an <strong>XRP wallet </strong>to store your currency safely and securely, which requires choosing a wallet and transferring your <strong>XRP </strong>from the exchange address to your newly generated ripple wallet address.</li><li>You are now done with the <strong>BUY </strong>process. If you want to sell your <strong>XRP </strong>at any time and cash out <strong>USD → Bank Account</strong>, you now have to reverse the process you just completed.</li></ul><p>Not only is this a grueling process, you can also lose a lot of money exchanging multiple times due to fluctuating exchange rates. After telling the newly interested cryptocurrency spectators this process, almost all of them say things like “that’s ridiculous”, or “I’m not doing that”, but the most widely received response I get is “I don’t want to miss out on this amazing currency, can you do it for me?”. It’s very off-putting and disheartening for people to get so excited over something, just to be crushed with unneeded complications in processes that can be easily improved and shortened. This is where our platform will thrive.</p><p>Our platform is an application that will simplify this process into an easy 2 step process:</p><ul><li>Link your bank account or preferred card of use. (yes, even a credit card!)</li><li>Start a <strong>sale </strong>or <strong>purchase</strong> order through the user interface of our iOS app or website.</li></ul><p>That’s it, then you will be notified when your order has been filled just like a normal stock exchange or cryptocurrency exchange. The technology behind our apps and sites allows us to directly connect to the Ripple Block Chain which is avoided by most third party sites due to the complex nature of the code. Many sites take short cuts and integrate with pre existing exchanges and claim that they are innovating and improving the process. The sad truth is, many of these sites popping up are just using the existing flow and introducing themselves as a middleman to charge you even more money to exchange.</p><p>We will set ourselves apart from the pack by directly communicating with the Ripple Block Chain and allowing users to use the payment methods they want to use without introducing unnecessary exchanges. Stay tuned for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a0cfde558a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>