A picture in which a man, labeled “developer” checks out another woman labeled “context” while with his girlfriend labeled “redux”
A picture in which a man, labeled “developer” checks out another woman labeled “context” while with his girlfriend labeled “redux”
Pictorial Showing the State of Developer Interest in Context

When I first learned how to use Redux, it was a bit overwhelming keeping up with the different files, functions, types, actions, and reducers necessary to make it work. After I got the hang of it, using it felt almost like second nature — it’s highly structured, it’s easy to tell where bugs are coming from, and there’s a repeatable pattern when building out features. But when I learned about the React Context API I was baffled by how simple it was to manage state across components, and I wondered why I had been using Redux at all.

I set…


If you’ve just learned a new framework or language, the leap from building simple, straightforward apps to building something with lots of moving parts can seem insurmountable. At least, that’s how I felt when implementing one of my first projects in react. I had an idea I was passionate about, but no roadmap, examples, or even certainty that it was possible.

My goal was to build a web app that enables users to draw AR face filters, but since I was new to react and javascript, I wasn’t sure if this was even something I could do at my skill…


If you’re thinking about transitioning into tech, it can be hard to choose the right path. Depending on a multitude of factors, you might consider going back to college, learning on your own using the thousands of free resources online, or signing up for a coding bootcamp.

There are pros and cons to each approach; college would likely plunge you into student debt for decades to come and provide no job training or assistance finding a job post graduation, but many employers see it as a necessity. Bootcamps, while less expensive, still cost upwards of $15,000 and require loans if…


As a software engineering student, it can be daunting to even begin thinking about how large companies build and maintain software. Going from building simple apps with no users to an enterprise setting where an app has multiple teams working in tandem, new features being deployed, and millions of users who expect no downtime can be unfathomable to novice engineers (myself included).

In light of this, I set out to break down one of the most common software architecture styles that I encountered when researching how large companies build and maintain software.


At some point in our lives, we’ve all come across the idea that computers “speak” binary — a cryptic wall of 0s and 1s that somehow builds up to everything we see and do in our digital lives. Even as you read these words, the device you are using is somehow manipulating 0s and 1s to make it possible.

As a software engineering student, and more generally as a curious person, I wanted to bridge the gap between the polished interfaces that I interact with on a daily basis and the underlying mechanisms at work to enable them. This is…


As an artist transitioning into computer science, nothing struck fear into my heart like seeing mathematical notation.

Gif of Winona Ryder looking confused with math equations floating around her comically
Gif of Winona Ryder looking confused with math equations floating around her comically

When it came to understanding the runtime of algorithms and how it scales given an input, (time complexity) I was overwhelmed with the mathematical notation, coefficients, graphs, proofs, and concepts that seemed a lot more complex than they actually are. I thought I’d need to solve equations to be able to effectively find the runtime of my functions. Thankfully, I discovered that for the most part the runtime of algorithms can be figured out intuitively by following a small set of rules.

First…


When I started to learn about software engineering few things stumped me as much as recursion. I was able to grasp loops, data structures, and algorithms, but a succinct four line recursive function left my brain short circuiting.

Gif of Patrick from Spongebob with his brain short circuiting
Gif of Patrick from Spongebob with his brain short circuiting

Recursive functions are functions that call themselves, thereby repeating the logic they encapsulate until (hopefully) an end condition, or a base case is met. Since a recursive function calls itself and repeats its own logic, without a base case it would theoretically repeat forever, but in practice you’ll get a stack overflow when your function is called too many times.

The part…

Patricia Arnedo

Curious and passionate software engineer that uses way too many gifs.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store