Oddbean

Here's a little team-building "secret": there are 3 types of builders (and by a builder, I consider anyone truly building something for somebody else: engineers, designers, drug developers, founders, construction people, hairdressers, cooks, executive coaches, professors, etc). 1. Those who can ship a highly usable product. It doesn't matter if people use it because of the experience or because it just works. What matters is that people use it and come back for more. 2. Those who can ship a product, but it's never used by anyone. The majority of open-source projects, internal projects, VC-backed startups, and small businesses die here. Many builders can ship. Very few can ship usable things. 3. Those who cannot ship a product: 3.1. with skill: The project stays under development forever and, even if it ships, it never pleases any user. Fear of negative reactions when shipping, overengineering, and user cluelessness are big problems. 3.2. without skill: The builder is simply unable to create any workable product or to lead a team into it. The vast majority of people you meet in your career are 3s. You don't want them. There are not enough 1s out there. So, you want the 1s leading the 2s, but never, EVER, allow the 2s to take over the 1s.

I'm a One (1), with a stellar product every family needs, many people buy, love, use, and tell others about, but I'm clueless when it comes to marketing...😳 https://SILVERengines.com I'd expect more bitcoiners (because not typical normies) to know the value of colloidal silver, but have yet to find buyers paying in sats.🤔

I disagree @Vitor Pamplona . I think these descriptions are better suited to the products themselves, rather than the builders. People (and teams) succeed, fail, and pivot strategies all the time. I know I do. 1. Products that are shipped and used. 2. Products that are shipped and not used. 3. Products that are not shipped. The key is to always aim for 1, knowing that 2 and 3 are also possibilities at any time. As far as who “you don’t want” on your team … anybody who does NOT see 1, 2, or 3 as a possible outcome for a product at any time.

these cannot be determined until some time has passed and a few tries have been made note also that sometimes you can be building something and it's nearly done and then they pull the plug and then what? was that because it took too long or was it that the project ran out of funding and/or part of the team crapped out that was building parts that my work depended on (or they just stopped working and lost their marbles, which happened to a lot of people during covid i think also, amethyst is still buggy in places and not so great i use it very often, give me nostrudel any day, just to call a spade a spade

also, some people don't actually know how long or how many people are required to deliver some given set of features i had a manager ask me regarding someone else's work that was recently released if it reflected anything on my and my colleague's work on replicatr and the simple fact is the other project had several years going into it, and 5 workers, and i was just me and a junior on his first project... it needs another two months and probably another set of eyes running the tests and ironing out its resource leak bugs, which already i squashed 3 of them leading up to the final release can't make a house without enough bricks and rebars and cement and tiles and windows and doors, and if you only have two guys working on it that will take more than twice as long as having 4 due to efficiencies of parallelism