I applied to 700+ internships for the Summer 2021 recruiting cycle. I got many interviews, but also many rejections that came with the interviews. I see most people talking about their success, but not enough people talking about what they learned from each rejection.
I will be outlining the 3 most hurtful rejections I received this year, all of which I had interviewed with (online assessments do not count). For the sake of anonymity, I will not be sharing company names, but some of them may be painfully obvious.
The naïve solution to the famous Fibonacci problem is exponential and most people can solve it in constant time. But can we do better? Definitely.
This is a classic problem in which the nth term is the sum of the previous two terms. The first two terms are 1 and 1. The third is 2, the fourth is 3, then 5, 8, etc.
In today’s world, it is increasingly easy to access material on programming on the internet. There are tons of courses with video lectures as well as YouTube tutorials labeled something like “Learn Python In Just 5 Hours!” Yet many people (including myself in the past) struggle to learn online.
After countless courses and programming crash courses, I’ve finally discovered the methods to get the most out of online learning. In the interest of helping others to benefit from what I’ve learned, I wanted to put together an article laying out how best to learn from online tutorials.
Once in a while, I come across an extraordinary programmer or software engineer. When that happens, my first instinct is to observe the way they work and carry themselves. Here are some things I have noticed that many successful software engineers do.
Although it's true that you can go to a university and find a job with just a bachelor’s degree (or without one), the truth is that for longevity in tech, you have to stay up to date. Every successful software engineer or programmer takes time to learn new technologies.
With how fast technologies and frameworks roll out, it's…
The symptoms are mild at first, but a lack of awareness and ability to contain it immediately causes a rapid spread. No, I’m not talking about COVID-19, I’m talking about disorganized code. If it isn’t fixed it right away, it’ll affect everything after it. Luckily, convoluted code can be easily prevented by applying the single-responsibility principle.
Here’s what Wikipedia says the Single-responsibility principle means:
The single-responsibility principle (SRP) is a computer-programming principle that states that every module or class should have responsibility over a single part of the functionality provided by the software, and that responsibility should be entirely encapsulated…
A common misconception that many (including myself in the past) have is that you need to pay money to host a website with a custom domain. That couldn’t be further from the truth.
So you’re satisfied with how your website looks on localhost. Now what? If you haven’t got a GitHub account, go ahead and make one. Then, create a new repository. You can choose to make it public or private.
I’m going to assume you already know a bit of Node.js and React.js for this tutorial. If not, don’t worry, I’ll explain things as we go. …