<?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 Polina Soshnin on Medium]]></title>
        <description><![CDATA[Stories by Polina Soshnin on Medium]]></description>
        <link>https://medium.com/@polinadotio?source=rss-a2ce3ec87397------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ri6Qtzw9vnuh7onxSFRZjA.jpeg</url>
            <title>Stories by Polina Soshnin on Medium</title>
            <link>https://medium.com/@polinadotio?source=rss-a2ce3ec87397------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 01:04:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@polinadotio/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[Designing better Angular directives]]></title>
            <link>https://medium.com/@polinadotio/designing-better-angular-directives-c48555adbd7f?source=rss-a2ce3ec87397------2</link>
            <guid isPermaLink="false">https://medium.com/p/c48555adbd7f</guid>
            <category><![CDATA[angularjs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Polina Soshnin]]></dc:creator>
            <pubDate>Sat, 18 Jun 2016 05:04:45 GMT</pubDate>
            <atom:updated>2017-09-09T18:30:40.087Z</atom:updated>
            <content:encoded><![CDATA[<p>There is a common pitfall when designing directives.</p><p>Let’s say you are fetching user profile information. Consider the following directive definition:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f421b1da48a25ddbd76a0f528d0128f3/href">https://medium.com/media/f421b1da48a25ddbd76a0f528d0128f3/href</a></iframe><p>and its accompanying template:</p><pre>&lt;div class=&quot;profileInfo&quot;&gt;</pre><pre>  &lt;profile-title <br>    ng-if=”profile” <br>    title=&quot;profile.title&quot;&gt; <br>  &lt;/profile-title&gt;</pre><pre>  &lt;profile-description <br>    ng-if=”profile”  <br>    description=&quot;profile.description&quot;&gt; <br>  &lt;/profile-description&gt;<br> <br>&lt;/div&gt;</pre><p>There are two of problems with this approach.</p><h3>Problem #1</h3><p>The most obvious issue is the use of <strong>profile.title</strong> and <strong>profile.description</strong> in the template. Scope.profile is not available until the <strong>$http.get</strong> request in the link function finishes. The template may (and probably will) render before the request finishes, which will cause <strong>profile.title</strong> and <strong>profile.description</strong> to be called on an undefined value.</p><p>Note that the following solution does not work:</p><pre>&lt;div class=&quot;profileInfo&quot;&gt; </pre><pre>  &lt;profile-title <br>    ng-if=”profile” <br>    title=&quot;profile.title&quot;&gt; <br>  &lt;/profile-title&gt; </pre><pre>  &lt;profile-description <br>   ng-if=”profile”  <br>   description=&quot;profile.description&quot;&gt; <br>  &lt;/profile-description&gt;<br> <br>&lt;/div&gt;</pre><p>The reason is that the <strong>profile-title</strong> and <strong>profile-description</strong> directives will still try to compile, which will try to evaluate the title and description attributes so they can be passed to each directive’s scope.</p><p>The solution is to place an ng-if=”profile” on a parent element:</p><pre>&lt;div ng-if=”profile” class=&quot;profileInfo&quot;&gt;</pre><pre>  &lt;profile-title <br>    ng-if=”profile” <br>    title=&quot;profile.title&quot;&gt; <br>  &lt;/profile-title&gt;</pre><pre>  &lt;profile-description <br>   ng-if=”profile”  <br>   description=&quot;profile.description&quot;&gt; <br>  &lt;/profile-description&gt;<br> <br>&lt;/div&gt;</pre><p>With this approach, Angular will not attempt to compile the child directives until <strong>scope.profile</strong> is populated when the <strong>$http.get</strong> request finishes (if it finishes successfully). Using this pattern, the inner content does not become visible until profile is present on the scope.</p><h3>Problem #2</h3><p>The second issue with the directive example is much less obvious, and it has to do with the following code snippet:</p><pre>$http.get(&quot;/api/profiles/&quot; + scope.profileId)</pre><p>In the scope directive definition, <strong>profileId</strong> is passed in from a parent directive in the element attributes. <strong>ProfileId</strong> may not be available on the scope at the time the link function runs. Put another way, the link function might run before Angular sets up the scope. In this example, the GET request might end up looking like <strong>/api/profiles/undefined</strong>.</p><p>There are two ways around this. One is to store any data the link function needs on a service which gets initialized before any directives are compiled, for example, in module.run. This is the recommended approach: whenever possible have data be held by services instead of directives.</p><p>TODO: Talk more about the recommended approach from a technical/philosophical perspective.</p><p><em>Originally published at </em><a href="http://polina.io/writing/2016/ng-directive-scope-link.html"><em>polina.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c48555adbd7f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Technical Interviewing Roadmap]]></title>
            <link>https://medium.com/factory-girl/your-technical-interviewing-roadmap-14ead29c468d?source=rss-a2ce3ec87397------2</link>
            <guid isPermaLink="false">https://medium.com/p/14ead29c468d</guid>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[jobs]]></category>
            <dc:creator><![CDATA[Polina Soshnin]]></dc:creator>
            <pubDate>Sat, 23 Apr 2016 04:54:28 GMT</pubDate>
            <atom:updated>2016-04-23T04:54:28.883Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s go over organizing your interview process like a boss.</p><h3>Part One: Organization</h3><p>Keep track of your interviews as they navigate through different states. I’ve tried using both Asana and Trello, and find Trello to work very well. Based on my experience interviewing, these are the possible states:</p><ul><li><strong>Applied</strong>: Online, Referral, or Career Fair/Hiring Network.</li><li><strong>Coding Challenge</strong>: HackerRank timed toy problem(s), multiple choice, or take home project.</li><li><strong>Phone Screen Recruiter</strong>: Behavioral interview.</li><li><strong>Phone Screen Hiring Manager</strong>: Professional background, trivia web/cs questions, personal projects.</li><li><strong>Phone Screen Coding</strong>: CoderPad shared live coding or verbally explain toy problem algorithm with an engineer.</li><li><strong>Onsite</strong>: Whiteboarding algorithms/systems design, behavioral, live coding/pairing, presenting/extending project.</li><li><strong>Offer</strong>: Compensation, base salary, etc.</li><li><strong>Completed</strong>: no longer in the interviewing process.</li></ul><p>Link to <a href="https://trello.com/b/4eJNcg7E/interviewing-trello-board">Trello template</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7j8g6JrQHtfe2RMI.jpg" /></figure><h4>How to use:</h4><ul><li>Number your apps to keep track of how many you’ve done. You’ll be able to see the last number in your Trello history stream.</li><li>Paste the job title and copy of description of job in the card to be able to reference job description later: I’ve found that companies will sometimes take down the job description and then 2 weeks later ask for an interview and at that point I would have forgotten what I had applied to, so document it! It also helps to have it in front of you when you’re interviewing.</li><li>Document your entire process with a company in card comments: what went well, what didn’t go well, what questions were asked, when did you last ping them, etc.</li></ul><h4>Google Drive</h4><p>In addition to tracking, it’s incredibly important that you keep all of your application and interviewing materials organized and up to date. This is what worked for me:</p><ul><li>Resume (PDF)</li><li>Resume (Original)</li><li>Resumes</li><li>Cover Letters</li><li>Cover Letter Template</li><li>One tailored cover letter per company applied</li><li>Email Templates</li><li>Scheduling</li><li>Rejection</li><li>Thank Yous</li><li>Negotiation</li><li>Behavioral Phone Screen Worksheet</li><li>Angelist Template</li><li>Apps and Questionnaires (custom applications, ex. essay questions/multiple choice)</li><li>Company List/Notes</li><li>Recruiter Screen Notes</li><li>Personal Project Review</li><li>Additional Phone Screen Notes to help you feel prepared</li></ul><h4>Github</h4><ul><li>Algorithms and toy problem repo</li></ul><p>I found that redoing toy problems and seeing my progression through them/doing them in different ways was very helpful. Documenting my toy problem process on Github was also satisfying and kept me motivated to do it at least once a day.</p><h3>Part Two: Execution</h3><p><strong>Applications</strong>:</p><ul><li>Initially apply to up to 5 a day. Start at 5 or more a day in the first couple weeks.</li><li>When you have just about as many companies as you feel comfortable interviewing with at a given time, stop sending applications or keep it to 1–2 a day. This will depend on the individual, but I wouldn’t ramp up applying again until you have less active interviews in your funnel than you’d like.</li></ul><p><strong>Phone Screens</strong>:</p><ul><li>One hour warmup (Interviewing is a performance. Figure out what works for you).</li><li>I schedule phone interviews in the mornings (9am-12pm). Figure out if there’s a good time of day for you.</li><li>I have a sheet of paper with me with the name of the interviewer(s) written on it, the name of the company, a reference of the job description handy, a reference of my notes pertaining to the kind of interview, and a list of questions specific to the company.</li><li>Make sure you have a glass of water.</li><li>I put my phone on speakerphone, which works pretty well for me and lets me take notes. Some people prefer nice headphones.</li><li>I also have my computer handy and a copy of my resume. Sometimes a recruiter/hiring manager will want you to take a look at something online in the middle of the interview.</li></ul><p><strong>Onsite</strong></p><ul><li>Bring a folder with you to the onsite and your computer/power cord.</li><li>Bring extra copies of your resume.</li><li>Bring a water bottle.</li></ul><p><em>Originally published at </em><a href="http://polina.io/writing/2016/organizing-your-interview-process.html"><em>polina.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14ead29c468d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/factory-girl/your-technical-interviewing-roadmap-14ead29c468d">Your Technical Interviewing Roadmap</a> was originally published in <a href="https://medium.com/factory-girl">Polina Soshnin</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>