<?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 Seema Ullal on Medium]]></title>
        <description><![CDATA[Stories by Seema Ullal on Medium]]></description>
        <link>https://medium.com/@seemaisms?source=rss-ba0300164b16------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*6qcG36UXngkzJ58V.jpg</url>
            <title>Stories by Seema Ullal on Medium</title>
            <link>https://medium.com/@seemaisms?source=rss-ba0300164b16------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:16:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@seemaisms/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[Learning to speak up]]></title>
            <link>https://medium.com/@seemaisms/learning-to-speak-up-266f2d5a72f3?source=rss-ba0300164b16------2</link>
            <guid isPermaLink="false">https://medium.com/p/266f2d5a72f3</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[lessons-learned]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[speaking-up]]></category>
            <dc:creator><![CDATA[Seema Ullal]]></dc:creator>
            <pubDate>Mon, 07 Oct 2019 23:48:19 GMT</pubDate>
            <atom:updated>2019-10-07T23:52:53.821Z</atom:updated>
            <content:encoded><![CDATA[<h4>Lessons I’ve learned that have helped me speak up and deliver effective feedback</h4><p>During a recent interview, a candidate asked me about my biggest learnings during my time at Gusto, both technical and otherwise. It was easy for me to pinpoint my biggest area of non-technical growth. When I started, I was super reluctant to speak up or mention things I’d noticed whereas now, I am a (possibly annoyingly) vocal person on our team.</p><p>I’ve been thinking about how this happened, especially as I approach my four year anniversary at the company. I’m still a pretty introverted and shy person; however, I’ve learned to speak up, even when it’s not something I’m comfortable with. I realized that doing so is better than the alternative — staying quiet and regretting it.</p><p>But what specifically helped me get to this point? I can think of a few things, some that naturally occurred due to my work environment and some I had to more directly focus on myself. Here are the lessons I’ve learned that I hope will help others in a similar position.</p><p><strong>Lesson 1: Give your opinion when people seek it out </strong><br>I distinctly remember being in a meeting where there were only one or two dominant voices in the discussion. I had a lot of imposter syndrome and so I assumed they knew more about the topic than me and didn’t offer my perspective. Then, someone said, <em>“Seema, what do you think?”</em></p><p>This simple act of asking me for my thoughts went a long way. I shared what was on my mind along with why, and I was pleasantly surprised to discover that I was able to highlight some things that had been overlooked.</p><p>I found this was the first step to eventually participating on my own without anyone asking and later raising topics on my own: simply being willing to be open and honest when someone asked me a question.</p><p><strong>Lesson 2: Start with the ways you are most comfortable with</strong><br>I was always more comfortable expressing myself non-verbally, so when I began opening up and sharing my opinion, I initially did this through things like email or a chat conversation. This allowed me to think about how to best formulate my thoughts and express them clearly and concisely.</p><p>Later, I pushed myself to speak up face to face as well. I initially started this by planning some of what I had to say in advance. When I wanted to talk to my manager about focusing our conversations more on my career trajectory, I wrote out what I wanted to say in advance and then let them know I wanted to share some feedback in our next 1:1. Eventually, I felt more comfortable just speaking up in the moment, without having to plan out what I would say. The multi-step process of starting with what I was most comfortable with, then moving a little outside of it, and finally embracing what I was initially anxious about proved immensely helpful.</p><p><strong>Lesson 3: Don’t be afraid to disagree, but be open and flexible as well</strong><br>It’s uncomfortable to be a dissenting voice, but sometimes it is necessary and the only way to raise awareness of things. That being said, there have been occasions when I’ve felt strongly about something only to realize there were other factors I was missing.</p><p>Share the reasons behind your thinking, but also ask questions to get insight on where others are coming from. Some of the things I personally like to ask are “What are your thoughts?”, ‘Do you mind explaining a bit more?”, and making sure that I understand the other side accurately by saying “Just to make sure I understand correctly, you are saying ___.”</p><p>Gaining perspective from the other side can also help you find common ground. I found myself disagreeing with the technical design of a feature during a pairing session and asked about some of the decisions made. Not only was I able to learn more about the reasons behind how it was implemented and gain context I didn’t realize I lacked, but we were also able to work together to improve the code and find a better solution.</p><p><strong>Lesson 4: Be as specific and actionable as possible</strong><br>One of the most useful things I have learned is about how to deliver useful feedback. The key is to be as specific as possible.</p><p>If you find yourself consistently waiting for code reviews from a teammate, rather than saying “You never review my code quickly enough”, you can say “I noticed that the last 2 code reviews I assigned you took 5 days each. This makes it hard for me to deliver the stories within our sprint. Can we work together to make sure the time for feedback works for both of us?”</p><p>By highlighting a specific example, identifying the impact of it, and then offering to figure out a shared solution, you can make a lot more progress. Part of this also means bringing up things in a timely manner, as soon as you notice them to avoid generalizations, including phrases that involve absolutes like “always” or “never”. Focus on the specific things you notice, how they affected you (and why you care), and stay focused on actions and results.</p><p><strong>Lesson 5: Apply the lessons you’ve learned to help others also speak their mind</strong><br>The last lesson is simple: pay it forward by encouraging others to speak their mind, sharing what you have learned, and setting an example by willing to speak up even when it’s outside your comfort zone. If you are in meetings where a few people are dominating the conversation, bring it up with them on an individual basis and also encourage those less comfortable participating to do so. Simply just asking them for their opinion can go a long way.</p><p><a href="https://www.seemaullal.com/blog/finding-my-voice/">Cross posted on my website</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=266f2d5a72f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Polymorphic Associations in Rails]]></title>
            <link>https://medium.com/@seemaisms/polymorphic-associations-in-rails-d55bb72753a5?source=rss-ba0300164b16------2</link>
            <guid isPermaLink="false">https://medium.com/p/d55bb72753a5</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[polymorphism]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[activerecord]]></category>
            <category><![CDATA[rails]]></category>
            <dc:creator><![CDATA[Seema Ullal]]></dc:creator>
            <pubDate>Mon, 20 Feb 2017 08:03:05 GMT</pubDate>
            <atom:updated>2018-06-17T02:33:13.976Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first saw polymorphic associations in Ruby on Rails code, I was a little confused. However I have since realized that using this type of association make perfect sense in certain situations and Rails provides a elegant and easy way to model this.</p><h4>Normal Associations</h4><p>Most of our time, a model association that will always refer to the same type of model. Imagine a Student model which belongs to a Teacher and also has one Address. Assuming a single student has only one teacher and one address, the student model will look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/237/0*5vdrDjZmf5IqYuLw.png" /></figure><p>and the rails code will look something like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cf9685c6316c0903b0f6dbc4e07b9baa/href">https://medium.com/media/cf9685c6316c0903b0f6dbc4e07b9baa/href</a></iframe><p>This is what we are used to seeing in most SQL databases– the teacher_id and address_id on the student model tell you which Teacher and which Address is associated with a student. This works since we know in advance what the model type of the associations will be (Teacher and Address).</p><h4>What If The Association Can Refer to Multiple Type of Models?</h4><p>Imagine that you are designing a database where you have a Payments table and each Payment can be for a Employee, Company, or Contractor. You could have columns for employee_id, company_id, and contractor_id and only store the one that the payment is associated with.</p><p>For example, if the Payment is for an Employee, you would store employee_id and have company_id and contractor_id be null.</p><p>There are several issues with this solution. For one, you will always have at least 2 columns that are null and if you add more model types that the payment could be associated with, this number grows. The code will also look something like this, which loses a lot of the readability you normally get with Ruby on Rails:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a4e396a02a5680f9e8ae043b06974b22/href">https://medium.com/media/a4e396a02a5680f9e8ae043b06974b22/href</a></iframe><p>If you look at the above code, it isn’t clear that a payment should only be associated with an employee OR a company OR a contractor. You could add a comment letting the person reading the code know that this is the case or have validations to enforce that only one of the 3 is set, but this too starts to get messy quickly.</p><p>Another potential solution would be to have different types of payment- EmployeePayment,CompanyPayment, and ContractorPayment. Since these are likely to share a lot of code, this solution will lead to a lot of repetition and a bunch of tables that are nearly the same.</p><p>Polymorphic associations allow for a more desirable solution.</p><h3>Polymorphic Associations</h3><p>With polymorphic associations, you store both the id of the associated model along with its type. So in the above example, Payment would have a payee_type and payee_id. Now, if a payment was for an employee, you would store the employee id as payee_id and then store &quot;Employee&quot; as &quot;payee_type&quot;.</p><p>Let’s look at how we would create this in Rails:</p><p>First, create the Payment table:</p><pre>rails g model Payment amount:Float payee_id:integer payee_type:string</pre><p>Now, your app/models/payment.rb will need to contain similar to the following in order to define the polymorphic relationship (note that the above migration won&#39;t do this automatically though you can <a href="https://richonrails.com/articles/rails-model-generator-shortcuts">use a generator that does set this up</a>.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a95727a5440c586a1dcf9bc491035c96/href">https://medium.com/media/a95727a5440c586a1dcf9bc491035c96/href</a></iframe><p>We also need to make sure that Employee, Company, and Contractor have a relationship with Payment since one employee can have multiple payments and so on.</p><p>Here is what the code for Employee may look like; Company and Contractor will be very similar:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e86c3fab0693e9f84aeaa852b139eb7c/href">https://medium.com/media/e86c3fab0693e9f84aeaa852b139eb7c/href</a></iframe><h4>Querying with Polymorphic Associations</h4><p>With the above approach, we can easily find the payments for a given employee or company or contractor. For example, if we want the payments for the first contractor, we could use the following code using ActiveRecord: Contractor.first.payments. Rails is smart enough to know that this means you want records where payee_type is &quot;Contractor&quot; and payee_id matches the id of the first contractor.</p><p>Rails makes it equally easy to specify polymorphic relationships. Instead of assigning payee_id AND payee_type, you can just assign payee and it will take care of setting the two columns. Here&#39;s an example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f5f9f196af6159a7f0a07e9884039cab/href">https://medium.com/media/f5f9f196af6159a7f0a07e9884039cab/href</a></iframe><p>The bottom line: if you have a model that has an association that could be several different types, polymorphic associations can be useful.</p><p><em>Originally published at </em><a href="http://seemaullal.com/blog/polymorphic-associations-in-rails-when-and-why-to-use-them/"><em>www.seemaullal.com</em></a><em> on February 20, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d55bb72753a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Git Commands You Should Be Using if You Aren’t Already]]></title>
            <link>https://medium.com/@seemaisms/git-commands-you-should-be-using-if-you-arent-already-fcb9deab928f?source=rss-ba0300164b16------2</link>
            <guid isPermaLink="false">https://medium.com/p/fcb9deab928f</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[terminal]]></category>
            <category><![CDATA[version-control]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Seema Ullal]]></dc:creator>
            <pubDate>Sat, 07 Jan 2017 06:23:42 GMT</pubDate>
            <atom:updated>2018-06-17T02:11:50.099Z</atom:updated>
            <content:encoded><![CDATA[<p>At my first internship, nobody told me about their version control system (which was significantly more painful than using Git is anyways).</p><p>Inevitably, something went wrong one day and I lost a lot of work. I used my own rudimentary version control after that, making copies of my code in 10 different places and naming the copies things like<em> “finally working version 03–24–13”</em>. When I finally started using a different version control system and later Git, I wished I could go back in time and save myself all the time and head banging that not a proper VCS caused.</p><p>However if you’re mostly just using git commit -m and git add and basic branching, you are missing out on some of the commands that make git especially useful. One thing I won&#39;t mention here is <strong>interactive rebasing *</strong> which I will write a later blog post on.</p><p>Here are a few git commands that I wish I had used sooner than later.</p><ol><li>git commit -p (git add -p is similar but only adds the files instead of commiting them): <strong>look at each change and only commit the things you want to</strong></li></ol><p>If you have ever worked on a codebase with a lot of files (or even if you haven’t) there have probably been times you accidentally edited a file you didn’t mean to– maybe you accidentally added a space or a typo to a file or had a leftover binding.pry or debugger or an embarrassing comment/note to yourself. There are sometimes changes you made that you actually don’t want to (accidentally) commit.</p><p>git commit -am or git add . or other similar commands are dangerous because you have no idea what the changed files contain. You can do git diff first but that&#39;s an additional step to remember.</p><p>git commit -p shows you each change you have made and asks you whether it should actually add them to the commit change list. If you indicate no, the changes are preserved but just not committed</p><p>I personally use git commit -p for the following reasons:</p><ul><li>to make sure I am only committing things I actually intend to commit</li><li>to help me split a huge amount of changes into smaller commits</li><li>when I change multiple parts of a file but only want to commit a few of those changes (instead of the whole file)</li></ul><p>When you git commit -p you get a nice summary of each change and are asked whether you want to include it in the commit. Here is an example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/569/0*VgUUBLw2jNmxDh_f.png" /></figure><p>While it takes a bit longer to initially commit (since you are looking at each change), git commit -p will definitely save you from lots of revisions, mistakes, and ultimately save you time. It is the only way I commit most of the time and has been super helpful.</p><p>2 . git reset HEAD^ <strong><em>Undo your last commit</em></strong></p><p>While I still use git stash quite a bit to store changes to files that I want to temporarily store away and not be part of my code (often when switching branches), I find that it can be hard to manage all your stashes and remember what is going on (even if you use use git stash save to specify a description for the stash) - git reset HEAD^ removes the most recent commit but still keeps all of the changes it has made. This is great when you want to edit or add to the previous commit or when the commit is a &quot;temporary&quot; work in progress commit that you are just storing temporarily</p><p><strong>My use case for this is either when I have made a bunch of changes that I intend to break up later into smaller commits or when I want to have a temporary stopping point to come back to.</strong> I have an alias, g undo for this which makes it super easy for me to remember. If you want to &quot;undo&quot; multiple commits, you can do git reset HEAD^2 or git reset HEAD~2 ( <a href="http://www.paulboxley.com/blog/2011/06/git-caret-and-tilde">here is a great resource</a> on the difference between those two)</p><p>3.git stash <strong><em>copying and pasting your file changes</em> </strong><br> I have this bad habit of sometimes starting to make changes on the wrong branch. - I also often make changes to a branch and then need to switch branches but don&#39;t want to commit my changes just yet (lately I have been using the git reset^HEAD for this particular thing however).</p><p>Sometimes, I also go down a particular path and realize it may be the wrong one and need to start over but don&#39;t want to lose all my changes in case I need them in the future. - <strong>git stash is perfect for all of these situations. It basically takes all of your changes and &quot;cuts&quot; them and stores them away. Later on, you can use</strong><strong>git stash apply or </strong><strong>git stash pop to &quot;paste&quot; the changes back into your code</strong> (the latter deletes the stored changes from storage after &quot;pasting&quot; them while the former keeps them around. I almost always use git stash pop since once you paste the changes, you either will stash them again or commit them and there is no reason to keep them stored).</p><p>The problem with just git stash is that it can be hard to figure out which stash contains what changes. <strong>I personally always use </strong><strong>git stash save (description) to give my stashes a description I can later read and understand.</strong> When you do git stash list, you are shown a list of all the stashes you currently have stored including any descriptions you included Normally, git stash pop (and apply) default to the last stash (the most recent one) but you can also specify which one you would like to pop/apply/show (show tells you which files were changed). I have the aliases gsh (for git stash) and gsv (for git stash save) since I use these super often.</p><p>Here are some slides from a talk on Git that I gave to students at <a href="http://www.hackbrightacdemy.com/">Hackbright Academy</a></p><p><a href="http://slides.com/seemaullal/deck-7-11#/">Git It</a></p><p>These are just a few of a bunch of Git commands that I use constantly. Becoming more familiar with git (and having a ton of aliases) has made my life a whole lot easier and also helped avoid a lot of mistakes.</p><p>Feel free to email me if you have any questions. Thank you for reading!</p><p><em>Originally published at </em><a href="http://www.seemaullal.com/blog/life-saving-git-commands/"><em>www.seemaullal.com</em></a><em> on January 7, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fcb9deab928f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Further thoughts on interviewing]]></title>
            <link>https://medium.com/@seemaisms/further-thoughts-on-interviewing-33014192bdb8?source=rss-ba0300164b16------2</link>
            <guid isPermaLink="false">https://medium.com/p/33014192bdb8</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[interviewing]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding-interviews]]></category>
            <category><![CDATA[job-search]]></category>
            <dc:creator><![CDATA[Seema Ullal]]></dc:creator>
            <pubDate>Wed, 04 Nov 2015 20:21:07 GMT</pubDate>
            <atom:updated>2018-06-16T22:48:40.728Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently wrote down some thoughts on interviewing and thought they might make a good blog post. This is sort of a follow up to <a href="https://medium.com/@seemaisms/finding-your-first-job-as-a-software-engineer-9f1ad61ada7f">my previous post, which was more the job search as a whole</a> (this is more interview specific).</p><p>I would definitely say that every interview (and interview process as well) is different. I had some interviews that were very knowledge based– questions like “What are the 4 common HTTP methods and when would you use them?”</p><p>Others were more about your thought process, critical thinking, and how you solve a problem. These types of interviews are more language agnostic– they care more about general programming and problem solving ability then if you know specific bits of information.</p><p>Of course, you still need to know enough details about some programming language to solve these more general questions. Others may even require knowledge of a particular language. A good example of this was one of my interviews, where I got asked a general programming problem but the question required me to know things like scope in Javascript (and how to use `call` and `apply` and `bind to change the “this”). I definitely think it’s important to be quite comfortable with one language at the minimum, but also flexible enough to program in a language you don’t know.</p><p>I would say there are kind of 3 general kinds of interview questions, at least for more entry level or “junior” roles:</p><ol><li>the knowledge based ones (usually these are more short answer and way more common for more scoped roles like front-end positions)</li><li>Code Wars like problems: questions that are not too hard to understand but more about whether you can write code that works and is well written)</li><li>Questions that are more algorithmic in nature (data structures related a lot of them time)</li></ol><p>Sometimes the 2nd and 3rd category overlap, where you have a question that mainly tests whether you can write good (and working code) but it may also cause you think about how to best solve the problem. I think the main difference between category 2 and 3 is that problems in the second are a bit more straightforward while the third requires more creativity and thought.</p><p>It obviously helps to know what you should expect at the interview. I found this out 3 ways: by asking the people who set up my interviews (so either the person scheduling it, or if I had a phone interview with an engineer, I would ask them about their onsite interview format), by asking other people who work with, and using <a href="http://www.glassdoor.com/">Glassdoor</a> (a super helpful resource).</p><p>I mention a few specific resources at t<a href="https://medium.com/@seemaisms/finding-your-first-job-as-a-software-engineer-9f1ad61ada7f/#061a">he end of my previous post</a>, but I mostly just did Code School problems, reviewed concepts, and sometimes did questions from Cracking the Coding Interview and other sources. I think a good general principle is dividing each day between interviews (both on sites and phone screens), practicing and preparing, emailing people you know to refer you, applying through AngelList and StackOverflow careers, and also reserving some time for non job search things.</p><p><em>Originally published at </em><a href="http://seemaullal.com/blog/further-thoughts-on-interviewing/"><em>www.seemaullal.com</em></a><em> on November 4, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33014192bdb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding your first job as a software engineer]]></title>
            <link>https://medium.com/@seemaisms/finding-your-first-job-as-a-software-engineer-9f1ad61ada7f?source=rss-ba0300164b16------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f1ad61ada7f</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[interviewing]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[coding-interviews]]></category>
            <category><![CDATA[first-job]]></category>
            <dc:creator><![CDATA[Seema Ullal]]></dc:creator>
            <pubDate>Sun, 13 Sep 2015 08:21:14 GMT</pubDate>
            <atom:updated>2018-06-16T19:03:19.814Z</atom:updated>
            <content:encoded><![CDATA[<p>After I finished up my teaching fellowship at <a href="http://www.fullstackacademy.com/">Fullstack Academy</a> in July, I spent about a month (which felt like a lot longer at the time) interviewing for my first full-time software engineer position. Eventually, I accepted a job that I am super excited about in mid-August (conveniently, I chose not to start until next month). My goal in writing this is to share some of my thoughts on the interview process– things that I wish I had known and/or things that helped me in my own search and interviewing. —</p><h4>1. Be persistent</h4><p>The job search can be exhausting, frustrating, and deflating at times. Most people will receive many more rejections than offers, and a lot of these rejections will be things out of your control (for me, this was most commonly “We are looking for more experienced candidates”) and before you even get a chance to prove your qualifications through an interview.</p><p>If you are truly interested in a company that turns you down for not having enough experience or something similar, and believe they would be a good fit for what you are looking for, you should email them and let them know why they should consider your despite your lack of experience. Mention specific things that distinguish you and make you right for the job. Even if it doesn’t work, you have very little to lose, and the company might even remember you to consider you for future openings.</p><p>If you do interview with a company and they don’t offer you a position, I <strong>strongly</strong> suggest asking for feedback. There were 2 reasons I am glad I asked for feedback. One, it helped me improve as a candidate and two, a lot of the people I spoke with were nice and not only gave me constructive criticism but also pointed out things they did like about my interviews. This is a nice confidence boost in what can be a tough time.</p><h4>2. Do your Research</h4><p>This might seem obvious, but read about the company and ask the people interviewing questions. <a href="http://www.glassdoor.com/index.htm">Glassdoor</a> is a great way to learn about the experiences of employees at companies you are interviewing at and their Interviews section can give you some insight as to what to expect.</p><p>Make sure you have questions to ask your interviewers. There are some questions I asked almost every interviewer/company I spoke with (for example, “What is one interesting and challenging problem you have worked on at this company”) but it is good to have more specific questions also. You also might be interviewing with multiple people- some may be engineers, some may be product managers, some may do other things. Have a good variety of things to ask and make sure they aren’t questions you could easily find out from the company’s website. You should be interested in the company and the work they do, and the questions you ask can demonstrate this to your interviewers.</p><h4>3. Practice- but don’t memorize things</h4><p>There was a time when I did a large number of problems from <a href="http://www.amazon.com/Cracking-Coding-Interview-6th-Edition/dp/0984782850/"><em>Cracking the Coding Interview</em></a> because I thought I needed to know a bunch of fancy algorithms to get a job. I still think this book is a good resource, but don’t get too caught up with memorizing the solutions in it. Why not?</p><ul><li><strong>Every interview is different.</strong> Some will ask you to do coding exercises (most of mine were on a whiteboard or piece of paper, with a few in a shared code editor where they could see what I was typing [this was always during a phone screen]) while others will ask you most knowledge based questions (these types of questions were also far more frequently asked in phone screens). Again, this is part of doing your research and knowing what to expect from the interview (you can also ask about interview format when you set the interview up).</li><li><strong>Good interviewers will come up with unique problems.</strong> It’s easy to ask commonly known questions, like those listed on Glassdoor or in the CTCI book. However, since well prepared candidates will have seen these when they were preparing for the interview, they don’t tell the company much about you. Memorizing solutions won’t help you if get asked a question you have never seen before.</li><li><strong>On that note, if you see a question you have seen before, be honest.</strong> Even if you think you are being a great actor and acting confused and then miraculously coming up with an answer after being deep in thought, you are not doing yourself any favors. A huge part of interviewing is showing the interviewer how you think, how you approach tough problems. If you have seen the solution, even if you try to pretend you haven’t, this process is going to be different and will not truly show how you approach a problem. Note: In my interviews, there were I think 4 or 5 interview questions I got asked that I had seen before. All but 1 of the interviewers made me do the question anyway, even after I told them I had seen the problem. So don’t lie about it as a way to get out of a question you are confused by.</li><li><strong>There are some basic ways of thinking about problems and analyzing your solutions that you should know.</strong> This is definitely not a complete list but some of these include: using the <a href="https://en.wikipedia.org/wiki/Greedy_algorithm">greedy</a> approach, knowing when to use <a href="https://en.wikipedia.org/wiki/Dynamic_programming">Dynamic programming</a>, recursion, <a href="https://en.wikipedia.org/wiki/Big_O_notation">Big O Notation</a>, data structures (I didn’t get asked about these in most interviews, but I did in some so it pays off to know the basics).</li></ul><h4>4. Use the interview process to decide whether you really want to work at the company</h4><p>You can tell a lot about a company through their interview process. Are they apathetic, or do they actually seem to care about you and want you to work there? Do they ask you thoughtful questions or did they just find some random problem from HackerRank that they clearly had not looked at in detail? (this actually happened to me; when I asked my interviewer questions about the problem, he could not answer them…) Do the employees at the company seem excited about what they do?</p><p><strong>A lot of people think of the interview process in terms of how to best impress the employer. I like to think of it more about finding the perfect match, a place to work that is the right fit for both you and the employer.</strong> It should be a place that you actually want to work, and a place that is excited to have you join their team. Use the interview process to learn about the company and to help you determine these things. Figure out what you value most, and if the position has what you are looking for. If possible, talk to employees who work there about their experiences and see if they can answer any questions you still have.</p><p><strong>Job searching can be tough, but when you find the right job, it will be worth it. Everyone’s process is different, but I think one way to divide your time is to divide it between these things:</strong></p><ol><li>practicing/studying/coding (see the resources I mentioned below for some ideas on where to do this)</li><li>contacting people you know who work in the industry (or friends of friends who are at companies you are interested in– use LinkedIn to help you figure this out!)</li><li>applying to places where you do not have referrals (AngelList and StackOverflow careers are two sites a lot of people I know have used; I personally did not use either very much so I cannot say much about them)</li><li>interviewing- make sure you have enough time to devote proper time and energy to your interviews. I tried to schedule no more than 1 in-person interview and 1 phone screen a day; there were times this did not work out, but that was how I liked to balance my time</li><li>Do something completely unrelated to finding a job. I do think it is very important to rest, relax, and do other things as well.</li></ol><p>Best of luck to anyone reading this position who might be in the hunt for their first job as a software developer!</p><h4>Lastly, here are some of the resources I used to practice my skills while I interviewed (along with those I already mentioned like the CTCI book):</h4><ul><li><a href="http://www.codewars.com/">Codewars</a></li><li><a href="http://exercism.io/">Exercisms</a></li><li><a href="http://katemats.com/interview-questions/">Epic List of Interview Questions from kate{mats}</a></li><li><a href="https://projecteuler.net/">Project Euler</a></li><li><a href="https://github.com/h5bp/Front-end-Developer-Interview-Questions">Frontend Developer Questions</a> . <em>Note: I didn’t use this resource much because I was not too interested in pure frontend positions but if you are interviewing for a position involving a particular language or framework, make sure you Google interview questions about that language or framework and are prepared to answer them</em></li><li>this set of Javascript problems that I put together <a href="https://github.com/seemaullal/preacto-workshop">https://github.com/seemaullal/preacto-workshop</a>. Each has corresponding tests you can run to check your solution and explanations.</li><li><a href="https://github.com/seemaullal/CrackingTheCodingInterview-JS">some of the <em>Cracking the Coding Interview</em> problems in JavaScript that I’ve solved</a> <em>This is something that I have since taken a long hiatus from (so that I can learn Ruby) but there</em> <em>are a few solutions there from when I was contributing to the project.</em></li></ul><p><em>Originally published at </em><a href="http://seemaullal.com/blog/technical-interviews/"><em>www.seemaullal.com</em></a><em> on September 13, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f1ad61ada7f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No API? No Worries.]]></title>
            <link>https://medium.com/@seemaisms/no-api-no-worries-a89a0e3221a9?source=rss-ba0300164b16------2</link>
            <guid isPermaLink="false">https://medium.com/p/a89a0e3221a9</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[cheerios]]></category>
            <category><![CDATA[web-scraping]]></category>
            <dc:creator><![CDATA[Seema Ullal]]></dc:creator>
            <pubDate>Sat, 13 Jun 2015 22:31:28 GMT</pubDate>
            <atom:updated>2018-06-16T18:52:27.536Z</atom:updated>
            <content:encoded><![CDATA[<p>When <a href="http://munzicodes.com/">Munzi Codes</a> and I first made the <a href="http://www.bechdelerator.com/">Bechdelerator</a> during a hackathon a while ago, we needed to get movie scripts so we could analyze them.</p><p>Unfortunately, we soon discovered that there was only one real source for them and it was a bit of a pain to work with. Here is a screen shot of where the scripts came from:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*ZlpN7v-3PCicZr9K" /></figure><p>There was no API, no easy way to predict what the links to the scripts would be, and no apparent way for users to quickly get a script for a specific movie.</p><p>Since we had a limited amount of time, we focused on what would be more impressive for the hackathon- analyzing the movie scripts, making a graph using D3 that represented conversations between characters in the movie, and predicting whether the movie <a href="https://en.wikipedia.org/wiki/Bechdel_test">passed the Bechdel tes</a>t.</p><p>The only way for people to use our site was to manually copy and paste the script from the website. Clearly a less than ideal solution, and even our own friends and family did not want to use the site.</p><p>When we finally decided that copying and pasting needed to end and wanted to find a way to get the information directly from <a href="http://www.imsdb.com/">IMDSB</a>, we quickly decided on using <a href="https://github.com/cheeriojs/cheerio">Cheerio</a> to scrape the information we needed from the site and the <a href="https://github.com/request/request">Request</a> library to make requests to the site.</p><p>Cheerio is awesome because it allows you to essentially write jQuery and use CSS selectors to get content from a website.</p><p>For example, here is part of the HTML from the IMDSB website:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2c158f3ab1cb7d37cb2a7fe80b7ed49b/href">https://medium.com/media/2c158f3ab1cb7d37cb2a7fe80b7ed49b/href</a></iframe><p>To get the data we need, after installing and requiring the Cheerio and Request node modules (you can do this easily with npm install cheerio or npm install request), we can now do things like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a7e4f0c7452eea4175e4893a905492d3/href">https://medium.com/media/a7e4f0c7452eea4175e4893a905492d3/href</a></iframe><p>The code above has previously loaded all of the HTML from <a href="http://www.imsdb.com/all%20scripts/">IMDSB</a> using the request library. We need to then get the table that contains all the links to movie scripts. Since we can see from the HTML of the page that this table has a child with the text “All Movie Scripts”, we can use</p><pre>$(&quot;h1:contains(\&quot;All Movie Scripts\&quot;)&quot;).parent();</pre><p>to get the table element.</p><p>Next, since the every movie script link has ‘/Movie Scripts’ in its URL, we can use</p><pre>$(&#39;a[href^=&quot;/Movie Scripts&quot;]&#39;)</pre><p>to get an array like object of every &lt;a&gt; element that has a link to a movie script. Note that while this is an array like object an we can use .map on it, it is not actually an array and that is why we use Array.prototype.slice.call on it to convert it to an actual array.</p><p>Now that we have the list of all movie script links, we can render a page that uses this data using a template engine (we used <a href="http://paularmstrong.github.io/swig/">Swig</a>).</p><p>Once a user selects a script from our list of all scripts, we then use the URL of the script and the cheerio library to actually get the text of the script and then analyze it with our algorithm.</p><p>Cheerio makes crawling HTML pages very simple since you can just use CSS selectors (just like you do in jQuery) to select the page elements you want. It is a great option when working with data sources that have no API or other way to easily access the information you need. I definitely recommend checking it out and adding it to your next project.</p><p><em>Originally published at </em><a href="http://seemaullal.com/blog/no-api-no-worrries/"><em>www.seemaullal.com</em></a><em> on June 13, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a89a0e3221a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>