While not a seasoned developer yet, I have long been interested in D3.js since its initial release in 2011 (wait, it’s been 10 years already?!)
Below are three…
Another relatively new tool I have noticed being thrown around in the dev world is GraphQL.
Aside from the two-pointer technique demonstrated in my previous post, I have been grokking another popular algorithmic mental model: the sliding window.
If you have never heard of the sliding-window technique, I strongly recommend watching this video tutorial before diving into the example below. …
When dealing with strings and arrays in the context of algorithm challenges, our first instinct usually revolves around built-in methods.
Let’s take a look at this seemingly easy problem:
Given a sorted (ascending) array of integers,
write a function that returns a sorted (ascending) array
which contains the square…
Technical interviews come in all shapes and sizes. Some companies go for the traditional algorithm challenges, others tend to be more creative, such as this Fullstack Engineer interview I had the other day.
Toward the end of a fun, relaxing conversation, the interviewer gave me a quick challenge: Answer a…
Last week I shared three handy dev tools that let us format our console outputs beyond the plain-old
console.log(). Today I learned one more neat trick to "prettify" our console.
This trick is so simple, all you need to do is add a special indicator inside your
console.log() to debug, print out variables, and log results of our current operations to make sure we are on the right programming path.
Indeed, console.log() seems powerful enough, but did you know there are other cool methods in the Console API that can also…
Unlike coding tests, where you solve algorithm problems with a keyboard silently, coding interviews go beyond keyboard communications.
It can be a daunting task, as the interviewer can see every move you make on a shared screen.
And if that wasn’t nerve-racking enough, you also need to speak out, expressing…