<?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 Oleksandr Nikolaichuk 🇺🇦 on Medium]]></title>
        <description><![CDATA[Stories by Oleksandr Nikolaichuk 🇺🇦 on Medium]]></description>
        <link>https://medium.com/@almostengineer?source=rss-22a0f86b6168------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FdQ6BNksTDP_uLcCk-t8fQ.png</url>
            <title>Stories by Oleksandr Nikolaichuk 🇺🇦 on Medium</title>
            <link>https://medium.com/@almostengineer?source=rss-22a0f86b6168------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:05:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@almostengineer/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[From procedural code to decorator pattern]]></title>
            <link>https://almostengineer.medium.com/from-procedural-code-to-decorator-pattern-e0a71959e71e?source=rss-22a0f86b6168------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0a71959e71e</guid>
            <category><![CDATA[decorators]]></category>
            <category><![CDATA[procedural-programming]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[design-patterns]]></category>
            <dc:creator><![CDATA[Oleksandr Nikolaichuk ]]></dc:creator>
            <pubDate>Sun, 11 Dec 2022 17:53:08 GMT</pubDate>
            <atom:updated>2022-12-13T07:41:26.654Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6gbcdXr3QrAl0daP690GfQ.jpeg" /></figure><p>Motivation: Show how design patterns can improve our spaghetti procedural code and resolve separation of concerns problems of procedural code</p><p>Real-example of decorators solve problems and help to maintain and extend existing code and write new without changing the old one</p><p>We started the project from simple screens without any authorization flow as a typical start-up. For HTTP requests we decided to write a simple manager instead of a huge Alamofire/Moya (or similar) ready to use 3rd party library. (<strong>CODE 1</strong>)</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7e0c4bb61747b8cfe2ac6ecd42971916/href">https://medium.com/media/7e0c4bb61747b8cfe2ac6ecd42971916/href</a></iframe><p>After the successful MVP, we deiced to extend our iOS team, and write more modules, flows, and features. And first of all, we needed the auth flow. And it means that our code should be modified and extended. (<strong>CODE 2</strong>)</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/49b2f5fffa2f63fd9b2b14e13a1202d9/href">https://medium.com/media/49b2f5fffa2f63fd9b2b14e13a1202d9/href</a></iframe><p>The code above was extended and takes more responsibilities. This leads to more bugs because this one class works with 3 different responsibilities and you can easily break something while fixing some part of this code. It means that this code has more than one axis of change</p><p>But it is not the end, and after the refresh token process, we needed the third logic for our HTTP manager — a permanent block of users. And the new code looks like <strong>CODE 3</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4fa63488746e6355a022efc15a85578d/href">https://medium.com/media/4fa63488746e6355a022efc15a85578d/href</a></iframe><p>Right now, after 3rd iteration of changes, we can see that our code is a mess. It has a lot of responsibilities, high complexity, and is not easy to read form. In the real project, we had 5, but even with 3, we see that it gets harder and harder to understand and maintain this code. Also, it is hard to remove some of the logic, for example, block list logic, or rollback to just simple <em>httpClient</em> without any auth logic</p><h3>How to solve this?</h3><p>When the problem is clarified, we can try to solve this with design patterns. Our problem is to intercept the request and do the custom work before or after the actual request to the server in the general way our problem is to extend existing code instead of changing it. The decorator pattern is brilliant for problems like this. At first, we need to define the main protocol for work with our HTTP client <strong>CODE 4</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0bb918aabe528e8af64c261be7dc30d9/href">https://medium.com/media/0bb918aabe528e8af64c261be7dc30d9/href</a></iframe><p>Our simple HTTP client that has only 1 responsibility to send a request and deliver a response will look like <strong>CODE 5</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/aa707682e37c42d4de5643105142b32c/href">https://medium.com/media/aa707682e37c42d4de5643105142b32c/href</a></iframe><p>Now we need to add refresh token logic and this is the urgent moment when the decorator pattern solves the main problem of extending the existing code. We should create a new class that conforms to the <em>httpClient</em> protocol and holds the reference on another <em>httpClient</em> object. The main here is that we should use protocol, not the actual type of our <em>httpClient</em>. Our new class can only intercept the request, check token expiration, refresh and ask decorate how to work with the request after. This Decorator knows only how to deal with refreshing logic and saving credentials. No other responibilietes from not realated areas (<strong>CODE 6</strong>)</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/38c6ab08469eb16fe15d7cfd806ef94d/href">https://medium.com/media/38c6ab08469eb16fe15d7cfd806ef94d/href</a></iframe><p>The third part of <em>httpClient</em> is the blocking list. Our client should check if the current account is permanently blocked and returns a specific error without any network call. The plan is the same, new decorator which will be responsible only for blocking list logic <strong>CODE 7</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/87732ba3895c1339c59b51e33adfff6a/href">https://medium.com/media/87732ba3895c1339c59b51e33adfff6a/href</a></iframe><p>We finished creating our decorators and I want to add one bonus requirement. For our analytics, we need to measure the actual requests time it takes to get a response from the server (<strong>CODE 8</strong>)</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8d67e2f0b923adfae0e23bd01e0160f8/href">https://medium.com/media/8d67e2f0b923adfae0e23bd01e0160f8/href</a></iframe><p>How to work with this bunch of objects?</p><p>We need a place where all of these objects will be combined together. The factory method is a great pattern that helps to hide the complexity of the creation of the objects graph and add a simple point to use this object graph over the application without forming this object graph each time when you need this (<strong>CODE 9</strong>)</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/40f692bbb23b8cd6ebad30d04c7bd93a/href">https://medium.com/media/40f692bbb23b8cd6ebad30d04c7bd93a/href</a></iframe><p>These decorators have their own responsibilities and can be easily removed, tested, or changed. It is super easy to find a bug only in token refreshing logic or in blocking list logic. For more clarification — the real work of this code is next. If the load method will be called from the client.</p><p>All these objects already conform to <em>HTTPClientProtocol</em> that’s why the client controller also can depend on this protocol. All of these decisions lead to more testable code. Because this client with the dependency injections can be replaced with the spy of stub <em>httpClient</em> in the automation testing process (<strong>CODE 10</strong>)</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4bc901712f47e2828e4273a4b6ac4214/href">https://medium.com/media/4bc901712f47e2828e4273a4b6ac4214/href</a></iframe><p>When the load method will be called, then our objects graph will work in a next way</p><p>1. <em>PermanentBlockHTTPClientDecorator</em> checks if users are already blocked or now and send a load command to the next decorator</p><p>2. <em>RefreshCredentialsHTTPClientDecorator</em> as the next decorator checks if the token is expired, refreshes it if needed, and sends a load command to the next decorator</p><p>3.<em>HTTPClientLoggerDecorator</em> as the next decorator starts to measure the real network request and send a load command to the next decorator</p><p>4. <em>HTTPClient</em> as the last main root object makes a simple network request and returns the response to the previous decorator</p><p>5. <em>HTTPClientLoggerDecorator</em> as the previous decorator ends the measure of network call, writes the results to some storage and returns a response to the previous decorator</p><p>6. <em>RefreshCredentialsHTTPClientDecorator</em> and <em>PermanentBlockHTTPClientDecorator</em> as previous decorators just return the response to the controller</p><h3>Advantages</h3><p>1. Single responsibility and dependency inversion principles are not violated. Decorators are separate objects which have their own responsibilities and can leave even in other modules/frameworks because their dependency is inverted and they depend on protocol and the code (our view controller) depends on protocol, not on actual objects. Also, these objects can be written by different programmers in parallel. All that you need is to define <em>HTTPClientProtocol</em></p><p>2. With the factory method it is easy to define a single object graph of a huge list of simple objects with some single responsibilities like token refreshing, logging, blocking list, and reusing it across the application. You can also build combine these objects in different ways for different environments. For example for production, you don’t want to use <em>HTTPClientLoggerDecorator</em> because it will lead to performance issues. It is easy to define once in the factory method which objects and how should be combined for different environments</p><p>3. Automated testing is a super powerful tool for high-quality development. Such principles as dependency inversion, single responsibility, and dependency injection will lead to easy-to-test software because all of their parts can be spied, stubbed, and mocked in the testing process</p><h3>Disadvantages</h3><p>The main disadvantage here is testing. All of these objects should be tested in good projects because this is a production code written by us. Even clean and maintainable code should be tested and it takes time.</p><p>In the next post “From Decorator design pattern to Universal abstraction” I will talk about Universal abstraction and how to use Combine in a functional programming paradigm instead of a decorator design pattern. It solves the main disadvantage of the decorator pattern with lack of testing and looks more functional which is more consistent with SwiftUI frameworks and declarative way of thinking</p><p><a href="https://www.linkedin.com/in/alexander-nikolaychuk-40727812b">LinkedIn</a> <a href="https://twitter.com/alexksnikol">Twitter</a> <a href="https://alexalmostengineer.co.ua/software-development-blog-alex_almost_engineer/">Original Blog</a> <a href="https://github.com/alexnikol">Github</a> <a href="https://www.hackerrank.com/alexEngineer">HackerRank</a></p><p>Photo by <a href="https://unsplash.com/@lastnameeaster?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">La-Rel Easter</a> on <a href="https://unsplash.com/s/photos/blocks?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bVw6mZlxU_4Oa1QVz7eUpQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0a71959e71e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[iOS CI/CD workflow with GitHub Actions, tests, deployment to Appstore, Codeclimate integration]]></title>
            <link>https://almostengineer.medium.com/ios-ci-cd-workflow-with-github-actions-tests-deployment-to-appstore-codeclimate-integration-6f2954015e39?source=rss-22a0f86b6168------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f2954015e39</guid>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[github-actions]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[code-climate]]></category>
            <dc:creator><![CDATA[Oleksandr Nikolaichuk ]]></dc:creator>
            <pubDate>Thu, 17 Nov 2022 13:22:13 GMT</pubDate>
            <atom:updated>2022-12-11T15:46:43.848Z</atom:updated>
            <content:encoded><![CDATA[<p>Real workflow with GitHub Actions, test coverage base from Codeclimate, Appstore deployment</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QbKuHRR5cUfnSYuwUT_tvw.jpeg" /></figure><p><strong>This post covers:</strong></p><ul><li>Add GitHub Actions workflows to your application</li><li>Build and test iOS applications, showing the results of tests in a convenient way on the GitHub Actions report page</li><li>Sending code coverage of tests to Codeclimate, Cobertura, Slather, and Codeclimate status badges</li><li>Deploy to Appstore, work with the sign-in certificate, and provision file</li><li>Workflow example on a real project</li></ul><h3>Motivation</h3><p>The free setup which Github Actions for tests, build, deployment to Appstore, and Codeclimate</p><p>GitHub Actions is a freemium service which build-in and available for any GitHub repository. It will be free for 2,000 minutes per month. Detailed billing details you can find <a href="https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions">here</a>.</p><p>Codeclimate free tool for open-source projects and this is a great tool for finding some duplications, code smells, and other mess places in your project. Of course, Codeclimate like any static analyzer can’t understand specific composition problems or polymorphic similarities of code, but it can help you to find these places, and you can decide if this place has real problems and refactor if needed. Very useful for massive code bases. Also, Codeclimate works with code coverage info, generates code coverage status badges, and analyzes trends of your code coverage compared to production code. Codecliamte is a tool for almost all platforms, not only iOS, that’s why we need to convert (with Slather) our Xcode test report to a general code coverage report format (Cobertura) and send it to the codeclimate project. More about <a href="https://docs.codeclimate.com/docs/configuring-test-coverage">configuring test coverage</a> for codeclimate. Detailed billing info you can find <a href="https://codeclimate.com/quality/pricing">here</a>.</p><h3>Codeclimate, encryption, secrets</h3><h4>Encryption of provision and certificate files</h4><p>Before workflow setup, we need to generate provision and distribution certificate for deploy workflows. This post doesn’t cover this, because it is a lot of examples over the internet. After creating and downloading <em>Some.mobileprovision</em> and <em>SomeDistribution.cer</em> files we need to encrypt them into <em>.gpg</em> files, and the .cer file should be converted to<em> .p12</em> file before encryption. You can find examples of encrypting files in the gist file below. The encrypting process will ask you for a secret for future decryption. You need to save it in the repository secret section here as <em>SECRET_KEY</em>. It will be visible only to you:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jpwvv3AfEF3lGW2aanDE-Q.png" /></figure><p>Encrypted files <em>SomeDistribution.p12.gpg</em> and <em>Some.mobileprovision.gpg </em>you need to save in .github/secrets. <strong>Make sure to save encryption .gpg files, not the real certificate and provision.</strong></p><h4>Codeclimate</h4><p>Sign up into the Codeclimate service and link your repository <a href="https://codeclimate.com/login/github/join">here</a>. Copy test reporter id. Save it in GitHub secrets as <em>CC_TEST_REPORTER_ID</em>. It will be used for sending Cobertura test reports in the Codeclimate service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uE1J9u7uBD2r-XFeg16YaA.png" /></figure><p>Badges you can find here and add this markdown code to README.md in the root of the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*70a38A8ZR_USP0J2ulJ10Q.png" /></figure><h4>Apple IDs</h4><p>You need to create an app-specific password to deploy your application in Testflight from GitHub Actions. It is easy with <a href="https://support.apple.com/en-us/HT204397">these steps</a>. Save your apple id and newly created specific password to Github secrets as <em>APPLEID_PASSWORD</em> and <em>APPLEID_USERNAME</em>.</p><h3>Workflow files</h3><p>In the code examples below, you need to change workspaces, schemes, and project names as it uses in your project. Code examples have comments in urgent places.</p><p>For adding workflow you need to create in the root of the project next folders <em>.github/workflows/AnyName.yml</em>. I will use the CI_iOS.yml name for my workflow. So, we need to create 3 files for 3 different workflows in <em>.github/workflows/</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b8d3850dc3f4fb6d0a8bcff804f3a3dd/href">https://medium.com/media/b8d3850dc3f4fb6d0a8bcff804f3a3dd/href</a></iframe><p>Here you can control the process of your actions and see the result:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z8r3Hfsu39TEAkPTvimxCw.png" /></figure><h3>Pitfalls</h3><ul><li>Make sure to copy <em>exportOptions.plist</em> in the<em> .github/secrets</em> folder and change values from your project.</li><li>Slather needs a custom directory for derived data, make sure to use the same <em>derivedDataPath</em> for <em>xcodebuild</em> and <em>slather</em> commands</li><li>Slather crashed if you have modules without tests and put the item into the list of “Test coverage for specific targets” in scheme settings.n</li><li>In-App specific password creation flow make sure to copy the password, not the aliases name of the password.</li><li>Bundle increment does not work if your project has enabled setting with auto-generated <em>Info.plist</em> file. It should be turned off</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mchsn8ytgJQ_3hABILyA_A.png" /></figure><ul><li>Make sure that you have turned off the Automatic sign-in for the Release configuration which will be used for archiving in deploy workflow.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*MCm-rCIQwrjLVtGNNx7LOQ.png" /></figure><ul><li>If your tests fail, then you can find a readable format for logs, instead of just reading logs from the script results. You can find it here and they are generated only for “CI iOS” with 3rd party script <em>kishikawakatsumi/xcresulttool@v1</em>. Check “CI iOS” file.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PMUXUZXxcHsEcDPOUO_0-Q.png" /></figure><h3>Real project with these workflows</h3><ul><li>I used this workflow for my personal public repo, you can find how it works together for a real project <a href="https://github.com/alexnikol/Podcats">here</a>.</li><li>The “CI iOS” workflow runs on each pull request to the main branch. If all tests are passed — this pull request can be merged</li><li>The “Main” workflow runs on any push to the main branch and runs tests, gather and send coverage of the all system to the codeclimate</li><li>The “Deploy” workflow runs on push to the deploy/deploy_podcast_iphone_ios branch. It will archive, export, and send the new build to the Testflight</li></ul><h3>You can ask any questions and help me to improve this guide and pitfalls section!</h3><p><a href="https://www.linkedin.com/in/alexander-nikolaychuk-40727812b">LinkedIn</a> <a href="https://twitter.com/alexksnikol">Twitter</a> <a href="https://alexalmostengineer.co.ua/software-development-blog-alex_almost_engineer/">Original Blog</a> <a href="https://github.com/alexnikol">Github</a> <a href="https://www.hackerrank.com/alexEngineer">HackerRank</a></p><p>Photo by <a href="https://unsplash.com/@xoforoct?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">EJ Strat</a> on <a href="https://unsplash.com/s/photos/Workflow?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bVw6mZlxU_4Oa1QVz7eUpQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f2954015e39" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decoding JSON with endless nesting in Swift. Recursion in use]]></title>
            <link>https://almostengineer.medium.com/decoding-json-with-endless-nesting-in-swift-recursion-in-use-8538f206d626?source=rss-22a0f86b6168------2</link>
            <guid isPermaLink="false">https://medium.com/p/8538f206d626</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[decoding]]></category>
            <category><![CDATA[json]]></category>
            <category><![CDATA[parsing]]></category>
            <category><![CDATA[recursion]]></category>
            <dc:creator><![CDATA[Oleksandr Nikolaichuk ]]></dc:creator>
            <pubDate>Mon, 25 Jan 2021 10:40:09 GMT</pubDate>
            <atom:updated>2021-01-25T11:38:25.211Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kzjkzcKLiNGO9lxYmqWxXQ.jpeg" /></figure><p>Hi, this is a #FastTip about decoding JSON with endless nesting. I found this question in the iOS devs community and decide to help. Hope it will be useful!</p><p>For decoding, we will use the <em>Decoding protocol</em> from <a href="https://developer.apple.com/documentation/swift/swift_standard_library/encoding_decoding_and_serialization">Standard Swift Library</a></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5b27ebc8cb95a15319be7bbeda637c64/href">https://medium.com/media/5b27ebc8cb95a15319be7bbeda637c64/href</a></iframe><p>As you can see, the JSON can have every level of nesting as you need. For testing and applying for the work with endless process of anything, it is super useful to know about <a href="https://en.wikipedia.org/wiki/Recursion_(computer_science)">recursion</a>.</p><p>A little trick here, that struct <em>Object</em> has parameter <em>“sub_elements”</em> with type Optional(Array of Objects). That’s how any Object can have other Objects in these parameters and these objects can have other objects and so on.</p><p>Another urgent part here is a type of “sub_elements” — this is Optional Array. By this Optional type, we can easily check that this is the last level of nesting. You can see that in <em>showElements</em> function.</p><p>In the <em>showElements</em> function, you can also see a recursion example when <em>showElements</em> will call another <em>showElements</em> while all levels will be printed.</p><p>Result of calling <em>showElements</em> will be:</p><pre> — Item 6ECF5DA1–0558–436C-93E7-CCED4461866D Group<br> — — Item 4412C2FA-47D3–4524-A054-F06AE843DA45 Group 2<br> — — — Item 4315FAC2–0809–478C-BED8–54F28B0A9A57 Shape 1<br> — — — Item D2985D5B-B98A-4549-A4ED-3742583A2532 Image 1<br> — — — Item C67F6AE9–2EA5–4850-AA00–2A1DB8EB4167 Group 3<br> — — — — Item 718F235A-E2FB-4A05-A2A9–198CFA6B135A Shape 2<br> — — — — Item 0C232502-A0D6–4BC7-B4DD-178B0BFE8BB0 Image 2<br> — — Item 99BBAA31–0A9D-46F8–89C7-BD7EE444919E Shape<br> — — Item B5281F95–72A4–4973–9A70–18ABF1D3DD92 Image</pre><h3>My social media</h3><p><a href="https://www.linkedin.com/in/alexander-nikolaychuk-40727812b">LinkedIn</a> <a href="https://twitter.com/alexksnikol">Twitter</a> <a href="https://www.instagram.com/alexalmostengineer/">Instagram</a> <a href="https://alexalmostengineer.co.ua/software-development-blog-alex_almost_engineer/">Original Blog</a> <a href="https://github.com/alexnikol">Github</a> <a href="https://www.hackerrank.com/alexEngineer">HackerRank</a></p><p>Photo by <a href="https://unsplash.com/@chuttersnap?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">CHUTTERSNAP</a> on <a href="https://unsplash.com/s/photos/deep-forest?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><p><em>Originally published at </em><a href="https://alexalmostengineer.co.ua/decoding-json-with-endless-nesting-recursion-in-use/"><em>https://alexalmostengineer.co.ua</em></a><em> on January 25, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8538f206d626" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design patterns: Facade. Real examples in Swift]]></title>
            <link>https://almostengineer.medium.com/design-patterns-facade-real-examples-in-swift-c36cf67a3fee?source=rss-22a0f86b6168------2</link>
            <guid isPermaLink="false">https://medium.com/p/c36cf67a3fee</guid>
            <category><![CDATA[swift-programming]]></category>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[software-archi]]></category>
            <dc:creator><![CDATA[Oleksandr Nikolaichuk ]]></dc:creator>
            <pubDate>Sun, 13 Dec 2020 18:01:39 GMT</pubDate>
            <atom:updated>2020-12-13T18:02:11.715Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tqni1Bnr2m9I1MO97EJbjw.jpeg" /></figure><p>This article is a part of the design patterns post series. Design patterns, in general, are key to stop reinventing the wheel in most of the common developer challenges. I think that design patterns are great as a resource which can spend your time.</p><p><a href="https://alexalmostengineer.co.ua/purgatory-of-tutorials-todo-applications-frameworks-technologies-how-to-move-in-the-right-direction/">Here</a> you can find a post about the difficulties of a variety of tutorials and courses, and there a gave a list of <strong>sharable</strong>knowledge and technologies which will be useful on any developer’s job and which you can apply to any platform and stack.</p><h3>But let’s talk about the Facade pattern</h3><blockquote><strong><em>Facade</em></strong><em> is a </em><strong><em>structural</em></strong><em> design pattern that provides a simplified interface to a library, a framework, or any other complex set of classes.</em></blockquote><blockquote><em>From book “</em><a href="https://refactoring.guru/design-patterns/book"><em>Dive into design patterns</em></a><em>”. (It is not an ad)</em></blockquote><p>The explanation is pretty simple, but the main problem of all design patterns and shared knowledge, in general, is an abstraction. That means that the same definition can be understood differently. That’s why the main goal here is to understand the pattern principle and apply it to real tasks.</p><h3>Real examples or situations where the facade in any form of implementation should be applied</h3><p>Let’s remember the “Back to the Future Part III” movie. There is a huge mechanism in a Doc’s garage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/1*N7AvCyhQfog-Jzw5KSXp-g.jpeg" /><figcaption>Looks great, but anyone can’t work with this, except you Doc</figcaption></figure><p>And only after launching this machine we understood that it is just a refrigerator. You can imagine that this machine is a software of some difficult but useful library or framework. This difficult form of any mechanism (or software) creates a lot of problems:</p><ol><li>Only the creator of the library or framework can quickly launch, setup, or adapt this library of frameworks to work. All other developers should learn the implementation of this event if they don’t have to.</li><li>Different developers can setup this library or framework in a wrong, non-optimal way (because they can’t and don’t want to learn the core of this library and framework, they just don’t have time for it).</li><li>One day this library or framework can be changed, updated, or replaced on another difficult complex solution, and points 1 and 2 should be repeated, and all code that depends on the old library should be refactored.</li></ol><h3>Facade Swift implementation part</h3><p>These problems are pretty common to any software development because we always work with third-party libraries or with custom solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PlzcDILHC0IiH1B7D4LvLA.png" /><figcaption>Custom plugin for payments</figcaption></figure><p>Let’s imagine that you are working on a project where someone from your team wrote the custom payment library and this library even has documentation. But it is not a key here and you still need to read and understand this documentation, write your setup of this library (or find it in another place in this project). And even if you will be done it is still difficult to replace this library with another later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JMH-4cp2MSf3u_je0uNP5w.png" /></figure><p>This simple facade can solve a lot of problems with difficult complex software. All of these manipulations inside the <em>makePayment</em> function should be written each time in all modules which need payment functionality. But with this <strong>facade</strong>, you can easily work with it without any knowledge about this library. All that you need here is to understand that you just have a list of customer payment methods and simple function which can do magic for you under the cut.</p><p>So this facade should be written by the creator of this library or one developer which can spend time on this. After that, any of the developers only with basic knowledge of this payment system can easily create an instance of this facade class and use it in any place that they need. If the library will be changed (it is important to leave the facade functions signatures as it was before), all places where this facade used will be unaffected. In a worst-case even if the facade will change his functions name, parameters, and return types — that can be anyway easier to rewrite few functions calls then replace all uses of the library without facade.</p><h3>Third-party libraries</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NhLb_nIX-9d-Ldrgp31aUg.png" /></figure><p>Try to hide third-party libraries behind the facades. Real example. What if we have some ImageSlideshow library. It is super convenient to wrap it in protocol + extension, or some facade class. It easily hides the gallery implementation and you can just easily call this single openGallery method without knowing about ImageSlideshow. If you need to change this library to another — you can just rewrite this class. A library like this should be isolated and then it can be easily changed later.</p><p>Photo by <a href="https://unsplash.com/@moino007?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">DDP</a> on <a href="https://unsplash.com/s/photos/mechanism?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><h3>Resources</h3><p><a href="https://refactoring.guru/design-patterns/book">https://refactoring.guru/design-patterns/book</a></p><p><a href="https://www.amazon.com/Design-Patterns-Object-Oriented-Addison-Wesley-Professional-ebook/dp/B000SEIBB8">https://www.amazon.com/Design-Patterns-Object-Oriented-Addison-Wesley-Professional-ebook/dp/B000SEIBB8</a></p><h3>My social media</h3><p><a href="https://www.linkedin.com/in/alexander-nikolaychuk-40727812b">LinkedIn</a> <a href="https://twitter.com/alexksnikol">Twitter</a> <a href="https://alexalmostengineer.co.ua/software-development-blog-alex_almost_engineer/">Original Blog</a> <a href="https://github.com/alexnikol">Github</a> <a href="https://www.hackerrank.com/alexEngineer">HackerRank</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c36cf67a3fee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Display data in the right way in Swift. List, Date, Number, and Measurement formatters]]></title>
            <link>https://almostengineer.medium.com/display-data-in-the-right-way-in-swift-list-date-number-and-measurement-formatters-a7ce22fedb4d?source=rss-22a0f86b6168------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7ce22fedb4d</guid>
            <category><![CDATA[measurementformatter]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[dateformatter]]></category>
            <category><![CDATA[data-presentation]]></category>
            <dc:creator><![CDATA[Oleksandr Nikolaichuk ]]></dc:creator>
            <pubDate>Thu, 03 Sep 2020 16:01:02 GMT</pubDate>
            <atom:updated>2021-05-17T06:12:00.297Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sXeDp0GuXgKz6ZF9yhnZmQ.png" /></figure><p>The main goal of this article is to share my experience in formatting data. Most of the apps have to show date, time, list of data, or transform and display mass, angle, duration, area, speed, volume, energy, length, temperature, pressure, and other kinds of measurements. It is very important to display data in the right way with proper format, units, imperial or metric measurements, localized.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LTdnWWrQFGANi4A1" /><figcaption>Photo by <a href="https://unsplash.com/@rgrzybowski?utm_source=medium&amp;utm_medium=referral">Radek Grzybowski</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>My Social Media</h3><p><a href="https://www.linkedin.com/in/alexander-nikolaychuk-40727812b">LinkedIn</a> <a href="https://twitter.com/alexksnikol">Twitter</a> <a href="https://alexalmostengineer.co.ua/software-development-blog-alex_almost_engineer/">Original Blog</a> <a href="https://github.com/alexnikol">Github</a></p><h3>1. DateFormater</h3><p><em>DateFormater</em> — formatter class that converts between dates and their textual representations. DateFormater has a lot of properties, but the most useful of them are <strong>dateFormat</strong>, <strong>timeStyle</strong>, <strong>dateStyle</strong>, <strong>amSymbol</strong>, <strong>pmSymbol</strong>, and <strong>timeZone</strong>.</p><p><strong>dateFormat</strong> — <em>String</em> property for custom date and time format. Very useful if you need to show time in some non-default format.</p><pre>let dateFormater = DateFormatter()<br>dateFormater.dateFormat = &quot;dd MMM, yyyy - hh:mm:ss&quot;<br>let now = dateFormater.string(from: Date())</pre><pre>//CONSOLE: now<br>05 May, 2020 - 03:37:12</pre><p><strong>dateStyle</strong>, <strong>timeStyle</strong> — <em>DateFormatter.Style</em> property for showing preselected formats of date and time. <em>DateFormatter.Style</em> has <strong>none</strong>, <strong>short</strong>, <strong>medium</strong>, <strong>long</strong>, <strong>full</strong> cases. Formats will be shown below.</p><pre>dateStyle = .none // - nil<br>dateStyle = .short // - 6/5/20<br>dateStyle = .medium // - Jun 5, 2020<br>dateStyle = .long // - June 5, 2020<br>dateStyle = .full // - Friday, June 5, 2020timeStyle = .none // - nil<br>timeStyle = .short // - 3:47 PM<br>timeStyle = .medium // - 3:47:56 PM<br>timeStyle = .long // - 3:47:56 PM GMT+3<br>timeStyle = .full // - 3:47:56 PM Eastern European Summer Time</pre><p><strong>amSymbol</strong>, <strong>pmSymbol</strong> — custom symbols for AM and PM parts in date and time.</p><p><strong>timeZone</strong> — for which timezone to convert date and time. List of <a href="https://gist.github.com/mteece/80fff3329074cf90d7991e55f4fc8de4">timezones</a></p><h3>Examples:</h3><ul><li>For example, we have a timestamp and need to show the date and time:</li></ul><pre>let date = Date(timeIntervalSince1970: 1591361276)<br>let dateFormater = DateFormatter()<br>dateFormater.timeStyle = .short<br>dateFormater.dateStyle = .long<br>let dateString = dateFormater.string(from: date)</pre><pre>//CONSOLE: dateString<br>June 5, 2020 at 3:47 PM</pre><ul><li>For example, we have a timestamp and need to show the time in specific timezone and custom AM and PM parts:</li></ul><pre>let date = Date(timeIntervalSince1970: 1591361276)<br>let dateFormater = DateFormatter()<br>dateFormater.timeStyle = .short<br>dateFormater.dateStyle = .none<br>dateFormater.amSymbol = &quot;Ante meridiem&quot;<br>dateFormater.pmSymbol = &quot;Post meridiem&quot;<br>dateFormater.timeZone = TimeZone(identifier: &quot;Antarctica/Rothera&quot;)<br>let dateString = dateFormater.string(from: date)</pre><pre>//CONSOLE: dateString<br>9:47 Ante meridiem</pre><h3>2. ListFormatter</h3><p><em>ListFormatter</em> — formatted class for array representation. it is a cool way to show a list of data in a human-readable format.</p><pre>let animals = [&quot;Cat&quot;, &quot;Dog&quot;, &quot;Bird&quot;]<br>let formater = ListFormatter()<br>formater.locale = Locale(identifier: &quot;en_US&quot;)<br>let displayList = formater.string(from: animals)</pre><pre>//CONSOLE: displayList<br>&quot;Cat, Dog, and Bird&quot;</pre><p>It is easy to set any locale to <em>ListFormatter</em>, and the list will be like below. List of all <a href="https://gist.github.com/jacobbubu/1836273">Locales</a>.</p><pre>let animals = [&quot;Cat&quot;, &quot;Dog&quot;, &quot;Bird&quot;]<br>let formater = ListFormatter()<br>formater.locale = Locale(identifier: &quot;fr_FR&quot;)<br>let displayList = formater.string(from: animals)</pre><pre>//CONSOLE: displayList<br>&quot;Cat, Dog et Bird&quot;</pre><p>Of course, if you want to show list only with commas, you can use the old way:</p><pre>let animals = [&quot;Cat&quot;, &quot;Dog&quot;, &quot;Bird&quot;]<br>let displayList = animals.joined(separator: &quot;, &quot;)</pre><pre>//CONSOLE: displayList<br>&quot;Cat, Dog, Bird&quot;</pre><h3>3. NumberFormatter</h3><p><em>NumberFormatter</em> — super useful formatter for formating prices, percents. You can see a default usage of NumberFormtter.</p><pre>let priceFormatter = NumberFormatter()<br>priceFormatter.locale = Locale(identifier: &quot;en_FR&quot;)<br>priceFormatter.numberStyle = .currency<br>let displayPrice = priceFormatter.string(from: 20.5)</pre><pre>//CONSOLE: displayPrice<br>€20,5</pre><p><strong>numberStyle</strong> — is an enum like in DateFormatter and ListFormatter like above. numberStyle has next cases: <strong>none, decimal, currency, percent, scientific, spellOut, ordinal, currencyISOCode, currencyPlural, currencyAccounting</strong>. This a screen from official <a href="https://developer.apple.com/documentation/foundation/numberformatter/style">documentation</a> when you can see all differences between numberStyle types and different locales.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*33YIS-rpy4cnmIl9uYicRg.png" /></figure><h4>Ordinal numberStyle in NumberFormatter</h4><p>I want to pay your attention on <strong>ordinal</strong> numberStyle. It is useful when you want to show index numbers like <em>1st, 2nd</em>.</p><pre>let numberFormatter = NumberFormatter()<br>numberFormatter.numberStyle = .ordinal<br>let firstPlace = numberFormatter.string(from: 1)<br>let secondPlace = numberFormatter.string(from: 2)<br>let anotherPlace = numberFormatter.string(from: 33)</pre><pre>// CONSOLE: firstPlace, secondPlace, anotherPlace<br>&quot;1st&quot;, &quot;2nd&quot;, &quot;33rd&quot;</pre><h4>SpellOut numberStyle in NumberFormatter</h4><pre>let numberFormatter = NumberFormatter()<br>numberFormatter.numberStyle = .spellOut<br>let result = numberFormatter.string(from: 234.5)</pre><pre>// CONSOLE: firstPlace, secondPlace, anotherPlace<br>&quot;two hundred thirty-four point five&quot;</pre><h3>4. MeasurementFormatter</h3><p><em>MeasurementFormatter</em> — A formatter that provides localized representations of units and measurements. It is a less used formatter but is insanely useful when you need to display different data in different units. <em>MeasurementFormatter</em> can work with a ton of preset units. It is a list of provided units:</p><blockquote>UnitAcceleration, UnitAngle, UnitArea, UnitConcentrationMass, UnitDispersion, UnitDuration, UnitElectricCharge, UnitElectricCurrent, UnitElectricPotentialDifference, UnitElectricResistance, UnitEnergy, UnitFrequency, UnitFuelEfficiency, UnitInformationStorage, UnitLength, UnitIlluminance, UnitMass, UnitPower, UnitPressure, UnitSpeed, UnitTemperature, UnitVolume.</blockquote><p><strong>Measurements of the same unit can be added or subtracted, multiplied, or divided.</strong></p><p>I will show you a few examples with different Units, and after that, you can easily use other of them which not covered in my examples.</p><p>MeasurementFormatter has <strong>unitOptions</strong> and <strong>unitStyle</strong> properties. it is easy to set up the needed format of presentation.</p><p><strong>unitOptions</strong> has 3 cases — <strong>providedUnit</strong><em>, </em><strong>naturalScale</strong><em>, </em><strong>temperatureWithoutUnit</strong><em>.</em></p><ul><li><strong>providedUnit</strong> — displays the unit of measure without any converting. Locale won’t affect if <strong>unitOptions</strong> set to <strong><em>providedUnit</em></strong></li><li><strong>naturalScale</strong> — displays the unit depend on the current locale of the formatter. Formatter can decide to convert the value from the given unit to a specific another for a better and complex presentation view. (you can set 0.1 kilometers, and formatter will show you 100m instead 0.1km.</li><li><strong><em>temperatureWithoutUnit</em></strong> — displays temperature without any unit.</li></ul><p><strong>unitStyle</strong> has 3 cases — <strong>short, </strong><strong>medium, </strong><strong>long</strong> formats. For example, formatted 1 kilometer will be — <strong>1km</strong>, <strong>1 km</strong>, <strong>1 kilometers</strong> respectively</p><h4>How to show UnitSpeed in the specific unit without converting:</h4><pre>let measurementFormatter = MeasurementFormatter()<br>var speedMeasurement = Measurement(value: 0.000001, unit: UnitSpeed.kilometersPerHour)<br>measurementFormatter.unitOptions = .providedUnit<br>measurementFormatter.unitStyle = .short<br>let result = measurementFormatter.string(from: speedMeasurement)</pre><pre>// CONSOLE: result<br>50km/h</pre><p><strong>unitOptions</strong> must be <strong>providedUnit</strong> because we don’t convert or formate speed to another unit.</p><h4>How to convert UnitLength to another unit:</h4><pre>let measurementFormatter = MeasurementFormatter()<br>measurementFormatter.unitOptions = .providedUnit<br>measurementFormatter.unitStyle = .long</pre><pre>var miles = Measurement(value: 2, unit: UnitLength.miles)<br>miles.convert(to: .centimeters)<br>let displayString = measurementFormatter.string(from: miles)</pre><pre>//CONSOLE: displayString<br>321,868.8 centimeters</pre><p>Make sure you need to set <strong>unitOptions</strong> to <strong>providedUnit</strong>, because <strong>naturalScale</strong> will convert centimeters back to miles (because it is the main option of <strong><em>naturalScale</em></strong> mode).</p><h4>How to present a localized UnitMass:</h4><pre>let measurementFormatter = MeasurementFormatter()<br>measurementFormatter.unitOptions = .naturalScale<br>measurementFormatter.unitStyle = .medium<br>measurementFormatter.locale = Locale(identifier: &quot;en_US&quot;)</pre><pre>var massMeasurement = Measurement(value: 10, unit: UnitMass.kilograms)<br>let displayString = measurementFormatter.string(from: massMeasurement)</pre><pre>//CONSOLE: displayString<br>22.046 lb</pre><p>Make sure you need to set <strong>unitOptions</strong> to <strong>naturalScale</strong> because <strong>providedUnit</strong> will prevent the localized converting that we actually need.</p><h4>How to add, subtract, multiply, or divide Measurements?</h4><pre>let measurementFormatter = MeasurementFormatter()<br>measurementFormatter.unitOptions = .providedUnit<br>measurementFormatter.unitStyle = .medium</pre><pre>let firstMeasure = Measurement(value: 10, unit: UnitAngle.degrees)<br>let secondMeasure = Measurement(value: 10, unit: UnitAngle.radians)<br>var sum = firstMeasure + secondMeasure<br>sum.convert(to: .radians)<br>let displayString = measurementFormatter.string(from: sum)</pre><pre>//CONSOLE: displayString<br>10.175 rad</pre><h3>Conclusions:</h3><p>In my opinion, even theses 4 formatters can do your code more flexible, readable, and maintainable. Formating and converting is a huge part of each app. You always need to prepare your data from the server to human-readable convenient form. Of course, you can write all these formatters and convertors by yourself, but it is silly to reinvent the wheel each time in each app. That’s why it is crucial to understand and use these formatters for a better user experience.</p><h3>Additional Resources:</h3><p><a href="https://gist.github.com/mteece/80fff3329074cf90d7991e55f4fc8de4">Timezones List</a></p><p><a href="https://gist.github.com/jacobbubu/1836273">Locales List</a></p><p><a href="https://developer.apple.com/documentation/foundation/measurementformatter">MeasurementFormatter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7ce22fedb4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#FASTTIPS 12]]></title>
            <link>https://medium.com/series/fasttips-12-8e51778f8e65?source=rss-22a0f86b6168------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e51778f8e65</guid>
            <dc:creator><![CDATA[Oleksandr Nikolaichuk ]]></dc:creator>
            <pubDate>Wed, 02 Sep 2020 20:08:35 GMT</pubDate>
            <atom:updated>2020-09-02T20:08:35.682Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QiZvfPr1C26ogVPiC7wD4w@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xDSEGR34LZx1kaSrlweLWA@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e51778f8e65" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#FASTTIPS 11]]></title>
            <link>https://medium.com/series/fasttips-11-b2bbaf7a7a46?source=rss-22a0f86b6168------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2bbaf7a7a46</guid>
            <dc:creator><![CDATA[Oleksandr Nikolaichuk ]]></dc:creator>
            <pubDate>Tue, 01 Sep 2020 19:14:07 GMT</pubDate>
            <atom:updated>2020-09-01T19:14:07.342Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yS2jlPJmllXoNAc5OY3yqw@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*blNMVMMCkfaz_44yK56Jgw@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oXqbpAqb_zUH7LWtLyrqsg@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2bbaf7a7a46" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#FASTTIPS 10]]></title>
            <link>https://medium.com/series/fasttips-10-d1becdcb0fbb?source=rss-22a0f86b6168------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1becdcb0fbb</guid>
            <dc:creator><![CDATA[Oleksandr Nikolaichuk ]]></dc:creator>
            <pubDate>Mon, 31 Aug 2020 20:20:20 GMT</pubDate>
            <atom:updated>2020-08-31T20:20:20.371Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZF7A-qqxJJAxlEpJwIYqqA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iW21tDb9vQy5PLzl3XQX4g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ztY3gIOXKRWjl_MbUL_38A.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1becdcb0fbb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#FASTTIPS 9]]></title>
            <link>https://medium.com/series/fasttips-9-69921fdd552b?source=rss-22a0f86b6168------2</link>
            <guid isPermaLink="false">https://medium.com/p/69921fdd552b</guid>
            <dc:creator><![CDATA[Oleksandr Nikolaichuk ]]></dc:creator>
            <pubDate>Thu, 27 Aug 2020 19:56:12 GMT</pubDate>
            <atom:updated>2020-08-27T19:56:12.454Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kiajvqo2Gg37YgUBYOvWOw@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKL0h7oebxZGGF0NBZ_EJA@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69921fdd552b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#FASTTIPS 8]]></title>
            <link>https://medium.com/series/fasttips-8-2968944fbe44?source=rss-22a0f86b6168------2</link>
            <guid isPermaLink="false">https://medium.com/p/2968944fbe44</guid>
            <dc:creator><![CDATA[Oleksandr Nikolaichuk ]]></dc:creator>
            <pubDate>Wed, 26 Aug 2020 16:54:08 GMT</pubDate>
            <atom:updated>2020-08-26T16:54:08.948Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J6DGpUimVJ8YSj-llxYkFg@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z_lIC2ql_PAFMzaOr6j2Eg@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2968944fbe44" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>