I am a fullstack software engineer in New York City. My programming language is Javascript, and I am proficient in the NERD (Node.js, Express, React/Redux, and Databases(PostgreSQL)) stack. I am a psychology major, turned yoga instructor, turned web developer. I love traveling and exploring new places, and enjoy a challenging hike through nature. I spend most of my time doing yoga, attending concerts, and hanging out with my dog Max. I am a bananagrams master, and love solving puzzles.
I graduated from New York University with a BS in Applied Psychology, which was deeply rooted in culture, education, and research. I loved learning about what makes people tick, and the complexities of the human experience. I realized toward the end of my time at NYU that I was compelled by the experience of trying to understand something extremely complex (the human mind!), rather than by the prospect of a career in the field. I initially started playing around with HTML and CSS to pass the time, but I soon fell in love with coding. I love programming because it marries my love of puzzles/problem solving, my deep desire to understand complexity, and my creative fire to build useful tools. I am so excited to be in a field that is constantly changing, and am looking forward to career of continuous learning!
Platypus is an app that allows users to collaborate on a single playlist. One user hosts a room and is given a room key to invite others to join that room. Anyone with the room key can access the playlist of that room and search for songs to add or vote on what they want to hear. Users are limited to one vote per song so they cannot override the wishes of the majority, and the crowd favorite will always be the next in queue. Platypus was developed in 2.5 weeks from inception to "completed" (is anything ever really done?). I worked on all aspects of this project, and there were two major hurdles:
Setting up socket rooms so each room only received information intended for that specific room
Limiting users to one vote per song, per room, which involved an overhaul of our schema and a through table linking to another through table
Team Members: Marielle Combier-Kapel, Eileen Galindo, Samiul Huque, Keith Nocera
Timeless Watches is a retail website with the look and feel of luxury. Shoppers can browse as a guest or a logged in user, and view all of our watches, or click on a watch to see specific details. When a watch is added to the cart, you can add more or remove it entirely. The cart persists if you refresh and even if you log out, your cart will be waiting for you when you log back in. A user can checkout using stripe, and view their order history. Users can also update their profile information, but only admins can delete products from the site. This site was completed in 1 week, and some major hurdles included:
Cart persistence through most use-cases, but not when a logged in user logs out
Implementing the stripe api to take payment
Team Members: Marielle Combier-Kapel, Eileen Galindo, Sasha Kayola, Jason Levine
Node
Express
React
Redux
React-Redux
Sequelize
CSS
PostgreSQL
Stripe API
Local Storage
Sessions
Google OAuth
SPACE FINDER
React Native application to locate privately owned public spaces in NYC
Have you ever walked past a building and realized there were trees in the lobby? Or maybe it was an outdoor space with tables and chairs and a waterfall? New York City has hundreds of these spaces that are privately owned (well maintained), but open for use by the general public. I have only ever discovered these spaces by accidentally walking past one, or having someone who happened to walk past one tell me about it. So I created Space Finder which takes the data from the city of New York, and gives you the exact locations with pins on a map, and a description of the type of space that is there. Space Finder was created in 4 days for a hackathon and had many hurdles such as:
The data was originally in Microsoft Access which I was unable to open on a mac, so I used a PC to convert the data into JSON
The data itself was not as comprehensive as I had hoped, hence the use of the MapQuest geocoding API
I learned a new technology for this project, React Native with expo, and figured out that expo runs on it's own local host so the server I created had to use my computer's IP address, which changed depending on my location
