crazy times...
It’s been a privilege to help support this community and to work alongside dang, who has been a great friend and mentor for many years. It’s a great responsibility, to keep HN a healthy and thriving community, and I’m continually amazed to see all the ways dang puts thought and energy into it.
One final note is that it was never part of the negotiations that I was expected to know or learn Arc, yet somehow in the onboarding process the HN Arc repo has found its way onto my machine, so it feels like the bait and switch is on…
How do we break this mold? While this absolutely does happen with some management, it's not all management in my experience.
I am an engineer that's found myself in a management role, and I want my team to do exactly this--don't invest tons of up-front effort trying to guess the models and abstractions we're gonna need. Build, iterate, and we'll clean it up when we know what we don't know right now.
It is blatantly obvious to me that things will be on shaky ground, I have a keen sense of what will break and when. And I'm totally good with that! I put "architect for real" time into the roadmap.
But even still, I get pushback, sometimes a lot of it. Like the idea of shipping functional-but-ugly code is somehow totally unacceptable for some reason (even when it's obvious the "pretty" version isn't even future-proofed or appreciably better). And the excuse is usually "Well we'll never have time to fix it".
<img width="1056" height="792" src="July2023.jpg" alt="Hi,
Dynamicland is still going, just quietly. We closed the Oakland space for covid, but Realtalk development and collaborations have continued -- basically as originally planned, if more slowly due to our small size.
I'm hoping to spend the summer working on bionano, and get back to the new Dynamicland website in the fall. It might be ready by the end of 2023? It'll have everything.
I'll try posting at @bret@dynamic.land (currently Mastodon until we have time to do our own thing in Realtalk). (I'd appreciate if you don't ask for my opinions about things.)
Thanks, -Bret">
Say you have an email list of 100000 investors, you ask ChatGPT to produce 100000 predictions and send these out to each investor.
Assuming ChatGPT is as good as a coin flip, 50000 investors receive good predictions. The next week you have ChatGPT produce 50000 predictions and send them out to those winners, you now have 25000 who have gotten two good predictions.
Rinse and repeat four more times and congratulations, you now have a client list of over 1500 people who have received six weeks of good predictions and are ready for you to manage all of their wealth using these insanely accurate AI predictions.
[1] https://www.washingtonpost.com/archive/business/2004/06/20/a...
Its amazing to see the people that won on the previous Nth rounds believe that their next tip was a "sure thing".
>The grandson of a legendary musician, Ben grew up in wealth and luxury.
If they're trying to avoid the "poor little rich boy story," they did a poor job.
I said nothing about it being unsuited for HN. I take issues with the story telling, not it being posted here.
I think you're taking my example a little too literally there... it's an example. The point is to save the reveal (spoilers?) till the end so that you can relate to the story more.
spoiler, since that's how this article is written Do they think I'd go "oh, who cares about Elvis' grandson?" More likely people wouldn't know anything about his grandson and back out after the first line.
As to whether or not this is appropriate for HN, I'm also not so sure... but I enjoyed reading it.
Well, it looks like a big fail right off the bat.