1
I am looking for advice, as I really am torn between 4 options.
For more than a decade I did mostly front end and some back end.
I've launched a few products (all have failed) and co-founded a startup, long ago.
I'm a UI-centric, product enthusiast, who's next big thing he'd like to explore is Deep Learning, specifically image processing.
The four companies I'm considering are:
* Lemonade - pros: great product, mature company (better compensation); cons: mature company (I'm looking for a place where I can do more than just code)
* Gong - pros: great product, mature company; cons: mature company
* Deepdub - pros: cool idea, small team (I will be able to touch product, UI/UX); cons: nothing that's worth mentioning
* AI21 Labs - pros: great product, mid size (more aspects I can take part of); cons: nothing that's worth mentioning
I am leaning towards the smaller ones, as I believe I will have more "creative freedom" (the ability to "one-man-show" stuff, as I really enjoy doing*), but I feel like mentioning the other 2 is still relevant.
I'm trying to keep this post as short as possible, I hope this gives a pretty good description of my dilemma.
Considering all companies seem have great people, who seem fun to work with (AI21 exceptionally), how would you approach this question?
* note that I am a team player, and leading a 3-4 person "squad" is a dream, but I don't aim for that right now)
The request it for a Grouped Tabs mechanism, similar to what Chrome introduced. It lets you create a "group" of adjacent tabs, where groups can have a name and color, displayed next to it.
If you like it and would like to see it implemented (or at least die peacefully in VSCode's backlog), please upvote it in the VSCode's repo issues.
The link is: https://github.com/microsoft/vscode/issues/100335
Sorry if this violates any rules.
With HEY, Apple is again, picking on a small company, but probably the biggest one so far. Basecamp isn't Adobe.
Apple is also probably facing an upcoming EU investigation.
So far Apple had no reason whatsoever to acknowledge indie developers' needs (in that context). But HEY is different. With HEY, Apple has a chance to get a shit load of great PR for "showing mercy" for what is widely considered and comparatively speaking, a small company.
If they let HEY off the hook, they lose a buck or two, nothing that they're going to notice, BUT, get the PR they need for whatever's coming their way from the regulators, and a ton of developers, and some of the public.
The app was pretty simple, search for YouTube video through it (I was using YouTube's search API) select one of them and get a magic link, share that link with a friend and you'll both watch that video (in sync) while video chatting with one another.
Things worked great until I published it on HN. It got to the front page and enjoyed a good amount of visitors. And then it broke.
That's how I learnt about YouTube's search quota limit. I was under the impression the thing should last for a daily usage. Turned out I was wrong.
I have contacted YouTube that same day, they have a pretty lengthy form you fill for quota requests. I filled that form and waiting.
And waited.
And waited a bit more, until I got an email from them asking for more explanations. I don't know what they wanted to know more as the app was DEAD SIMPLE, but I needed the quota increase so I provided them with everything I thought was relevant.
I sent that email, and continued waiting. And waiting. And I'm still waiting.
I find the way YouTube is handling this is really unfortunate. YouTube's API offers some great abilities that allow for some interesting products. But YouTube doesn't seem to care about it. That's very disappointing.
Anyhow, today I removed the search feature from the app (you can now only paste YouTube videos to get the magic link). I also open-sourced the project, you can check it out here: https://github.com/dutzi/the-gives
Has anyone else experienced this?
So I made a tiny animation orchestrating library for React and React Router and wrote the following post about it and a bit about why thee declarative approach to animations is such a nightmare for me.
https://dutzi.party/animating-route-transitions-using-react-router/
The relevant bit:
> I don’t like writing complex animations in a declarative manner. They’re great for interactions, but I find that compared to animations written in an imperative way, the learning curve is steep, code readability suffers and playing around (just testing stuff out) is not as fun as the feedback loop tends to be longer. That may be because I started my way out as a Flash (ActionScript) developer, where tween animations were very popular...
Would love to hear why declarative animation libraries are so popular with React (other than the fact that they follow React's basic approach to well, everything).