182 karma · joined March 6, 2013
CreatorML (Startup): https://creatorml.com
YouTube: https://www.youtube.com/CharlesWeill
GitHub: https://github.com/cweill
Twitter: https://twitter.com/CharlesWeill
LinkedIn: https://www.linkedin.com/in/cweill
Website: https://charlesweill.com
Basically my understanding is that high-level competitive Jiu Jitsu (Gi) can be extremely dull to watch, because of the point system disincentiving taking any risks. So that's when No-Gi submission-only competitions became popular to watch. 20+ minute rounds without any points scorable for the first half.
Here's another free option: https://www.remove.bg/
See Cornell's ergonomics lab guide: https://ergo.human.cornell.edu/AHTutorials/typingposture.htm...
I don't work for openAI but I would guess they are going to keep working on RL (e.g hide and seek, gym, DoTA style Research) to push the algorithmic SoTA. But translating that into a physical robot interacting with the physical world is extremely difficult and a ways away.
Before: https://youtu.be/7vSBCZ1mnL4
After: https://youtu.be/0IvfL4z7XHw (uploaded today)
1. Intelligence 2. Work ethic 3. High Integrity
While the first two can easily be judged, the last one is extremely tough to identify, and generally requires some incident in the company to reveal the integrities of the co-founders. Any suggestions how to identify high integrity early on?
Try being a beginner again at something.
After I burnt out, I started making YouTube videos. Even though I'm a total beginner at it, I'm having a lot of fun, and am making tangible progress!
I also underestimated the impact of having my work burned in front of me after 2 years of overtime and sacrifice. The money afforded me some level of financial Independence which at least gives me the optionality to choose whether I want to suffer this again.
I'm thinking of following in your footsteps. Wish me luck!
As a result, What makes a "team" is it's leadership structure, I.e it's determined by the number of engineers who want to be leaders (which includes accountability and ownership). If you have a team with multiple leader-types who want more ownership, and a natural seam in the solution space emerges to spin-off, they will tend to become the communication hubs for other engineers, and eventually spin out into their own subteam with their own microservice. They'll want their own abity to release when necessary, and choose dependencies without needing to convince everyone beyond their immediate subteam.
In short, if you're 1 person, microservices make little to no sense given the addition work and complexity involved. If you're more than 1 engineer, it depends on individual engineers willingness to be a lead and own a whole part of the system and become a communication hub. Companies like Google and Amazon will have lots of microservices because so many engineers want to be tech leads (either for promotion or self-fulfillment).