<?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[CodeNation Engineering - Medium]]></title>
        <description><![CDATA[CodeNation Engineering blog - Medium]]></description>
        <link>https://medium.com/codenation-engineering?source=rss----4696563e14f2---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>CodeNation Engineering - Medium</title>
            <link>https://medium.com/codenation-engineering?source=rss----4696563e14f2---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:05:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/codenation-engineering" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Fundamentals of networking in AWS]]></title>
            <link>https://medium.com/codenation-engineering/fundamentals-of-networking-in-aws-3ad3d0dc01dd?source=rss----4696563e14f2---4</link>
            <guid isPermaLink="false">https://medium.com/p/3ad3d0dc01dd</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Rishav Kumar]]></dc:creator>
            <pubDate>Sun, 01 Dec 2019 13:07:12 GMT</pubDate>
            <atom:updated>2019-12-01T17:18:50.414Z</atom:updated>
            <content:encoded><![CDATA[<p>People use AWS as a virtual datacenter, so they deploy various services there like EC2 instances, RDS instances, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IgMP3MHEnF8DpKIY" /></figure><p>Now, these instances/machines need to live somewhere in the datacenter and typically need to connect to the Internet. This is where VPC comes into the picture. I will use the term instance interchangeably with <em>machine</em> throughout this post. By <em>instance</em>, I mean the deployment of a service.</p><p>AWS has different regions, where it has its data centers. In those regions, we have availability zones. So if North Virginia is a region with id <em>us-east-1</em>, we have availability zones (AZs) <em>us-east-1a</em>, <em>us-east-1b</em>, <em>us-east-1c, etc.</em> They provide multiple AZs for resilience, so if one AZ is having some issues, deployments in other AZs won’t be affected. So you deploy your instances in a particular AZ, which in turn belongs to a particular region.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rcbSUJ3enu0eIJs-" /></figure><p>As you can see in the image above, VPC is an isolated network in a region, and it spans all the AZs in that region.<br>When you create an AWS account, it gives you a default VPC. I will explain what all things a default VPC offers, then I will show you how you can create one yourself.</p><p>A default VPC gives you four things -</p><ol><li>IP address ranges/CIDR block</li><li>Subnets in availability zones</li><li>Routers to route out to the internet</li><li>Security groups and network access control lists (NACLs) for security</li></ol><p>So, I will be talking about each of these 4 topics -</p><ol><li>IP addressing</li><li>Creating Subnets</li><li>Routing</li><li>Security</li></ol><p>In some places, I will also be explaining some standard networking terms like CIDR blocks, etc. If you are familiar with them, feel free to skip them.</p><h3>IP addressing</h3><p>In the default VPC, AWS gives you some range of IP addresses so that anything that will be deployed in that VPC will get an IP address from that IP address range. We denote IP address ranges with a CIDR (Classless Inter-Domain Routing) block. For example, AWS gives you 172.31.0.0/16 range of addresses for the default VPC.</p><pre>Let&#39;s understand this CIDR block - Open any IP calculator like <a href="http://jodies.de/ipcalc">http://jodies.de/ipcalc</a> and calculate the IP ranges that belong to this CIDR block.</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LDBj0MXwj-0Awt5_" /></figure><pre>As you can see in the image, where 16 is the netmask, saying the first 16 bits in the addresses are constant (here equal to 172.31), so that gives us the option to change rest 16 bits. By changing the last 16 bits i.e., previous two blocks of 8 bits (172.31.x.x), we can generate 65536 (256*256) IP addresses. That&#39;s how you represent the IP address range with CIDR blocks.</pre><p>So, In the address range 172.31.0.0/16 (172.31 describes the network because of the 16 netmask, and 0.0 part will describe the host i.e., the actual system on the network)</p><p>Also, 172.31.0.0/16 falls within RFC 1918 ranges. RFC 1918 are reserved IP address ranges for private networks, so they don’t exist publicly on the Internet. So if you create something in your VPC, its IP address is not going to conflict with anything on the Internet because its private. If you want to talk to something on the Internet, you can’t have an IP address conflict. Even when you have two services talking to each other on-premise, both of those services’ VPCs should have different CIDR ranges so that IP addresses of instances inside them don’t overlap, because overlapping addresses can’t talk to each other easily.</p><p>So, when you create a VPC, you specify a CIDR block (saying all the machines that will be deployed in this VPC will receive an IP address from this range).</p><h3>Creating Subnets</h3><p>Subnets are sub-networks inside a VPC. As we know, VPC is specific to a region, and subnets are specific to availability zones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OTcgLRYPCKkE0l3c" /></figure><p>For example, if a VPC belongs to a region us-east-1, this region will have AZs <em>us-east-1a</em>, <em>us-east-1b</em>, <em>us-east-1c</em>, etc.</p><p>Now you can assign a subnet to each of these AZs, so that machines in these AZs can talk to each other across AZs. Subnets receive IP address ranges that are subdivisions of the IP address/CIDR range VPC has been assigned. For example-<br>VPC - 172.31.0.0/16 <br>Subnets - 172.31.0.0/24, 172.31.1.0/24, 172.31.2.0/24</p><p>So here again looking at the network mask in each subnet (24) first three numbers denote the network (172.31.x), and the last number denotes the machine, so here we can have about 251 (2⁸ = 256, but 5 of them are reserved by AWS for its internal networking) machines in each subnet.</p><blockquote>Machines are launched in a specific Subnet. So, machines receive IP addresses from the address range of Subnets and Subnets receive address range from the address range of the VPC. Needless to say, each subnet belongs to a VPC.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VGslTvwD8f409SMZ" /></figure><blockquote>We are talking about IPV4 addresses here, and You can also configure the machines to receive IPV6 addresses.</blockquote><h3>Routing in a VPC</h3><p>To talk between the addresses, we need to be able to route, and the routing table tells the system how to move the packets around, where to put the next packet.</p><p>Basically, a routing table contains routes. A route is a destination - target mapping.</p><blockquote><strong>Destination</strong>- Destination CIDR where you want traffic from your subnet to go. For example, an external corporate network with a 172.16.0.0/12 CIDR.<br><strong>Target</strong>- Target through which to send the destination traffic; for example, an internet gateway.</blockquote><p>AWS gives you a default Main route table for every VPC. You can create custom route tables and also associate them with a subnet (for example, when you don’t want any data to be allowed to leave a subnet). AWS also creates a default route for communication within the VPC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tXVV_MlNyjCtqr9s" /></figure><p>In this image, the first route is the default route 172.31.0.0/16 — local, It says any traffic that is destined to an IP address belonging to this CIDR block should be routed internally/locally, or that is destined to somewhere inside this VPC.</p><p>Second route <em>0.0.0.0/0 - igw-5a67df33</em> says that traffic destined to any other IP address should be routed through Internet gateway (<em>igw-5a67df33</em> is its id). <em>0.0.0.0/0</em> denotes all IPV4 addresses, so if any other entry in your route table doesn’t handle the traffic, this route entry will. So you can say the routing table is used in order of the most specific to the least specific route rule.</p><blockquote>Every VPC has a default route table that says everything that’s inside my CIDR range, (in any of the AZs) is inside my VPC, and they can talk to one another. So considering the CIDR ranges we assigned to a subnet earlier, say 172.31.0.0/24, Now if a request comes for 172.31.0.1, it will be routed internally on the local network.</blockquote><p>That’s about communication within a VPC. How do you connect machines in that VPC to the Internet?<br>To connect to the internet, you need -</p><ol><li>some form of connection to the internet</li><li>some route to the internet</li><li>some public address (172.31.x.x we are using in our example is a private address, not available on the internet)</li></ol><p>For a machine to connect to the Internet, It has to be present in a public subnet.</p><blockquote><em>what is a public subnet?</em></blockquote><blockquote>AWS doesn’t let you create private or public subnet as such. A subnet is public or private based on its routing table.<br>If a subnet allows outgoing requests (to the Internet) by connecting to the internet gateway, it is a public subnet.<br>If a subnet blocks outgoing requests to the Internet or redirects them to a NAT (network address translation) gateway, it is a private subnet.</blockquote><blockquote><em>But why do you need to connect the private subnet to a NAT gateway?</em></blockquote><blockquote>For use cases where your machine wants to remain private but needs to fetch something from the Internet (say to download updates). For that, you create a subnet, you don’t create a route to connect it to the internet gateway, but if needed, you rather connect it to a NAT gateway. NAT gateway is a one-way valve, and it only allows responses to the requests that come from inside, rejects outside (from the Internet) requests. NAT gateway is created in a public subnet and connected to Internet gateway (igw). So it acts as a proxy between your private subnet and the internet gateway.</blockquote><p>Now to deal with the 3 points mentioned above.</p><ol><li>Public IP address - create the instance in a public subnet, Also while creating the instance, check the option to assign it a public (elastic) IP address (say 198.51.100.3 is assigned). It will still have a private address as well.</li><li>Need a connection to the Internet - create an Internet gateway and connect it to the VPC.</li><li>Route - create a route <em>0.0.0.0/0 - igw_id</em> in the public subnet’s route table. When you connect the subnet to <em>igw</em> (Internet gateway), this machine having address 198.51.100.3 can talk to anything on the Internet, and anything on the Internet can talk to it as well, like a typical web server.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*9HxOX2ykuruaOy0lNPAQeA.png" /></figure><h3>Security</h3><p>Here we will discuss three things -</p><ol><li>Security groups</li><li>Network access control lists (NACLs)</li><li>Flow logs (for monitoring, analyzing network traffic, debugging network calls)</li></ol><p>Let’s first see why do we need security? (especially Security groups here)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1KFmKu-JSEoYKI3D" /></figure><p>Consider this case, where you have one logical group of machines for web servers and one for the backend. Now we have an obvious constraint, things on the Internet should be allowed to talk to the webserver, and only webserver group should be allowed to talk to the backend group.</p><ul><li>The webserver will have to allow 0.0.0.0/0 traffic rule.</li><li>The backend will have only allow webservers group traffic rule.</li></ul><p>So here, we can assign one security group to web servers instances and another security group to backend instances.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8EVN5d6T0gyvQf7w" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y51v1ir0YHal8jYd" /></figure><h4>1. Security groups</h4><p>As is evident from the example above, security groups are distributed firewalls, and they are specific to an instance/machine. Also, Security groups are stateful.<br> Stateful means if a request comes from one direction, it automatically sets permission for the response to the request that comes from the other direction. But that doesn’t mean if you created an inbound access rule, then you don’t need outbound access rules.</p><blockquote><em>what are inbound and outbound rules?<br></em>The inbound rules govern how externally initiated connections are handled, such as serving HTTP requests, for instance. The outbound rules govern how internally initiated connections are handled, such as fetching server updates with yum or apt.</blockquote><blockquote><em>The stateful nature of security groups can be compared to a router (Not exactly, though). The router protects your computer from the evils of the Internet. Traffic can’t come through your router to your computer. However, if you make a request to go to a website, that request goes out of your router, and the response is allowed back in because it is stateful. That is, the router remembers that you made the request to that website, and it permits the response to come back to your computer.</em></blockquote><h4>2. NACLs</h4><p>NACLs gives you the option to set ALLOW/DENY traffic rules. But they are specific to a subnet. NACLs are stateless, So you will have to allow traffic rules in both directions explicitly. Please refer to AWS documentation for when to use security groups and when to use NACL.<br> For example, you can use NACLs when you want a rule to allow/deny traffic from a particular network or range of IP addresses. NACLs are relatively short compared to security groups. So, If you are writing complex rules around ports and IP addresses, you should probably use security groups.</p><blockquote>Security Group acts as a firewall for associated Amazon EC2 instances, controlling both inbound and outbound traffic at the instance level, while ACLs act as a firewall for associated subnets, controlling both inbound and outbound traffic at the subnet level.</blockquote><h4>3. Flow Logs</h4><p>Flow logs work at VPC, subnet, and instance level. You can dump the network calls to s3 or cloudwatch and analyze the traffic flow. You can configure it in your VPC (you will find a flow logs tab). Flow logs contain network interface, source IP address and port, destination IP address and port, bytes, accept/reject.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hMNf7OpdJGe5uRE0" /></figure><p>Now you can debug your traffic rules like an inbound ssh request is getting rejected, so you should check if you have set up that rule.</p><blockquote>You also have DNS options in VPC to map those IP addresses to some names. Check out Route53 for details.<br>You can check AWS direct connect, transit gateway for building inter-VPN connection.</blockquote><p>Let’s discuss in comments if you have anything to add, and give me claps. 🙂<br>Thanks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ad3d0dc01dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codenation-engineering/fundamentals-of-networking-in-aws-3ad3d0dc01dd">Fundamentals of networking in AWS</a> was originally published in <a href="https://medium.com/codenation-engineering">CodeNation Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rapid prototyping product innovations]]></title>
            <link>https://medium.com/codenation-engineering/rapid-prototyping-product-innovations-64739c0a8123?source=rss----4696563e14f2---4</link>
            <guid isPermaLink="false">https://medium.com/p/64739c0a8123</guid>
            <category><![CDATA[efficiency]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[process]]></category>
            <dc:creator><![CDATA[Nitin Labhishetty]]></dc:creator>
            <pubDate>Mon, 22 Oct 2018 04:41:52 GMT</pubDate>
            <atom:updated>2018-10-22T04:41:51.654Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to efficiently keep realizing new ideas in your products</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gl38KsClm6FVaq4P" /><figcaption>Lego blocks are a brilliant example of Rapid Prototyping Innovation! Photo by <a href="https://unsplash.com/@kellysikkema?utm_source=medium&amp;utm_medium=referral">Kelly Sikkema</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Businesses strive for 2 things:</p><ol><li>Efficiency</li><li>Innovation</li></ol><p><strong>The paradox of efficiency, beautifully explained in this </strong><a href="https://www.digitaltonto.com/2017/we-too-often-ignore-the-tradeoff-between-innovation-and-optimization/"><strong>article</strong></a><strong>, is that you can get increasingly better at something that matters less and less</strong>. Efficiency requires standardization and control to drive predictable outcomes. Innovation on the other hand, requires breathing room for creativity. It needs freedom to experiment and fail. This begs the question, <em>Can we not have both? </em>What will it take to be efficient and innovative?</p><p>Our approach at CodeNation has been to bring innovations to a space of its own, free from the shackles of traditional efficiency processes and models. And then, we define new models of efficiency for the innovation space. The result is a model for rapid prototyping product ideas.</p><p>Product innovation breaks down to 3 stages:</p><ol><li>Problem</li><li>Solution</li><li>Application</li></ol><h4>Problem</h4><p>This is identifying the problem to be solved. Here’s where we take guesses at what could take us into the future, “what would keep us ‘relevant’?” This requires broad perspective, context and vision. A lot of this is driven by org leaders, whose role gives them the necessary experience.</p><h4>Solution</h4><p>Once the problem is identified, we need to come up with the solution. <strong>This is the innovation space</strong>. You make ventures into unchartered territories, try new ideas, experiment with different approaches and sometimes fail while doing so. The outcome is a concept of a solution that will work. Here, we define different models for efficiency, described later in this article.</p><h4>Application</h4><p>Once the solution has been figured and the unknowns have been resolved, the concept needs to be taken to production. Here comes the standard model for feature specs, agile development, sprint planning and so on.</p><h3>The 3S model for efficient Innovation</h3><p>The idea is to quickly try out ideas, and make progress towards the end goal. To achieve this, we developed the 3 S rapid prototyping model:</p><blockquote>Spec — Standardize — Stories</blockquote><p>We use this deeply in our workflow at CodeNation. This is how it works:</p><h4>I. [S]pec</h4><p>Write a 3–6 pager on the new idea. There is no way someone can write a 6 pager on an idea without thinking deeply about it. This has 2 fundamental advantages:</p><ol><li>It is very helpful in understanding the real hard problem we’re solving, who are the target audience, how does it help the users in a real world use case and so on. Bad ideas get filtered early / lead to great ideas. End result is always a well-though-out proposal.</li><li>There is great clarity on what we’ve set out to achieve over the next couple of months. When you are in an innovative environment, it is easy to get side tracked. Once we spent 2 months refining an ML based recommender model while it wasn’t a significant part of the solution. This wasn’t core to the problem but a nice to have thing. Revisiting specs helps us course correct in such situations and avoid them in the first place. In summary, the spec is great at setting the vision and direction for the whole team.</li></ol><p>Traditional development has had specs for a while. The “Idea Spec” is fundamentally different in the questions it answers. You need to identify what questions are relevant in the context of your innovations.</p><h4>II. [S]tandardize</h4><p>There is a vast array of choices for implementing a solution. Often we spend time figuring out the best selection of tools: is it performant? does it have a community? is it under active development? etc. It takes time &amp; effort to make a decision. <strong>In truth, for early stage prototypes, you can do away without the “most efficient” or “best” choice.</strong> Tech today combined with cloud platforms like AWS easily allows us to support loads up to several thousand users before putting in effort on “scaling the system”</p><p>Keeping this in mind, we’ve created a quickstart template used across most of the projects:</p><ol><li>Containerized deployments on EngineYard straight from github.</li><li>Django + mod_wsgi + Apache for web services</li><li>Celery for orchestrating long running / periodic async tasks</li><li>RabbitMQ broker as a task queue broker</li><li>Cloudwatch with a setup that automatically pushes docker logs of all containers from EngineYard</li><li>Aurora for MySQL</li></ol><p>A Quickstart script automatically initialize a django project configured to work with a newly created MySQL db and config to enable and linked with celery.</p><p><strong>And so we’re able to setup a new project with a functional web service connected to a db ready to process heavy tasks if needed, containerized and deployed . All of this in &lt;5 minutes.</strong></p><p>By automating, centralizing such boilerplate work, we are able to give more time to solving the actual problem.</p><h4>III. [S]tories</h4><p>Every week, all of us write a “story” on what we want to do next week and why. This gets everyone thinking about their project and work, and induces a self-management of projects. Stories are great in understanding the evolution of the project as well. Most of all, it brings efficiency through thought.</p><p>So that’s our 3 S model of efficient innovations. Spec — Standardize — Stories</p><p><em>Want to join us in developing interesting product innovations? look out for our </em><a href="http://codenation.co.in/hiringevents.html"><em>hiring events</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64739c0a8123" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codenation-engineering/rapid-prototyping-product-innovations-64739c0a8123">Rapid prototyping product innovations</a> was originally published in <a href="https://medium.com/codenation-engineering">CodeNation Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The power of Knowledge Graphs in Search]]></title>
            <link>https://medium.com/codenation-engineering/the-power-of-knowledge-graphs-in-search-1087300f5390?source=rss----4696563e14f2---4</link>
            <guid isPermaLink="false">https://medium.com/p/1087300f5390</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[knowledge-graph]]></category>
            <category><![CDATA[codenation]]></category>
            <category><![CDATA[search]]></category>
            <dc:creator><![CDATA[Nitin Labhishetty]]></dc:creator>
            <pubDate>Wed, 08 Aug 2018 06:06:38 GMT</pubDate>
            <atom:updated>2018-08-08T11:09:00.889Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to build a kickass search using Knowledge Graphs</h4><p>Search is underrated. On average, <a href="http://www.mckinsey.com/industries/high-tech/our-insights/the-social-economy">20% of a knowledge worker’s day</a> is spent looking for the information they need to get their work done. That’s <strong>an entire day </strong>spent in searching from every week!</p><p>At CodeNation, we’ve taken a shot at improving search for our team and products.</p><blockquote>One big challenge in search is understanding what the user “wants”, not just what the user “asked for”</blockquote><p>Knowledge Graphs helped us greatly in understanding the user intent in a search query.</p><h3>The problem of ambiguity</h3><p>Modern languages are very advanced, yet still have a great potential in causing confusion:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V-pJr2V6E95flQinRLP3Dw.png" /><figcaption>“That’s not what I meant!”</figcaption></figure><p>This makes it super hard to search for what the user “wanted” and not what the user “asked for”. <strong><em>Ambiguity in search mainly stems from one word having multiple meanings</em></strong>. One example is python: Is the user looking for “snake” or “programming language” or “monty python”?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GKpB2SU6GeO7u0OLQqrbRQ.png" /><figcaption>22 meanings of the word “Python” recognized by DuckDuckGo</figcaption></figure><p>This problem often occurs with abbreviations as well. NLP — “<em>Natural Language Processing</em>” or “<em>National Liberal Party</em>” or “<em>Nucleoplasmin</em>” ?</p><h3>The problem of expression</h3><p>Sometimes, the search phrase is not expressive enough to capture all results. A plain text search for btc will not return a lot of relevant results, which have content on “Bitcoin”. Try comparing the search results for btc and bitcoin on different search engines.</p><p>Often, it is useful to have more phrases e.g. semantic machines conversation ai is much more expressive than just semantic machines.</p><h3>Understanding the query using Knowledge Graphs</h3><p>Knowledge Graphs are awesome! Think of it like a human’s common sense and world knowledge captured in graph form. Knowledge Graph can serve as the brains behind comprehension systems. Knowledge Graph was made popular by Google, and is used in it’s search and the knowledge cards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*5Enwr77OEO6771oSUO2x8Q.jpeg" /><figcaption>Google’s Knowledge Graph <a href="https://www.google.com/intl/bn/insidesearch/features/search/knowledge.html">src</a>.</figcaption></figure><p>A typical knowledge graph contains title, descriptive details and connections of various entities. Here are some examples from the <a href="https://www.wikidata.org/wiki/Wikidata:Introduction">Wikidata</a> knowledge base:</p><pre>{<br>  <strong>“label”: “Scotland”,</strong><br>  “aliases”: [<br>   “Alba”,<br>   “Scotland, United Kingdom”,<br>   “SCT”,<br>   “Caledonia”,<br>   “Scot”,<br>   “Scots”,<br>   “Scottish”<br> ],<br> “id”: “Q22”,<br> “descriptions”: [<br> “country in North-West Europe, part of the United Kingdom”<br> ],<br> “slug”: “scotland”<br>}</pre><pre>{<br>  <strong>&quot;label&quot;: &quot;universe&quot;,<br>  </strong>&quot;aliases&quot;: [<br>    &quot;space&quot;,<br>    &quot;Cosmos&quot;,<br>    &quot;outer space&quot;,<br>    &quot;universe (class)&quot;,<br>    &quot;universe, a&quot;<br>  ],<br>  &quot;id&quot;: &quot;Q1&quot;,<br>  &quot;descriptions&quot;: [<br>    &quot;totality of planets, stars, galaxies, intergalactic space, or all matter or all energy&quot;<br>  ],<br>  &quot;slug&quot;: &quot;universe&quot;<br>}</pre><p>Using a Knowledge Base like this, you can solve several problems of search:</p><ol><li><strong>Alias resolution</strong> — “Scot”, “Caledonia” point to Scotland.</li><li><strong>Word sense disambiguation</strong> — In a search for python flask, use the connections of the graph. The graph nodes of “python programming language” and “flask web framework” will be strongly connected.</li><li><strong>Abbreviation expansion</strong> — NLP can be found in the aliases of Natural Language Processing node.</li><li><strong>Query expressivity</strong> — The knowledge graph gives description, aliases and closely connected concepts to a given word. For a search like Steve Jobs you can add terms like CEO and Apple to increase recall.</li></ol><p>These enhancements can be done at query enrichment phase or baked into your index (<a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-synonym-tokenfilter.html">Elasticsearch</a> and Solr allow you to configure dictionaries). <strong><em>Besides enhancing the search, you can find answers to user queries from the Knowledge Graph itself</em></strong>. This is a non-traditional search, where it also functions as a Q&amp;A system, and is an interesting direction to explore.</p><p>The advantage of Knowledge Graph is that it goes beyond the English language dictionary in understanding context &amp; vocabulary. <em>If you build an ontology of all the knowledge in your organization, then you can get domain specific enhancements</em>.</p><p>Knowledge Graphs have a lot of potential in designing intelligent systems. We continue to be excited in exploring this idea for new product innovations.</p><p><em>Want to join us in developing interesting product innovations? look out for our </em><a href="http://codenation.co.in/hiringevents.html"><em>hiring events</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1087300f5390" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codenation-engineering/the-power-of-knowledge-graphs-in-search-1087300f5390">The power of Knowledge Graphs in Search</a> was originally published in <a href="https://medium.com/codenation-engineering">CodeNation Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Consistent Innovation]]></title>
            <link>https://medium.com/codenation-engineering/consistent-innovation-35ba004b6963?source=rss----4696563e14f2---4</link>
            <guid isPermaLink="false">https://medium.com/p/35ba004b6963</guid>
            <category><![CDATA[codenation]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Nitin Labhishetty]]></dc:creator>
            <pubDate>Fri, 27 Jul 2018 13:07:51 GMT</pubDate>
            <atom:updated>2018-07-27T14:51:46.932Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to create a cadence for innovations in your company</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J4q2UDg_iW5Z9E59" /><figcaption>Photo by <a href="https://unsplash.com/@freegraphictoday?utm_source=medium&amp;utm_medium=referral">G. Crescoli</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Innovation drives the future. It keeps your company and your products exciting, relevant and valuable. <strong><em>The hard part about innovation is doing it consistently.</em></strong> More so in fast paced, high impact businesses, where you’re hard pressed by targets, quarterly results and customer success.</p><p><strong>How do you regularly come up with and implement kickass new ideas? Can we create a factory of innovations?</strong></p><p>These are two questions we’ve been asking ourselves for the last 4 years at CodeNation. CodeNation is the “<em>innovation factory</em>” for the <a href="http://www.eswcapital.com/">ESW Capital group</a>. We work on coming up with product innovations across the group. After much experimentation, this is what works for us to consistently deliver innovations:</p><h4><strong>1. Experiment rapidly</strong></h4><p>Speed is of the essence in innovation. This gives us the freedom to try out a lot of things and make a lot of mistakes. You will fail a couple of times before getting it right, it’s best to fail fast. Remember to:</p><blockquote><strong><em>Maximize speed, not minimize risk.</em></strong></blockquote><h4><strong>2. Open communication</strong></h4><p>Open channels of information create a strong flow of ideas across the team. Information stuck in silos creates little pockets of knowledge, which tremendously reduces innovation. A significant part of creativity is mixing and matching ideas, cross application of concepts. <strong><em>The leadership must create chances for conversation, exchange of ideas and route information across the company.</em></strong></p><h4><strong>3. Small, close teams create massive impact</strong></h4><p>Small teams increases an individual’s impact on the team mission, which drives them to take <strong><em>higher ownership</em></strong>. Small teams are easily aligned, work closely together, and have complete visibility of each other. This encourages high performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WbClaoQ0nIFb-LOR" /><figcaption>Photo by Pascal Swier on Unsplash</figcaption></figure><h4><strong>4. Create an environment that allows taking risks</strong></h4><p>If people are too afraid to make mistakes, you won’t have a team that dreams big or takes risks. Innovation requires accepting the “possibility of failure”. Don’t nuke a team whose experiment didn’t work out, coach them to salvage the learnings and pick themselves up right after. <strong><em>Encourage taking on hard problems to solve.</em></strong></p><h4><strong>5. Hire the smart, hungry and creative ones, make them a part of hiring</strong></h4><p>A small team of brilliant individuals create “massive impact”. Innovation requires people who can dream, improvise and adapt. <strong><em>Standard hiring process of asking DSA questions (for the developers) isn’t enough for finding good innovators.</em></strong> Have discussions that test the candidates creativity, planning and other skills. Involve everyone from the team in taking interviews. They will understand what are the qualities the company values and also attract like minded talent.</p><h4><strong>6. Make a framework for various stages of innovation</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TbZxc5iWJqg02yIn" /><figcaption>Photo by <a href="https://unsplash.com/@thoughtcatalog?utm_source=medium&amp;utm_medium=referral">Thought Catalog</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Deciding on an idea, laying out a vision and plan, making incremental developments, testing the product and all other stages in the life cycle of an innovation should be optimized for speed. <strong><em>Create standard frameworks that help the teams quickly move through each phase of innovation.</em></strong></p><h4><strong>7. Have fun</strong></h4><p>Happy teams achieve more. They can take on harder challenges, and their positivity reflects in the products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*W-Ybak47fMapGGkN" /><figcaption>Photo by <a href="https://unsplash.com/@bernardhermant?utm_source=medium&amp;utm_medium=referral">Bernard Hermant</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It’s been an interesting journey in figuring out how to build an awesome innovation factory at CodeNation, and we’re still experimenting. If you’re interested in finding out about some of the exciting ideas we’re working on, follow the updates on the <a href="https://medium.com/codenation-engineering">CodeNation Engineering blog</a>.</p><p><em>Want to join us in developing interesting product innovations? Look out for our </em><a href="http://codenation.co.in/hiringevents.html"><em>hiring events</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35ba004b6963" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codenation-engineering/consistent-innovation-35ba004b6963">Consistent Innovation</a> was originally published in <a href="https://medium.com/codenation-engineering">CodeNation Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hello World! ]]></title>
            <link>https://medium.com/codenation-engineering/hello-world-87835d7372c8?source=rss----4696563e14f2---4</link>
            <guid isPermaLink="false">https://medium.com/p/87835d7372c8</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[hello-world]]></category>
            <category><![CDATA[codenation]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[CodeNation]]></dc:creator>
            <pubDate>Fri, 27 Jul 2018 12:47:32 GMT</pubDate>
            <atom:updated>2018-07-27T12:47:31.837Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to the CodeNation engineering blog. We are a small team of mad scientists on a mission to bring the future to the products and customers at <a href="http://eswcapital.com/">ESW Capital</a> Group. Our work revolves around creating product innovations in software systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ILMYivRgd2BDp94-x4GWhQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A5V7SrntiZrFoq8xz8kDNQ.jpeg" /><figcaption>Random days at work</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M6M4FpG173B1xsCkcgFu_g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7ssqKTO44DVrML4nGz7yEA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dVMpVqzMFkNpgF3dxFV3TA.jpeg" /><figcaption>Adventure, travel and partying @ CodeNation</figcaption></figure><p>The culture of partying, adventure and fun runs deep at CodeNation, but most of all, we have a very deep passion for technology. In this blog, we hope to share this love with the community. Stay tuned for stories from the innovators at CN!</p><p><em>Visit our </em><a href="http://codenation.co.in/index.html"><em>website</em></a><em> to know more about us. You can find us on </em><a href="https://www.facebook.com/codenation.india"><em>Facebook</em></a><em> and </em><a href="https://www.linkedin.com/company/codenation"><em>LinkedIn</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87835d7372c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codenation-engineering/hello-world-87835d7372c8">Hello World! 👋</a> was originally published in <a href="https://medium.com/codenation-engineering">CodeNation Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>