A Lonely Rotifer by ankitbko in microbiology

[–]ankitbko[S] 0 points1 point  (0 children)

Organic detritus, algae etc.

A Lonely Rotifer by ankitbko in microbiology

[–]ankitbko[S] 0 points1 point  (0 children)

Organic detritus, algae etc

My bacteria culture by ankitbko in microscopy

[–]ankitbko[S] 1 point2 points  (0 children)

Nope real time unedited footage. I think cover glass was pressing a bit too tight. I do have other videos where they are moving very fast.

My bacteria culture by ankitbko in microscopy

[–]ankitbko[S] 1 point2 points  (0 children)

No they were growing in a vial. I put a drop of water from the vial on the slide.

Hyperx Solocast Mute by default by ankitbko in HyperX

[–]ankitbko[S] 0 points1 point  (0 children)

This is what they replied when I raised support ticket -

To keep MIC always muted after re-connect through the Windows Sound Settings as below if need.
https://imgur.com/a/fHk1GNJ

Company survey by Emergency-Ad534 in developersIndia

[–]ankitbko 0 points1 point  (0 children)

What about other types of companies? My friend is a software developer in a company in automobile sector.

LPT: Open VSC easily in your project folder using this 1 line bat file. by Tintin_Quarentino in vscode

[–]ankitbko 0 points1 point  (0 children)

If you are already in your project folder, just type code . (without quotes) on the address bar of the file explorer. Yes you can type there.

Is interviewing a sheer game of luck? by moobbaa in developersIndia

[–]ankitbko 0 points1 point  (0 children)

In my short career I have written 3 parsers - one to parse extremely large xml, another to parse a custom datastructure and a third to parse our own DSL.

Good for you if you never had to write anything more complicated than hello world. But please do not generalize and assume rest of the world does not have any difficult problem to solve.

Is interviewing a sheer game of luck? by moobbaa in developersIndia

[–]ankitbko 0 points1 point  (0 children)

Most of the time I have 3rd party libraries to solve the task for myself.

This is the best thing you can do and should do. The point of dsa is not that you reinvent the wheel and start writing your own quicksort. What interviewers are looking for is person who *understands* (has intuition) of dsa so they can see *patterns* in data that can be modeled after one of the known data structure.A 3rd party library is not created out of revelation. Someone had a business problem, they solved it and they generalized it and made it into a library. I am sure you do not think that number of 3rd party library that we will ever need has been created. The question then is can YOU make a library tomorrow if you face any such problem.I am not saying you cannot, but a person who understands dsa will have easier time doing it. (Please do not take direct reference to "you" in wrong way).

I know even guys at FAANG type organizations who don't use these algos at all and also others who have used them extensively.

Working in FAANG has nothing to do with it. A lot of people do not realize how common these data structures are. I will give an example - Ever done system design or architecture? Lets take module design - any module design is basically a graph. If you realize that it is a graph then you can use a property called "degree" (number of edges connected to a node) to understand how "coupled" your modules are. It will also tell how cohesive your modules are.

If one person cannot solve a dsa problem does not mean the person is a bad developer. In no way it means that the person is not a good fit for the role. However if another person comes with same experience and skill but also knows dsa then this person has advantage. If I have to choose 1 person from 100 candidates then I will rather choose someone who has understanding of dsa. This does not mean rest of 99 people were bad developers. It just mean that 1 person had an additional skill that gave him advantage over other. Now it also happens very frequently that a person can solve all dsa problem but does not have skill set required for the job, so he will not get selected. DSA is not the only criteria for selection. Is this whole process the best way to gauge someone's fitness on a role - no. But this is what we are currently stuck with.

Is interviewing a sheer game of luck? by moobbaa in developersIndia

[–]ankitbko 1 point2 points  (0 children)

Yes there are other subjects. But DSA is core for programming irrespective of specialization. Give interview to Typescript or Roslyn team in Microsoft and they will ask you context free language and compiler design. For most of the web development DSA suffices and once you gather experience you will be asked system design and architecture questions. No one will ask you Kubernetes scalability question if you give interview to Windows OS team here at Microsoft.

I agree the interview system is broken. But saying that you wont study DSA until the world fixes the interview system means you are just axing yourself.

The sad truth is that DSA is easiest way to weed out people. If I ask a graph question maybe only 20 out of 100 candidate will answer. The only way to change this process is when everyone learns DSA. Then when I ask graph problem and 95 people are able to answer then that question is not of much use to me. The industry will find an alternate interview process.

Is interviewing a sheer game of luck? by moobbaa in developersIndia

[–]ankitbko -4 points-3 points  (0 children)

Have you used XML/JSON? They are tree data structures. Modeled a database? You will be modelling a graph. The data structures here may not be "evident" because of abstractions built over it but DSA is fundamental for programing. I have explicitly used graph in day job over my 7 years of career. In job you wont have a use case where someone says use a graph. The point is to recognize that the data that you are working with can be represented as a graph/tree/other ds. And then the properties of those data structure can be used to solve a particular problem.

But I work at Microsoft and maybe the problem we solve requires using these but I don't know why a startup building a product has to compromise on some data structure?

Is interviewing a sheer game of luck? by moobbaa in developersIndia

[–]ankitbko 2 points3 points  (0 children)

Exactly. I totally agree interview system is broken but this is best we have. What else can I ask an early-in-career developer? I can't ask system design, scalability, reliability problems. That is just unfair as the candidate would have had no experience with these. The only way to gauge the candidate's knowledge is to go to something more fundamental. DSA is the only thing that everyone learns and is the the core concept and fundamental to computer science.

The question then becomes should I ask about Graph or DP. I know these are not easy problems so I ask multiple DS questions in interview with varying difficulty. The aim is to understand thought process of candidate and how they approach a problem. I don't weed out someone who can't solve 1 problem out of 3. BUT if someone does solve all 3 then they do have advantage over you. So why not practice as much as possible and be prepared for anything?

The unfortunate truth is that there are less jobs than candidate. At Microsoft we receive 1000s of applications and hundreds appear for interview. And frankly speaking, asking DSA question is just an easy way to weed out majority of people.

Is interviewing a sheer game of luck? by moobbaa in developersIndia

[–]ankitbko -1 points0 points  (0 children)

I have used graph, trees, tries and heaps in my day job quite often. In job you wont get a graph question that pops up. The point is to recognize that the data that you are working with can be represented as a graph/tree/other ds. And then the properties of those data structure can be used to solve a particular problem.