Butter (http://butter.us) is looking for an analytical, impact-driven back-end developer who will work with our team to troubleshoot and improve current back-end applications and processes.
In this role you will use your understanding of programming languages and tools to analyze current code and formulate more efficient processes, solve problems, and create a more seamless experience for users.
An online workshop suite that is part video conferencing, part workshop planning, part data analytics tool for people that host and run online workshops. It’s called MeetButter (https://MeetButter.io)
Ever since the pandemic, a lot of facilitators (design thinking, corporate workshops, internal brainstorms) were forced to move online. We found a gap in the video conferencing market for this group of niche users, and decided to fully focus down on that niche.
What started out as a React + Firebase app has now evolved into a complex full stack system. The industry is still ripe for innovation and ideas that we can play around with.
MeetButter http://meetbutter.io is looking for a Full Stack Tech Lead and also a Backend Developer (two separate roles). We are building the most powerful and delightful platform to facilitate online workshops and trainings.
We're using Jitsi (which is open source) but are also testing out various third party providers such as Daily.co and Agora.io
We want to focus on improving the meeting flow experience and interactions, which is why we leverage open source or third party providers for the video conferencing tech.
I built the blog over a weekend using Gatsby. It's super neat!
Gatsby is pretty flexible, I'm even able to make things like filters and queries, add tags. SEO is super easy, and their image processing is top notch. Highly recommend it.
I connected it to Netlify so that it auto-updates every time I make a git commit. If you're not familiar with the term Jamstack, you should explore it. There's so much cool stuff being done these days with static websites.
Yes, I love the Design Thinking process. I ran my own dev agency before, and would always recommend clients to do a Design Thinking workshop with my team. It's really the best way to break down a big 6+ month project into bite-sized pieces.
I agree, I wouldn't invest a couple of weeks and just call it a day.
An MVP is the start of a conversation with your target market. That's how we're approaching it. It'll take more than 3 weeks to reach product-market fit, we're just super excited to kickstart the journey!
I agree, every project is different. I don't believe that my experiences and advice should be a catch-all for all projects and teams everywhere, there are too many permutations.
Without defining the variable X (for X amount of weeks) that you should take for an MVP, the general advice for MVP is to build as little as possible, launch fast, fail fast, and reiterate.
There are industries where the barriers of building an MVP are much higher. For example, in ML you need to train your algo huge amounts of data. In the automotive industry, you need to meet a lot of minimum requirements to even enter the market.
Oh no! Our branding was totally tongue-in-cheek, we felt that it was fun. But if it's conjuring negative images when you see it, that's totally bad! I'll feedback this to the rest of the team.
I don't believe you can slap together something in 3 weeks and call it a day.
We did it to gather market sentiment and feedback for an idea, any signals or signs to show that we were in the right direction.
Your MVP is the start of a conversation with your users / target market. Reiteration and pivoting your initial MVP based on user feedback will slowly inch you towards product-market fit. That is the long, hard slog.
In regards to building low-hanging fruits (hackathon timeframe ideas), some low-hanging fruits have deeper roots. You might find deeper problems that give you better insights on how to build something that people really want.
It took us 3 weeks in total from inception, prototyping, to setting up a full project like you said (linting, CI CD, AWS containers, database).
To be more accurate, the breakdown is more like this:
• 5 days of discussing, investigating the problem, and design thinking. We took our sweet time here :p
• 2 days of creating a prototype (in the article I mentioned a weekend, using Firebase and React)
• 5 days of reiterating prototype and design within a closed group of testers (family and friends)
• 5 days of MVP design (landing page, branding, etc) and proper project and infra set up (migrating to AWS, database, CI CD, staging and production environments, etc).
Butter (http://butter.us) is looking for an analytical, impact-driven back-end developer who will work with our team to troubleshoot and improve current back-end applications and processes.
In this role you will use your understanding of programming languages and tools to analyze current code and formulate more efficient processes, solve problems, and create a more seamless experience for users.
Our main tech stack: GraphQL, NodeJS, React, NextJS, Redux, Python, Postgres.
Benefits: Work from whenever, forever. Flexible work hours. Equipment budget. Unlimited paid vacation. Health insurance.
Application form: https://careers.butter.us/a77ef4ffc8704729a136edf65b7b04ac