Bootcamp graduates don’t get jobs, only Engineers do 🙁
Software Engineering is one of the most exciting things in my life, it’s second only to the fact that I get to call the most amazing woman in the world mine 😉. In my time, I’ve had the opportunity to work with many amazing people at different jobs, and I currently at the most amazing company building the most amazing piece of software and towards one of the most revolutionary ideas I’ve been exposed to in a long while!
How did I end up here? Deep in the matrix 💭
Since my last article, I’ve built two full-stack Rails/React applications, one of which is a hobby/passion project, ShowJunkie (demo login:
ShowJunkiePerson), and another is my personal portfolio (the subject of today’s discussion).
So I decided to be adventurous and venture into rewriting my personal portfolio, and in a bid to indulge my curious self a bit more, I decided I wanted to upload my project images directly to AWS and store the link in my Postgres database for reference in my client-side React app.
Well, I succeeded — but not without high-fiving my forehead a million times and…
I currently work for Microverse, a school for remote software developers that’s totally free until you get a job, as a part-time technical-support engineer and student mentor. One of the best parts of the job is the privilege to perform code reviews for software engineers in the program as well as interacting with so many people from diverse backgrounds, being able to experience each person’s life/thought process as if it were your own.
Three months and 300+ code reviews later, I can confidently say reading through code; learning from many diverse perspectives; offering help; navigating conflict/tension; providing clarity, motivation, and…
At some point, everyone has had a song stuck in their head(good or bad) and for me, that song was the programming problem I’m writing about today. Now that it’s solved and the melody has been resolved in my head, I’d like to share my knowledge with you.
I’ll show you the problem statement shortly, along with some test cases you can run the code against, then I’ll dive into showing you how I freed myself from this problem.
If you haven’t had any experience with them, check out this tutorial on deques. Also, I’d like to say that you…
Hello coders! I’ve decided to write more about abstract data structures and solve at least one programming interview problem with each one so stay tuned for more excitement.
Today, we are going to stack some moola or cash, however you prefer to refer to it.
In this tutorial, I will solve the min-stack problem in O(1) time and throw in an extra feature to also keep track of the max element in the stack.
Very quickly, I will explain what a stack is, for those who haven’t had any encounters with one. And if you have, keep reading because I’ve…
Guess what? Compilers aren’t, in fact, psychic beings who can see through your every line of code. I’m about to you give you some insight into how exactly they’re able to call you out every time you mismatch a pair of brackets.
Today we’ll be solving a problem on balancing brackets. I’ll show you the problem statement and a brute force approach and give you a hint before we dive into the solution: to pause a bit and try to think about the problem. …
Hello, fellow coffee junkies! Today I’m walking you through one of my favorite problems: the sliding maximum window.
Outwardly, this may look like a fairly simple problem, and it is, with a brute force approach, you could be done in minutes or if you have great brain and finger speed co-ordination like I do, seconds.
I’ll show you the problem statement in a moment — pause reading and try to figure it out on your own if you like. Hint: A Deque is your best bet.
Check out this tutorial on Deques if you need a refresher or help to…
If you’re reading this, I’m guessing you already know what a deque is and you are trying to implement one in Ruby, or you’re in the process of learning about deques.
Very briefly, I will try to refresh your memory or add to your knowledge of deques.
A deque is an abstract data structure. Deque is an acronym for a double-ended queue.
To explain it’s importance, I will assume you have some knowledge of big O notation and the notations for some of the in-built data structures in the programming language you use to create your bugs.
Consider the array…