Visit an article from any free news outlet and you’ll likely see some of the following:
Product managers are continually being asked to solve problems. It’s arguably our job. For many of us, stakeholders come to us every day with requests like “add this integration,” or “build this feature.” This is where the minefield lies — you must be able to sift through the never ending sea of opportunities, symptoms, problems, and solutions to 1) understand the real problem/opportunity 2) evaluate if it’s a problem/opportunity worth solving and 3) be effective at developing solutions that deliver results. It can be daunting.
In this post we’ll cover the following topics:
1. Prioritize your time and make better…
It’s been almost ten years since Marc Andreessen famously wrote about how software is eating the world. Ten years on, and it looks like he was onto something.
Product managers are needed in nearly every industry, and it’s not slowing down any time soon. It is an amazing time to be working in tech as you really do have the privilege and opportunity to choose your own adventure. That being said, you need to tread carefully, especially if you’re early in your product career. …
Clubhouse has taken the world by storm. Everyday I get notifications that one of my long-lost contacts have signed up for the service. They have built a phenomenal engine of viral growth — let’s take a look at how they’ve done it.
We all know what it’s like to have username envy — those first name Twitter handles are a prime example. Tapping into this desire to claim a limited resource, Clubhouse allows anyone to claim a username, even if they have not yet been invited or made an account. …
This week we’ve started working with React and Redux — it’s been a lot to take in so I wanted to take this opportunity to sketch out the basic flow of data when using Redux.
Redux helps us mange the state of our app by providing us with one centralized location for the state, a simple system to manage state modifications, and a mechanism to ‘subscribe’ to state updates.
Redux has three main principals:
You’re in the process of writing a new application and you push all your code up to git — great! One problem though, often times we need to store sensitive information like API keys or login information and we don’t want this to be visible to the world. There are many ways that you can choose to obscure these files from public view, but if you intend use Heroku with your app, there is one obvious solution — Figaro.
Figaro is a simple gem that allows you to easily set environment variables that can be used to hold sensitive information…
Searching and Sorting on Rails with Ransack
The most recent rails project I worked on was a simple marketplace application where users could browse products, add them to their cart, ‘checkout’, and see their order history. We ended up getting it to work pretty well, but the natural next step was making the navigation of the products easier.
Our products class had many attributes, like name, price, and quantity in stock. It would be helpful if the user could interact with the website to sort the data based on what they were interested in. Our method of displaying the products…
A few weeks ago I had my first exposure to relational databases. In this post I’ll go over the basics of relational databases and Active Record by referencing a recent lab that our class worked on.
Our goal was to make a basic web app that mapped the relationships between three classes:
It is important to remember that every class/model will be represented by a table. Each row represents a single instance of the class, and the columns represent the various attributes a model can be assigned (name, ID, age, etc.). …
It’s been over three months since I was first accepted to the Flatiron School’s immersive web program. Now that I have officially completed my first week, here’s some background information, tips and resources that I think will be beneficial to all future Flatiron students that are getting ready to start their program.
No two days are exactly the same, but we typically spend a few hours every day in lecture going over new topics or reviewing previous labs. The rest of the day is spent working on labs via the Learn platform (just like the prework), pair programming, or working…