Oddbean

This is what we seem to have settled on. Easier to find a better, additional dev, than another Laeserin. Especially cuz he's so good that I'm like, I'll just see myself out, y'all have fun with that. 😅 Now that they aren't constantly hand-holding me, the speed and complexity of their interactions has gone way up. It reads like Greek to me, now, but it's more productive.

I'm now in charge of opening up markets for products we're building, by getting those event types into greater use, mostly by using them myself and showing people what they can be useful for, and helping the devs who already have such products make them better (competition is good, strong competition is better). Buggy products devoid of attractive sample data are DOA and I looked around at all of these little projects that just go nowhere and that seems to be a major problem. Needed someone techy enough to write in new event types using prototype-level clients, but chatty enough to not just write "test test testing" in the content. 🤣 Been great, watching the different spheres sort of open up and expand. If you raise the quality and the quantity of the sample data people see, when they open up the app, that spurs them to add something of their own. We've got wiki, ngit, and articles covered, already. Just need to add magazine, collections, and book publishing to the set, so I'll soon be writing modular articles, like @liminal defined. https://flycat.club/post/dc4cd086cd7ce5b1832adf4fdd1211289880d2c7e295bcb0e684c01acee77c06/1690844272584 nostr:naddr1qvzqqqr4gupzphzv6zrv6l89kxpj4h60m5fpz2ycsrfv0c54hjcwdpxqrt8wwlqxqqxnzd3exqurgdpjxuer2wp5rp4zsy

It was actually sort of humbling, for me, as I didn't even realize that they were writing in Simple Coder, until I left them alone for a bit and then went back and tried to understand what they were writing about while I was gone, and it was like OMG I literally can't recognize the words, anymore. 😅 I can't even tell what the topic is. Good grief.

I have always been a polymath, but not an expert in anything. I always hired people that were smarter than me and when it comes to coding, that's pretty much everybody 😂 I am, however, able to see the whole vision and bring the various elements, run by way smarter people than me, together.

Well, it can be a bit useless, on its own, but it's the trait that maximally leverages the other traits and you can spread it very thin over a large group of people. So, it makes sense that there are many more detail thinkers than system thinkers, and then some middle number with both abilities.

I need to know enough about coding to be able to understand other people's programming logic, and to be able to pinpoint a bug in the code, but if it gets too complex or the topic is too obscure, I'm lost. There are some things you can only really understand if you regularly and actively work on them.

I was a "bad" coder until 4GL's came along. I realised I needed to delegate and trust to better coders. I was very lucky, I had a genius coder work for me. He re-wrote a colleagues year long coding project in a weekend because he could see a way to do it better and he always delivered projects with significantly more nuance and understanding than I could ever conceive. Yet I had to encourage him as he didn't understand his own talent or worth and he also needed me to keep him focused in the correct direction and end goal. This is him: https://www.linkedin.com/in/lee-weekes-0426662b/ I employed him at Densitron, before a hostile takeover removed me. I think the last 15 years have been safe work at interesting locations around the world, but coding slot machines for 15 years has to be boring AF. In our time, we created a type of Wolfram Alpha, before it became the thing it is today.

My code isn't bad, but it isn't very good, either. I'm best at anything stronger on informal logic, like design and test, or algorithm design or marketing. Programming is just applied formal logic, which is something I can do, but it's a chore for me.

It's two different jobs, so if you focus on the one, you'll neglect the other. That's why I recommend getting together a team, with someone who does "the other half", and then interact on a team basis. On the rare occasion, when you write, they can raise your reach by interacting with your post. And they can test out what you're building and work on marketing it.