<?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[HackerBay - Medium]]></title>
        <description><![CDATA[Thousands businesses use HackerBay&#39;s tools to build high quality products on time. - Medium]]></description>
        <link>https://medium.com/hackerbaycompany?source=rss----99ccbc404747---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>HackerBay - Medium</title>
            <link>https://medium.com/hackerbaycompany?source=rss----99ccbc404747---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:23:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/hackerbaycompany" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Generating More Difficult Mazes]]></title>
            <link>https://medium.com/hackerbaycompany/generating-more-difficult-mazes-3052b6660024?source=rss----99ccbc404747---4</link>
            <guid isPermaLink="false">https://medium.com/p/3052b6660024</guid>
            <category><![CDATA[haskell]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[functional-programming]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[James Bowen]]></dc:creator>
            <pubDate>Wed, 17 Apr 2019 03:39:28 GMT</pubDate>
            <atom:updated>2019-04-17T03:39:28.204Z</atom:updated>
            <content:encoded><![CDATA[<p>In the <a href="https://www.mmhaskell.com/blog/2019/4/1/building-a-bigger-world">last part</a> of this series, we established the fundamental structures for our maze game. But our “maze” was still rather bland. It didn’t have any interior walls, so getting to the goal point was trivial. In this next part, we’ll look at an algorithm for random maze generation. This will let us create some more interesting challenges. In upcoming parts of this series, we’ll explore several more related topics. We’ll see how to serialize our maze definition. We’ll refactor some of our data structures. And we’ll also take a look at another random generation algorithm.</p><p>If you’ve never programmed in Haskell before, you should download our <a href="https://www.mmhaskell.com/beginners-checklist">Beginners Checklist</a>! It will help you learn the basics of the language so that the concepts in this series will make more sense. The State monad will also see a bit of action in this part. So if you&#39;re not comfortable with monads yet, you should read our <a href="https://www.mmhaskell.com/monads">series</a> on them!</p><h3>Getting Started</h3><p>We represent a maze with the type Map.Map Location CellBoundaries. For a refresher, a Location is an Int tuple. And the CellBoundaries type determines what borders a particular cell in each direction:</p><pre>type Location = (Int, Int)</pre><pre>data BoundaryType = Wall | WorldBoundary | AdjacentCell Location</pre><pre>data CellBoundaries = CellBoundaries<br>  { upBoundary :: BoundaryType<br>  , rightBoundary :: BoundaryType<br>  , downBoundary :: BoundaryType<br>  , leftBoundary :: BoundaryType<br>  }</pre><p>An important note is that a Location refers to the position in discrete x,y space. That is, the first index is the column (starting from 0) and the second index is the row. Don&#39;t confuse row-major and column-major ordering! (I did this when implementing this solution the first time).</p><p>To generate our maze, we’ll want two inputs. The first will be a random number generator. This will help randomize our algorithm so we can keep generating new, fresh mazes. The second will be the desired size of our grid.</p><pre>import System.Random (StdGen, randomR)</pre><pre>…</pre><pre>generateRandomMaze<br>  :: StdGen<br>  -&gt; (Int, Int)<br>  -&gt; Map.Map Location CellBoundaries<br>generateRandomMaze gen (numRows, numColumns) = ...</pre><h3>A Simple Randomization Algorithm</h3><p>This week, we’re going to use a relatively simple algorithm for generating our maze. We’ll start by assuming everything is a wall, and we’ve selected some starting position. We’ll use the following depth-first-search pattern:</p><ol><li>Consider all cells around us</li><li>If there are any we haven’t visited yet, choose one of them as the next cell.</li><li>“Break down” the wall between these cells, and put that new cell onto the top of our search stack, marking it as visited.</li><li>If we have visited all other cells around us, pop this current location from the stack</li><li>As long as there is another cell on the stack, choose it as the current location and continue searching from step 1.</li></ol><p>There are several pieces of state we have to maintain throughout the process. So the State monad is an excellent candidate for this problem! Let&#39;s make a SearchState type for all these:</p><pre>data SearchState = SearchState<br>  { randomGenerator :: StdGen<br>  , locationStack :: [Location]<br>  , currentBoundaries :: Map.Map Location CellBoundaries<br>  , visitedCells :: Set.Set Location<br>  }</pre><pre>dfsSearch :: State SearchState ()<br>dfsSearch = ...</pre><p>Each time we make a random selection, we’ll use the randomR function that returns the appropriate value as well as a new generator. Then we&#39;ll use a normal list for our search stack since we can push and pop from the top with ease. Next, we&#39;ll track the current state of the maze (it starts as all walls and we&#39;ll gradually break those down). Finally, there&#39;s the set of all cells we&#39;ve already visited.</p><h3>Starting Our Search!</h3><p>To start our search process, we’ll pull all our information out of the state monad, and examine the stack. If it’s empty, we’re done and can return! Otherwise, we’ll want to consider the top location:</p><pre>dfsSearch = do<br>  (SearchState gen locs bounds visited) &lt;- get<br>  case locs of<br>    [] -&gt; return ()<br>    (currentLoc : rest) -&gt; do<br>      ...</pre><h3>Finding New Search Candidates</h3><p>Given a particular location, we need to find the potential neighbors. We want to satisfy two conditions:</p><ol><li>It shouldn’t be in our visited set.</li><li>The boundary to this location should be a Wall</li></ol><p>Then we’ll want to use these properties to determine a list of candidates. Each candidate will contain 4 items:</p><ol><li>The next location</li><li>The bounds we would use for the new location</li><li>The previous location</li><li>The new bounds for the previous location.</li></ol><p>This seems like a lot, but it’ll make more sense as we fill out our algorithm. With that in mind, here’s the structure of our findCandidates function:</p><pre>findCandidates<br>  :: Location -- Current location<br>  -&gt; Map.Map Location CellBoundaries -- Current maze state<br>  -&gt; Set.Set Location -- Visited Cells<br>  -&gt; [(Location, CellBoundaries, Location, CellBoundaries)]<br>findCandidates currentLocation bounds visited = ...</pre><p>Filling in this function consists of following the same process for each of the four directions from our starting point. First we check if the adjacent cell in that direction is valid. Then we create the candidate, containing the locations and their new boundaries. Since the location could be invalid, the result is a Maybe. Here&#39;s what we do for the &quot;up&quot; direction:</p><pre>findCandidates =<br>  let currentLocBounds = fromJust $<br>        Map.lookup currentLocation bounds<br>      upLoc = (x, y + 1)<br>      maybeUpCandidate = case<br>        (upBoundary currentLocBounds, Set.member upLoc visited) of<br>        (Wall, False) -&gt; Just<br>          ( upLoc<br>          , (fromJust $ Map.lookup upLoc bounds)<br>              { downBoundary = AdjacentCell currentLocation }<br>          , currentLocation<br>          , currentLocBounds { upBoundary = AdjacentCell upLoc }<br>          )<br>        ...</pre><p>We replace the existing Wall elements with AdjacentCell elements in our maze map. This may seem like it&#39;s doing a lot of unnecessary work in calculating bounds that we&#39;ll never use. But remember that Haskell is lazy! Any candidate that isn&#39;t chosen by our random algorithm won&#39;t be fully evaluated. We repeat this process for each direction and then use catMaybes on them all:</p><pre>findCandidates =<br>  let currentLocBounds = fromJust $ Map.lookup currentLocation bounds<br>      upLoc = (x, y + 1)<br>      maybeUpCandidate = …<br>      rightLoc = (x + 1, y)<br>      maybeRightCandidate = …<br>      downLoc = (x, y - 1)<br>      maybeDownCandidate = …<br>      leftLoc = (x - 1, y)<br>      maybeLeftCandidate = …<br>  in  catMaybes [maybeUpCandidate, maybeRightCandidate, … ]</pre><h3>Choosing a Candidate</h3><p>Our search function is starting to come together now. Here’s what we’ve got so far. If we don’t have any candidates, we’ll reset our search state by popping the current location off our stack. Then we can continue the search by making another call to dfsSearch.</p><pre>dfsSearch = do<br>  (SearchState gen locs bounds visited) &lt;- get<br>  case locs of<br>    [] -&gt; return ()<br>    (currentLoc : rest) -&gt; do<br>      let candidateLocs = findCandidates currentLoc bounds visited<br>      if null candidateLocs<br>        then put (SearchState gen rest bounds visited) &gt;&gt; dfsSearch<br>        else ...</pre><p>But assuming we have a non-empty list of candidates, we’ll need to choose one. This function will update most of our state elements, so we’ll put in in the State monad as well:</p><pre>chooseCandidate<br>  :: [(Location, CellBoundaries, Location, CellBoundaries)]<br>  -&gt; State SearchState ()<br>chooseCandidate candidates = do<br>  (SearchState gen currentLocs boundsMap visited) &lt;- get<br>  ...</pre><p>First, we’ll need to select a random index into this list, which assumes it is non-empty.:</p><pre>chooseCandidate candidates = do<br>  (SearchState gen currentLocs boundsMap visited) &lt;- get<br>  let (randomIndex, newGen) = randomR (0, (length candidates) - 1) gen<br>      (chosenLocation, newChosenBounds, prevLocation, newPrevBounds) =<br>        candidates !! randomIndex</pre><p>Since we did the hard work of creating the new bounds objects up above, the rest is straightforward. We’ll create our new state with different components.</p><p>We get a new random generator from the randomR call. Then we can push the new location onto our search stack. Next, we update the bounds map with the new locations. Last, we can add the new location to our visited array:</p><pre>chooseCandidate candidates = do<br>  (SearchState gen currentLocs boundsMap visited) &lt;- get<br>  let (randomIndex, newGen) = randomR (0, (length candidates) - 1) gen<br>      (chosenLocation, newChosenBounds, prevLocation, newPrevBounds) =<br>        candidates !! randomIndex<br>      newBounds = Map.insert prevLocation newPrevBounds<br>        (Map.insert chosenLocation newChosenBounds boundsMap)<br>      newVisited = Set.insert chosenLocation visited<br>      newSearchStack = chosenLocation : currentLocs<br>  put (SearchState newGen newSearchStack newBounds newVisited)</pre><p>Then to wrap up our DFS, we’ll call this function at the very end. Remember to make the recursive call to dfsSearch!</p><pre>dfsSearch = do<br>  (SearchState gen locs bounds visited) &lt;- get<br>  case locs of<br>    [] -&gt; return ()<br>    (currentLoc : rest) -&gt; do<br>      let candidateLocs = findCandidates currentLoc bounds visited<br>      if null candidateLocs<br>        then put (SearchState gen rest bounds visited) &gt;&gt; dfsSearch<br>        else (chooseCandidate candidateLocs) &gt;&gt; dfsSearch</pre><h3>Incorporating Our Search</h3><p>As a last step in our process, we need to incorporate our search function. At the most basic level, we’ll want to execute our DFS state function and extract the boundaries from it:</p><pre>generateRandomMaze :: StdGen -&gt; (Int, Int) -&gt; Map.Map Location CellBoundaries<br>generateRandomMaze gen (numRows, numColumns) =<br>  currentBoundaries (execState dfsSearch initialState)<br>  where<br>    initialState :: SearchState<br>    initialState = ...</pre><p>But we need to build our initial state. We’ll start our search from a random location. Our initial stack and visited set will contain this location. Notice that with each random call, we use a new generator.</p><pre>generateRandomMaze gen (numRows, numColumns) =<br>  currentBoundaries (execState dfsSearch initialState)<br>  where<br>    (startX, g1) = randomR (0, numColumns - 1) gen<br>    (startY, g2) = randomR (0, numRows - 1) g1</pre><pre>    initialState :: SearchState<br>    initialState = SearchState<br>      g2<br>      [(startX, startY)]<br>      … -- TODO Bounds<br>      (Set.fromList [(startX, startY)])</pre><p>The last thing we need is our initial bounds set. For this, I’m going to tease the next part of the series. We’ll write a function to parse a maze from a string representation (and reverse the process). Our encoding will represent a “surrounded” cell with the character ‘F’. So we can represent a completely blocked maze like so:</p><pre>generateRandomMaze gen (numRows, numCols) = …<br>  where<br>    …</pre><pre>    fullString :: Text<br>    fullString = pack . unlines $<br>      take numRows $ repeat (take numColumns (repeat &#39;F&#39;))</pre><p>Finally, we’ll apply the mazeParser function in Megaparsec style. You&#39;ll have to wait for next week to see how to implement that! It will give us the appropriate cell boundaries.</p><pre>generateRandomMaze gen (numRows, numColumns) =<br>  currentBoundaries (execState dfsSearch initialState)<br>  where<br>    (startX, g1) = randomR (0, numColumns - 1) gen<br>    (startY, g2) = randomR (0, numRows - 1) g1</pre><pre>    initialState :: SearchState<br>    initialState = SearchState<br>      g2<br>      [(startX, startY)]<br>      initialBounds<br>      (Set.fromList [(startX, startY)])</pre><pre>    initialBounds :: Map.Map Location CellBoundaries<br>    initialBounds = case Megaparsec.runParser<br>      (mazeParser (numRows, numColumns) &quot;&quot; fullString of<br>        Right bounds -&gt; bounds<br>        _ -&gt; error &quot;Couldn&#39;t parse maze for some reason!&quot;</pre><pre>    fullString :: Text<br>    fullString = ...</pre><p>You can also look at our <a href="https://www.github.com/jhb563/MazeGame">Github repo</a> for some details. You’ll want the part-2 branch if you want more details about how everything works!</p><h3>Conclusion</h3><p>Generating random mazes is cool. But if we want to make a replayable game, we’ll need some way of storing mazes. In the next part, we’ll look at some code for dumping a maze to an output format. We’ll also need a way to re-load from this stored representation.</p><p>In preparation for that, you can read our series on <a href="https://www.mmhaskell.com/parsing">Parsing</a>. You’ll especially want to acquaint yourself with the <a href="http://hackage.haskell.org/package/megaparsec">Megaparsec library</a>. We go over this in <a href="https://www.mmhaskell.com/parsing-4">Part 4</a> of the series!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3052b6660024" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackerbaycompany/generating-more-difficult-mazes-3052b6660024">Generating More Difficult Mazes</a> was originally published in <a href="https://medium.com/hackerbaycompany">HackerBay</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Checklist for publishing a story to Medium.]]></title>
            <link>https://medium.com/hackerbaycompany/checklist-for-publishing-a-story-to-medium-aaf811b68526?source=rss----99ccbc404747---4</link>
            <guid isPermaLink="false">https://medium.com/p/aaf811b68526</guid>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[greatest-hits]]></category>
            <category><![CDATA[blogging-tips]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Nawaz Dhandala]]></dc:creator>
            <pubDate>Mon, 06 Aug 2018 11:20:48 GMT</pubDate>
            <atom:updated>2018-08-15T10:46:30.047Z</atom:updated>
            <content:encoded><![CDATA[<h4>Here’s a quick list of things you need to do before you submit your story for review on any of our publications.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Z9VgMkehuH_bOZthwjH5g.jpeg" /></figure><p>Here’s a checklist to publish articles on Medium. We use this checklist to review stories for all of our publications. Our publications include — <a href="http://blog.cloudboost.io/">CloudBoost</a>, <a href="http://medium.com/fyipe">Fyipe</a>, <a href="http://blog.hackerbay.io/">HackerBay</a>, <a href="http://medium.com/hackerbay-university">HackerBay University</a>, <a href="https://medium.com/hackerbaylabs">HackerBay Labs</a>, <a href="https://medium.com/hackerbay-ventures">HackerBay Ventures</a>, <a href="https://medium.com/flowappplatform">Flow</a>, and <a href="https://hackerbay.io/">more</a>.</p><blockquote>We invite anyone to publish stories to any of our publications.</blockquote><p>If you wish to contribute. Please send an email to hello@hackerbay.io with your Medium username, story link (this can be a draft), and the name of the medium publications you want to publish to. We’ll add you as a writer and have your article reviewed, edited and published!</p><p>Here’s what all this means for you as a writer:</p><ul><li>We won’t plaster your story with advertisements, or put it behind a paywall (or “email wall” or anything — no weird tricks).</li><li>You can include links to your own blog or service, and even affiliate links, as long as it’s done tastefully and transparently.</li><li>Your stories are yours. We don’t lay any claim to them. You can cross-post them wherever you want. Other newspapers and websites may even approach you about syndicating them or translating them. That’s fine with us. We just ask that — since we invest a lot of time in editing and promoting your stories — you don’t remove them from our Medium publication once we’ve published them.</li></ul><h3>Educate your readers</h3><p>Educate your readers and teach them something new. Cut all the fluff. Get to the point — fast. Do not waste their time. This is the only reason they’re spending time on your story.</p><h3>Write original content</h3><p>Do not read 10 other articles and write your story along the same lines. World needs original content and if you cannot do that — Do not start writing it. Only write blogs on topic that you already know and have experience in.</p><h3>Check for grammar and spellings</h3><p>There’s a <a href="https://www.grammarly.com/">free tool</a> that can help you do this. Make sure you do this before submitting your blog for review.</p><h3>Tags</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*xm-vKu_INQS9c1z8Mwu8MQ.png" /><figcaption>Tag example on a Medium article.</figcaption></figure><p>It’s important you tag all of your stories. Medium allows 5 tag per story. Use all of them. Please make sure you select 2 high influence tags (there should be a number when you select a tag, more the better) and 2 low-influence tags (less number of tags). The idea is your story will be the first one to show up when people search for low influence tags on a longer term basis, and high influence tags works better to get followers short term.</p><h3>Images</h3><ul><li><strong>Pick a cover image:</strong> Cover images are a must for all stories. Stories without cover images get 5 times less traction than the one’s that do. Pick a decent cover image. It should align with your story, be engaging to look at and should tempt someone to click on your story.</li><li><strong>Never pick highly used images: </strong>They’re not attractive and often boring.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Edya9xrJgs-JBSGn9Zi4OQ.png" /><figcaption>Highly used cover image.</figcaption></figure><p>You can change that image to this for example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fmic2n5ksXL3FOuIfhnEAA.png" /><figcaption>A new cover Image. More attractive and more engaging.</figcaption></figure><ul><li><strong>Stock photography:</strong> Give your story some love by picking a beautiful, free picture from <a href="https://unsplash.com/">Unsplash</a>.</li><li><strong>Captions</strong>: Please add captions to all of your images. It helps SEO your story.</li></ul><h3>Title</h3><ul><li><strong>Don’t use clickbait:</strong> “You won’t believe this one ridiculously effective headline dark pattern”</li><li><strong>Don’t use listicles:</strong> “11 outrageous headlines that will compel people to read your Medium story”. Sometimes listicles make sense, a lot of times — they don’t.</li><li><strong>Length:</strong> Make sure your title is neither too short nor too long. Ideal length is between 5–9 words,</li><li>Distill your entire story to one headline. Make sure your article resonates with it. Do not deviate from your headline in your story.</li><li><strong>Make sure your headline is 80 characters or fewer</strong>. Otherwise, the title will get truncated in news feeds when people share your article on Facebook and Twitter.</li><li><strong>Analyse your headline</strong>: Here’s a <a href="https://coschedule.com/headline-analyzer">tool</a> that lets your analyse your headline. People click on emotional content. More emotional, the better.</li></ul><h3>Links</h3><p>Always have links in the same line. I’ve linked to <a href="https://hackerbay.io/">HackerBay’s website</a> in this example. Never link like this — <a href="http://hackerbay.io./">http://hackerbay.io.</a></p><h3>Quotes</h3><ul><li>Highlight important sentences and quotes. Quotes from other famous famous people add credibility.</li></ul><h3>Code</h3><p>When you’re posting code. Use the Medium Code Block to write content. You can also embed JSFiddle or CodePen. Do not write code as text.</p><h3>Content</h3><ul><li>Do not use all caps. It’s called SHOUTING at your reader.</li><li>Make sure you have at least one quote in your blog. If your can’t highlight things on your blog. It’s not worth reading int he first place.</li><li>Divide your story into different sections and make it easier for reader to parse through it.</li></ul><h3>Post on Social Media</h3><p>When we publish your story. Please post your story to your Twitter, Facebook and Facebook feed. It helps get visibility.</p><h3>Conclusion</h3><p>We’re looking forward to reading your submissions. I hope we can help you further improve your stories, and reach a much wider audience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aaf811b68526" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackerbaycompany/checklist-for-publishing-a-story-to-medium-aaf811b68526">Checklist for publishing a story to Medium.</a> was originally published in <a href="https://medium.com/hackerbaycompany">HackerBay</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting started with Ansible playbooks]]></title>
            <link>https://medium.com/hackerbaycompany/getting-started-with-ansible-playbooks-565cb9ba1283?source=rss----99ccbc404747---4</link>
            <guid isPermaLink="false">https://medium.com/p/565cb9ba1283</guid>
            <category><![CDATA[ansible]]></category>
            <category><![CDATA[process-improvement]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[scripting]]></category>
            <dc:creator><![CDATA[Vidhita Kher]]></dc:creator>
            <pubDate>Mon, 26 Mar 2018 12:15:40 GMT</pubDate>
            <atom:updated>2018-03-26T12:15:40.189Z</atom:updated>
            <content:encoded><![CDATA[<p>I started my journey in Ansible playbook automation with the idea of moving away from traditional script automation tools and deployment models on virtual machines to something more simple, sequential , agent-less and powerful in terms of the configuration management and workflow orchestration required in Cloud environment. And ANSIBLE was the answer.</p><p>Below is the step by step guide on how to get started with playbook creation, execution and troubleshooting in Ansible:</p><p><strong>Creating a Playbook — Know How:</strong></p><p>I began my first playbook creation by converting the existing Network Shell script for product installation on virtual machine in cloud environment to a playbook.</p><p>Playbooks are expressed in YAML format and mostly consists of a series of sequential ‘tasks’. At a very basic level, a task is nothing more than a call to an ansible module , which are predefined set of system commands ,resources etc.</p><p>To have an overview of playbook creation , here is the official link to the documentation on the same: <a href="http://docs.ansible.com/ansible/latest/playbooks_intro.html#basics">AnsiblePlaybooks</a></p><p><strong>Steps to execute playbook:</strong></p><p>1. The first step in executing a playbook is to check for any syntax errors while writing the playbook</p><p>— <strong><em>ansible-playbook test.yml — syntax-check</em></strong></p><p><strong><em>2.</em></strong> Below is the step to execute a playbook</p><p>— <strong><em>ansible-playbook test.yml</em></strong></p><p><strong><em>3.</em></strong> For detailed debugging step by step for a playbook use this command:</p><p><strong>— ansible-playbook test.yml — step -vv</strong></p><p><strong>Troubleshooting a playbook:</strong></p><p>Most common errors faced while executing a playbook are:</p><p>1. <strong>no such file or directory</strong></p><p>— Usually for this kind of error, you need to look if the permissions of the file is set to execute for that particular file</p><p>— Another thing to check is if you are running the playbook as root user or any other non-root ansible user which has the required privileges to execute the playbook.</p><p>— Another basic error could be that the file is not copied properly to the target server before execution</p><p>2. <strong>Permissions denied</strong></p><p>— You may need to check if the id you’re using is having enough permissions to execute the playbook or you need to be root otherwise.</p><p><strong>Best practices to be followed:</strong></p><p>1. Copy the required sh script,tar, zip files whatever is required for installation of any of the software/products on the virtual machines for which we are writing the ansible playbook in the proper folder structure in your GIT repository</p><p>2. It is a best practice to provide the name all the tasks which are performed in the playbook to increase the readability of the same by another user.</p><p>3. Always mention the target hosts in your playbook at the top before beginning the actual playbook. Please make sure you may also need to add the same in /etc/ansible.cfg file on the MAIN server.</p><p>4. Throughout the development of any playbook if you’re stuck with any command, use the official guide <a href="http://www.ansible.com/">docs.ansible.com</a> to lookup for any command, it’s syntax and various parameters used along with it.</p><p>5. For e.g.: for executing a shell script via Ansible playbook , we have two modules available in ansible: <strong>Shell</strong> module and <strong>Script</strong> module.</p><p><strong>Pro Tip:</strong> Using the -step -vv ( verbose) while playbook execution can help playbook developers troubleshoot and optimize if at all required their scripts interactively and — when things go wrong — provide valuable triage information.</p><p>Automation frees admins up to focus on efforts that help deliver more value to the business by speeding time to application delivery, and building on a culture of success.</p><p>Leave me a comment below if you’re facing any issues while playbook creation,execution, troubleshooting etc in Ansible and I will be happy to help!.<br>Happy Learning ! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=565cb9ba1283" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackerbaycompany/getting-started-with-ansible-playbooks-565cb9ba1283">Getting started with Ansible playbooks</a> was originally published in <a href="https://medium.com/hackerbaycompany">HackerBay</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building An MVP? Prepare A Product Requirements Document First]]></title>
            <link>https://medium.com/hackerbaycompany/building-an-mvp-prepare-a-products-requirements-document-first-6cd81b76a232?source=rss----99ccbc404747---4</link>
            <guid isPermaLink="false">https://medium.com/p/6cd81b76a232</guid>
            <category><![CDATA[prd]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Ideaction]]></dc:creator>
            <pubDate>Mon, 05 Feb 2018 16:27:16 GMT</pubDate>
            <atom:updated>2019-11-15T14:07:40.757Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ldutkKTyxiCVnPYiWcMdxg.jpeg" /></figure><p>“Is the glass half-empty or half-full?” That isn’t simply a cute riddle to ask children or a tired cliché used by armchair psychologists.</p><p>When a number of people are involved in the app development process, particularly when they’re coming from different backgrounds (for example a product development team, a financial manager and an app designer), they’re bound to view things quite differently.</p><p><strong>Time</strong> is one of the greatest obstacles a company faces when building an app.</p><p>The product must be fine-tuned and ready for market before any potential competitors<em> enter</em> the same space.</p><p>And nothing wastes more time than confusion over the goals and specs for an app; misunderstandings or miscommunications often send a designer back to the drawing board time after time, in order to “correct” problems that never should have arisen in the first place.</p><p>Proper communication is crucial when developing an app.</p><p>One of the best ways to facilitate that communication is by creating a <strong>products requirements document</strong> (PRD) before work actually begins.</p><p><strong>How Do You Construct a PRD?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8JIRCBwOXw3-8mjeev3x9g.jpeg" /></figure><p>In reality, there are <strong>two key reasons</strong> for creating a products requirements document.</p><p>The first is to ensure that <em>all </em>members of the in-house team, from business experts to “idea” people, are on the same page.</p><p>The second gives the designer a clear roadmap to the functionality and features he needs to include.</p><p>The best way to construct a PRD is to answer a series of important questions in written form, to make sure that nothing is left out.</p><p>Some of the answers will undoubtedly be valuable for everyone involved in the process, but to make things easier we’ll break them down into the “business” and the “technical.”</p><p><strong>Business Questions to be Answered in a PRD</strong></p><p>All of these questions should be discussed and agreed upon (as much as possible) by the members of the in-house development and business teams, although preliminary participation by the designer on functional issues can definitely be helpful.</p><p>As you’ll see, many of the answers give the designer important information he’ll need — particularly the ones dealing with functions and features.</p><p>· Why do we want to build this app? What problem will it solve? What user needs or desires will it fill? In short, what’s the overriding vision?</p><p>· Exactly how will the app work, and who is the target audience? What functions and features will it provide and what level of expertise will users need to use it? Sample user profiles and a general flow chart can be enormous assets here.</p><p>· Does the same or a similar app already exist?<br> If so, would ours be an improvement or advancement that people would actually be motivated to download? Can we take the existing product and build on its functionality or the successes and failures of its developers?<br> If not, has someone already gone down this road and<strong> failed</strong>? If they have, was it because of technical or design failures, or was the market simply not interested in the app?</p><p>· Do we already have a platform or similar product which can be modified or added to, in order to build the new app?</p><p>· How big is the prospective market for this app, what marketing channels will we use to promote it, what’s the proposed financial model and is the project economically viable?</p><p>· How important is the success of this app to our company goals?</p><p>· What assumptions are we making which may have to be revised during the development process?</p><p>Once these questions have been answered, it’s time to move on to the second part of the PRD — which will largely determine whether you end up with a success or a turkey.</p><p><strong>Technical Questions to be Answered in a PRD</strong></p><p>A few of the major technical considerations for an app have already been addressed in the “business” section of the products requirement development, such as the target users and the features to be included.</p><p>Much more specificity is needed in the “technical” section, and here are key questions to answer in that part of the PRD.</p><p>· Which platforms must the app operate on, and are there multiple platform/OS versions to be supported?</p><p>· Are there current company or third-party software and standards to be accommodated, or are there existing hosting, developer and analytics accounts, APIs or other services (such as GPS locators) which must be utilized for development? If new services or credentials must be acquired, which ones are necessary and/or preferred?</p><p>· How will the app be supported after its release and will future versions be provided? If so, how long will the initial version be viable, and on what timetable will updates be required?</p><p>· Will there be a premium or members’ area, and how will the verification process work with the company’s servers or outside providers? Will there be e-commerce functionality and which provider(s) should be used? Does there need to be an offline mode?</p><p>· Does the app need to be compatible with existing third-party app distribution stores or models?</p><p>· What company and user documentation will be required?</p><p>· Are there any budgets or financial constraints to be aware of?</p><p>· What is the timeline for creation of a prototype (if desired), an MVP, further iterations and final release? What criteria must be met at each stage?</p><p>One final ingredient must be included in a PRD — and it can’t be expressed by a sentence or paragraph.</p><p>The general flow chart for the app discussed earlier is helpful for in-house and preliminary use, but its non-specific nature can cause a designer to either flounder or go off in an <em>unanticipated</em> direction.</p><p>A detailed sitemap (with wireframes, if possible) will ensure that the designer has a clear picture of the layout, user experience and functionality you envision.</p><p>And descriptions of each page in the map will avoid the “I just assumed that you’d include a search box” conversations that cost a great deal of time (and often expense) in discussion and redesign.</p><p>Detailed sitemaps and descriptions also provide a baseline for the weekly update meetings or conversations you should be having with the designer.</p><p>When <em>inevitable</em> problems crop up and changes are needed, the documentation allows everyone involved in the process to visualize the alterations being considered, and agree on the best way <strong>forward</strong>.</p><p><em>Need a hand with getting your PRD constructed? Don’t have the time or budget to hire an in house developer and designer? Let us take the stress off of your shoulders, visit </em><a href="http://ideaction.io/"><em>Ideaction.io</em></a><em> to schedule a call today</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cd81b76a232" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackerbaycompany/building-an-mvp-prepare-a-products-requirements-document-first-6cd81b76a232">Building An MVP? Prepare A Product Requirements Document First</a> was originally published in <a href="https://medium.com/hackerbaycompany">HackerBay</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Static analyzers for Swift and Objective-C]]></title>
            <link>https://medium.com/hackerbaycompany/static-analyzers-for-swift-and-objective-c-5adb53c848e8?source=rss----99ccbc404747---4</link>
            <guid isPermaLink="false">https://medium.com/p/5adb53c848e8</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[static-code-analysis]]></category>
            <category><![CDATA[swift-programming]]></category>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[objective-c]]></category>
            <dc:creator><![CDATA[Zorin Evgeny]]></dc:creator>
            <pubDate>Tue, 30 Jan 2018 18:26:32 GMT</pubDate>
            <atom:updated>2018-01-31T20:40:57.449Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://habrahabr.ru/post/321162/">(Version in Russian)</a></p><h4>Foreword</h4><p>There is a number of <a href="https://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis#Objective-C.2C_Objective-C.2B.2B">articles</a>, devoted to the static analyzer for C/C++/C#, Java, etc. Concerning research activities in the use of various static analyzers for native development for MacOS / iOS, they are paid much less attention.<br> <br> This article offers an analysis of the application of the static code analyzers that are used in different on ObjC — and Swift-based projects. At the same time, this is not a review, but rather some application notes of various tools to find errors of one or another kind of the code, starting from the memory leaks and finishing by vulnerabilities searches. However, the data do not pretend to objectivity and completeness of the findings, as well as the depth of results obtained analysis on each tool.</p><h4>Introduction</h4><p>Several years ago, being still a beginner iOS developer, I faced with the problem of verifying the quality of code written in ObjC for the iOS application. Unfortunately, I didn’t always succeed to find mistakes and to discuss the code with more skilled colleagues in the absence thereof. The first negative feedbacks, though they were perceived constructively, but anyway, led to the loss of customers who wanted to evaluate the examples of code developer before the conclusion of the contract. As a result, there has been a need for application of tools that identify a maximum of code defects before displaying them to the customer. I note, it was always important to get reports on the quality of the code in <a href="https://en.wikipedia.org/wiki/Continuous_integration">Continuous Integration</a>, after the all the commits to identify potential problems in the developed product.<br> <br> I had to work in different teams with different projects from solo to distributed ones, with a team located on different continents. The skill level of the colleagues ranged from entry level up to architect’s one. The teams’ composition was analogically and constantly undergoing changes and this despite the fact that every year the new versions of Swift appeared and ObjectiveC was <a href="https://developer.apple.com/library/content/releasenotes/ObjectiveC/ModernizationObjC/AdoptingModernObjective-C/AdoptingModernObjective-C.html">not standing still</a>.<br> <br> All these factors stimulated the search for tools to identify the maximum number of errors and to make the code more consistent and easy to read.</p><h4><a href="http://clang-analyzer.llvm.org/">Clang Static Analyzer</a></h4><p>This is the first built-in analyzer, which any XCode-user meets. To analyze the code each time the application is started, it is necessary to make settings described <a href="https://github.com/boredzo/Warnings-xcconfig">here</a>. These guidelines should be used by all users as the first step of verification code before each its commit.<br> <br> The lack of support for Swift strongly limits the fields of its use. Of course, in XCode, there is <a href="http://clang.llvm.org/docs/AddressSanitizer.html">Address Analyzer</a> and <a href="http://clang.llvm.org/docs/ThreadSanitizer.html">Thread Sanitizer</a>, which supports Swift — but these tools are not static analyzers and can be used only when running an application, that is run time.<br> Suitable for a preventive search of potential memory-leaks and errors in the code structure.</p><h4><a href="http://fauxpasapp.com/">Faux Pas</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WYLze1i_T1ANbF7SH38gbg.png" /><figcaption>Main Faux Pas Report after analysis ObjC project</figcaption></figure><p>Faux Pas (<em>wrong step- Fr.</em>) — the first third-party static analyzer, with which I had to face, having a full-fledged GUI and CLI. After the start of its use, the code quality was noticeably higher. It helped to identify in my on ObjC-projects from 20% to 50% of the hidden bug. The most curious one was the fact that at the first its run the tool identified exactly those mistakes that the customer noticed. That was the main argument why, in fact, it was decided to get this tool for private money of the developer rather than to wait until the entire company would make active use of it.<br> <br> Unfortunately, not all colleagues perceived this instrument positively — some felt that the analyzer should be free of charge, others — complained about a large number of settings, not wanting to understand them.<br> <br> The main drawback — the lack of Swift-support, but the developers promise its <a href="http://fauxpasapp.com/faq/#does-faux-pas-support-swift-code-in-my-projects">support</a>, at least for now they do not announce the date.<br> <br> The less important problem — is that <a href="http://fauxpasapp.com/faq/#does-faux-pas-support-xcode-workspaces">the workspaces are not directly supported</a> — it has to be checked either through the command line (to configure the workspace check), either individually by each project, that, in turn, is not always convenient.<br> <br> Nevertheless, Faux Pas finds problematic areas of code that are contrary to Apple Coding Guidelines. For example, <a href="https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/ProgrammingWithObjectiveC/EncapsulatingData/EncapsulatingData.html#//apple_ref/doc/uid/TP40011210-CH5-SW6">the use of self.propety in init and dealloc,</a> reminds about the use of Modern ObjC syntax, Missing NSNotificationCenter observer detachment and <a href="http://fauxpasapp.com/rules/">so on.</a> Easily <a href="http://fauxpasapp.com/blog/2014/continuous-integration/">integrated into the CI.</a><br> <br> The generated report in Json or plist is better to convert into something more readable. The report contains a detailed description of the problem; it also provides links to external rules. Despite the fact that, sometimes, the references rely on stackoverflow, but not the white paper, it is still not a significant disadvantage.<br> <br> The example of results of done work of the tool is given above. To run the analyzer in the XCode, for subject problem detection, it’s possible to use CLI.</p><p>To analyze the report presented in JSON a small application was written which generated reports in Excel with the sampling by each problem in the representation similar to the GUI FauxPas.<br> <br> Concerning configuration of the analyzer, the tool is configured with:<br> GUI, CLI arguments and configuration files. The way to create its own rules was not detected.</p><h4><a href="http://oclint.org/">OCLint</a></h4><p>The analyzer was first met in a small but long-lived project of a German company written in ObjC. The developers of this company were very conservative and did not want to transfer for Swift, because of the complexity of migration to the new versions of this language.<br> <br> Despite the fact that OCLint allows to change and add rules through <a href="http://docs.oclint.org/en/stable/devel/scaffolding.html#creating-rules-with-scaffolding">Scaffolding</a>, this, however, requires a lot of time. In the process of development in the company, the code will not be committed to the repository until all the alerts of the analyzer will be fixed. Some of the verification rules were not always processed correctly. To eliminate all the alerts of the analyzer it had to use workarounds (crutches), that made the team eventually to refuse from the support of this analyzer.<br> <br> Nevertheless, the analyzer allows to reveal:</p><ul><li>Empty operators if/else/try/catch/finally without expressions,</li><li>Unused local variables and parameters</li><li>Reports of high cyclomatic complexity</li><li>Responds to redundant code from the if operator and unused braces</li><li>Allows to find the inverted logic and variables redirection</li></ul><p>The analysis time of a small project is enough big (in comparison with the Clang analyzer), and if your project has not previously used this tool, it can give a huge amount of alerts that will complicate the primary analysis. That is why, if the wish to check the entire code base and receive a huge list of alerts is not available, you can write a small script that checks only changed files before commit, that is important for any analyzer.<br> <br> As a standard, it is <a href="http://docs.oclint.org/en/stable/guide/xcode.html">integrated</a> into XCode through <a href="https://gavrix.wordpress.com/2013/02/28/integrating-oclint-in-xcode/#more-117">build Script</a>.<br> <br> The tool is rather flexible, but, nevertheless, it would be good to have a more advanced heuristic analysis of the code, as this tool exists for a long time. Currently, there is a need in the plugin extensions for the XCode of this analyzer that would simplify its use significantly.</p><h4><a href="https://codebeat.co/">Codebeat</a></h4><p>The Cloud Codebeat analyzer supports both ObjC, and Swift, that was critically important when the product was selected for use in a specific project. One of the drawbacks was that the test was carried out only after a commit came to GitHub before pull request, thus making the development process slightly unstructured in our case. At the time of writing this article, the developers promised to release the automatic code review utility to completely minimize the participation of developers in the process. It is an urgent task, in connection with the irregular or inattentive checks of the code in teams of developers in some projects with a human review.<br> <br> It supports Swift + Obj-C, Python, and Ruby, that is very convenient for mobile development.<br> <br> The ObjC code analysis does not work satisfactorily. This is due to the fact that the company is focused mainly on the analysis of Swift code, and the work with ObjC has been added recently and requires a further construction.<br> <br> Regarding the product support, it is at the top position. Always there was an opportunity to contact the customer service for a day, and even at weekends, there was a necessary assistance.<br> <br> Regarding configuring <a href="https://hub.codebeat.co/docs/metrics-customization">metrics</a>, it can be done by creating its own json-file and by changing the validation rules. Nevertheless, the possibility to create new rules of verification or modify existing ones is absent. However, the developers assured me, this possibility is planned in the future.<br> <br> This tool is free for opensource projects and for private repositories, the <a href="https://codebeat.co/pricing">price</a> is not too high, by the way, the trial period lasts three months, that can be considered sufficiently democratic.</p><h4><a href="http://fbinfer.com/">Infer</a></h4><p>The Facebook product, which has <a href="https://code.facebook.com/posts/1648953042007882/open-sourcing-facebook-infer-identify-bugs-before-you-ship/">opened</a> its own code analyzer is suitable not only for the analysis of projects on iOS but for Android/Java- development.<br> <br> Immediate running of the analyzer in the command line for the test project failed, but after the creation of the <a href="https://github.com/facebook/infer/issues/552">query for</a> Github, I was let into some of the subtleties of its settings. I even managed it to integrate into XCode using the <a href="https://developer.apple.com/library/content/documentation/OpenSource/Conceptual/ShellScripting/Introduction/Introduction.html#//apple_ref/doc/uid/TP40004268-TP40003516-SW1">“Run build script”.</a><br> <br> To run the analyzer further it was created an additional scheme — Infer in Xcode, by analogy with other analyzers that use CLI. In the particular case, the big benefits of its use were not identified. Perhaps it makes sense to use this tool in other larger cross-platform complex projects.</p><h4><a href="https://github.com/realm/SwiftLint">SwiftLint</a></h4><p>Very popular among the Swift-developers analyzer is that one which has a <a href="https://github.com/norio-nomura/SwiftLintForXcode">plugin for the XCode</a>, that is very convenient.<br> <br> The <a href="https://github.com/github/swift-style-guide">GitHub’s Swift Style Guide</a> was taken as a basic rule. There is a possibility of creating own regex-based verification rules. In particular, it is very easy to create rules for refactoring when new functionality is added to expand the classes of tools, for example, the NSLocalizedString() function is becoming simply a field in NSString (or String) class extension.<br> <br> In the specific case of the teams worked on distributed branches, which were without refactoring. With the help of «autocorrect» option, the code can easily be led to a common style when the code was merged into a single branch.<br> <br> SwiftLint was used in a big hybrid project containing both ObjC and Swift code. The author of the idea of its introduction into the project, unfortunately, did not know about the vicissitudes of «autocorrect» option application — and put checking in the «Run Script» in the Xcode. Of course, in large projects with a team that has no common synchronization point, not all set this tool immediately. At the same time, there was a migration for the Swift 3.0, that certainly added confusion to the new commits.<br> <br> Beginning from the 0.16.0 version, some rules of false positive alarms have appeared, for example, the <a href="https://github.com/realm/SwiftLint/issues/1234">large_tuple</a> projects ceased to be compiled through the build script. In addition, not all of the rules were properly processed that is common to many analyzers, and it forces to use the workarounds, which the code quality suffers. This problem made to relate more accurately to the introduction of SwiftLint into “Build phases script” for each project.<br> <br> This tool was also integrated into Jenkins, that obviously improved the control over the code base project.</p><h4><a href="https://github.com/sleekbyte/tailor">Tailor</a></h4><p>Tailor is a cross-platform static analyzer for Swift. Quite unusual is the fact that the Windows platform is supported thereof.<br> <br> It was used as an alternative to the SwiftLint based on pilot projects. However, at this time it only supports Swift 2, that does not meet modern requirements a little. However, there is an <a href="https://github.com/sleekbyte/tailor/issues/469">issue enchantment</a> for Swift 3.0.1 support. It supports code style rules for the Swift Programming Language, GitHub, Ray Wenderlich, and Coursera.<br> <br> To support the pods and the workspace it is recommended to use the following <a href="https://github.com/sleekbyte/tailor/issues/470#issuecomment-274246972">recommendation</a>.<br> <br> The ability to create its own custom rules is not observed, although the probability that it exists, is available, but this should be carefully studied out.<br> <br> It is integrated into Xcode through the “Build Script”. To suppress the alerts like <a href="https://github.com/sleekbyte/tailor/wiki/Rules#trailing-whitespace">trailing-whitespace</a>, which immediately begin to put to trouble from the first its usage.<br> It is recommended to use the keys:</p><p><em>tailor — </em><strong><em>except</em></strong><em>=brace-style,trailing-whitespace</em></p><p>The report by wish can be displayed in HTML, JSON or XCode format that is convenient enough for the use in CI when publishing the results on the web server.</p><h4>Formatting in Swift Style</h4><p>Speaking of the analyzers it can not be but mentioned about the code “formatters” for a specific style guide.<br> Despite the fact that they are not static code analyzers, and as well format code to Swift Style, however, they serve the same purpose of detecting errors by bringing code to a single style, allowing better to perceive the code by the programmer and, consequently, to quickly identify the problem sections of the code.</p><h4><a href="https://github.com/nicklockwood/SwiftFormat">SwiftFormat</a></h4><p>It is convenient because it gives the ability to create its own rules to meet the specific code style command. The configuration takes place by means of CLI, which can not be by all liked. Nevertheless, it can be installed as a plug-in for XCode.</p><h4><a href="https://github.com/Jintin/Swimat">Swimat</a></h4><p>The tool can be used both as by CLI, and Xcode extension. It is, indeed, a good tool, even though it contains several critical bugs that lead to a drop of the XCode during its use. However, the developer quickly eliminates them. The ability to add your own <a href="https://github.com/Jintin/Swimat/issues/112">verification</a> rules are available.<br> <br> In the particular case, it was used for formatting a small project code, which proved to be the best one in terms of convenience and given results.<br> <br> Both formatters are comfortable to use as an extension for XCode, and at the moment they are supported and improved.</p><h4><a href="https://www.checkmarx.com/">Checkmarx</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MA7fVFfYaaQ46WD3OCeapw.png" /><figcaption>General report page</figcaption></figure><p>In fact, at times, there are projects from customers, who are critically related to the manufactured product. For such projects, it is better to use the <a href="https://www.checkmarx.com/glossary/static-application-security-testing-sast/">Static Application Security Testing (SAST)</a> solution for source code audit of the company Checkmarx.<br> <br> This cloud-based solution, that is, the tool, can be located either on the local server for development or on the company’s server Checkmarx. It is a well-advanced analyzer, which uses its own patented technologies. Checkmarx, which earlier worked closely with the US Department of Defense, has a lot of interesting developments concerning the research of various vulnerabilities. It maintains Swift, but in the specific case, the ObjC project was under analyzing. Unfortunately, it does not have the plugin extension for Xcode.<br> <br> Reporting is very informative and presentable. One of the pages is cited above.</p><p>The informative report may contain from 10 to 300 pages, depending on your project. The report also gives an explanation on how to fix the problem, and even the examples are cited. A common mistake for all the projects that were analyzed was “Third Party Keyboard Enabled”, that was associated with a possible vulnerability when installing third-party keyboards for iOS (though, one of the analyzed applications didn’t contain the keyboard input fields).</p><h4>Afterword</h4><p>Some tools for static code analysis would be still good for an acquaintance in practice, eg, <a href="https://www.sonarsource.com/why-us/products/languages/swift.html">Sonar</a>. However, due to the product high price and complexity of installing such a possibility has not come yet. At the same time for some interesting projects, it is of interest to try <a href="http://solarsecurity.ru/products/solar_inCode/">Solar inCode</a> to find vulnerabilities in the code for customers, worrying about the security of their applications. To my regret, this product could not be got even for the Demo-version.<br> <br> Many of the above-mentioned tools helped to create products more stable and more resistant to various vulnerabilities in the code. In principle, any analyzer — is an unbiased judge, to whom you are indifferent and have no personal claim to him, that makes the work more objectively and orderly.<br> <br> Nevertheless, it is obvious that there are no perfect tools, and even the use of all existing code analysis tools is not a silver bullet. Not to mention, the cases of false tool alarm when you have to use workarounds to meet the requirements of the analyzer. In this regard, the human review will always be important to at least identify semantic errors like “dragState”, instead “drugState” or “cacheData”, instead “cashData” (though you can set autocorrection option…).</p><h4>Useful links</h4><p>· <a href="https://codeascraft.com/2014/01/15/static-analysis-with-oclint/">Static Analysis with OCLint</a></p><p>· <a href="http://abrahamkang.blogspot.ru/2016/04/getting-most-out-of-static-analysis-and.html">Guide for Static Analysis.</a></p><p>· <a href="https://atscaleconference.com/videos/getting-the-most-out-of-static-analyzers/">Getting the most out of static analyzers</a></p><p>· <a href="https://realm.io/news/slug-jp-simard-swiftlint/?utm_campaign=iOS%2BDev%2BWeekly&amp;utm_medium=email&amp;utm_source=iOS_Dev_Weekly_Issue_283">«Watch Your Language!»: The Road to Cleaner Code with SwiftLint</a></p><p>· <a href="https://developer.apple.com/videos/play/wwdc2016/412/">Thread Sanitizer and Static Analysis</a></p><p>· <a href="https://developer.apple.com/library/prerelease/content/documentation/DeveloperTools/Conceptual/debugging_with_xcode/chapters/about_debugging_w_xcode.html">About Debugging with Xcode</a></p><p>· <a href="https://clang.llvm.org/docs/ClangFormat.html">ClangFormat</a></p><p>· <a href="https://github.com/nst/objc_dep">Graph the import dependancies in an Objective-C project</a></p><p>· <a href="http://uncrustify.sourceforge.net/">Uncrustify</a></p><p>· <a href="https://pmd.github.io/pmd-5.4.1/usage/cpd-usage.html">PMD</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5adb53c848e8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackerbaycompany/static-analyzers-for-swift-and-objective-c-5adb53c848e8">Static analyzers for Swift and Objective-C</a> was originally published in <a href="https://medium.com/hackerbaycompany">HackerBay</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why optimization is everything in mobile AR and VR]]></title>
            <link>https://medium.com/hackerbaycompany/why-optimization-is-everything-in-mobile-ar-and-vr-b54a5dc411b5?source=rss----99ccbc404747---4</link>
            <guid isPermaLink="false">https://medium.com/p/b54a5dc411b5</guid>
            <category><![CDATA[augmented-reality]]></category>
            <category><![CDATA[mobile-application]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[virtual-reality]]></category>
            <category><![CDATA[optimization]]></category>
            <dc:creator><![CDATA[Umbra 3D]]></dc:creator>
            <pubDate>Tue, 30 Jan 2018 08:57:52 GMT</pubDate>
            <atom:updated>2018-01-30T08:57:52.441Z</atom:updated>
            <content:encoded><![CDATA[<p>Creating high performance AR/VR applications is challenging. Here are five reasons why it’s especially challenging on mobile devices.</p><h3>1. High frame rates drive great user experience</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*T7rUcsGlLbN3N1uP.jpg" /></figure><p>High application frame rate is key to a great user experience. Without it, user interface response is slow, making every user input feel choppy or delayed. Worst of all, fluctuating frame rates are a leading cause of nausea for users in AR and VR applications. Simply put, the frame rate for an AR application should never drop below 60 frames per second. And for VR, a constant 120 fps is ideal, as motion sensitivity is heightened in a fully enclosed experience with no externally visible static reference points.</p><p>However, achieving such high numbers is not easy. At 60 fps there’s only 16 milliseconds to render each frame and process everything the application needs to deliver a quality user experience. At 120 fps, the time is cut to half of that.</p><p>In most 3D applications, the graphics create the greatest processing load. While there is very powerful graphics hardware available for desktop computers that can process highly complex 3D, the hardware available for mobile devices is far more limited due to power and thermal constraints. For these resource-constrained mobile AR and VR devices, automated graphics optimization is the most important part of achieving the performance required for a smooth and responsive experience.</p><h3>2. Better performance means longer battery life</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/489/0*ZB34szaWpBZIbto9.jpg" /></figure><p>3D and especially pass-through AR, such as the Apple ARKit, demands a great deal of performance from mobile rendering hardware. Almost every component of the device is involved in creating the user experience, putting a huge strain on power consumption. With highly optimized code and content, a mobile device’s battery will last considerably longer, leaving users with ample power to do other critical things with their devices like, say, make a phone call. If the optimized 3D enables the processor to work less hard to achieve a reasonable frame rate, the device will literally consume less battery power per frame rendered.</p><h3>3. Very high resolution is needed for AR and VR</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*TqitKrtPFEW4WSk2.jpg" /></figure><p>Mobile devices nowadays have impressive displays with super sharp images. The sharp image is the result of high resolution — current mobile displays boast millions of pixels. In immersive 3D applications every single pixel needs to be updated every single frame, causing a massive amount of work for the graphics processing unit. And the more impressive the graphics, the more work is needed from the GPU.</p><p>However, for realistic AR and VR experiences of the future, today’s resolutions are not nearly enough. Because AR/VR displays are so close to users’ eyes and partially magnified through lenses, they will need even higher resolution to prevent our eyes from noticing the individual pixels. This problem can be seen today with currently available headsets.</p><p>Solving this challenge will be a big challenge, especially on mobile. There are companies like <a href="http://varjo.com/">Varjo </a>tackling the hardware resolution problem, but all those extra pixels need to be rendered with content that matches the much higher resolution.</p><p>All this adds up to much more work for the processors and a lot more memory and bandwidth needed for delivering the content. Intelligently optimizing 3D will be an essential piece of the delivery process to ensure that super high-quality content can actually be rendered in high fidelity on end user devices.</p><h3>4. High resolution 3D content takes up a LOT of space</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*ieD4eBL-6Ee1KiMG.jpg" /></figure><p>Compared to static content such as photos or video, interactive 3D content needs to work from any camera angle and location. The data size requirement for achieving the desired resolution from every possible view point can easily grow to be hundreds of gigabytes or even terabytes, and just storing and transferring those amounts of data becomes a challenge in itself. On desktop machines this problem is (relatively) easy to solve with hardware by just adding more disk space. Obviously, this is not viable alternative on mobile.</p><p>Optimization will be key for enabling mobile devices to render large, complex 3D scenes and objects given that storage capacity on these devices is limited…especially since that storage space is potentially shared with other assets such as personal photos, videos and music.</p><h3>5. Users expect fast app startup and loading times</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*OrqoLTUTEfs21xo0.png" /></figure><p>Mobile application users expect a smooth user experience which includes a snappy user interface and fast application installation and startup times. Downloading the content required for 3D applications, or simply loading pre-installed content into active memory at start-up time could take much longer than the user is willing to tolerate.</p><p>To avoid this, 3D data should be streamed to the device. That said, true 3D content streaming is a lot more complicated than, for example, video streaming. Solutions where the rendering is done in the cloud and only the resulting images are streamed don’t really work in interactive 3D applications. Simply put, the resulting round trip latency is too high for a good user experience. Keeping the rendering on the end-user device and streaming the content as optimized 3D models is the only future-proof solution.</p><p>Umbra creates solutions for optimizing and delivering 3D content for current and future devices.</p><ul><li>If you are developing your own AR or VR application, you can test our <a href="http://umbra3d.com/signup">Unity integration for free</a></li><li>If you work with BIM, CAD or other 3D design, you can use our <a href="https://info.umbra3d.com/ios-app">iOS application</a> to bring your designs to life in augmented reality</li><li>Read on our thoughts on the <a href="https://blog.umbra3d.com/blog/3dcontentarcloud">AR cloud</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b54a5dc411b5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackerbaycompany/why-optimization-is-everything-in-mobile-ar-and-vr-b54a5dc411b5">Why optimization is everything in mobile AR and VR</a> was originally published in <a href="https://medium.com/hackerbaycompany">HackerBay</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Forget datasource & delegate: a new approach to UITableView]]></title>
            <link>https://medium.com/hackerbaycompany/forget-datasource-delegate-a-new-approach-to-uitableview-b61dc9a99ba7?source=rss----99ccbc404747---4</link>
            <guid isPermaLink="false">https://medium.com/p/b61dc9a99ba7</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swift-programming]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[declarative-programming]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Daniele Margutti]]></dc:creator>
            <pubDate>Thu, 25 Jan 2018 17:05:18 GMT</pubDate>
            <atom:updated>2018-04-28T08:05:47.397Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong><em>A new updated version of this article, containing a new efficient approach and support for UICollectionView is </em></strong><a href="https://medium.com/@danielemargutti/tables-collections-with-type-safe-declarative-approach-fa3efbf590d?source=linkShare-c71a0dc753e2-1524430910"><strong><em>available at this link</em></strong></a><strong><em>.</em></strong></blockquote><p>TableViews are everywhere; for years before the introduction of Collection Views they were one of the fundamental block of every application’s.<br>Even if now we are able to replace the entire functionality with the combo of UICollectionView &amp; UICollectionViewFlowLayout (<em>take a look at “</em><a href="https://pspdfkit.com/blog/2017/the-case-for-deprecating-uitableview/"><em>The case for deprecating UITableView</em></a><em>“</em>) they still play a key role during the everyday work life of any iOS developers.</p><p>Frankly I always hated the way in which we prepare and manage contents inside table for several different reasons:</p><ul><li><strong>tons of boilerplate code to declare data source &amp; delegates</strong>. I loved the datasource/delegate pattern, but we can do better and we can do it in Swift, of course.</li><li>it’s <strong>weak:</strong> declare cell via identifiers (literals!), cast and finally use them; in our new strong-typed world this is a nightmare we need to avoid.</li><li><strong>complex tables are a nightmare to prepare and manage; </strong>usually you will end up in a world full of if/switch conditions to allocate one cell instead of another, do an action if the you tapped this or another cell and so on. I just want to declare content and do actions.</li><li><strong>Your view controllers are easy to become full of apparently-non-sense-conditions</strong> used to manage the content of your tables.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*bB6IUaYV0vGOkJgxbrsIsg.gif" /><figcaption><em>By Alex Kao (http://alexkao.ninja)</em></figcaption></figure><h3>What you will get</h3><p>In this article you will get a different way to play with UITableView ; it’s called <strong>declarative approach</strong> and it allows to simplify the entire workflow to manage the content of the table views.</p><p>The following code is the only code you need to populate a table with football players and manage the tap on each:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c42d064cdae94b465a650f0bbc42007/href">https://medium.com/media/3c42d064cdae94b465a650f0bbc42007/href</a></iframe><p><strong>Just few lines of code, no delegate, no data source.<br></strong>Everything is clean and readable and you can manage even complex layouts and operations (add/remove/move sections and rows) with simplicity and cleanliness.<br>Let’s do it!</p><h3>A declarative approach</h3><p>Once your table is generated dynamically you may need to add, remove or show particular cells or sections based upon conditions or events; moreover you need to fire the right actions based upon selected cell: both your numberOfRows , cellAtIndex and didSelect delegate functions are easy to become a hornet’s nest of if/switch conditions (<em>if tapped cell is that but you are not logged in, but when are logged the index is plus one because you have the other cell</em>… does this remind you of anything?).</p><p>A declarative approach is able to solve this and other problems.<br>My goals are:</p><ul><li><strong>Cell rendering is a business of the cell</strong>. Let the cell do its damn job. If you still using tableView(tableView: UITableView, cellForRowAtIndexPath indexPath:IndexPath) as root for your rendering its time to stop that. Make your code <a href="https://www.google.it/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=14&amp;cad=rja&amp;uact=8&amp;ved=0ahUKEwiS8K7KxuHWAhXF7hoKHfTPDikQFghpMA0&amp;url=https%3A%2F%2Fscotch.io%2Fbar-talk%2Fs-o-l-i-d-the-first-five-principles-of-object-oriented-design&amp;usg=AOvVaw1ovYKcT16hO8PyaJUy9_wQ"><strong>SOLID</strong></a>.</li><li><strong>Its time to make a step forward from DataSource/Delegate</strong>. Setup the cell’s class, a model and use declarative methods to add/remove or manage rows into the table. No more data source, no more delegate, just <strong>plain understandable functions: </strong><em>add row, add section, remove row, move section…</em></li><li><strong>Type-safe cell allocation and automatic registration.</strong> Describe your cell classes, the model represented and let the library take care of the rest.</li><li><strong>Functional</strong>. Cell configurations is easy; you can observe events and manage the behaviour (<em>onTap, onSelect…</em>) of the cells in a pure functional manner.</li><li><strong>Support Auto Sizing</strong>. Easily supports Auto-Layout and provide a simple mechanism to specify the height of a cell or leave the class decide the best one upon described constraints.</li><li><strong>Easy support for animations</strong>. Like as performBatchUpdates for UICollectionView we want manage automatically the animations related to content change <em>(I don’t want to see what is changed and call the related animation function…it’s not my business)</em></li></ul><h3>The Architecture</h3><p>Our approach uses three basic elements to describe the table and its content:</p><ul><li>TableManager : this class manage the data of the table, it expose functions to add/remove or move <em>cells</em> and <em>sections</em>. You will allocate an istance of TableManager for each UITableView : it will be only dataSource and delegate of the table itself.</li><li>Section : it represent a section into the table: it may contains Rows , optional header / footer (as plain Strings or custom UITableViewHeaderFooterView subclasses ). You will refer to the function of Section to add/remove/move rows (<em>cells</em>).</li><li>Row : it represent the single row (a <em>cell</em>); it’s an open class conforms to RowProtocol : it defines the UITableViewCell class used to render data and the model accepted by the cell: once needed the cell will receive the instance of your model and you will be able to render your data.</li></ul><p>Each Row is created with a model instance and a represented cell; each Section is created with Row array, optional header/footer. TableManager is the entry point to manage the content displayed.</p><p>That’s all!</p><p>The following diagram explain how the architecture works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/945/1*fMN2JpldhK0knqKbS4x_kg.png" /></figure><p><strong>…This article continues on my blog; </strong><a href="http://danielemargutti.com/2017/10/08/forget-datasource-delegates-a-new-approach-to-uitableview/"><strong>click here to show it</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b61dc9a99ba7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackerbaycompany/forget-datasource-delegate-a-new-approach-to-uitableview-b61dc9a99ba7">Forget datasource &amp; delegate: a new approach to UITableView</a> was originally published in <a href="https://medium.com/hackerbaycompany">HackerBay</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[12 Weeks as an iOS Developer Apprentice]]></title>
            <link>https://medium.com/hackerbaycompany/12-weeks-as-an-ios-developer-apprentice-89a61829ec12?source=rss----99ccbc404747---4</link>
            <guid isPermaLink="false">https://medium.com/p/89a61829ec12</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swift-programming]]></category>
            <dc:creator><![CDATA[Justine Kay]]></dc:creator>
            <pubDate>Thu, 25 Jan 2018 13:15:49 GMT</pubDate>
            <atom:updated>2018-01-25T13:15:49.331Z</atom:updated>
            <content:encoded><![CDATA[<h3>Week 12</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*6-haJT-SLbUMRM7j3J-b9g.jpeg" /></figure><p>What a crazy awesome ride it has been.</p><p>Week 12 of 12 I continued to work on the same client project without interruption. It was pretty similar to the previous 4 weeks of learning and growth <em>except…</em></p><p>I also signed an offer to start as a full-time iOS developer in Intrepid’s New York office beginning immediately the following week.</p><p>I’m truly honored to be a part of such a fabulous team.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3o85xuZs2EDXdulprW%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fsuitsusanetwork-suits-rachel-zane-3o85xuZs2EDXdulprW&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3o85xuZs2EDXdulprW%2Fgiphy.gif&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/32a5f7336d730f9d791108c46af516b6/href">https://medium.com/media/32a5f7336d730f9d791108c46af516b6/href</a></iframe><p>Last year I was fortunate to have been accepted into a highly selective, rigorous and hands-on iOS development program. Here’s a little more about <a href="https://medium.com/@JustineBethKay/creating-a-more-inclusive-tech-community-ea034ccda2b2#.tnauo5ux7"><strong>Access Code</strong></a> and <a href="http://www.c4q.nyc/"><strong>Coalition for Queens</strong></a>.</p><p>I worked hard and the Access Code program gave me a solid base of knowledge and educational experience. It fully prepared me for the next step: turning that education into a profession.</p><p>I came to Intrepid hoping the apprenticeship would provide that step and I definitley got what I came for.</p><p>Here’s what I gained in 12 Weeks as an iOS Developer Apprentice:</p><h4>Professional Experience</h4><p>I needed experience working in the field with other developers and product professionals on big projects with deadlines and clients to answer to.</p><p>The appenticeship gave me many opportunities to work with other developers, product managers, designers and even clients.</p><p>Mentorship started from the very beginning. We were each assigned a mentor and everyone else who worked there was also very open and willing to help whenever asked.</p><p>The first two weeks were lectures on tools and work flow. It was a solid introduction on how the entire team at Intrepid works to communicate and produce effectively and efficiently.</p><p>The apprentice project gave me an opportunity to build a product from scratch on a tight deadline with a project manager and more experienced software engineers as mentors.</p><p>Working on the client project exposed me to a complex, fully developed codebase. The tasks I was assigned gave me just enough responsibility to ease me into the process and just enough challenge to feel like I was truly accomplishing something.</p><p>I was introduced to clients as a member of the team. This was key. It made me feel like I really was making a valuable contribution, even just as an apprentice.</p><h4>Professional Skills</h4><p>I needed to dive into fully functioning projects written by more experienced programmers and contribute to them. I needed to be able to reach out to those same programmers when I had a question. I needed them to review my code and give me critical feedback.</p><p>The engineers at Intrepid are conscious of the legacy they will leave behind. They’re not interested in just hacking together a project. There is genuine care and concern for producing quality code.</p><p>This was very important to me in my search for professional opportunities. I believe in code as craft and I’m always looking for ways to become a better engineer. I wanted to join a team of individuals that matched my strong work ethic and high aspirations.</p><p>Through the apprenticeship I had the opportunity to work with so many like-minded individuals that are dedicated to their craft and passionate about becoming better at what they do.</p><p>Continuous learning and improvement is important to me no matter how experienced I may become. It was crucial for me to find a culture that actively practices this and nurtures those who are new and less experienced as well.</p><p>Not only for my own benefit as a junior, but so that when I became more experienced I would be in an environment that supported me in giving back to the community through mentoring new juniors.</p><p>Everyone at Intrepid was super supportive and willing to share their experience and knowledge. There truly is a culture of teaching, learning, and continuous growth thriving here.</p><p>I ended up feeling very much at home.</p><p>Writing this blog has really helped me solidify some of the knowledge I’ve gained. It would have been impossible to condense everything I’ve learned into these weekly posts, but I tried to share as much as possible.</p><p>It was important for me to practice the art of explaining complex topics in a simple and understandable way. I believe it’s one of the best ways to deepen your own understanding.</p><p>I also felt a responsibility to share my experience as a junior in order to help and encourage others just starting out. Technical blogging as a junior is far from fear-free, but the more opportunities you give yourself to verbalize what you’re learning, the better.</p><p>You’ll be able to better explain yourself and your ideas to your colleagues and seniors as well as to clients and family members who have absolutely no idea what it is you actually do.</p><p>Being able to communicate effectively and efficiently across levels is a huge part of becoming a professional.</p><p>And when we share what we know, we not only take responsibility for our own growth and development but we simultaneously nurture community.</p><p>So I will continue to write and contribute in other ways as much as I can to help foster a community in which everyone can thrive.</p><p>Stay tuned and keep coding…</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fi.imgur.com%2F7ylJyoh.mp4&amp;src_secure=1&amp;url=https%3A%2F%2Fi.imgur.com%2F7ylJyoh.gifv&amp;image=https%3A%2F%2Fi.imgur.com%2F7ylJyoh.gif%3Fnoredirect&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=video%2Fmp4&amp;schema=imgur" width="300" height="300" frameborder="0" scrolling="no"><a href="https://medium.com/media/49d3569010ea4739cedcdce897ed920a/href">https://medium.com/media/49d3569010ea4739cedcdce897ed920a/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F1dcWGdOBg0wcU%2Ftwitter%2Fiframe&amp;src_secure=1&amp;url=http%3A%2F%2Fgiphy.com%2Fgifs%2Fwink-finger-guns-kristen-bell-1dcWGdOBg0wcU&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F1dcWGdOBg0wcU%2F200.gif&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="284" frameborder="0" scrolling="no"><a href="https://medium.com/media/b657709739083cd5ba49bc37f2faea17/href">https://medium.com/media/b657709739083cd5ba49bc37f2faea17/href</a></iframe><p>Feel free to reach out with any questions about <a href="http://intrepid.io/">Intrepid</a> or <a href="http://c4q.nyc/">C4Q</a>’s <a href="http://www.c4q.nyc/accesscode">Access Code</a> program. I’d be happy to hear from you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89a61829ec12" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackerbaycompany/12-weeks-as-an-ios-developer-apprentice-89a61829ec12">12 Weeks as an iOS Developer Apprentice</a> was originally published in <a href="https://medium.com/hackerbaycompany">HackerBay</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using PDF Pinner To Pin PDFs to Android Home Screen]]></title>
            <link>https://medium.com/hackerbaycompany/using-pdf-pinner-to-pin-pdfs-to-android-home-screen-2480121230bc?source=rss----99ccbc404747---4</link>
            <guid isPermaLink="false">https://medium.com/p/2480121230bc</guid>
            <category><![CDATA[pdf]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Paras Singh Sidhu]]></dc:creator>
            <pubDate>Tue, 23 Jan 2018 14:52:55 GMT</pubDate>
            <atom:updated>2018-03-03T15:57:11.630Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aES7y0Fp76gOtCdy7UmvYw.png" /></figure><p>This is a story (technical part included) about one of my recent android application. As a student, I need to access PDF files frequently. Every time I need to so, I need to open File Explorer or Adobe Acrobat and find the desired file to open it. Uff… very effort-some 😜 Being a programmer, we just love to automate our tasks. So I thought of putting the files straight to the home screen. But how will I do it, I thought? A quick Google search 🌐 and almighty StackOverflow showed that it’s easy to pin the files to home screen in Android using Intent. So as soon as my semester exams finished, I gone after this task. It was fun designing and coding the app and here’s how it looks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*iJ6om2NWqOAtmIt6lHOjPQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*Tqwnogvi5jFu_Tw9O41wWA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*Eql-SS0R7afmJeEGGj69YQ.png" /></figure><h3>Development</h3><p>The design part was easy and I used simple styled buttons, powerful RecyclerView and some radio buttons. The only thing here is that some design elements behave differently in Android Oreo due to its restrictive behaviour. More on it in later section.</p><p>Since the app should pin PDF files to home screen, it should be able to pin multiple files at once. To choose files, I used <a href="https://github.com/DroidNinja/Android-FilePicker">Android-FilePicker</a> library which provides user-friendly interface to select files of desired extension. Once user chooses the files, file name and path are passed to an ArrayList which is passed to our RecyclerViewAdapter to inflate the list in the main UI.</p><p>In main user interface, there’s an option to edit shortcut name. This option actually edits the name in ArrayList. Then user can choose from any of two icons and press Pin File(s) button to finish the task… wait not yet… 😐</p><h3>Android Oreo Support</h3><p>If you’re not on Android 8.0 or above, the files should have been pinned to home screen with a success message. But what if OS is Oreo or 8.0+? Google introduced a new ShortcutManager API in Oreo to handle pinning of any type of shortcut to home screen. This is done to ensure fake/spam apps don’t pin unwanted icons to home screen. But this new API comes with a restriction that you can’t pin multiple files in one go. You have to pin them one by one.</p><p>As I wrote before that some design elements will behave differently in Oreo, upon pressing “Pin File(s)” button, a system dialog will appear asking for permission.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/653/1*mB-xETH7K9i4Scv4sMCy0A.png" /></figure><p>Once you add this shortcut, PDF Pinner will ask you to “Pin Next File” if you have multiple files selected. You can press that to progress similarly. You can see the following code on how to use ShortcutManager API:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e876bf5fcf088ecbb4d98f07b9a10a2d/href">https://medium.com/media/e876bf5fcf088ecbb4d98f07b9a10a2d/href</a></iframe><h3>Wrap Up</h3><p>PDF Pinner is available to download in <a href="https://play.google.com/store/apps/details?id=com.parassidhu.pdfpin"><strong>Play Store</strong></a>. It’s one of my first open-source project and you can see full code in my Github repo:</p><p><a href="https://github.com/sidhuparas/PDFPinner">sidhuparas/PDFPinner</a></p><p>If you have some suggestions, you can create an issue in repo or make a pull request. I will be happy to further improve PDF Pinner 😃</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2480121230bc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackerbaycompany/using-pdf-pinner-to-pin-pdfs-to-android-home-screen-2480121230bc">Using PDF Pinner To Pin PDFs to Android Home Screen</a> was originally published in <a href="https://medium.com/hackerbaycompany">HackerBay</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Joget Workflow v6 Released]]></title>
            <link>https://medium.com/hackerbaycompany/joget-workflow-v6-released-8718320039a?source=rss----99ccbc404747---4</link>
            <guid isPermaLink="false">https://medium.com/p/8718320039a</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[jogetworkflow]]></dc:creator>
            <pubDate>Wed, 17 Jan 2018 12:00:10 GMT</pubDate>
            <atom:updated>2018-01-17T12:04:31.957Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s here! The Joget team is excited to announce that the stable version of <a href="http://www.joget.org/joget-workflow-v6/">Joget Workflow v6</a> is now released.</p><p>Joget Workflow is a modern open source low-code/no-code app development platform that makes it faster and easier to build enterprise applications and automate processes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xvQcEVYwqfH3jfRU." /></figure><h3>Feature Overview</h3><h4>App Center</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yNco7gaMm2y-Ew5h." /></figure><ul><li>The App Center is a customizable landing page providing users with quick and secure access to apps.</li><li>​Seamless integration with the <a href="https://marketplace.joget.org/">Joget Marketplace</a> allows for easy downloads of additional apps and plugins.</li></ul><h4>Processes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QIh15oIn6eTxBzoO." /></figure><ul><li>Drag and drop to visually build and configure process workflows.</li><li>Supports simple or complex processes including synchronous or asynchronous deadlines for reminders or escalation requirements.</li></ul><h4>Forms</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E-g_-faqTbZGWaTI." /></figure><ul><li>​Drag and drop to visually build and configure forms.</li><li>​Many powerful form elements for diverse needs including grids, spreadsheets, signatures, etc.</li></ul><h4>Lists</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gWs2XKonNWN_t8K3." /></figure><ul><li>Drag and drop to visually build and configure tabular lists and reports.</li><li>​Built-in support for filtering, sorting, paging and exporting to various document formats.</li></ul><h4>Userviews</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZiayEo_6hvQXZuoQ." /></figure><ul><li>​Say goodbye to uninspired user interfaces expected in business apps, drag and drop to build user interfaces that embraces Google’s Material design philosophy.</li><li>​Responsive to fit desktop and mobile devices, many powerful UI elements such as dashboards, calendar views, charts and many more are available.</li></ul><h4>Plugins &amp; Integration</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/0*q8XfjSNdjd8g62Hp." /></figure><ul><li>Dynamic plugin architecture allows for developers to extend functionality of the platform.</li><li>Integration to external systems via various APIs and plugins.</li></ul><h3>What’s New in Joget Workflow v6?</h3><p>With more than 1,600 installations worldwide across various industries (including finance, manufacturing, IT, and more), Joget Workflow v6 is the next generation of a proven platform for a wide spectrum of users ranging from Fortune 500 companies to government agencies and small businesses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*22lCrta5DTghU3mE." /></figure><p>Joget Workflow v6 has a two pronged focus: User Experience (UX), and App Maintainability and Performance:</p><h4>User Experience</h4><ul><li>Enhanced App User Experience for Desktop and Mobile</li><li>Customizable App Center with Joget Marketplace Integration</li><li>Dashboard Capabilities</li><li>Calendar View</li><li>Unobtrusive Admin and Design Interface</li><li>Design Apps Anytime, Anywhere with Support for Touch Devices</li><li>Excel-Like Functionality With the Spreadsheet Element</li><li>Improved User Experience with AJAX Support in Multi-Paged Forms</li></ul><h4>App Maintainability and Performance</h4><ul><li>Improved App Maintainability with Advanced Tools</li><li>Enhanced Configuration Options for Codeless Apps</li><li>Improved Performance with Userview Caching</li><li>Database Connection Monitoring and Leak Detection</li><li>Additional Plugins Out of the Box for Greater Flexibility</li><li>Latest Upgrades Under The Hood</li><li>Improved JSON Tool for Integration</li><li>Simpler Email Configuration with Platform-Wide Settings</li><li>Enhanced Security with Multi-Factor Authentication (MFA)</li></ul><p>Find out in more detail here: <a href="http://www.joget.org/joget-workflow-v6/">http://www.joget.org/joget-workflow-v6/</a></p><h3>Why Joget Workflow?</h3><p>Joget Workflow combines the best of business process management (BPM), workflow, and rapid application development in a platform that’s <a href="http://blog.joget.org/2016/11/the-3-key-principles-of-joget-workflow.html">simple, flexible and open</a>.</p><ul><li>Web-based visual approach empowers non-coders to build and maintain apps anytime, anywhere</li><li>Reduces time to market, from months to weeks or days</li><li>Apps built are mobile ready, cloud ready</li><li>APIs for integration and plugin architecture for extensibility</li><li>“App Store” for enterprise apps — Joget Marketplace</li></ul><p>The trend toward low-code and no-code open source platforms is disrupting the enterprise app development space. As the world becomes increasingly digital, software is more important than ever to enterprises as part of their <a href="http://blog.joget.org/2017/05/digital-transformation.html">digital transformation</a> strategy.</p><p>Instead of traditional enterprise software development approaches taking years of effort resulting in inflexible solutions, app development on the Joget Workflow platform is more accessible and manageable to coders and non-coders alike.</p><h3>Resources</h3><ul><li><a href="https://www.joget.org/download">Download Joget Workflow</a> or <a href="https://www.jogetcloud.com/">Sign Up for Joget Cloud</a></li><li>Learn more in the <a href="http://community.joget.org/">Knowledge Base</a></li><li>Join the community in the <a href="http://answers.joget.org/">Community Q&amp;A</a></li><li><a href="https://www.joget.org/enterprise-pricing">Enquire about the Joget Workflow Enterprise Edition</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8718320039a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackerbaycompany/joget-workflow-v6-released-8718320039a">Joget Workflow v6 Released</a> was originally published in <a href="https://medium.com/hackerbaycompany">HackerBay</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>