Playbook (https://www.playbook.com) | Software Engineer | San Francisco or Remote (US timezones +/- 1 hour)
The tools for keeping track of creative work haven't gotten an update since Dropbox launched. You wouldn't expect the creative process to involve hours of digging through folders and files, but it does, and we're here to change that.
Playbook is a visual cloud storage platform for creatives. Whether you're a designer, marketer, photographer, or artist, your tools should help you stay in flow. Your current and past work should be right at your fingertips, and it should be a snap to bring in collaborators or share your projects with the world.
We're a small team of ~10, growing quickly and looking for help as we scale. We're hiring generalist software engineers (2+ years exp) and a senior infrastructure-focused software engineer. Our stack is Rails/React/GraphQL/Postgres. More here:
Playbook (https://www.playbook.com) | Software Engineer | San Francisco or Remote (US timezones +/- 1 hour)
The tools for keeping track of creative work haven't gotten an update since Dropbox launched. You wouldn't expect the creative process to involve hours of digging through folders and files, but it does, and we're here to change that.
Playbook is a visual cloud storage platform for creatives. Whether you're a designer, marketer, photographer, or artist, your tools should help you stay in flow. Your current and past work should be right at your fingertips, and it should be a snap to bring in collaborators or share your projects with the world.
We're a small team of ~10, growing quickly and looking for help as we scale. We're hiring generalist software engineers (2+ years exp) and a senior infrastructure-focused software engineer. Our stack is Rails/React/GraphQL/Postgres. More here:
> His latest Twitch deal includes a performance quota; he streams 200 hours a month.
50 hours a week of on-stream time! And any other business/branding/merchandizing must happen on top of those 50 hours where he already has to be 100% on. It does sound exhausting.
Playbook (https://playbook.com) | Software and Infrastructure Engineer | San Francisco or Remote (US timezones +/- 1 hour)
The tools for keeping track of creative work haven't gotten an update since Dropbox launched. You wouldn't expect the creative process to involve hours of digging through folders and files, but it does, and we're here to change that.
Playbook is a visual cloud storage platform for creatives. Whether you're a designer, marketer, photographer, or artist, your tools should help you stay in flow. Your current and past work should be right at your fingertips, and it should be a snap to bring in collaborators or share your projects with the world.
We're a small team of 9, growing quickly and looking for help as we scale. We're hiring generalist software engineers (2+ years exp) and a senior infrastructure-focused software engineer. Our stack is Rails/React/GraphQL/Postgres. More here:
Playbook (https://playbook.com) | Software and Infrastructure Engineer | San Francisco or Remote (US timezones +/- 1 hour)
The tools for keeping track of creative work haven't gotten an update since Dropbox launched. You wouldn't expect the creative process to involve hours of digging through folders and files, but it does, and we're here to change that.
Playbook is a visual cloud storage platform for creatives. Whether you're a designer, marketer, photographer, or artist, your tools should help you stay in flow. Your current and past work should be right at your fingertips, and it should be a snap to bring in collaborators or share your projects with the world.
We're a small team of 8, growing quickly and looking for help as we scale. We're hiring generalist software engineers (2+ years exp) and a senior infrastructure-focused software engineer. Our stack is Rails/React/GraphQL/Postgres. More here:
What I got from the article was that system as a whole is consistently throwing roadblocks in the way of experimental/small-time science. The author focuses on YouTube, but also cites a government investigation as well as deplatforming by PayPal, Square, LinkedIn, Amazon, Facebook, and Patreon. These are private companies, with their own policies, but private companies are part of the system too. So I don't think the concerns are conflated.
Regarding YouTube, I think the author would agree with you:
> The problem is big tech companies making billions of dollars aren’t capable of doing basic analysis of scientific work, or hiring a team that can, which is why the best they’re capable of on the pandemic front, for example, is attaching a link to the CDC website on every post that mentions “Covid” or “vaccine.”
I don't think we need to assign blame to YouTube here, but it's still the reality, and we should consider what it means for access to science.
Maybe we (as a society) should in fact keep experimental science off YouTube. (I don't agree, but I can see an argument.) Even in that case, the decisions made here are disproportionate. The author starts the article by describing how he's banned from even logging in, not just uploading; he ends by saying how he has to worry about being locked out of his email. I agree with the author that we're in dangerous territory by giving companies unilateral control over this process, even if we do it for good reasons.
Playbook is a media management tool that acts as a beautiful, organized home base for creative work.
We're looking for a senior backend engineer (4+ years experience, Ruby on Rails is a plus) to join our Founding Team. You'll be working on problems like visual search, image similarity/tagging, and large-scale data pipelines. More info: https://www.playbook.com/p/play/founding-engineer.
About us: we're a small team (6 of us total; 4 engineers). We care about creativity, freedom to shape your work, and product-building over cult-building. We're a seed-stage company backed by Founder’s Fund, Abstract, Inovia, and others.
Please email hello@playbook.com to apply or learn more!
I really like hooks. I previously spent a lot of time in HOCs, and I find hooks much simpler. But I also have problems with #5 (control flow):
The main issue I have with hooks is that I can't easily trace why updates are being triggered in my app; this makes it hard to debug performance issues. For example, my app once got really slow, and the profiler told me that a root(ish)-level component was causing a lot of re-renders. Unfortunately, that component used multiple hooks, and the only way I was able to isolate the problem was by binary-searching, deleting hooks until the re-renders stopped.
Not sure if this helps or is relevant, but I like to think of a component as a physics function.
For example, at t = 0, the output is one thing. When t = 1, the output is another. The same way of thinking can be applied to hooks. Some hooks only execute at t = 0, and at that time, variables x, y, and z also have specific values.
Hopefully you can think this way and your values won't intertwine so much that it becomes hard to trace.
The 'magic' involved in hooks is a tradeoff; there are real benefits in the way you can consolidate logic, or mix in behaviors. Personally, I strongly prefer hooks to HOCs.
Many technologies have magical behaviors and are still very popular and useful (Rails comes to mind). I'm really liking the pros and cons being brought up in the rest of this thread.
To me this is the most visible win. useSelector for Redux, useIntl for react-intl, useHistory for react-router, useStyles for material-ui, etc. Almost every library I use radically simplified their API by adopting hooks.
It also makes types much easier to analyze (whether using, say, VSCode's inference or Typescript) when using hooks. With HOCs, types tended to get lost through the arbitrary amount of <Wrapped {...props} /> chains.
