45 karma · joined November 16, 2010
"I'm brainstorming a business venture that is a cross between a boutique clothing store and DIY sewing classes. It’s called Style & Stitch. You can shop for clothes and learn to make your own. Please help me brainstorm some ideas for as a mind map (using Markmap markdown)."
You can ask it to combine ideas from different domains together for extra creativity (above example is output of one such attempt). Often it's not that creative on first attempt but if you prompt it with something like "how about some zanier ideas" it will do better.
I also like to prompt it with "output XYZ .. as a table with columns for X, Y, Z" or similar to get a nice markdown table of its output where it makes sense.
Devs are already doing this with adding comments with Github copilot .. might be an interesting way to close out the loop without putting too much process in.
In this vein, there's a good quote from Elon Musk in Everyday Astronaut's interview with him at Starbase: "A guided missile is going in the wrong direction at any given point in time, but it course-corrects.
You don't want to be a super precise cannonball when you don't even know where the target is."
Then when they realised that we didn't have enough Pfizer being made they tried to say that people under 50 can get it after consulting their doctor but by then they'd scared off lots of people. Pfizer is also harder to administer as it needs special refrigeration equipment.
A lot of people are also hesitant to getting the vaccine, perhaps because until recently most states apart from Victoria hadn't experienced large numbers of cases, deaths or lengthy lockdowns. That's started to change with the spread of the delta variant and more lockdowns etc.
https://a16z.com/2019/10/03/the-environment-capitalism-techn...
If meaningful beneficial changes come out of this review then they will be reported in the media in the context of his spat with Amazon, regardless of the impact on Amazon itself. Otherwise it's unlikely that those changes will be deemed newsworthy (because they aren't salacious and they don't directly affect people's lives), or if they are reported that they will be easily absorbed.
Linking any changes to the fight with Amazon provides a mental anchor with previous coverage given that any changes may take months to be put into place.
The author initially states that all relational databases are good for is speed but then goes on to highlight flaws in their object store that could all have been mitigated by using an RDS:
* schema changes without needing to write programs to update all your data
* data aggregation (and in fact any sort of adhoc reporting)
* data storage independence.
There's also no mention of data integrity but this is a big risk as soon as the original authors are no longer involved.
Object oriented data stores are hierarchical/network databases. Relational databases were introduced to replace these years ago and for good reason.
It's no harder to write a courteous and constructive criticism than it is to write a harsh and mildly condescending one. The former can serve to foster creative discussion while the latter often kills it.
For example. I read the article and think ok, this SAP HANA in-memory technology sounds interesting. I google it, go to their website and see a two minute video that supposedly explains it.
I think cool I'll watch that to get an overview of what it's all about. I watch the first twenty seconds after which I'm still actually eager to learn more. But then the video stops and they put an overlay telling me I need to register to continue watching the video. WTF!
So I still have not much idea of what it is and frankly no further inclination to find out.