Small team of designers and engineers working on sociological based problems that software can solve. Profitable company, you'll ship code in your first week, we look at software to solve problems not introduce new ones. Looking for polyglot backend focused (Node.js, Laravel, React, Mongo, AWS is mostly our stack) professionals who will be able to release production ready features to potentially millions of users. Heavy consumer focus, so you'll use the products you ship, too.
Small team of designers and engineers working on sociological based problems that software can solve. Profitable company, you'll ship code in your first week, we look at software to solve problems not introduce new ones. Looking for polyglot backend focused professionals who will be able to release production ready features to potentially millions of users. Heavy consumer focus, so you'll use the products you ship, too.
A lot of folks are asking about the math breakdown. So here it is:
- 3 employees discussing design at $110/k/y or $43/h napkin
- 1 founder discussing design at $90/k/y or $36/h napkin
- 1 meeting — $165
3 days of work to follow:
- 1 designer making edits — $903
- 2 working on projects related to said design — $1806
Total: $2874
- ~2 hour meeting to discuss, examine, make notes, etc. — $335
Total: $3,209.00
- Opportunity cost of founders 3 hours — $1,100 napkin (based on potential hourly value not pay)
Total: $4,309.00
Please note this is generally napkin math based on my own experiences & numbers. It is generally impossible to get an exact number but you can get very close.
Why is this included? If two people are working on the back end for a widget, and the designer spends 3 days changing the colors of buttons and types of sliders on a widget, why does this mean that the two people working on the backend aren't making their usual progress in the meantime? Maybe they lose a few hours of time to integrating the design changes, but a few days?
Thanks for the comment. The estimation is for a series of feedback items which is fairly common for those types of sittings. In general you can expect a 3 day churn.
>Multiply that by how many team members involved in the meeting
Are you multiplying the full three days by the number of people in the meeting or are you just multiplying the hour of meeting by everyone in the meeting? The 4300 figure would be 100 hours or 3 days for 4 people. Even if there are a few changes, it sounds more like 4 people talking about changes and one person making them, which even with 3 days of changes would only be $1200. The other 3 people can work on other things during those 3 days.
Yeah I think it's all in the works. But I really love the idea, it's really refreshing to see people out to help others. To me it's almost like personal business consulting, but free. Just multiple helpful tips to achieving your goals.
Wow this is a really useful tool. Especially for the power-users. A lot of development that I am having my team do is based on and for those power-users. I think that's the best way to start getting a lot of use. Since basically, we are all becoming power users, and setting ourselves up with that goal initially, will hopefully cover the chances of success. Overall, this is great! Nice job!
User Experience. No one said there was a problem to solve, but someone did say it was a tip to help polish things up for your users experience on your Web site or app. See Pownce, they do this same trick.
Small team of designers and engineers working on sociological based problems that software can solve. Profitable company, you'll ship code in your first week, we look at software to solve problems not introduce new ones. Looking for polyglot backend focused (Node.js, Laravel, React, Mongo, AWS is mostly our stack) professionals who will be able to release production ready features to potentially millions of users. Heavy consumer focus, so you'll use the products you ship, too.
Building many products, like: http://collective.world
Please email: devjobs@thought.is with links to products you've built and resume.