<?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 ⌘⌥ Rafael Barbosa  on Medium]]></title>
        <description><![CDATA[Stories by ⌘⌥ Rafael Barbosa  on Medium]]></description>
        <link>https://medium.com/@rafavinnce?source=rss-6645ecc98480------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ifsUG31KMViFzHTZl57Ojw.png</url>
            <title>Stories by ⌘⌥ Rafael Barbosa  on Medium</title>
            <link>https://medium.com/@rafavinnce?source=rss-6645ecc98480------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:08:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rafavinnce/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[Flutter Internationalization the Easy Way — using Provider and JSON]]></title>
            <link>https://medium.com/@rafavinnce/flutter-internationalization-the-easy-way-using-provider-and-json-986eb5d76822?source=rss-6645ecc98480------2</link>
            <guid isPermaLink="false">https://medium.com/p/986eb5d76822</guid>
            <category><![CDATA[internacionalização]]></category>
            <category><![CDATA[internationalization]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[flutter-location]]></category>
            <dc:creator><![CDATA[⌘⌥ Rafael Barbosa ]]></dc:creator>
            <pubDate>Wed, 15 Jul 2020 11:41:55 GMT</pubDate>
            <atom:updated>2020-07-15T11:44:35.176Z</atom:updated>
            <content:encoded><![CDATA[<h3>Flutter Internationalization the Easy Way — using Provider and JSON</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xzVhGIx0cvocRPW7.png" /></figure><p>If you are going to deploy your app to users who speak another language then you’ll need to “internationalize” it. Flutter offers good <a href="https://flutter.io/tutorials/internationalization/">documentation</a> on how to set up your localized values for each locale that your app supports. but it can be sometimes unclear and hard to implement or hard to manage.</p><p>In this tutorial, we are going to learn how to localize our apps <strong>the simple way</strong> by using JSON files to store your data in multiple languages.</p><h3>Getting Started</h3><p>Let’s create a new Flutter project and clean your main.dart file. In this tutorial, my app has 2 languages which are English(LTR) and Arabic(RTL). The App will show sentences by device language.let’s do it</p><h3>Prepare Your Project</h3><p>before writing any actual code we need to create the files containing translated strings<strong> </strong>first and update the <strong>pubspec.yaml</strong> file.</p><h3>Create the language files</h3><p>Create a new folder <strong>i18n</strong> in the project root. This folder will hold all of the language files. Our project, we will have 2 Language Arabic and English so we will create <strong>en.json</strong> and ar<strong>.json</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*vVqfDvkB9IOQAaQXxiLR2Q.png" /></figure><p>These files will contain only simple <strong>key-value pairs</strong> of strings. Using JSON is beneficial, because similar to XML, you can just give it to a translator without them needing to access your code.</p><p>en-US.json</p><pre>{<br>  &quot;title&quot;: &quot;Hello!&quot;,<br>  &quot;Message&quot; : &quot;This is English&quot;<br>}</pre><p>pt-BR.json</p><pre>{<br>  &quot;title&quot;: &quot;Olá Mundo!&quot;,<br>  &quot;Message&quot; : &quot;Este é Brazileiro&quot;<br>}</pre><h3>Update pubspec.yaml</h3><p>Flutter has a localization package for translating own component by languages. so we need to add it .open pubspec.yaml file and add flutter_localizations to your dependencies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/369/1*xOzkc3qC1Pc5sPdsMFqd4g.png" /></figure><p>since you’ve just added new language JSON files, you need to <strong>specify them as assets</strong> in order to access them in code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/386/1*w_85Dtdr29dvUVuRVDXTIg.png" /></figure><h3>Create DemoLocalizations Class And Delegate Class</h3><p><strong><em>DemoLocalizations</em></strong><em> Class </em>is the main class of localization. This class will load all sentences by given language then this class gives sentences by the loaded languages. This class uses load a method for loading the sentences from json files and it can get sentences from loaded sentences with translate method. My Language service will work by sentence keys.</p><pre><strong>class </strong>AppLocalizations {<br>  <strong>final </strong>Locale locale;<br><br>  AppLocalizations(<strong>this</strong>.locale);<br><br>  // Helper method to keep the code in the widgets concise<br>  // Localizations are accessed using an InheritedWidget &quot;of&quot; syntax<br>  <strong>static </strong>AppLocalizations <em>of</em>(BuildContext context) {<br>    <strong>return </strong>Localizations.<em>of</em>&lt;AppLocalizations&gt;(context, AppLocalizations);<br>  }<br><br>  // Static member to have a simple access to the delegate from the MaterialApp<br>  <strong>static const </strong>LocalizationsDelegate&lt;AppLocalizations&gt; <em>delegate </em>=<br>  _AppLocalizationsDelegate();<br><br>  Map&lt;String, String&gt; _localizedStrings;<br><br>  Future&lt;bool&gt; load() <strong>async </strong>{<br>    // Load the language JSON file from the &quot;lang&quot; folder<br>    String jsonString =<br>    <strong>await </strong>rootBundle.loadString(&#39;i18n/${locale.languageCode}.json&#39;);<br>    Map&lt;String, <strong>dynamic</strong>&gt; jsonMap = json.decode(jsonString);<br><br>    _localizedStrings = jsonMap.map((key, value) {<br>      <strong>return </strong>MapEntry(key, value.toString());<br>    });<br><br>    <strong>return true</strong>;<br>  }<br><br>  // This method will be called from every widget which needs a localized text<br>  String translate(String key) {<br>    <strong>return </strong>_localizedStrings[key];<br>  }<br>}</pre><p>you still need to provide a way for Flutter to step in and decide when the <strong>load()</strong> method will be called and which locale will be used. Flutter localization uses delegates for initialization. this is why we will create a delegate class to be able to use that class.</p><pre><strong>class </strong>_AppLocalizationsDelegate<br>    <strong>extends </strong>LocalizationsDelegate&lt;AppLocalizations&gt; {<br>  // This delegate instance will never change (it doesn&#39;t even have fields!)<br>  // It can provide a constant constructor.<br>  <strong>const </strong>_AppLocalizationsDelegate();<br><br>  @override<br>  bool isSupported(Locale locale) {<br>    // Include all of your supported language codes here<br>    <strong>return </strong>[&#39;en&#39;, &#39;ar&#39;].contains(locale.languageCode);<br>  }<br><br>  @override<br>  Future&lt;AppLocalizations&gt; load(Locale locale) <strong>async </strong>{<br>    // AppLocalizations class is where the JSON loading actually runs<br>    AppLocalizations localizations = <strong>new </strong>AppLocalizations(locale);<br>    <strong>await </strong>localizations.load();<br>    <strong>return </strong>localizations;<br>  }<br><br>  @override<br>  bool shouldReload(_AppLocalizationsDelegate old) =&gt; <strong>false</strong>;<br>}</pre><p>The Final file (locate in /lib/app_localizations.dart):</p><pre>import &#39;dart:convert&#39;;<br><br>import &#39;package:flutter/cupertino.dart&#39;;<br>import &#39;package:flutter/services.dart&#39;;<br><br>class AppLocalizations {<br>  final Locale locale;<br><br>  AppLocalizations(this.locale);<br><br>  <em>// Helper method to keep the code in the widgets concise<br>  // Localizations are accessed using an InheritedWidget &quot;of&quot; syntax<br>  </em>static AppLocalizations <em>of</em>(BuildContext <em>context</em>) {<br>    return Localizations.<em>of</em>&lt;AppLocalizations&gt;(<em>context</em>, AppLocalizations);<br>  }<br><br>  <em>// Static member to have a simple access to the delegate from the MaterialApp<br>  </em>static const LocalizationsDelegate&lt;AppLocalizations&gt; <em>delegate </em>=<br>  _AppLocalizationsDelegate();<br><br>  Map&lt;String, String&gt; _localizedStrings;<br><br>  Future&lt;bool&gt; load() async {<br>    <em>// Load the language JSON file from the &quot;lang&quot; folder<br>    </em>String jsonString =<br>    await rootBundle.loadString(&#39;assets/i18n/${locale.languageCode}-${locale.countryCode}-${locale.countryCode}.json&#39;);<br>    Map&lt;String, dynamic&gt; jsonMap = json.decode(jsonString);<br><br>    _localizedStrings = jsonMap.map((<em>key</em>, <em>value</em>) {<br>      return MapEntry(<em>key</em>, <em>value</em>.toString());<br>    });<br><br>    return true;<br>  }<br><br>  <em>// This method will be called from every widget which needs a localized text<br>  </em>String translate(String <em>key</em>) {<br>    return _localizedStrings[<em>key</em>];<br>  }<br>}<br><br>class _AppLocalizationsDelegate<br>    extends LocalizationsDelegate&lt;AppLocalizations&gt; {<br>  <em>// This delegate instance will never change (it doesn&#39;t even have fields!)<br>  // It can provide a constant constructor.<br>  </em>const _AppLocalizationsDelegate();<br><br>  <em>@override<br>  </em>bool isSupported(Locale <em>locale</em>) {<br>    <em>// Include all of your supported language codes here<br>    </em>return [&#39;en&#39;, &#39;ar&#39;].contains(<em>locale</em>.languageCode);<br>  }<br><br>  <em>@override<br>  </em>Future&lt;AppLocalizations&gt; load(Locale <em>locale</em>) async {<br>    <em>// AppLocalizations class is where the JSON loading actually runs<br>    </em>AppLocalizations localizations = new AppLocalizations(<em>locale</em>);<br>    await localizations.load();<br>    return localizations;<br>  }<br><br>  <em>@override<br>  </em>bool shouldReload(_AppLocalizationsDelegate <em>old</em>) =&gt; false;<br>}</pre><h3>Make the MaterialApp localized</h3><p>The setup of the localization happens inside the <strong>MaterialApp </strong>widget, which is the root of a Flutter app. Here you <strong>specify which languages are supported</strong></p><pre><strong>class </strong>MyApp <strong>extends </strong>StatelessWidget {<br>  @override<br>  Widget build(BuildContext context) {<br>    <strong>return </strong>MaterialApp(<br>      supportedLocales: [<br>        Locale(&#39;en&#39;, &#39;US&#39;),<br>        Locale(&#39;pt&#39;, &#39;BR&#39;),<br>      ],<br>      localizationsDelegates: [<br>        AppLocalizations.<em>delegate</em>,<br>        GlobalMaterialLocalizations.<em>delegate</em>,<br>        GlobalWidgetsLocalizations.<em>delegate</em>,<br>      ],<br>      home: AppLang(),<br>    );<br>  }}</pre><p>Now we have all the setup done to start working.</p><h3>Translating text in the UI</h3><p>to translate your Just call the <strong>of()</strong> helper static method on <strong>AppLocalizations() </strong>to get the instance properly set up by Flutter and then translate using the keys you’ve specified in the JSON files!</p><pre>import &#39;package:app/app_localizations.dart&#39;;</pre><pre><strong>class </strong>AppLang <strong>extends </strong>StatelessWidget {<br>  @override<br>  Widget build(BuildContext context) {<br>    <strong>return </strong>Scaffold(<br>      appBar: AppBar(<br>        title:    Text(AppLocalizations.<em>of</em>(context).translate(&#39;title&#39;)),<br>      ),<br>      body: Center(<br>        child: Text(AppLocalizations.<em>of</em>(context).translate(&#39;Message&#39;)),<br>      ),<br>    );<br>  }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/543/1*VeLm-T2hrH05unGhDSWNUg.png" /></figure><p>Now to test if this works. Go to the app <strong>Settings </strong>and change the language to <strong>Brazil</strong> and re-open the app and you will see that the message and title are translated immediately to <strong>Brazil.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/1*k_GZfTgbKzUQZn6ZlSI9ag.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/543/1*czHmu-iYMdYE84S0uBEcIQ.png" /></figure><p>Done!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=986eb5d76822" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[test]]></title>
            <link>https://medium.com/@rafavinnce/test-28112d5a89ea?source=rss-6645ecc98480------2</link>
            <guid isPermaLink="false">https://medium.com/p/28112d5a89ea</guid>
            <dc:creator><![CDATA[⌘⌥ Rafael Barbosa ]]></dc:creator>
            <pubDate>Wed, 22 May 2019 13:58:12 GMT</pubDate>
            <atom:updated>2019-05-22T13:59:30.826Z</atom:updated>
            <content:encoded><![CDATA[<p>fdsfdsf</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28112d5a89ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[test pwa]]></title>
            <link>https://medium.com/@rafavinnce/test-pwa-d01a33ec85da?source=rss-6645ecc98480------2</link>
            <guid isPermaLink="false">https://medium.com/p/d01a33ec85da</guid>
            <dc:creator><![CDATA[⌘⌥ Rafael Barbosa ]]></dc:creator>
            <pubDate>Thu, 25 Apr 2019 16:50:56 GMT</pubDate>
            <atom:updated>2019-05-15T21:41:19.142Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/@lucashenriquedeabreu/progressive-web-app-aplicando-as-t%C3%A9cnicas-de-pwa-em-angular-6-87ee22444d19">Progressive Web App: Aplicando as técnicas de PWA em Angular 6</a></p><p><a href="https://www.quora.com/Which-is-better-SPA-single-page-apps-or-PWA-progressive-web-apps">https://www.quora.com/Which-is-better-SPA-single-page-apps-or-PWA-progressive-web-apps</a></p><ul><li><a href="https://developer.okta.com/blog/2017/07/20/the-ultimate-guide-to-progressive-web-applications">The Ultimate Guide to Progressive Web Applications</a></li><li><a href="https://developer.okta.com/blog/2017/05/09/progressive-web-applications-with-angular-and-spring-boot">Build Your First Progressive Web Application with Angular and Spring Boot</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bRI5to79FDZJyz1uq4UVug.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d01a33ec85da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HPC — High Performance Cluster]]></title>
            <link>https://medium.com/@rafavinnce/hpc-high-performance-cluster-708434e82426?source=rss-6645ecc98480------2</link>
            <guid isPermaLink="false">https://medium.com/p/708434e82426</guid>
            <category><![CDATA[hpc]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[⌘⌥ Rafael Barbosa ]]></dc:creator>
            <pubDate>Tue, 22 Jan 2019 02:49:10 GMT</pubDate>
            <atom:updated>2019-01-22T02:53:30.642Z</atom:updated>
            <content:encoded><![CDATA[<h3>HPC — High Performance Cluster</h3><p>Solution architecture: HPC cluster deployed in the cloud<br>High performance computing (HPC) applications can scale to thousands of compute cores, extend on-premises big compute, or run as a 100% cloud native solution. This HPC solution including the head node, compute nodes, and storage nodes, runs in AWS or Azure with no hardware infrastructure to maintain.</p><p>This solution is built on the Azure managed services or AWS Console: Virtual Machine Scale Sets, Virtual Network and Storage. These services run in a high-availability environment, patched and supported, allowing you to focus on your solution instead of the environment they run in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZU5Yj7WVGha88vGwaQMpAw.png" /></figure><h3>HPC head node(jumpbox)</h3><ul><li>The HPC head node(jumpbox) runs on-premises or within Azure as a virtual machine.</li><li>Virtual networking available with all instances is used to achieve high bandwidth and microsecond latencies between compute nodes.<br>Storage nodes can also be run within virtual machines.</li></ul><h3>Virtual Machine Scale Sets</h3><ul><li>Availability sets ensure that the application is available and resilient to updates and hardware faults.</li><li>Virtual machines communicating via Virtual network(NSG — network security group) are placed within the same availability set.</li></ul><h3>Virtual Network</h3><ul><li>Virtual Network provides IP connectivity between the head node, compute nodes, and storage nodes.</li></ul><h3>Storage</h3><ul><li>Storage blobs(or shared disks storage) store the disks backing the virtual machines and provides long-term storage of unstructured data and executable files used by the HPC application.</li><li>can be network-sharing services (NFS), storage account manager services, or shared virtual disks in the VMs between the containers.</li></ul><h3>CI/CD Proccess</h3><ul><li>The CI/CD(Continuous Integration/Continuous Deployment) has a constructs one of the most important parts of the application life cycle.</li><li>We build important rules during the design, design and development of the apps that are implemented through cicd pipelines.</li><li>For each Client there are two different pipelines, develop and master.</li><li>Pipeline develop builds all the rules necessary to move up test and local development automation environments or in test VMs in the cloud.</li><li>Master pipeline covers rules that involve approves of other team members in the demands created through build, cluster configurations, and all-in-one VMs, and business rules for various deployments in production environments.</li></ul><h3>Monitoring &amp; Instrumentation</h3><ul><li>With performance management quickly identify if there are any problems, how many users are impacted, and perform a risk analysis to find and fix the problem.</li><li>We get effective performance monitoring, alerts, and easy-to-use dashboards to help ensure applications are available and performing as expected.</li><li>Seamless integration with your DevOps pipeline using Team Services, Git, AWS and our webhooks.</li><li>Detect and diagnose application performance exceptions and issues.</li><li>Detect Azure Cloud Services behaviors, anomalies, failure counts, and performance changes. Receive notifications and alerts with rich diagnostic information to enable you to respond to problems at the speed desired by your customers.</li><li>With distributed instrumentation in the cloud (AWS, Azure, Elasticsearch, Logstash, Kibana, App Insights) we detect cloud service behaviors, anomalies, failure counts, and performance changes. Receive notifications and alerts with rich diagnostic information to enable you to respond to problems at the speed desired by your customers. Integrated with SLACK 😃</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=708434e82426" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gitflow — Branch Guide]]></title>
            <link>https://medium.com/@rafavinnce/gitflow-branch-guide-8a523360c053?source=rss-6645ecc98480------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a523360c053</guid>
            <category><![CDATA[version-control]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[gitflow]]></category>
            <dc:creator><![CDATA[⌘⌥ Rafael Barbosa ]]></dc:creator>
            <pubDate>Tue, 22 Jan 2019 02:45:36 GMT</pubDate>
            <atom:updated>2019-01-22T02:46:27.992Z</atom:updated>
            <content:encoded><![CDATA[<h3>Gitflow — Branch Guide</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*uUpzVOpdFw5V-tJ_YvgFmA.png" /><figcaption>atlassian gitflow</figcaption></figure><h3>What Is GitFlow?</h3><p><strong>Background</strong> — <a href="https://nvie.com/posts/a-successful-git-branching-model/">GitFlow</a> is a branching model for Git, created by Vincent Driessen. It has attracted a lot of attention because it is very well suited to collaboration and scaling the development team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/517/1*MzAJM2CvDSc8uCRFp_t1-A.png" /></figure><h3>Key Benefits</h3><h3>Parallel Development</h3><p>One of the great things about GitFlow is that it makes parallel development very easy, by isolating new development from finished work. New development (such as features and non-emergency bug fixes) is done in feature branches, and is only merged back into main body of code when the developer(s) is happy that the code is ready for release.</p><p>Although interruptions are a BadThing(tm), if you are asked to switch from one task to another, all you need to do is commit your changes and then create a new feature branch for your new task. When that task is done, just checkout your original feature branch and you can continue where you left off.</p><h3>Collaboration</h3><p>Feature branches also make it easier for two or more developers to collaborate on the same feature, because each feature branch is a sandbox where the only changes are the changes necessary to get the new feature working. That makes it very easy to see and follow what each collaborator is doing.</p><h3>Release Staging Area</h3><p>As new development is completed, it gets merged back into the develop branch, which is a staging area for all completed features that haven’t yet been released. So when the next release is branched off of develop, it will automatically contain all of the new stuff that has been finished.</p><h3>Support For Emergency Fixes</h3><p>GitFlow supports hotfix branches — branches made from a tagged release. You can use these to make an emergency change, safe in the knowledge that the hotfix will only contain your emergency fix. There’s no risk that you’ll accidentally merge in new development at the same time.</p><h3>How It Works</h3><p>New development (new features, non-emergency bug fixes) are built in feature branches.</p><p>Feature branches are branched off of the develop branch, and finished features and fixes are merged back into the develop branch when they’re ready for release:</p><p>When it is time to make a release, a release branch is created off of develop.</p><p>The code in the release branch is deployed onto a suitable test environment, tested, and any problems are fixed directly in the release branch. This <strong>deploy -&gt; test -&gt; fix -&gt; redeploy -&gt; retest</strong> cycle continues until you’re happy that the release is good enough to release to customers.</p><p>When the release is finished, the release branch is merged into master and into develop too, to make sure that any changes made in the release branch aren’t accidentally lost by new development.</p><p>The master branch tracks released code only. The only commits to master are merges from release branches and hotfix branches.</p><p>Hotfix branches are used to create emergency fixes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*GN-obzwc5M6dykitMpy9YQ.png" /></figure><p>hey are branched directly from a tagged release in the master branch, and when finished are merged back into both master and develop to make sure that the hotfix isn’t accidentally lost when the next regular release occurs.</p><p>From a <strong>CI/CD</strong> point of view, we only want to build and deploy the develop and master branches respectively.</p><p>The develop branch should be sent to a dev and/or test environments. The master branch ends up in production.</p><h3>FOR DEVs</h3><h3>Getting Started</h3><p><strong>Linux</strong><br>apt-get install git-flow</p><p><strong>Mac</strong><br>brew install git-flow</p><p>Git flow workflow — Historical Branches</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QgaWrMXzYobhcpJzHVkOXw.png" /></figure><h3>Develop and Master Branches</h3><p>Instead of a single master branch, this workflow uses two branches to record the history of the project. The master branch stores the official release history, and the develop branch serves as an integration branch for features. It’s also convenient to tag all commits in the master branch with a version number.</p><p>The first step is to complement the default master with a develop branch. A simple way to do this is for one developer to create an empty develop branch locally and push it to the server:</p><pre>git branch develop<br>git push -u origin develop</pre><p>This branch will contain the complete history of the project, whereas master will contain an abridged version. Other developers should now clone the central repository and create a tracking branch for develop.</p><p>When using the git-flow extension library, executing git flow init on an existing repo will create the develop branch:</p><pre>$ git flow init<br>Initialized empty Git repository in ~/project/.git/<br>No branches exist yet. Base branches must be created now.<br>Branch name for production releases: [master]<br>Branch name for &quot;next release&quot; development: [develop]</pre><pre>How to name your supporting branch prefixes?<br>Feature branches? [feature/]<br>Release branches? [release/]<br>Hotfix branches? [hotfix/]<br>Support branches? [support/]<br>Version tag prefix? []</pre><pre>$ git branch<br>* develop<br> master</pre><h3>Feature Branches</h3><p>Each new feature should reside in its own branch, which can be pushed to the central repository for backup/collaboration. But, instead of branching off of master, feature branches use develop as their parent branch. When a feature is complete, it gets merged back into develop. Features should never interact directly with master.</p><h3>Git flow workflow — Feature Branches</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JOlEPRYTJQDdlniwWndeRA.png" /></figure><p>Note that feature branches combined with the develop branch is, for all intents and purposes, the Feature Branch Workflow. But, the Gitflow Workflow doesn’t stop there.</p><p>Feature branches are generally created off to the latest develop branch.</p><h3>Creating a feature branch</h3><p>Without the git-flow extensions:</p><pre>git checkout develop<br>git checkout -b feature_branch</pre><p>When using the git-flow extension:</p><p>git flow feature start feature_branch</p><p>Continue your work and use Git like you normally would.</p><h3>Finishing a feature branch</h3><p>When you’re done with the development work on the feature, the next step is to merge the feature_branch into develop.</p><p>Without the git-flow extensions:</p><pre>git checkout develop<br>git merge feature_branch</pre><p>Using the git-flow extensions:</p><p>git flow feature finish feature_branch</p><h3>Release Branches</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RdfreU6QIY6fyBNTITwzSw.png" /></figure><p>Once develop has acquired enough features for a release (or a predetermined release date is approaching), you fork a release branch off of develop. Creating this branch starts the next release cycle, so no new features can be added after this point — only bug fixes, documentation generation, and other release-oriented tasks should go in this branch. Once it’s ready to ship, the release branch gets merged into master and tagged with a version number. In addition, it should be merged back into develop, which may have progressed since the release was initiated.</p><p>Using a dedicated branch to prepare releases makes it possible for one team to polish the current release while another team continues working on features for the next release. It also creates well-defined phases of development (e.g., it’s easy to say, “This week we’re preparing for version 4.0,” and to actually see it in the structure of the repository).</p><p>Making release branches is another straightforward branching operation. Like feature branches, release branches are based on the develop branch. A new release branch can be created using the following methods.</p><p>Without the git-flow extensions:</p><pre>git checkout develop<br>git checkout -b release/0.1.0</pre><p>When using the git-flow extensions:</p><pre>$ git flow release start 0.1.0<br>Switched to a new branch &#39;release/0.1.0&#39;</pre><p>Once the release is ready to ship, it will get merged it into master and develop, then the release branch will be deleted. It’s important to merge back into develop because critical updates may have been added to the release branch and they need to be accessible to new features. If your organization stresses code review, this would be an ideal place for a pull request.</p><p>To finish a release branch, use the following methods:</p><p>Without the git-flow extensions:</p><pre>git checkout develop<br>git merge release/0.1.0</pre><p>Or with the git-flow extension:</p><pre>git checkout master<br>git checkout merge release/0.1.0<br>git flow release finish &#39;0.1.0&#39;</pre><h3>Hotfix Branches</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t1sLb-xRLAIEJwpgiZUOWA.png" /></figure><p>Maintenance or “hotfix” branches are used to quickly patch production releases. Hotfix branches are a lot like release branches and feature branches except they’re based on master instead of develop. This is the only branch that should fork directly off of master. As soon as the fix is complete, it should be merged into both master and develop (or the current release branch), and master should be tagged with an updated version number.</p><p>Having a dedicated line of development for bug fixes lets your team address issues without interrupting the rest of the workflow or waiting for the next release cycle. You can think of maintenance branches as ad hoc release branches that work directly with master. A hotfix branch can be created using the following methods:</p><p>Without the git-flow extensions:</p><pre>git checkout master<br>git checkout -b hotfix_branch</pre><p>When using the git-flow extensions:</p><p>$ git flow hotfix start hotfix_branch</p><p>Similar to finishing a release branch, a hotfix branch gets merged into both master and develop.</p><pre>git checkout master<br>git merge hotfix_branch<br>git checkout develop<br>git merge hotfix_branch<br>git branch -D hotfix_branch</pre><p>$ git flow hotfix finish hotfix_branch</p><p>Example<br>A complete example demonstrating a Feature Branch Flow is as follows. Assuming we have a repo setup with a master branch.</p><pre>git checkout master<br>git checkout -b develop<br>git checkout -b feature_branch<br># work happens on feature branch<br>git checkout develop<br>git merge feature_branch<br>git checkout master<br>git merge develop<br>git branch -d feature_branch</pre><p>In addition to the feature and release flow, a hotfix example is as follows:</p><pre>git checkout master<br>git checkout -b hotfix_branch<br># work is done commits are added to the hotfix_branch<br>git checkout develop<br>git merge hotfix_branch<br>git checkout master<br>git merge hotfix_branch</pre><p>Summary<br>Here we discussed the Gitflow Workflow. Gitflow is one of many styles of Git workflows you and your team can utilize.</p><p>Some key takeaways to know about Gitflow are:</p><ul><li>The workflow is great for a release-based software workflow.</li><li>Gitflow offers a dedicated channel for hotfixes to production.</li></ul><p>The overall flow of Gitflow is:</p><ul><li>A develop branch is created from master</li><li>A release branch is created from develop</li><li>Feature branches are created from develop</li><li>When a feature is complete it is merged into the develop branch</li><li>When the release branch is done it is merged into develop and master</li><li>If an issue in master is detected a hotfix branch is created from master</li><li>Once the hotfix is complete it is merged to both develop and master<br>-All PRs must be against develop branch</li></ul><h3>Thanks!</h3><p>Refs:</p><ul><li><a href="https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow">Gitflow Workflow | Atlassian Git Tutorial</a></li><li><a href="https://nvie.com/posts/a-successful-git-branching-model/">A successful Git branching model</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a523360c053" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Start with Why: Creating a value proposition with the Golden Circle mode]]></title>
            <link>https://medium.com/@rafavinnce/start-with-why-creating-a-value-proposition-with-the-golden-circle-mode-5dbfa7b7efda?source=rss-6645ecc98480------2</link>
            <guid isPermaLink="false">https://medium.com/p/5dbfa7b7efda</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[successful-entrepreneurs]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[golden-circle]]></category>
            <category><![CDATA[intrepreneurship]]></category>
            <dc:creator><![CDATA[⌘⌥ Rafael Barbosa ]]></dc:creator>
            <pubDate>Tue, 22 Jan 2019 02:10:27 GMT</pubDate>
            <atom:updated>2019-01-22T02:25:08.286Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/853/1*8ZPQNMpWl_mt3ygLYCjSpw.png" /></figure><h3>Simon Sinek explains how to truly differentiate a brand when most fail</h3><p>Leadership expert Simon Sinek is perhaps best known for giving one of the most popular TED talks of all time, which you can view at the end of this post. Its focus is on how leaders can inspire cooperation, trust and change in a business based on his research into how the most successful organisations think, act and communicate.</p><p>I think that marketers will find most value in his Golden Circle model which helps give focus to how a business can stand out from similar competitors by communicating its differences. I was prompted to check it out after a recent workshop when discussing the importance of developing <a href="https://www.smartinsights.com/digital-marketing-strategy/online-value-proposition/">strong online value propositions</a> as part of a digital marketing strategy. One of the attendees working in B2B healthcare explained how they had used it with their agency to develop a more distinctive proposition for their brand amongst similar service providers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*UJc8YAoND4HC5r5LuVwZ3A.png" /></figure><p>Sinek is the author of several books on the topic of leadership. These include ‘Start With Why: How Great Leaders Inspire Everyone to Take Action’ which first popularised his now-famous Golden Circle concept. You can read more about this model and his background on <a href="https://www.startwithwhy.com/">Start With Why</a> .</p><p>Sinek’s Golden Circle idea is an attempt to explain why some people and organisations are particularly able to inspire others and differentiate themselves successfully. The neuroscience behind the Golden Circle idea is that humans respond best when messages communicate with those parts of their brain that control emotions, behaviour and decision-making.</p><h3>Why</h3><p>Sinek explains that ‘Why’ is probably the most important message that an organisation or individual can communicate as this is what inspires others to action. ‘Why’ is how you explain your purpose and the reason you exist and behave as you do. Sinek’s theory is that successfully communicating the passion behind the ‘Why’ is a way to communicate with the listener’s limbic brain. This is the part of our anatomy that processes feelings such as trust and loyalty — as well as decision-making.</p><p>Successfully articulating your ‘Why’ is a very impactful way to communicate with other humans, define your particular value proposition and inspire them to act. Sinek’s theory is that communicating ‘Why’ taps into the part of the listener’s brain that influences behavior. This is why the Golden Circle is considered such an influential theory of leadership. At organisational level, communicating your ‘Why’ is the basis of a strong value proposition that will differentiate your brand from others. He gives the example of Apple in video clip at the end of this article.</p><h3>How</h3><p>The organisation’s ‘How’ factors might include their strengths or values that they feel differentiate themselves from the competition. Sinek’s view is that ‘How’ messaging is also able to communicate with the limbic brain — the important part that governs behaviour and emotion. But his opinion is that organisations would do better to improve how they articulate their ‘Why’, in addition to ‘How’.</p><h3>What</h3><p>It’s fairly easy for any leader or organisation to articulate ‘What’ they do. This can be expressed as the products a company sells or the services it offers. For an individual it would be their job title. Sinek argues that ‘What’ messaging only engages with the neocortex — the part of our brain that’s rational. His argument is that this part of the brain is less of a driver of decision making than the limbic brain: the part that ‘Why’ and ‘How’ reaches better. Successful people and organisations express why they do what they do rather than focusing on what they do.</p><p>Some critics argue that Sinek’s model is actually just reflecting passion. Passionate leaders and passionate organisations express their commitment and enthusiasm authentically, and this is what inspires others rather than the manner in which they express themselves. Other critics argue that Sinek’s model implies humans don’t use their reason at all when making decisions, which is debatable.</p><p>I had the practical experience that this model really works by applying it as a template for all task requests in an Agile (kanban) team with an average of 20 people involved both internal and external. This was a mandatory requirement for any new feature / user history within the kanban framework where we had external and internal clients. As a result, we have solved some of the problems often addressed:</p><ul><li>Actual visibility of the needs passed by product owner and scrum master of the team.</li><li>Understanding of the team as a whole in any demand and possibility of multitasking, ensuring a better productivity.</li><li>Deliveries with better implementation in the final client.</li></ul><p>Find out more about Sinek’s Golden Circle theory by watching his talk at TED:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FIPYeCltXpxw%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DIPYeCltXpxw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FIPYeCltXpxw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b93a95ee92b21ab9eeba2c3f66b4f7ef/href">https://medium.com/media/b93a95ee92b21ab9eeba2c3f66b4f7ef/href</a></iframe><h4>Portuguese reference click here</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5dbfa7b7efda" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ITIL Series — Service Desk pattern]]></title>
            <link>https://medium.com/@rafavinnce/itil-series-service-desk-pattern-420372ace7c7?source=rss-6645ecc98480------2</link>
            <guid isPermaLink="false">https://medium.com/p/420372ace7c7</guid>
            <category><![CDATA[service-desk]]></category>
            <category><![CDATA[helpdesk]]></category>
            <category><![CDATA[itil]]></category>
            <dc:creator><![CDATA[⌘⌥ Rafael Barbosa ]]></dc:creator>
            <pubDate>Fri, 04 Jan 2019 12:41:47 GMT</pubDate>
            <atom:updated>2019-01-04T12:59:24.217Z</atom:updated>
            <content:encoded><![CDATA[<h3>ITIL Series — Service Desk pattern</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*08yj1RI5b4tGG1RInf6n1Q.png" /></figure><p><strong>What is ITIL?</strong></p><p><strong>Information Technology Infrastructure Library (ITIL) is a set of best practices for IT service management (ITSM) that focuses on aligning IT services with business needs. The right combination of technological automation and ITSM processes can help you towards achieving successful ITIL processes.</strong></p><p>ITIL is not a tool or a solution. ITIL is a framework of best practices that offers a means to an end. Implementing the ITIL framework can aid a business in aligning ITSM processes and help in measuring, governing, and reporting on support activities in accordance with business goals and globally accepted ITSM standards.</p><p>Every business needs to deal with IT incidents. Over time, they see that each incident has a life cycle with repetitive processes. Rather than simply logging and dealing with each of the problems, companies put ITIL into practice, and this includes the Help Desk area, which can benefit from this methodology to improve their services.</p><p>If we remember that the ultimate goal of companies is to serve customers well, and that the desire of every organization is to satisfy these customers through a controlled process, it is clear the importance of using a focused methodology to solve IT processes in a way more efficient.</p><p>In this post, we will show how ITIL works and list 5 methods that can be easily implemented in your Help Desk strategy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/555/0*C8nxXR73Nnd6wzNG" /></figure><h3>The Role of ITIL in Achieving ITSM Excellence</h3><p>The ITIL framework is a set of best practices that describes how IT resources should be organized to deliver business value, process documentation, and ITSM. ITIL best practices cover the following areas of ITSM, including:</p><ul><li>Incident management</li><li>Change management</li><li>Problem management</li><li>Service-level management</li><li>Continuity management</li><li>Configuration management</li><li>Release management</li><li>Capacity management</li><li>Financial management</li><li>Availability management</li><li>Security management</li><li>Help desk management</li><li>Knowledge management</li></ul><p>While there are expensive ITIL-certified solutions available, there is typically no guarantee that such a solution would help you attain superior support, productivity, and service delivery. What you need is an affordable IT help desk solution that is flexible and configurable to adjust your ITSM processes in accordance with ITIL standards. Without getting caught up with the terms “ITIL-certified” and “ITIL-ready”, look for easy-to-use and flexible help desk software that simplifies IT service management, and allows you to configure your ITSM workflows to suit your ITIL requirements.</p><p>Good practices in the ITIL portfolio are divided into five basic books, each with a different approach and being all complements to each other. Are they:</p><p>• Service Design;<br>• Service Strategy;<br>• Service Operation;<br>• Service Transition;<br>• Continual Service Improvement.</p><h3>Porque utilizar a metodologia ITIL?</h3><p>Sendo um parâmetro mundial de excelência para quem atua na área de TI, a grande maioria das empresas aderem às boas práticas do ITIL principalmente por se adaptar tanto para grandes organizações, como para pequenas empresas.</p><p>Ao padronizar procedimentos para a equipe de TI e definir as melhores práticas, a metodologia ITIL traz muitas formas de otimizar o trabalho, tais como:</p><p>• Fortalecimento da gestão de todos os ambientes da TI<br>• Melhoria contínua na satisfação dos usuários internos e clientes com os serviços da TI<br>• Diminuição dos custos operacionais de TI<br>• Orientação a processos com significativa redução nos tempos de execução e distribuição de serviços<br>• Diminuição gradativa da indisponibilidade dos recursos e sistemas de tecnologia da informação, causados por falhas no planejamento das mudanças e implantações em TI<br>• Reconhecimento da capacidade de gerenciamento pelos acionistas, colaboradores e clientes.</p><h3>SPOC (Single Point of Contact)</h3><p>O conceito do SPOC, ou Ponto Único de Contato, é uma das metodologias da Central de Serviços descrita pela ITIL. Um problema recorrente em diversas centrais de atendimento é o redirecionamento de setores. Em alguns casos, o agente não sabe ou não tem recursos para atender à dúvida do cliente. Então, ele o coloca em uma nova fila de espera para outro setor, o que aumenta a sua frustração. Em geral, isso só atrasa a resolução do problema.</p><p>Seguindo o SPOC, todo o <a href="https://conteudo.movidesk.com/atendimento-omnichannel/">trabalho de atendimento</a> deve ser realizado por apenas um agente, sem passagem de ligação. O atendente ficará responsável pela resolução do problema do cliente, evitando que ele repita as mesmas informações para diferentes pessoas, o que diminui o nível de frustração.</p><p>Caso o agente não saiba como solucionar a questão do cliente, ele mesmo deve buscar essa informação. Neste caso, o SPOC ajuda a melhorar a imagem do seu Help Desk junto aos clientes que ficarão mais satisfeitos.</p><h3>SLA (Service Level Agreements)</h3><p>Os <a href="https://conteudo.movidesk.com/5-passos-essenciais-para-definir-um-sla/">Acordos de Nível de Serviço</a> ditam a relação entre o Help Desk e seus clientes. Se um cliente faz ligações muito frequentes sobre uma mesma questão, então, a equipe terá menos tempo para lidar com o problema em si.</p><p>Pensando nisso, os livros de ITIL consideram que deve haver um tempo pré-estabelecido, onde o tempo de atendimento e resolução do problema possam ser previamente conhecidos.</p><p>Por exemplo, se após o contato o cliente sabe que seu problema será atendido em até 1 hora e solucionado em até 12 horas, ele não tem motivo para ligar antes que esse prazo expire. É uma maneira prática de otimizar o tempo da sua equipe e dar mais tranquilidade para quem foi atendido.</p><p>Claro que, se o Help Desk deixar ultrapassar esses prazos, as ligações serão inevitáveis. Por isso, essa metodologia só pode ser implementada com o auxílio de um <a href="https://conteudo.movidesk.com/facilitar-o-atendimento-clientes/">software que controle os responsáveis pelos chamados e os prazos de SLA.</a></p><h3>Base de conhecimento</h3><p>Este conceito, também proposto pela metodologia ITIL, tem como objetivo diminuir ainda mais o<a href="https://conteudo.movidesk.com/tempo-primeira-resposta-no-atendimento/">tempo de primeira resposta no atendimento</a> do seu Help Desk.</p><p>Muitos dos problemas apresentados no dia a dia, representam repetições de um mesmo cenário — e a melhor forma de resolver essas questões rapidamente é já ter uma solução pronta.</p><p>A <a href="https://conteudo.movidesk.com/base-de-conhecimento-itil/">base de conhecimento</a> é basicamente, um banco de dados que contém todas as informações sobre os erros mais comuns no negócio, porém já com uma solução pronta para ser aplicada. Dessa forma, possibilita aos agentes uma resolução rápida para determinados problemas, sem grandes dificuldades.</p><p>Toda vez que incidentes mais complexos são solucionados, os mesmos devem ser documentados na base de conhecimento para que todos os atendentes do Help Desk compartilhem essa informação. Assim, na próxima ocorrência do mesmo incidente, a solução será muito mais rápida se uma simples busca na base de conhecimento trouxer a solução.</p><h3>Níveis de suporte</h3><p>Esta metodologia consiste na separação da sua equipe de suporte em níveis, conforme o conhecimento de cada colaborador sobre o negócio.</p><p>Ou seja, o nível 1 é representado por profissionais que têm autonomia para lidar com problemas simples, e que possam identificar algo mais complexo, que deverá ser repassado aos agentes de nível 2. Os membros deste último detêm menos conhecimento que os membros de um nível 3 e assim por diante.</p><p>O objetivo principal dessa divisão é obter um aproveitamento melhor dos colaboradores da área de suporte e otimizar o investimento. Assim, agentes com um nível maior de conhecimento não terão seu tempo desperdiçado atendendo pequenos problemas, enquanto um cliente que busca uma solução complexa espera.</p><p>Selecionando os chamados a partir deste conceito, é possível ter um atendimento rápido para todo grau de incidente que ocorra, já que os incidentes mais simples serão respondidos rapidamente no nível 1 e os incidentes mais complexos terão maior atenção e dedicação dos especialistas dos níveis superiores.</p><h3>Melhoria contínua</h3><p>A melhoria contínua é uma prática comum já aplicada nos processos do mercado e que não podem ficar esquecida no Helpdesk. As etapas conhecidas como PDCA (Planejar, Executar, Verificar e Agir) são valiosas para que os processos da área se mantenham sempre atualizados, e para que evoluam constantemente. Veja como funciona:</p><p>• Planejar: identifique quais são os objetivos da TI e planeje seus processos de acordo<br>• Executar: execute os processos conforme planejado<br>• Verificar: analise os resultados da execução e veja se atingiu os objetivos da melhor maneira possível<br>• Agir: procure pontos que possam ser aprimorados nos processos e trabalhe para obter essas melhorias.</p><p>Assim como seus processos evoluem, a área de Help Desk deve evoluir também. Essa análise é o que permite que você saiba se a equipe está atendendo melhor hoje do que atendia no mês ou no ano passado.</p><p>A <strong>metodologia ITIL no Help Desk</strong> pode se mostrar uma grande aliada na gestão dos seus atendimentos. Agora que você entende um pouco melhor como funciona, pode considerar aplicá-lo em sua empresa.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=420372ace7c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Extend Angular DatePipe for Timezone Abbreviations Support]]></title>
            <link>https://medium.com/@rafavinnce/extend-angular-datepipe-for-timezone-abbreviations-support-d0b61b8956b1?source=rss-6645ecc98480------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0b61b8956b1</guid>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[angular-7]]></category>
            <category><![CDATA[datepipe]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[momentjs]]></category>
            <dc:creator><![CDATA[⌘⌥ Rafael Barbosa ]]></dc:creator>
            <pubDate>Tue, 06 Nov 2018 14:05:35 GMT</pubDate>
            <atom:updated>2018-11-06T14:11:39.500Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NhficfVkEffxGdzh6A7PZA.png" /><figcaption>PhpStorm IDE — momentDate Pipe</figcaption></figure><p>Recently I was researching what will be the best way to parse dates with user specific timezone on Angular V7.</p><p>But it seems time zones abbreviations is depreciated and you can only use a timezone parameter with DatePipe pipe but it’s really just a time zone offset number which is prone to incorrect parsing because of the daylight saving.</p><p>(e.g. there can be different offset number for same time zone depending on the time of year)</p><p>So I’m sharing a custom pipe that uses moment and moment timezone to extend DatePipe with the option to support also timezones abbreviations (“America/Sao_Paulo” etc)</p><p>Hope you find it helpful, and enjoy proper time zone date formatting :)</p><pre>import { Pipe, PipeTransform } from &#39;@angular/core&#39;;<br>import { DatePipe } from &#39;@angular/common&#39;;<br>import * as moment from &#39;moment-timezone&#39;;</pre><pre>/**<br>* A moment timezone pipe to support parsing based on time zone abbreviations<br>* covers all cases of offset variation due to daylight saving.<br>*<br>* Same API as DatePipe with additional timezone abbreviation support<br>* Official date pipe dropped support for abbreviations names from<br>Angular V5<br>*/</pre><pre>@Pipe({<br>  name: &#39;momentDate&#39;<br>})</pre><pre>export class MomentDatePipe extends DatePipe implements PipeTransform {</pre><pre>  transform(<br>    value: string | Date,<br>    format: string = &#39;mediumDate&#39;,<br>    timezone: string = &#39;Europe/Prague&#39;<br>  ): string {<br>    const timezoneOffset = moment(value).tz(timezone).format(&#39;Z&#39;);<br>    return super.transform(value, format, timezoneOffset);<br>  }<br>}</pre><p>Usage:</p><pre>&lt;td mat-cell <em>*matCellDef</em>=&quot;<strong>let </strong>element&quot;&gt;{{element.date | momentDate: &#39;yyyy-MM-dd HH:mm:ss&#39;}}&lt;/td&gt;</pre><pre>&lt;span&gt;{{message.datetime | momentDate: &#39;dddd, MMMM Do YYYY, h:mm:ss a&#39;}}&lt;/span&gt;</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0b61b8956b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[iTerm2 + zsh + oh-my-zsh + Material Design The Most Power Full Terminal on macOS]]></title>
            <link>https://medium.com/@rafavinnce/iterm2-zsh-oh-my-zsh-material-design-the-most-power-full-terminal-on-macos-332b1ee364a5?source=rss-6645ecc98480------2</link>
            <guid isPermaLink="false">https://medium.com/p/332b1ee364a5</guid>
            <category><![CDATA[shell]]></category>
            <category><![CDATA[mac]]></category>
            <category><![CDATA[iterm2]]></category>
            <category><![CDATA[oh-my-zsh]]></category>
            <dc:creator><![CDATA[⌘⌥ Rafael Barbosa ]]></dc:creator>
            <pubDate>Fri, 19 Oct 2018 12:25:35 GMT</pubDate>
            <atom:updated>2018-10-19T12:25:35.619Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wBDjXkEtw_vCchmm.jpg" /></figure><h3>Install Homebrew</h3><p>Open terminal and paste.</p><pre>$ /usr/bin/ruby -e “$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)&quot;</pre><h3>Install iterm2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*MWNOMJTSQnm7X5sjXYdGtQ.png" /></figure><p><a href="https://www.iterm2.com/img/logo2x.jpg">https://www.iterm2.com/img/logo2x.jpg</a></p><h3>What is iTerm2</h3><p>iTerm2 is a replacement for Terminal and the successor to iTerm that works on Macs with macOS 10.10 or newer. iTerm2 contains a number of features you will find extremely useful as a developer or power user of macOS.</p><h3>Quick Commands</h3><p>Why we must replace default macOS Terminal to iTerm2 ?</p><p><a href="https://www.iterm2.com/features.html">https://www.iterm2.com/features.html</a></p><ol><li>Go to download page <a href="https://www.iterm2.com/downloads.html">https://www.iterm2.com/downloads.html</a></li><li>After downloaded, drag and drop file into our Application folder.</li></ol><p>Or if you just type (require homebrew installed)</p><pre>$ brew cask install iterm2</pre><h3>Install oh-my-zsh</h3><p>The oh-my-zsh will be replace default terminal with zsh automatically when you installed.</p><p>Open terminal and paste.</p><pre>$ sh -c “$(curl -fsSL https://raw.githubusercontent.com/robbyrussell/oh-my-zsh/master/tools/install.sh)”</pre><h3>Set ZSH default Mac terminal</h3><ul><li>Open Apple &gt; System Preferences &gt; User&amp; Groups</li><li>Input Admin Password to unlock settings Right Click an our User in Advanced Options</li><li>In Login shall choose /bin/zsh and click OK</li><li>Restart Mac and open iterm2 again.</li></ul><h3>Decorate Our iTerm2 With Material Design Colours</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*skO2cJD-ol-T9J-G7CG6Rg.png" /></figure><p><a href="https://github.com/MartinSeeler/iterm2-material-design/blob/master/img/screen-mock-1.jpg">https://github.com/MartinSeeler/iterm2-material-design/blob/master/img/screen-mock-1.jpg</a></p><p>1. Open terminal and paste.</p><pre>$ cd Downloads<br>$ curl -O <a href="https://raw.githubusercontent.com/MartinSeeler/iterm2-material-design/master/material-design-colors.itermcolors">https://raw.githubusercontent.com/MartinSeeler/iterm2-material-design/master/material-design-colors.itermcolors</a></pre><p>2. Open iTerm2 that we already downloaded at the first section</p><p>3. Go to <em>iTerm2 &gt; Preferences &gt; Profiles &gt; Colors Tab</em></p><p>4. Click <em>Color Presets…</em> at the bottom right</p><p>5. Click <em>Import…</em></p><p>6. Select the material-design-colors.itermcolors file</p><p>7. Select the <em>material-design-colors</em> from <em>Load Presets…</em></p><p><em>Color File:</em></p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br>&lt;!DOCTYPE plist PUBLIC &quot;-//Apple//DTD PLIST 1.0//EN&quot; &quot;http://www.apple.com/DTDs/PropertyList-1.0.dtd&quot;&gt;<br>&lt;plist version=&quot;1.0&quot;&gt;<br>&lt;dict&gt;<br>	&lt;key&gt;Ansi 0 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.19215686619281769&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.18431372940540314&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.17647059261798859&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Ansi 1 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.31764706969261169&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.31764706969261169&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Ansi 10 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.79215681552886963&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.96470588445663452&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.7254902720451355&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Ansi 11 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.49803918600082397&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.89803916215896606&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Ansi 12 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.99607843160629272&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.84313726425170898&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.50196081399917603&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Ansi 13 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.67058825492858887&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.50196081399917603&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Ansi 14 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.92158126831054688&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.9924500584602356&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.65526837110519409&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Ansi 15 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.99999994039535522&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.99999994039535522&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.9999966025352478&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Ansi 2 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.75294119119644165&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.7450980544090271&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.73725491762161255&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Ansi 3 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.25098034739494324&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.84313732385635376&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Ansi 4 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.50196081399917603&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.50196081399917603&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.49803921580314636&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Ansi 5 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.50588232278823853&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.25098031759262085&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Ansi 6 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.85492348670959473&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.98838895559310913&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.39322873950004578&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Ansi 7 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.34509804844856262&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.34117648005485535&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.33725491166114807&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Ansi 8 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.77254897356033325&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.7450980544090271&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.69019621610641479&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Ansi 9 Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.50196081399917603&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.541176438331604&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Background Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.13725490868091583&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.12941177189350128&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.12156862765550613&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Badge Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;0.5&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.0&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.1491314172744751&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Bold Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.92941176891326904&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.93333333730697632&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.92941176891326904&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Cursor Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.5215686559677124&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.51372551918029785&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.5058823823928833&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Cursor Guide Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;0.25&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.9268307089805603&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.70213186740875244&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Cursor Text Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.0&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.0&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.0&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Foreground Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.94117647409439087&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.93333333730697632&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.92549020051956177&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Link Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.73333334922790527&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.35686275362968445&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.0&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Selected Text Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.94117647409439087&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.93333333730697632&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.92549020051956177&lt;/real&gt;<br>	&lt;/dict&gt;<br>	&lt;key&gt;Selection Color&lt;/key&gt;<br>	&lt;dict&gt;<br>		&lt;key&gt;Alpha Component&lt;/key&gt;<br>		&lt;real&gt;1&lt;/real&gt;<br>		&lt;key&gt;Blue Component&lt;/key&gt;<br>		&lt;real&gt;0.54509806632995605&lt;/real&gt;<br>		&lt;key&gt;Color Space&lt;/key&gt;<br>		&lt;string&gt;sRGB&lt;/string&gt;<br>		&lt;key&gt;Green Component&lt;/key&gt;<br>		&lt;real&gt;0.48627451062202454&lt;/real&gt;<br>		&lt;key&gt;Red Component&lt;/key&gt;<br>		&lt;real&gt;0.37647059559822083&lt;/real&gt;<br>	&lt;/dict&gt;<br>&lt;/dict&gt;<br>&lt;/plist&gt;</pre><h3>Install PowerLevel9k!</h3><p>Then it’s time to install PowerLevel9k using the OMZ way!</p><pre>$ git clone https://github.com/bhilburn/powerlevel9k.git ~/.oh-my-zsh/custom/themes/powerlevel9k</pre><p><a href="https://github.com/bhilburn/powerlevel9k">PowerLevel9k on Github</a></p><p>Then we set it on $HOME/.zshrc. Open a text editor and set:</p><p>ZSH_THEME=&quot;powerlevel9k/powerlevel9k&quot;</p><h3>Install FontForge</h3><pre>$ brew install fontforge</pre><h3>Install Nerd Fonts! Install Script</h3><p>Install patched font Mesmo LG S DZ Regular Nerd Font Complete ttf</p><h3>Install Neofetch</h3><p>A command-line system information tool written in bash 3.2+</p><pre>$ brew install neofetch</pre><h3>Show wireless in terminal</h3><p>To get the wireless signal monitoring to work, you need to create a symlink to your airport utility (MacOS):</p><pre>$ sudo ln -s /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport /usr/local/bin/airport</pre><h3>Configure iterm2 profile</h3><ul><li>Open iterm2 &gt; Preferences &gt; Profiles &gt; + &gt; Create your profile &gt; Colors Presets &gt; Import.</li></ul><h3>Import my colors preset</h3><p>&lt;link here&gt;</p><ul><li>Open iterm2 &gt; Preferences &gt; Profiles &gt; Text &gt; Change Font &gt; 14pt Mesmo LG S DZ Regular Nerd Font Complete ttf</li><li>Character spacing: Horizontal: 100 // Vertical: 126</li></ul><h3>Import power9k configs</h3><ul><li>Set ~/.zshrc and put</li></ul><pre>POWERLEVEL9K_MODE=&#39;nerdfont-complete&#39;</pre><pre># Please only use this battery segment if you have material icons in your nerd font (or font)</pre><pre># Otherwise, use the font awesome one in &quot;User Segments&quot;</pre><pre>prompt_zsh_battery_level() {</pre><pre>local percentage1=`pmset -g ps  |  sed -n &#39;s/.*[[:blank:]]+*\(.*%\).*/\1/p&#39;`</pre><pre>local percentage=`echo &quot;${percentage1//\%}&quot;`</pre><pre>local color=&#39;%F{red}&#39;</pre><pre>local symbol=&quot;\uf00d&quot;</pre><pre>pmset -g ps | grep &quot;discharging&quot; &gt; /dev/null</pre><pre>if [ $? -eq 0 ]; then</pre><pre>local charging=&quot;false&quot;;</pre><pre>else</pre><pre>local charging=&quot;true&quot;;</pre><pre>fi</pre><pre>if [ $percentage -le 20 ]</pre><pre>then symbol=&#39;\uf579&#39; ; color=&#39;%F{red}&#39; ;</pre><pre>#10%</pre><pre>elif [ $percentage -gt 19 ] &amp;&amp; [ $percentage -le 30 ]</pre><pre>then symbol=&quot;\uf57a&quot; ; color=&#39;%F{red}&#39; ;</pre><pre>#20%</pre><pre>elif [ $percentage -gt 29 ] &amp;&amp; [ $percentage -le 40 ]</pre><pre>then symbol=&quot;\uf57b&quot; ; color=&#39;%F{yellow}&#39; ;</pre><pre>#35%</pre><pre>elif [ $percentage -gt 39 ] &amp;&amp; [ $percentage -le 50 ]</pre><pre>then symbol=&quot;\uf57c&quot; ; color=&#39;%F{yellow}&#39; ;</pre><pre>#45%</pre><pre>elif [ $percentage -gt 49 ] &amp;&amp; [ $percentage -le 60 ]</pre><pre>then symbol=&quot;\uf57d&quot; ; color=&#39;%F{blue}&#39; ;</pre><pre>#55%</pre><pre>elif [ $percentage -gt 59 ] &amp;&amp; [ $percentage -le 70 ]</pre><pre>then symbol=&quot;\uf57e&quot; ; color=&#39;%F{blue}&#39; ;</pre><pre>#65%</pre><pre>elif [ $percentage -gt 69 ] &amp;&amp; [ $percentage -le 80 ]</pre><pre>then symbol=&quot;\uf57f&quot; ; color=&#39;%F{blue}&#39; ;</pre><pre>#75%</pre><pre>elif [ $percentage -gt 79 ] &amp;&amp; [ $percentage -le 90 ]</pre><pre>then symbol=&quot;\uf580&quot; ; color=&#39;%F{blue}’ ;</pre><pre>#85%</pre><pre>elif [ $percentage -gt 89 ] &amp;&amp; [ $percentage -le 99 ]</pre><pre>then symbol=&quot;\uf581&quot; ; color=&#39;%F{blue}&#39; ;</pre><pre>#85%</pre><pre>elif [ $percentage -gt 98 ]</pre><pre>then symbol=&quot;\uf578&quot; ; color=&#39;%F{green}&#39; ;</pre><pre>#100%</pre><pre>fi</pre><pre>if [ $charging = &quot;true&quot; ];</pre><pre>then color=&#39;%F{green}&#39;; if [ $percentage -gt 98 ]; then symbol=&#39;\uf584&#39;; fi</pre><pre>fi</pre><pre>echo -n &quot;%{$color%}$symbol&quot; ;</pre><pre>}</pre><pre>zsh_internet_signal(){</pre><pre>local color</pre><pre>local symbol=&quot;\uf7ba&quot;</pre><pre>if ifconfig en0 | grep inactive &amp;&gt; /dev/null; then</pre><pre>color=&quot;%F{red}&quot;</pre><pre>else</pre><pre>color=&quot;%F{blue}&quot;</pre><pre>fi</pre><pre>echo -n &quot;%{$color%}$symbol &quot;</pre><pre>}</pre><pre>POWERLEVEL9K_PROMPT_ON_NEWLINE=false<br>POWERLEVEL9K_PROMPT_ADD_NEWLINE=true<br>POWERLEVEL9K_RPROMPT_ON_NEWLINE=false<br>POWERLEVEL9K_SHORTEN_DIR_LENGTH=2<br>POWERLEVEL9K_SHORTEN_STRATEGY=&quot;truncate_beginning&quot;<br>POWERLEVEL9K_RVM_BACKGROUND=&quot;black&quot;<br>POWERLEVEL9K_RVM_FOREGROUND=&quot;249&quot;<br>POWERLEVEL9K_RVM_VISUAL_IDENTIFIER_COLOR=&quot;red&quot;<br>POWERLEVEL9K_TIME_BACKGROUND=&quot;black&quot;<br>POWERLEVEL9K_TIME_FOREGROUND=&quot;249&quot;<br>POWERLEVEL9K_TIME_FORMAT=&quot;\UF43A %D{%I:%M  \UF133  %m.%d.%y}&quot;<br>POWERLEVEL9K_RVM_BACKGROUND=&quot;black&quot;<br>POWERLEVEL9K_RVM_FOREGROUND=&quot;249&quot;<br>POWERLEVEL9K_RVM_VISUAL_IDENTIFIER_COLOR=&quot;red&quot;<br>POWERLEVEL9K_STATUS_VERBOSE=false<br>POWERLEVEL9K_VCS_CLEAN_FOREGROUND=&#39;black&#39;<br>POWERLEVEL9K_VCS_CLEAN_BACKGROUND=&#39;green&#39;<br>POWERLEVEL9K_VCS_UNTRACKED_FOREGROUND=&#39;black&#39;<br>POWERLEVEL9K_VCS_UNTRACKED_BACKGROUND=&#39;yellow&#39;<br>POWERLEVEL9K_VCS_MODIFIED_FOREGROUND=&#39;white&#39;<br>POWERLEVEL9K_VCS_MODIFIED_BACKGROUND=&#39;black&#39;<br>POWERLEVEL9K_COMMAND_EXECUTION_TIME_BACKGROUND=&#39;black&#39;<br>POWERLEVEL9K_COMMAND_EXECUTION_TIME_FOREGROUND=&#39;blue&#39;<br>POWERLEVEL9K_FOLDER_ICON=&#39;&#39;<br>POWERLEVEL9K_STATUS_OK_IN_NON_VERBOSE=true<br>POWERLEVEL9K_STATUS_VERBOSE=false<br>POWERLEVEL9K_COMMAND_EXECUTION_TIME_THRESHOLD=0<br>POWERLEVEL9K_VCS_UNTRACKED_ICON=&#39;\u25CF&#39;<br>POWERLEVEL9K_VCS_UNSTAGED_ICON=&#39;\u00b1&#39;<br>POWERLEVEL9K_VCS_INCOMING_CHANGES_ICON=&#39;\u2193&#39;<br>POWERLEVEL9K_VCS_OUTGOING_CHANGES_ICON=&#39;\u2191&#39;<br>POWERLEVEL9K_VCS_COMMIT_ICON=&quot;\uf417&quot;<br>POWERLEVEL9K_MULTILINE_FIRST_PROMPT_PREFIX=&quot;%F{blue}\u256D\u2500%f&quot;<br>POWERLEVEL9K_MULTILINE_LAST_PROMPT_PREFIX=&quot;%F{blue}\u2570\uf460%f &quot;<br>POWERLEVEL9K_CUSTOM_BATTERY_STATUS=&quot;prompt_zsh_battery_level&quot;<br># POWERLEVEL9K_LEFT_PROMPT_ELEMENTS=(context os_icon custom_internet_signal custom_battery_status_joined ssh root_indicator dir dir_writable vcs)<br>POWERLEVEL9K_LEFT_PROMPT_ELEMENTS=(os_icon custom_internet_signal custom_battery_status_joined ssh root_indicator dir dir_writable vcs)<br>POWERLEVEL9K_RIGHT_PROMPT_ELEMENTS=(command_execution_time  status  time)<br>HIST_STAMPS=&quot;mm/dd/yyyy&quot;<br>DISABLE_UPDATE_PROMPT=trueReload ZSH Config</pre><p>Run:</p><pre>$ source ~/.zshrc</pre><p>Voa la!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1010/1*56xYXbf-xh-hQW5iYaNYEQ.png" /></figure><p>Ref: <a href="https://github.com/bhilburn/powerlevel9k#installation">https://github.com/bhilburn/powerlevel9k#installation</a></p><p><a href="http://bluejamesbond.github.io/CharacterMap/">http://bluejamesbond.github.io/CharacterMap/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=332b1ee364a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Low-fidelity vs. high-fidelity prototyping]]></title>
            <link>https://medium.com/@rafavinnce/low-fidelity-vs-high-fidelity-prototyping-1bc262cad8d9?source=rss-6645ecc98480------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bc262cad8d9</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[prototype]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[⌘⌥ Rafael Barbosa ]]></dc:creator>
            <pubDate>Mon, 01 Oct 2018 15:42:44 GMT</pubDate>
            <atom:updated>2018-10-01T15:48:16.324Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_eRsmvyvEfx2z3DPD0oV9g.jpeg" /></figure><p>Design fidelity refers to the level of detail and functionality included in a prototype. Fidelity can vary in interactivity, visuals, content and commands, and other areas.</p><p>When you’re getting ready to begin prototyping, you’ll need to decide how closely you want it to match the end result, which will also dictate how much time and energy you need to put into it.</p><p><strong>Low-fidelity prototypes</strong>, for example, are simple and low-tech concepts. All you need to get started is a pen and paper. The goal is to turn your ideas into testable artifacts that you can then use to collect and analyze feedback in the early stages.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhOJyJ2lZkPs%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhOJyJ2lZkPs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhOJyJ2lZkPs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b92bc2721f3ab6f00d65fc4327953b91/href">https://medium.com/media/b92bc2721f3ab6f00d65fc4327953b91/href</a></iframe><p>On the other hand, <strong>high-fidelity prototypes</strong> are highly functional and interactive. They are very close to the final product, with most of the necessary design assets and components developed and integrated. Hi-fi prototypes are often used in the later stages to test usability and identify issues in the workflow.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FKsk2P14OXsQ%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DKsk2P14OXsQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FKsk2P14OXsQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/2f9833c12d5bb815e46c795b4a2a90c3/href">https://medium.com/media/2f9833c12d5bb815e46c795b4a2a90c3/href</a></iframe><p>Which one is better? That depends.</p><h3>Benefits of low-fi prototyping</h3><p><strong>Focus on design and concepts:</strong> Without the pressure of making every page linked, clickable, and interactive, you can worry less about the more technical parts of prototyping and spend more energy on ideation.</p><p><strong>Real-time iteration: </strong>Let’s say you’re gathering customer feedback on your sketched prototype. During this test, you can quickly redo part of the design based on customer comments in real time, in just a few minutes.</p><p><strong>Accessible to everyone:</strong> Everyone can doodle. With low-fidelity prototyping, even non-designers can participate in the <a href="https://invisionapp.com/inside-design/6-ways-speed-improve-product-design-process/">design process</a> and think through content, menus, and flow.</p><h3>Benefits of high-fidelity prototyping</h3><p><strong>More familiar to users:</strong> High-fidelity prototypes look like live software to customers, meaning participants would be more likely to behave naturally during <a href="https://invisionapp.com/inside-design/conduct-design-research/">testing</a>.</p><p><strong>Pinpoint specific components to test:</strong> You can dive deep into a single component (like flow, visuals, engagement, or navigation) during user testing. This allows you to get detailed feedback on certain elements of the design that would not be possible with pen and paper.</p><p><strong>Further reading: </strong><a href="https://invisionapp.com/inside-design/prototyping-rapid-prototyping/"><strong>Why all prototyping is rapid prototyping</strong></a></p><p><strong>More presentable to stakeholders:</strong> Clients and team members will get a clear idea of how the product will look and work before it ever goes live. You can also set clear expectations with developers in the early stages on how much time will be needed to build your prototype and have a finished product.</p><h3>Identify the right fidelity for your prototype</h3><p>Prototyping at the wrong fidelity is one of the <a href="https://invisionapp.com/inside-design/conduct-design-research/">top prototyping mistakes</a>. Unfortunately, there isn’t a one-size-fits-all solution. Instead, you should evaluate it based on each individual scenario.</p><p>For speed and flexibility, low-fidelity prototypes may be best. If you’re already working off customer feedback and want to gather more data on specific areas, you may choose high-fidelity prototypes.</p><p>The most important thing to remember: Just like you’d never listen to the same rock ’n’ roll song for every occasion, you shouldn’t default to the same level of fidelity when prototyping.</p><h3>Keep reading about prototyping</h3><ul><li><a href="https://invisionapp.com/inside-design/design-prototyping-play/">Prototyping and play: Innovation through playful interaction</a></li><li><a href="https://invisionapp.com/inside-design/designer-prototyping/">How one designer prototyped prototyping</a></li><li><a href="https://invisionapp.com/inside-design/free-wireframe-kit-form/">Download Form, a free wireframe kit</a></li><li><a href="http://startupsorocaba.com/startup-sorocaba-o-que-sao-prototipos-de-baixa-e-alta-fidelidade/">http://startupsorocaba.com/startup-sorocaba-o-que-sao-prototipos-de-baixa-e-alta-fidelidade/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bc262cad8d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>