I try to carve out about 2 hours a day to work on code problems. In addition to solving them, I find it really useful to write a brief expanation of my process. It gets me in the habit of putting words to my coding decisions, a skill that interviewers want to see when you’re working through a technical problem. Writing out the approach also helps with remembering certain strategies when encountering similar problems down the road.
Some of the knowledge gaps bootcamp graduates encounter are data structures and algorithms, so I thought it might be helpful to provide a walk-through of a basic array search problem found on Leetcode.
When I started learning React, I was always baffled by this phenomenon - I’m using a simple React component which has a input field with an onChange event attached. The onChange event fires, and updates the component state with the value from the input field. I log the input in the console to do some debugging like so:
You love the Fetch API. Like most of us, you grew up with Fetch API posters on your wall and by age 30 your arm is covered in a sleeve of Fetch API tattoos. The Fetch API lets you send Ajax requests with ease, and yes, it impresses little kids at a birthday parties.
I’ve been stuck inside, along with the rest of the responsible world, for the better part of three months. Looking out of the same windows, pacing down the same hallway, staring at the same walls, I found myself asking the same question over and over.