<?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 Dipankar Dutta on Medium]]></title>
        <description><![CDATA[Stories by Dipankar Dutta on Medium]]></description>
        <link>https://medium.com/@dipankardutta_61331?source=rss-44caae6df72------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*sksRs_wVMqg3RLya.</url>
            <title>Stories by Dipankar Dutta on Medium</title>
            <link>https://medium.com/@dipankardutta_61331?source=rss-44caae6df72------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:38:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dipankardutta_61331/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[Top 5 reason why people get rejected in technical interview?]]></title>
            <link>https://medium.com/crackthegoogle/top-5-reason-why-people-get-rejected-in-technical-interview-a7833f4f0072?source=rss-44caae6df72------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7833f4f0072</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[google-interview]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Dipankar Dutta]]></dc:creator>
            <pubDate>Fri, 31 May 2019 23:36:00 GMT</pubDate>
            <atom:updated>2019-05-31T23:36:00.843Z</atom:updated>
            <content:encoded><![CDATA[<ol><li><strong>Lack of problem solving skill.</strong></li></ol><p>Most of the interview questions are basic and related to fundamental of computer science like data structure or algorithms.So, You need to study them well before appearing the interview. As the problem are open ended, you are expected to find out alternative solution, trade of them and pick the best solution.</p><p><strong>2. Failed to write code in white board.</strong></p><p>Interviewee might come-up with the right algorithm but often failed to translate them in the code. Specially, when they write in pen and paper or in white board. Most people write the code in code editor. But in interview, you would be asked to write the code in the white board or pen and paper. So, there is not syntax highlighter or code completion.</p><p><strong>3. Not able to optimize the solution.</strong></p><p>Most interviewee able to find-out the naive solution - <strong>brute force</strong> technique to solve the problem, but able to optimized the solution to a given time/space complexity.</p><p><strong>4. Not able to derive the complexity.</strong></p><p>Finding the complexity or the performance of your solution would be hard if you don’t have the good understanding of time complexity or space complexity . It would be more difficult when you have used a library function in your code and don’t know how they are implemented internally.</p><p><strong>5. Not able to handle follow up questions.</strong></p><p>Most of the interviewer come up with followup questions when you are able to give the right answer. It’s mainly to cross check to confirm that you not memorize the solution and able to handle the problem in a different situation.</p><p>Have your interview scheduled? We ca n help you prepare by finding out if you are missing something. Schedule an <a href="http://www.crackthegoogle.com/">appointment</a> now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7833f4f0072" width="1" height="1" alt=""><hr><p><a href="https://medium.com/crackthegoogle/top-5-reason-why-people-get-rejected-in-technical-interview-a7833f4f0072">Top 5 reason why people get rejected in technical interview?</a> was originally published in <a href="https://medium.com/crackthegoogle">CrackTheGoogle</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple & easy to use “Signaling Server” that you love!]]></title>
            <link>https://medium.com/@dipankardutta_61331/simple-easy-to-use-signaling-server-that-you-love-53b2522fd6f5?source=rss-44caae6df72------2</link>
            <guid isPermaLink="false">https://medium.com/p/53b2522fd6f5</guid>
            <category><![CDATA[rtc]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Dipankar Dutta]]></dc:creator>
            <pubDate>Sat, 06 Oct 2018 10:54:32 GMT</pubDate>
            <atom:updated>2018-10-06T10:54:32.456Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why SimplePubSub ?</h3><p>Welcome to world’s simplest signaling solution. If you are prototyping some project which requires realtime communication between multiple devices or endpoints, you are in the right place.</p><p>SimplePubSub provides a quick and dirty way to test your prototype. The API is easy and quick — however not scalable.</p><h3>SDK</h3><p>I wrote the simple and handy API for signaling multiple endpoints which is connected to SimplePubSub server. Currently SDK is written is java and javascript — but fell free to write your own and contribute it here.</p><h4>JavaScript</h4><ol><li>Import the JS file in your webpage.</li></ol><pre>&lt;script&gt; https://raw.githubusercontent.com/dipankar08/SimplePubSub/master/sdk/js/client.js &lt;/script&gt;</pre><p>2. Connect to Server — This Steps is optional if you want to use default configuration or default server endpoint.</p><pre>SimplePubSub.init()</pre><p>3. Attach the callbacks</p><pre>SimplePubSub.attach({<br>    &#39;onConnect&#39;:function(){console.log(&quot;[TEST] onConnect&quot;)}, // called when the connection established <br>    &#39;onDisconnect&#39;:function(){console.log(&quot;[TEST] onDisconnect&quot;)}, // called when disconnect<br>    &#39;onError&#39;:function(){console.log(&quot;[TEST] onError&quot;)}, // called when error <br>    &#39;onMessage&#39;:function(t,d){console.log(&quot;[TEST] onMessage : topic:&quot;+t+&quot; Data:&quot;+d)}, // called when someone send message<br>    &#39;onSignal&#39;:function(t,d){console.log(&quot;[TEST] onSignal -&gt; Topic:&quot;+t+&quot; data:&quot;+d)} // send any siging message like <br>})</pre><p>4. Subscribe the topic of your interest</p><pre>SimplePubSub.subscribe(&quot;hello&quot;)</pre><p>5. Start publishing you data. As you have subscribed, your data will send to all other device in realtime.</p><pre>SimplePubSub.publish(&quot;hello&quot;,&quot;sent hello&quot;)</pre><p>6. If you don’t want to get the message for a topic, you can unsubscribe it as below:</p><pre>SimplePubSub.unsubscribe(&quot;hello&quot;)<br>SimplePubSub.publish(&quot;hello&quot;,&quot;sent hello&quot;) // will not send the event.</pre><h3>SERVER</h3><p>You can follow 3 quick steps to setup the server. This is build on top of node-js and ws. So please make sure that we have the latest version of node-js and npm installed in your server.’</p><pre>1. git clone  <a href="https://github.com/dipankar08/SimplePubSub">https://github.com/dipankar08/SimplePubSub</a></pre><pre>2. cd SimplePubSub; npm install; node src/server.js<br></pre><p>Congratulation your server is running in port 8081.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53b2522fd6f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>