People spend one-third of their lives asleep. What if employees could work during that time … in their dreams?
Prophetic, a venture-backed startup founded earlier this year, wants to help workers do just that. Using a headpiece the company calls the “Halo,” Prophetic says consumers can induce a lucid dream state, which occurs when the person having a dream is aware they are sleeping. The goal is to give people control over their dreams, so they can use that time productively. A CEO could practice for an upcoming board meeting, an athlete could run through plays, a web designer could create new templates—“the limiting factor is your imagination,” founder and CEO Eric Wollberg told Fortune.
Edit: someone else beat me to it, I cede to you my bruh
I just solved a coding problem this morning that I couldn’t last night because I RESTED MY BRAIN. I’m not making this up. This just happened.
I took a week off for Thanksgiving and came back to understand Dynamo DB single table patterns I was stuck on before leaving. Sleep learning is real!
Okay, but Dynamo DB is also pure baloney. Who thought a single table to include every type of entity was a good design? I’m frustrated because it works so well, but boy do I hate using it
I disagree, it’s quite performant and cost effective. I work for a very large software company and it scales to our needs very well. However, it is emphatically not the solution to everything nor is it a replacement for all traditional RDBMS use cases. It also takes a quite different mindset when thinking about your data than when using SQL.
IMO what it does really well is handle being a persistent data store for well-formed REST API endpoints. When you understand your access patterns and implement your GSIs correctly, a RDBMS can’t match the performance even with well tuned queries. Dynamo excels at giving you a record set when you know exactly which set of records you want and it’s based on one or two very simple conditions.
Where it falls behind is for data warehousing and reporting use cases. Dynamo is comparatively slow and inefficient when it comes to asking complex questions about the data. RDBMS systems are built for that use case and as such have extensive tools to optimize whatever wild queries you want to throw at it.
If you’re interested in learning about single table design, which is not good for all cases, check out this video. I’ve watched it quite a few times and it’s been the biggest help in wrapping my head around how to do the data modeling for it. https://youtu.be/KYy8X8t4MB8
Ok my steam deck finally finished updating. Time to go. 😁