<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Chintan Shah on Medium]]></title>
        <description><![CDATA[Stories by Chintan Shah on Medium]]></description>
        <link>https://medium.com/@chintan86?source=rss-5f6072eb565b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*YTv5t7Yegu8JheSC.jpeg</url>
            <title>Stories by Chintan Shah on Medium</title>
            <link>https://medium.com/@chintan86?source=rss-5f6072eb565b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:17:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chintan86/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Data Driven Recruitment Using Machine Learning]]></title>
            <link>https://medium.com/promact/data-driven-recruitment-using-machine-learning-42daeba2a28?source=rss-5f6072eb565b------2</link>
            <guid isPermaLink="false">https://medium.com/p/42daeba2a28</guid>
            <category><![CDATA[recruitment]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[Chintan Shah]]></dc:creator>
            <pubDate>Mon, 08 Oct 2018 11:46:15 GMT</pubDate>
            <atom:updated>2018-10-08T11:46:18.318Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Promact: Machine Learning" src="https://cdn-images-1.medium.com/max/1024/0*aQBJQ4GflMZLFbQh.jpg" /></figure><p>Data driven recruitment using Machine Learning</p><p>Machine learning is the most trending interdisciplinary field of study today. There are various methodology and representations to apply them to real-world situations. The areas could be vast like trending news topics, building recommendation engines, image, video and text recognition, improving cyber-security, self-driven cars and medical outcomes. The utilization of machine learning is so universal today that it is been used an umpteenth number of times by individuals, and they aren’t even aware of it. Moreover, it is considered as the best step forward towards AI.</p><blockquote>“Machine learning has the power to synchronize volumes of data and calculations that would make it impossible for an individual person to do,” says <a href="https://www.linkedin.com/in/rushi-soni/">Rushi Soni</a>, CTO of Promact; who is also currently a part of a team that is understanding and learning the basics of Machine Learning — Coursera with the help of the coursework taught by Andrew Ng.</blockquote><p>The ability to identify patterns in abundance is the superpower of machine learning. Organizations that use machine learning are more susceptible to make new discoveries and find solutions to issues faster. For example, here at <a href="https://www.promactinfo.com/">Promact</a>, there is a current team of highly skilled individuals developing a recruitment system which would help to analyze and give better results in areas of referrals, expected CTC, location, gender, age, company turnover ratio, external activity score and recommendations. With the help of machine learning and analyzing data from the previous computations, it will help in the better predictability of data-mining and statistical pattern recognition during the future <a href="https://questy.xyz/">recruitment</a> process.</p><p>Some live examples that we see around the globe of machine learning are:</p><ul><li>The hype for the self-driven Google car</li><li>Online purchase recommendations from sites like Amazon, Flipkart, etc.</li><li>One of the most crucial uses in the technology world — fraud detection</li></ul><p>With all the above means it possible to create innovative work at a faster time which is complex and would otherwise have taken up hours of work. The utilization of more advancement of machine learning will help to present more swift and reliable results.</p><p>And, the 4 points that can cover your base to machine learning are:</p><ul><li>Data preparation capabilities</li><li>Basic &amp; advanced algorithms</li><li>Quantifiability</li><li>Ensemble modeling</li></ul><p>Now, most industries have large volumes of data and understand the ways and importance in which machine learning can be helpful. Hence, giving them an edge over competitors to work more efficiently and effectively.</p><p><em>Originally published at </em><a href="https://www.promactinfo.com/blog/data-driven-recruitment-using-machine-learning/"><em>Promact — The Startup and Technology blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42daeba2a28" width="1" height="1" alt=""><hr><p><a href="https://medium.com/promact/data-driven-recruitment-using-machine-learning-42daeba2a28">Data Driven Recruitment Using Machine Learning</a> was originally published in <a href="https://medium.com/promact">Promact</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile app automation testing with Calabash — Writing and Executing Test cases]]></title>
            <link>https://medium.com/promact/mobile-app-automation-testing-with-calabash-writing-and-executing-test-cases-f9752ae4840f?source=rss-5f6072eb565b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9752ae4840f</guid>
            <category><![CDATA[calabash]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[mobile-app-automation]]></category>
            <dc:creator><![CDATA[Chintan Shah]]></dc:creator>
            <pubDate>Tue, 30 Aug 2016 07:36:07 GMT</pubDate>
            <atom:updated>2016-08-30T07:38:30.279Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="writing-and-executing-test-cases-with-calabash" src="https://cdn-images-1.medium.com/max/1024/0*br37R1MND_fYSPwW.jpg" /></figure><p>We will see how to write and execute test cases for Calabash. Before moving ahead, You must ensure that Calabash is setup properly on your system. If you need any help, refer to my earlier article on installation.</p><p><a href="https://www.promactinfo.com/blog/mobile-app-automation-testing-with-calabash-installation-ios/">Mobile app automation testing with Calabash - Installation (iOS) | Promact - The Startup and Technology blog</a></p><p>We will use a iOS demo project developed in Objective-C. We will see how to perform ‘Scroll’ through automation. It is hosted on <a href="https://github.com/Promact/ios-sample-calabash">GitHub </a>and is open for anyone to try.</p><p><strong>Step#0 Clone Repository</strong></p><p>If you have already cloned above repository or, have created your test project. You can skip this step.</p><pre>$ git clone <a href="https://github.com/Promact/ios-sample-calabash.git">https://github.com/Promact/ios-sample-calabash.git</a></pre><p>Once the repository is cloned try running the application in the simulator or on the actual device.</p><p><strong>Step#1 Setup feature file</strong></p><p>Open terminal at the path where you cloned/created your project and use the following command on your terminal to setup required files for writing test cases.</p><pre>$ calabash-ios gen</pre><p>It will ask few questions.</p><p><em>“This directory will contain all of your Calabash tests. Shall I proceed? (Y/n)</em>”</p><p>When you hit yes it will create <strong>features</strong> folder. Under the features folder, you will see <strong>sample.feature</strong> and two more folders <strong>steps</strong> and <strong>support</strong>. These folders contain calabash automation supported files We shall discuss these folders in future articles.</p><p>“ <em>I want to create a Gemfile for you. Shall I proceed? (Y/n)</em>”</p><p>Gemfile allows Ruby applications to manage the dependencies. It will add calabash-cucumber gem in this file.</p><p><strong>Step#2 Writing test cases</strong></p><p>Following is the way how I structured my test cases to perform ‘Scroll’ in the app. Calabash allows simple English language popularly known as <a href="https://github.com/cucumber/cucumber/wiki/Gherkin">Gherkin </a>to write test cases for automating the app.</p><pre>Feature: Scroll the Table<br>  Functionality of this test case is to test scrolling<br><br>  Scenario: Scroll Scenario<br>    Given I wait to see a navigation bar titled &quot;To do List&quot;<br>    When I scroll down<br>    Then I wait for 2 seconds<br>    Then I scroll down<br>    Then I wait for 2 seconds<br>    Then I scroll up</pre><p>The first line initiates feature. Line 2 describes the feature, functionality or business value. The line 2 is not parsed at runtime. A feature file may only contain one feature and many scenarios. Line 4 is the starting point for the scenario. This describes a particular use case in the application. Line 5–10 describes steps to be executed for the mentioned scenario.</p><p>Gherkin, like Python and YML, is a line-oriented language which uses indentation to structure the file. Proper indentation is necessary in your test cases.</p><p><strong>Step#3 Executing Test cases</strong></p><ul><li>Open terminal &gt;&gt; go to project directory &gt;&gt; enter ‘calabash-sandbox’ &gt;&gt; enter ‘cucumber’</li></ul><p>Command “cucumber” will run all the test cases written in “*.feature” file.</p><p>After completion of running test cases, results will look like,</p><figure><img alt="Screen Shot 2016-05-23 at 11.16.34 AM" src="https://cdn-images-1.medium.com/max/1024/0*RI7OMPeQoIMn2LN9.png" /></figure><p><strong>Calabash-iOS Console</strong></p><p>Calabash-iOS provides a console where you can search any elements and their properties in an app, It lists only elements which are currently visible on the screen.</p><pre>$ calabash-iso console</pre><p>You may see following messages on terminal</p><figure><img alt="Screen Shot 2016-05-23 at 10.57.42 AM" src="https://cdn-images-1.medium.com/max/572/0*Ao64p10vYdSmJBFz.png" /></figure><pre>&gt; query(&quot;*&quot;)</pre><p>this single command will work as accessibility inspector.</p><figure><img alt="Screen Shot 2016-05-23 at 11.05.48 AM" src="https://cdn-images-1.medium.com/max/1024/0*1KaMoxSJMgFodmFc.png" /></figure><p><strong>Happy Testing!</strong></p><p><em>Originally published at </em><a href="https://www.promactinfo.com/blog/mobile-app-automation-testing-with-calabash-writing-and-executing-test-cases/"><em>Promact — The Startup and Technology blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9752ae4840f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/promact/mobile-app-automation-testing-with-calabash-writing-and-executing-test-cases-f9752ae4840f">Mobile app automation testing with Calabash — Writing and Executing Test cases</a> was originally published in <a href="https://medium.com/promact">Promact</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile app automation testing with Calabash — Installation (iOS)]]></title>
            <link>https://medium.com/promact/mobile-app-automation-testing-with-calabash-installation-ios-fdbbd3c3dae4?source=rss-5f6072eb565b------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdbbd3c3dae4</guid>
            <category><![CDATA[calabash]]></category>
            <category><![CDATA[mobile-app-automation]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Chintan Shah]]></dc:creator>
            <pubDate>Mon, 01 Aug 2016 07:28:11 GMT</pubDate>
            <atom:updated>2016-08-01T10:35:15.840Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="get-started-with-calabash" src="https://cdn-images-1.medium.com/max/820/0*IJwy6a67fh5wxT40.jpg" /></figure><p><a href="http://calaba.sh/">Calabash </a>is an open source cross-platform framework developed by Xamarin that enables you to write and execute automated acceptance tests for mobile apps. It supports <a href="https://cucumber.io/">Cucumber</a> which allows you to express the behavior of your app using natural language that can be understood by non-technical QA guys.</p><p><strong>Introduction to Mobile app testing</strong></p><p>Mobile application testing is a process by which apps developed for mobile devices is tested for its functionality, usability, and consistency. Similar to web applications, We can also perform Functional, Performance, Usability, Security, and Load testing for verifying it’s behavior and functionality.</p><h4><strong>Prerequisites and Installation</strong></h4><p>Prerequisites</p><ul><li><a href="https://guide.macports.org/chunked/installing.xcode.html">XCode</a> &gt;= 6</li><li><a href="https://coolestguidesontheplanet.com/install-update-latest-version-git-mac-osx-10-9-mavericks/">Git</a> &gt;= 1.8</li><li><a href="http://brew.sh/">Homebrew</a> (Latest)</li><li><a href="https://www.ruby-lang.org/en/documentation/installation/">Ruby </a>(Latest Version)</li></ul><h4><strong>Installing Calabash framework</strong></h4><p><strong>Step #1 Install Calabash- OS X</strong></p><p>Execute the following command in your terminal to install calabash:</p><pre>$ curl -sSL <a href="https://raw.githubusercontent.com/calabash/install/master/install-osx.sh">https://raw.githubusercontent.com/calabash/install/master/install-osx.sh</a> | bash</pre><p>This will take a few minutes to get installed and you’ll get the following message at the end of installation:</p><pre>Done! Installed:</pre><pre>calabash-ios:       0.19.0</pre><pre>calabash-android:   0.7.3</pre><pre>xamarin-test-cloud: 2.0.0.pre2</pre><pre>Execute &#39;calabash-sandbox update&#39; to check for gem updates.</pre><pre>Execute &#39;calabash-sandbox&#39; to get started!</pre><pre><strong>Step #2 Link Calabash framework with your project</strong></pre><pre>Go to project directory and open terminal in that directory and start calabash using the following command:</pre><pre>$ calabash-sandbox<br>This terminal is now ready to use with Calabash.<br>To exit, type &#39;exit&#39;.</pre><pre>Now, link calabash framework using the following command:</pre><pre>$ calabash-ios download</pre><pre>Once you execute this command you may get may see the following informative message:</pre><pre>----------Info----------</pre><pre>caution: excluded filename not matched:  __MACOSX/*</pre><pre>caution: excluded filename not matched:  calabash.framework/.DS_Store</pre><pre>Next, open your project in XCode and go to <strong>Build Settings</strong>. Now, search for the term &quot;<em>Other Linker Flags</em>&quot;.</pre><figure><img alt="Screen Shot 2016-05-13 at 6.02.59 PM" src="https://cdn-images-1.medium.com/max/877/0*O0fKV-yST4JQSzoQ.png" /></figure><pre>Double click on “Debug” and check if CFNetwork Framework is added or not.</pre><figure><img alt="Screen Shot 2016-05-13 at 6.24.09 PM" src="https://cdn-images-1.medium.com/max/897/0*MBNGVy1bkIkwLV0e.png" /></figure><pre>If not, then click on ‘<strong>+</strong>’ button displaying on left bottom corner and type following command:</pre><pre>ObjC -force_load &quot;$(SOURCE_ROOT)/calabash.framework/calabash&quot;</pre><pre>Once you enter this command, the screen will look like above. Now run your application in the emulator.</pre><pre><strong>You&#39;re ready with Calabash for automating your iOS app!</strong></pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdbbd3c3dae4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/promact/mobile-app-automation-testing-with-calabash-installation-ios-fdbbd3c3dae4">Mobile app automation testing with Calabash — Installation (iOS)</a> was originally published in <a href="https://medium.com/promact">Promact</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Specification Pattern with C#]]></title>
            <link>https://medium.com/promact/specification-pattern-with-c-7ec36125ee45?source=rss-5f6072eb565b------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ec36125ee45</guid>
            <category><![CDATA[csharp]]></category>
            <category><![CDATA[domain-model]]></category>
            <dc:creator><![CDATA[Chintan Shah]]></dc:creator>
            <pubDate>Thu, 02 Jun 2016 08:04:04 GMT</pubDate>
            <atom:updated>2016-08-01T10:48:08.522Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*frDi58F_lW2anS3s.jpg" /></figure><p><strong>What is specification pattern?</strong></p><p>Specification pattern is a software designing pattern where business logic is maintained in single unit which can then be used to either validate business logic against domain model or can be used to chain business rules together using Boolean logic operands like AND,OR,NOT to retrieve expected results.</p><p>In this article, we will discuss about specification pattern. We will cover brief overview of specification pattern, its use in domain-driven development and its usefulness to keep DRY (Don’t Repeat Yourself) principle intact while implementing business logic. We will also discuss implementation of specification pattern together with repository pattern and c#’s generics to obtain generic abstract specification which will provide base of pattern.</p><p><strong>Example</strong></p><p>Let’s consider famous Employee as an entity with following property.</p><pre>public class Employee<br>{<br>     [DatabaseGenerated(DatabaseGeneratedOption.Identity)]<br>     public int Id { get; set; }<br>     public string Name { get; set; }<br>     public Designation Position { get; set; }<br>     public int TeamLeaderId { get; set; }<br>}</pre><pre>public enum Designation<br>{<br>     CEO,<br>     Manager,<br>     TeamLeader,<br>     SeniorDeveloper,<br>     JuniorDeveloper<br>}</pre><pre>Now suppose there is need to get the detail of Employees which are team leaders, here we will create EmployeeRepository which interacts with Employee data source.</pre><pre>So, we will create EmployeeRepository.cs along with IEmployeeRepository.cs</pre><pre>public class EmployeeRepository:IEmployeeRepository<br>{<br>	private readonly IDataRepository&lt;Employee&gt; _employeeRepository;</pre><pre>public EmployeeRepository(IDataRepository&lt;Employee&gt; employeeRepository)<br>	{<br>		_employeeRepository = employeeRepository;<br>	}<br>	//method to get the list of team<br>	public List&lt;Employee&gt; GetTeamLeaders()<br>	{<br>		return _employeeRepository.Fetch(x=&gt;x.Position==Designation.TeamLeader).ToList();<br>	}<br>}<br>OK, this looks simple. It could be complicated as more and more requirement increases.it creates problem when there is need to validate the logic as well as need to get list of employees from the repository method.</pre><pre>For example if at some point of time there is a need to check that Employee&#39;s Designation is Team leader. So controller method can be written as</pre><pre>public IHttpActionResult GetTeamMembers(int empId)<br>{<br>	var emp = _employeeRepository.GetEmployeeById(empId);<br>	if (emp.Position != Designation.TeamLeader)<br>	{<br>		return BadRequest(&quot;Employee is not a team leader&quot;);<br>	}<br>	return Ok();<br>}</pre><pre>In above code there is problem, as logic of deciding team leader is spread across two parts of application, one in GetTeamMembers method in controller and other in GetTeamLeaders method of repository. Which violates DRY principle and increases overhead to maintain code.</pre><pre>It becomes severe as size of code increases. So, to solve this problem specification pattern helps in keeping business logic in one single piece of unit.</pre><pre>So let&#39;s add specification for Employee.</pre><pre>We will create specification for employee to decide team leader,</pre><pre>public class TeamLeaderSpecification<br>{<br>     public Expression&lt;Func&lt;Employee, bool&gt;&gt; ToExpression()<br>     {<br>          return (x =&gt; x.Position == Designation.TeamLeader);<br>     }<br>     public bool IsSatisfiedBy(Employee employee)<br>     {<br>          var predicate=ToExpression().Compile();<br>          return predicate(employee);<br>     }<br>}</pre><pre>In above we have created class which contains specification to get expression which gives list of team leader and IsSatisfiedBy method provide way to validate the logic in controller.</pre><pre>Now we can use this specification to validate team leader criteria as follows,</pre><pre>var emp = _employeeRepository.GetEmployeeById(empId);<br>var teamLeaderSpec = new TeamLeaderSpecification();<br>if (!teamLeaderSpec.IsSatisfiedBy(emp))<br>{<br>     return BadRequest(&quot;Employee is not team leader&quot;);<br>}</pre><pre>And repository method can be refactored as,</pre><pre>//Add method to get the list of team<br>public List&lt;Employee&gt; GetTeamLeaders()<br>{<br>     var teamLeaderSpecification = new TeamLeaderSpecification();<br>     return _employeeRepository.Fetch(teamLeaderSpecification.ToExpression()).ToList();<br>}</pre><pre>Ok, so we have removed redundancy to decide team leader. But what if we also need to create specification for Company entity?</pre><pre>This is where Generics helps to provide specification for other entity.</pre><pre>Let&#39;s create generic specification class.</pre><pre>public abstract class Specification&lt;T&gt;<br>{<br>     public abstract Expression&lt;Func&lt;T, bool&gt;&gt; ToExpression();<br>     public bool IsSatisfiedBy(T entity)<br>     {<br>          Func&lt;T, bool&gt; predicate = ToExpression().Compile();<br>          return predicate(entity);<br>     }<br>}</pre><pre>we have created this class as abstract, it make sense as it has method defined without implementation, that method will be overridden by the other specifications and they will decide how to implement ToExpression method. So let&#39;s inherit this class to TeamLeaderSpecification class first.</pre><pre>Now TeamLeaderSpecification will looks like below,</pre><pre>public class TeamLeaderSpecification:Specification&lt;Employee&gt;<br>{<br>     public override Expression&lt;Func&lt;Employee, bool&gt;&gt; ToExpression()<br>     {<br>          return (x =&gt; x.Position == Designation.TeamLeader);<br>     }<br>}</pre><pre>Notice that ToExpression is overridden here and IsSatisfiedBy method is removed from TeamLeaderSpecification, actually it is moved to Specification class.</pre><pre>Again we are ready to create CompanySpecification as per company requirements and move on to expand Specification pattern. Like if we want to get the specification to get the company based on Id we would create,</pre><pre>public class CompanySpecificationById : Specification&lt;Company&gt;<br>{<br>     private readonly int _id;<br>     public CompanySpecificationById(int id)<br>     {<br>          _id = id;<br>     }<br>     public override Expression&lt;Func&lt;Company, bool&gt;&gt; ToExpression()<br>     {<br>          return (x=&gt;x.Id==_id);<br>     }<br>}</pre><pre>Here we have created specification using constructor call as id would be dynamic, so whenever we need to create specification we will created specification using constructor initialization.</pre><pre>So we are ready to use specification for different entities.</pre><pre>However we can also chain the specifications Like AND, OR, NOT</pre><pre>For example if we want to combine two specifications like we want to have employees with name Mark and Also he should be team leader then we can create AND specification in abstract class,</pre><pre>public abstract class Specification&lt;T&gt;<br>{<br>     public abstract Expression&lt;Func&lt;T, bool&gt;&gt; ToExpression();</pre><pre>public bool IsSatisfiedBy(T entity)<br>     {<br>          Func&lt;T, bool&gt; predicate = ToExpression().Compile();<br>          return predicate(entity);<br>     }</pre><pre>public Specification&lt;T&gt; And(Specification&lt;T&gt; specification)<br>     {<br>          return new AndSpecification&lt;T&gt;(this, specification);<br>     }<br>}</pre><pre>public class AndSpecification&lt;T&gt; : Specification&lt;T&gt;<br>{<br>     private readonly Specification&lt;T&gt; _left;<br>     private readonly Specification&lt;T&gt; _right;</pre><pre>public AndSpecification(Specification&lt;T&gt; left, Specification&lt;T&gt; right)<br>     {<br>          _right = right;<br>          _left = left;<br>     }</pre><pre>public override Expression&lt;Func&lt;T, bool&gt;&gt; ToExpression()<br>     {<br>          Expression&lt;Func&lt;T, bool&gt;&gt; leftExpression = _left.ToExpression();<br>          Expression&lt;Func&lt;T, bool&gt;&gt; rightExpression = _right.ToExpression();</pre><pre>BinaryExpression andExpression = Expression.AndAlso(leftExpression.Body, rightExpression.Body);</pre><pre>return Expression.Lambda&lt;Func&lt;T, bool&gt;&gt;(andExpression, leftExpression.Parameters.Single());<br>     }<br>}<br>We can now create Specification to generate query to get team leaders by name as follows,</pre><pre>public List&lt;Employee&gt; GetTeamLeaderByName(string name)<br>{<br>     var nameSpecification = new EmployeeNameSpecification(name);<br>     var teamLeaderSpecification = new TeamLeaderSpecification();<br>     return _employeeRepository.Fetch(nameSpecification.And(teamLeaderSpecification).ToExpression()).ToList();<br>}</pre><pre>We have now two methods to get the list of employees,</pre><pre>public List&lt;Employee&gt; GetTeamLeaderByName(string name)<br>{<br>     var nameSpecification = new EmployeeNameSpecification(name);<br>     var teamLeaderSpecification = new TeamLeaderSpecification();<br>     return _employeeRepository.Fetch(nameSpecification.And(teamLeaderSpecification).ToExpression()).ToList();<br>}</pre><pre>//method to get the list of team<br>public List&lt;Employee&gt; GetTeamLeaders()<br>{<br>     var teamLeaderSpecification = new TeamLeaderSpecification();<br>     return _employeeRepository.Fetch(teamLeaderSpecification.ToExpression()).ToList();<br>}<br>In both of the above methods we are creating Specifications in Repository, we can combine two methods in one to get the list of employees and give the responsibility of creating business rules to controller and give single responsibility to get employee list to Repository. We can do it by simply creating method in employee repository which takes specification of employees and give list of employees back,</pre><pre>public List&lt;Employee&gt; GetEmployees(Specification&lt;Employee&gt; employeeSpecification)<br>{<br>     return _employeeRepository.Fetch(employeeSpecification.ToExpression()).ToList();<br>}</pre><pre>that&#39;s it, we can now call this method from controller and force the controller to create business rule.</pre><pre>public IHttpActionResult GetTeamLeaders() <br>{<br>     var teamLeaderSpecification = new TeamLeaderSpecification();<br>     var teamLeaders = _employeeRepository.GetEmployees(teamLeaderSpecification);<br>     return Ok(teamLeaders);<br>}</pre><pre><strong>Conclusion</strong></pre><ul><li>Specification pattern helps to implement DRY principle along with repository pattern and Generics.</li><li>It also helps in implementing SRP (Single Responsibility Principle) and writing loosely coupled code.</li><li>Specification pattern also helps to maintain entity related business logic in single unit of code.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ec36125ee45" width="1" height="1" alt=""><hr><p><a href="https://medium.com/promact/specification-pattern-with-c-7ec36125ee45">Specification Pattern with C#</a> was originally published in <a href="https://medium.com/promact">Promact</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips on making the right Design decisions]]></title>
            <link>https://medium.com/promact/tips-on-making-the-right-design-decisions-c7110a4a07b9?source=rss-5f6072eb565b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7110a4a07b9</guid>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[problem-solving]]></category>
            <dc:creator><![CDATA[Chintan Shah]]></dc:creator>
            <pubDate>Sat, 30 Apr 2016 12:40:49 GMT</pubDate>
            <atom:updated>2016-08-01T10:35:18.687Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="design-decisions" src="https://cdn-images-1.medium.com/max/1024/0*8D40Uj9WzPtqUa_4.jpg" /></figure><p>Recently an aspiring designer asked me, what all does it take to have the right design decisions, how to decide if it’s the right design and what process to follow for any new design project.</p><p>I believe that design is misunderstood many a times. While the best works of design may seem simple and obvious, there’s a lot of work going on behind the scenes when design decisions are made. More than you might imagine.</p><p>I’d like to share some of my thoughts and insights on how design decisions should be made. These thoughts are simply a gist of what I have observed and learned over the course of time of my design experience.</p><ol><li><strong>Understanding Design</strong></li></ol><p>The common misconception about design is that it is just a process to make things look beautiful. In reality, Design is much more than that.</p><p>Design is not a process of beautifying things, just making things look nice or better than before. This assumption of design can be termed as ‘Craft’ and certainly that is a part of the designer’s job, but that is not the real job in its entirety.</p><ol><li><strong>Problem Solving</strong></li></ol><p>The success of design lies in its ability to solve the problem. But it has been a common observation that many designers tend to misjudge the problem. The general notion that the objective of the assigned project is the real problem is wrong.</p><p><em>There are 2 common mistakes that designers make when solving a problem in design: a. Obvious features get hidden, b. Insufficient scalability.</em></p><p>Everybody loves a product with lots of exciting features. But it is important to judge and prioritize the importance and usability patterns of the required features. Due to a lack of appropriate judgment it often results into a very complex product or a scenario where obvious features are hidden from direct access. The key to avoid this problem is to cut the complexity. The UI of the application must be as simple and intuitive as possible. Priority discoverability and learnability is very important to cut the complexity. The users must be able to discover the important features in the desired sequence. If the incorporated design employs a change as compared to the usual design processes, the user must be able to learn and remember the usability without making special efforts.</p><p>We often feel that many of the latest design updates by large tech companies are obvious and boring. Often their old designs looked more beautiful with complex structures and special effects.</p><p>For example, if we consider Facebook; being a designer I often feel that the design of Facebook is very plain and ugly. Same has been reciprocated among the design community and many good designers did also come up with beautiful redesigned layouts, got a huge applaud from the design community, but none of those designs have been turned into reality.</p><p><em>The Reason?</em></p><p>Not addressing the problems effectively. Facebook is a platform for the users across the whole world, not just for the English speaking users. In Facebook it is a need to translate each word, button and label into the native languages of the user. This constraint requires the consideration of a very high level of scalability. This cannot be solved just by a beautiful UI.</p><blockquote><strong>Beautiful design is certainly pleasant to the eyes but that will only come in use when the real problems and constraints are identified and solved.</strong></blockquote><ol><li><strong>Empathize</strong></li></ol><p>The best design process is the one that involves real users into the process. Involving real users into the process seems scary as we have a constant fear that the user may not understand our design flow. But that is exactly why we should have this process. Involving users will convey the project’s stakeholders about what their customers are doing, thinking, feeling and saying about their app.</p><ol><li><strong>Identify the beginning and the end</strong></li></ol><p>When working on a problem, it is very essential to identify the most prominent action a user would be performing when using the app, and leading the user along towards a desirable end goal. This will not only accomplish the purpose of the app but would also address the user’s needs and make them visit again.</p><p>I recently had a bad experience with one Grocery Ordering App. After the completion of the payment for my order I found it very difficult to figure out the tracking of my order. Had it been identified earlier that users may prefer tracking their recent orders, this experience could have been made better.</p><p>A good end leads us to a better beginning. As its said, “<em>All’s well that ends well</em>”.</p><p><strong>Summary</strong></p><p>When proceeding on a design task, you should ask questions like:</p><p>1 — What is the real problem your design will solve?</p><p>2 — Who is the real audience? Is your perceived solution really addressing their needs?</p><p>3 — Is my design considering the problems or scenarios that the users will encounter?</p><p>4 — What are the constraints or limitations that may affect my design decisions?</p><p>5 — Is your design approachable? Is it simple and intuitive enough that the user comes back again on your platform?</p><p><strong>Final Thoughts</strong></p><p>As a designer, I believe that:</p><blockquote><strong>It’s important to do what’s asked to you, but it’s also important to do what’s right.</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7110a4a07b9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/promact/tips-on-making-the-right-design-decisions-c7110a4a07b9">Tips on making the right Design decisions</a> was originally published in <a href="https://medium.com/promact">Promact</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2015 Year in Review for Promact]]></title>
            <link>https://medium.com/promact/2015-year-in-review-for-promact-d5deeeebc3ec?source=rss-5f6072eb565b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5deeeebc3ec</guid>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[crozi]]></category>
            <category><![CDATA[convozo]]></category>
            <category><![CDATA[annual-updates]]></category>
            <dc:creator><![CDATA[Chintan Shah]]></dc:creator>
            <pubDate>Fri, 01 Jan 2016 05:20:47 GMT</pubDate>
            <atom:updated>2016-08-01T10:35:16.730Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Welcome2016" src="https://cdn-images-1.medium.com/max/1024/0*1TrbZJGvKA9A6oye.jpg" /></figure><p>The year 2015 had been a wonderful ride for us. We have seen great success with our projects and taken big steps in our vision.</p><p>As the new year begins, it is a good time to review the year.</p><h4><strong>Tech Updates</strong></h4><ol><li><strong>Docker</strong><br>This year we explored Docker and fell in love with that technology. We saw a great tool that would eliminate hours of configuring clusters and managing them. Docker is to Infrastructure like JVM is to Programing language. You just need to create a Docker container and deploy on any machine that has basic kernel features.</li><li>We consulted a company at Gandhinagar for probable implementation of Docker. They had a huge cluster to manage with legacy code and multiple location to deploy.</li><li>We implemented Docker for our own Project management system Redmine. It allows us to upgrade Redmine faster.</li><li>This year we shall be working more on Docker and would be publishing few use case scenarios and tips for using it efficiently.</li><li><strong>Machine Learning</strong><br>This year we started 2 Mobile apps which presented us with the use case for Machine Learning. We have started with the very basics of machine learning on Azure. They provide a perfect environment to learn this. Essentially we are trying to build a recommendation engine which can be used by social media apps to provide high quality content for its users.</li><li><strong>Angular JS</strong><br>We had a very successful year with AngularJS. Although we are working on it since the last 3 years. This year we explored an exceptionally high number of new use cases for it. We are working on a very challenging client side application which is very heavy and hence we are exploring new ways to make use of AngularJS.</li><li>We have also explored a lot in the upcoming version of AngularJS i.e. Angular 2. We are really excited looking at its speed and performance &amp; eagerly awaiting its release. This year we will be working on a live project that would be utilizing Angular 2 and Material Design in more depth. Just waiting to explore more possibilities with Angular 2.</li><li><strong>Open Source Initiative</strong><br>We love open source and GitHub. Last year we introduced a new initiative for our employees to contribute to the open source world and earn rewards for the same. It’s a win-win situation for both. They can contribute to any open source project or Promact’s own open source projects. Anyone who wants to contribute can contact us. This year we expect more contributions from our team members.</li></ol><h4><strong>A year of Apps</strong></h4><p>2015 was a huge year for mobile apps. We created many new apps targeting a multitude of issues around and bringing out a solution. 2016 would be even bigger with app launches into the marketplace. Few of our significant achievements are as follows:</p><ol><li><strong>Convozo</strong><br>Convozo is one of our major apps developed this year. Developed for IOS as well as Android users, this platform is a space for connecting with Apps and much more. The amazing thing about this app is, it would open the world of apps to the common users and connect with them much better. This app would soon be available in the coming month.</li><li><strong>Crozi</strong><br>Crozi is yet another big achievement by Promact. We have developed a beautiful platform for sharing experiences in the form of stories. The beauty of this app is in the details of its design. Designed with the concepts of Material Design &amp; engineered with Machine Learning, this app is ought to bring awesomeness. Crozi will be released shortly on the Android platform.</li><li><strong>A dozen apps a year</strong><br>Our team developed several apps (IOS, Android and Hybrid). We made apps that are useful and impactful. And we are proud to release about a dozen apps in mid 2016, all handcrafted by Promact.</li></ol><h4><strong>The Page-turner</strong></h4><ol><li><strong>We turned 13 &amp; welcomed a new CEO</strong><br>Promact recently turned 13 on 10th October, 2015 &amp; we celebrated with a bang! An evening filled with celebration &amp; appreciation of our team, we entered the next year with a vision for awesomeness. On this day the Promact family welcomed the new CEO, Swaty Shah. With this move Promact moves one step ahead towards our vision to make this organization more technically strong and to bring about an environment of creativity and innovation.</li><li><strong>A new website &amp; blog</strong><br>This year we finally bid goodbye to our good old website &amp; welcomed our brand new website which is modern, slick, simple, mobile friendly and more informative. If you haven’t yet been there, check out our new website at <a href="https://promactinfo.com/">https://promactinfo.com/</a>. Additionally, we dedicated a brand new page to present Promact’s culture and career opportunities. Check out our career section at <a href="https://promactinfo.com/careers">https://promactinfo.com/careers</a>.</li><li>Also, how can we forget this new blog! We revamped this completely. This is just a beginning, stay tuned to our blog section and stay updated with the latest tech around.</li><li><strong>A new vision</strong><br>Growing old with a younger heart! We love startups. Promact’s management team themselves being involved in the startup world since a few years are very well equipped with the nits and grits of a startup. We just geared up ourselves to make our organization more startup friendly. We already worked with 4 cool startups this year!</li></ol><h4><strong>Fun, Frolic &amp; Celebrations</strong></h4><p>Fun and celebrations has always been a very important part of the Promact family. A year spent celebrating the festivities is a good year indeed. We started 2015 with Yoga and Uttarayan (a kite-flying festival), moving ahead with our Annual Olympics, a week full of fun days, proceeding ahead with Picnics, Teacher’s day celebration and a lot more. Again at the end of the year we geared up for Olympics 2016 which we would be beginning shortly. Stay geared up on our Olympics website (<a href="http://olympic.promactinfo.com/">http://olympic.promactinfo.com/</a>) to know the latest happenings.</p><h4><strong>2016 &amp; the road ahead</strong></h4><ol><li><strong>Advanced Machine Learning, Docker and Angular 2</strong><br>There is no limit to knowledge and learning. In 2016 we would be moving a step ahead to what we had started the previous year. This year there would be a lot of experimentation on Machine Learning, Docker and Angular 2.</li><li><strong>Apps in the marketplace</strong><br>This year would be very exciting for mobile apps. We will be releasing our hard-worked apps into the marketplace.</li><li><strong>Celebrations has already begun!</strong><br>Beginning the new year with celebrations, we now proceed on to our annual Olympics 2016 beginning next week. So stay tuned.<br>We wish you a very Happy New Year!</li><li>We hope 2016 gives you all that you have wished for.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5deeeebc3ec" width="1" height="1" alt=""><hr><p><a href="https://medium.com/promact/2015-year-in-review-for-promact-d5deeeebc3ec">2015 Year in Review for Promact</a> was originally published in <a href="https://medium.com/promact">Promact</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Planning Career from the Life of Karna from Mahabharata]]></title>
            <link>https://medium.com/@chintan86/planning-career-from-the-life-of-karna-from-mahabharata-ddb28f91fff5?source=rss-5f6072eb565b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ddb28f91fff5</guid>
            <dc:creator><![CDATA[Chintan Shah]]></dc:creator>
            <pubDate>Sun, 19 Jan 2014 11:03:17 GMT</pubDate>
            <atom:updated>2014-01-19T11:03:17.863Z</atom:updated>
            <content:encoded><![CDATA[<h4>Karna’s life taught many important lessons for modern world. But today I will be looking at it from point of view of IT engineer.</h4><p>Karna, Son of Suryadev(Sun) was one of the greatest archers of Mahabharata. It is said he was born to set an example of a life with trouble, dedication of friendship and giving nature.The view I am going to present is observed in major IT companies and general culture in India.</p><h4>Entrance exams for Ivy league universities</h4><p>Karna, was born with exceptional skills of archery. His first resistance came when he was child. <strong>As Karna was not shatriya he was not allowed to learn the art of warfare.</strong> He became interested in the art of warfare and approached Dronacharya. Lets consider Dronacharya as an Ivy League IT university in India. Karna was refused any training by Dronacharya on the basis that he was not shatriya. In today’s world. Even-though you have exceptional skills in IT you are required to go through the tedious process of entrance exams (AIEEE &amp; IIT-JEE). which would ask you everything from Biology to Chemistry even-though you are not interested in them. <strong>You are simply denied entry because you didn’t had aptitude towards those areas which has no relevance to IT.</strong></p><h4>Learning the art</h4><p><strong>Karna learned the skills of warfare from Parashurama</strong>. Consider Parashurama as Internet/WWW . As any skilled engineer would do when they don’t get admission into IITs and NITs. <strong>They learn everything from the Internet and become highly skilled.</strong></p><h4>Low acceptance from IT majors</h4><p>When Karna finished his learning from <strong>Parashurama. He cursed him that he will loose all knowledge required to fire the most powerful weapon Brahmastra</strong> when he will be in need of that weapon the most because of lie he told to Parashuram for obtaining knowledge. As with most self taught engineers cursed with limited acceptance from IT major in country. <strong>Unless you are from top universities you have almost no way of joining them.</strong></p><h4>Choice of company</h4><p>Karna, after learning all wanted to be accepted by society to be a good archer. In an attempt to justify his ego and achieve something he makes the biggest mistake of his life. He joins Kaurava accepting a tempting offer from Duryodhana . He got his own kingdom of Anga. He was now king. But soon started the frustration of being in wrong company. Whatever Duryodhana did was against rules and principles of Karna. But he was now under the big favor from Duryodhana. He just wanted to prove that he is a great warrior instead he got himself into a hell and was evidently going to dead end someday.</p><p>Now, Think Kaurava as any major IT company who doesn’t value skills but treats you as more efficient machine. They do pay you very well. But work life really sucks. You will spend most of your work life under frustration and the brand name of that company would never allow you to quite. evidently you will go towards a dead end in your career.</p><h4>Contribution to Open Source to your rescue</h4><p>Even-though Karna was on the wrong side and knew his eventual end. He was know as the great giver of everything. He gave away his armor, his strong weapons just because he was extremely generous giver. This was the ability that saved his name in the History. He is admired nowadays too even-though he choose wrong side and fought Pandavas.</p><p>You can also contribute something back to community. There are tons of Open Source projects where you can make contribution and salvage the situation. you can contribute and can get excellent job opportunities from better companies who have similar belief as yours. It can also be an opportunity to learn from others and doing things differently.</p><p>Overall, The views expressed here may not apply to all But it applies to major part of IT engineers in India. In the end my only advice is to learn from mistake Karna did and become better at planning career.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ddb28f91fff5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>