Reacto fullstack11/6/2023 ![]() I imagined myself failing to solve a hard challenge that I was not smart enough to figure out. I came to the interview expecting failure but not like this. ![]() Here I was, facing a really easy problem and blowing away an amazing opportunity. I didn’t consider some (or most) of the edge cases and all of a sudden, I got nervous again.Īs I was fixing the bugs with some hints from my interviewer my confidence started to go down.Įach edge-case highlighted by them that was not handled by my code was a blow to my ego.Įspecially as the problem was not hard at all. I jumped into coding immediately as I remembered solving a very similar problem a few days ago.Īfter coding my first solution in just a few minutes, we started testing and debugging together with the interviewer only to find out that my code was very buggy. Motivated by this realization that was triggered in my brain while the interviewer was presenting the problem, Of course, this was just the first step but I felt confident in my skills to overcome this obstacle. My dream of joining Big Tech wasn’t impossible at all. I realized that I had everything I needed to pass this interview. I saw that the first question was some simple recursion over a binary tree plus some simple math over the values I felt relieved. I came to the interview expecting something crazy and impossible to solve but when I had 45 minutes to solve 2 VERY SIMPLE code challenges. The first assumption held but the second one didn’t at all. Hard problems: I anticipated problems to be from the hardest LeetCode Medium set to anything in the Hard level.Half the time: You usually have 50 minutes to solve one problem (maybe with a follow-up question).More challenging than any I had before for two reasons: I didn’t feel ready at all but I also don’t think you will ever feel ready for this. Screwing up my first big chanceĪfter practicing for 2 months, it was time for my first coding interview with FAANG (recently renamed to MAANG). Where the fear has gone there will be nothing. And when it has gone past I will turn the inner eye to see its path. I will permit it to pass over me and through me. Fear is the little-death that brings total obliteration. In this post, I’m going to explore a topic rarely mentioned when talking about interviewing: How to think clearly under pressure. Where I describe my interviewing experience and thoughts in detail. ![]() This is the third in a series of blog posts Now that we know what promises are, how to use, and how to create them, we can actually get down to using the fetch() library we installed yesterday.Acing the Software Engineering Interview - Part III We'll represent this now with a setTimeout() that returns the time (like it's making a request to a slow API): function getCurrentTime ( ) ) Suppose we have a method that handles getting the current time for the clock called getCurrentTime() that fetches the current time from a remote server. For instance, if we're making a Happy New Years clock, it would be great to be able to synchronize the user's browser with everyone elses using a single time value for everyone so no-one misses the ball dropping ceremony. Now consider that we're using a different clock on some other remote machine. This is pretty straight-forward and works as the new Date() object represents the time the browser knows about. log ( 'The current time is: ' + currentTime ) ![]() It also allows us to treat these complex scenarios by using synchronous-like code.įor instance, consider the following synchronous code where we print out the current time in the JavaScript console: var currentTime = new Date ( ) Ĭonsole. Using a Promise object gives us the opportunity to associate functionality for an asynchronous operation's eventual success or failure (for whatever reason). What is a promiseĪs defined by the Mozilla, a Promise object is used for handling asynchronous computations which has some important guarantees that are difficult to handle with the callback method (the more old-school method of handling asynchronous code).Ī Promise object is simply a wrapper around a value that may or may not be known when the object is instantiated and provides a method for handling the value after it is known (also known as resolved) or is unavailable for a failure reason (we'll refer to this as rejected). Today we'll pick up from yesterday discussing the concept and the art of Promises. ![]() Yesterday we installed the fetch library into our create-react-app project we started on day 12. Today, we're going to look at what we need to know to understand Promises from a high-level, so we can build our applications using this incredibly useful concept. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |