As @Plinz puts it, “Powerful technology (for instance, new medication or macro economic modeling tools) is never fully without harm… Ethics committees are usually only incentivized towards prevention.” See thread on “Red Team” vs “Green Team”
INNOVATION
-
Code as Liability: Minimizing Complexity in Software Engineering
By
–
Code is a liability, not an asset. So goal of software engineer is delivering the maximum amount of desired functionality at the cost of the least amount of code complexity, even as desired functionality evolves over time.
-
Major AI Event Brings Together Leading Researchers and Experts
By
–
This truly was the AI event of the year. So much to reflect on! to @erikbryn @YejinChoinka Noam Chomsky, @bengoertzel @jeffclune David Ferrucci @AvilaGarcez
, @MichelleRempel @dileeplearning @sarahookr @AnjaKasp @KordingLab @kaifulee @frossi_t @SchmidhuberAI & @Montreal_AI -
Google’s R&D Innovation Hindered by Red Team Dominance
By
–
Google’s R&D is the most innovative in the world, but the ‘Red Team’ often goes unchallenged and gets their way. The leadership needs a strong ‘Green Team’ culture. They’ve been sitting on state-of-the-art large language models for years and haven’t released anything meaningful.
-
Creative Technology Video Essays Reactions Tutorials Interviews
By
–
Yeah! essays, reactions, tutorials, interviews on all things creative technology
-
Blockchain Solutions for Disrupting Ticketmaster’s Market Dominance
By
–
TL;DR – “Ticketmaster’s parent company is projected to gross $16 billion in 2022, more than the entire U.S. record industry grossed in 2021.” Any blockchain companies working on disrupting this because it needs to be messed with. https://
prospect.org/power/ticketma
sters-dark-history/
… -
Jürgen Schmidhuber’s Fascination with Metalearning and Algorithm Innovation
By
–
Now Jürgen Schmidhuber @SchmidhuberAI He is most fascinated by metalearning — systems that invent learning algorithms for new types of problems.
-
Amazon’s 1998 Memo Origins of Workflow State Tracking Models
By
–
so excited to find the origins of the workflow model in this 1998 internal Amazon memo – I think this directly led to AWS SWF and Temporal. it turned out that tracking state changes wasn't just an afterthought, but should be the basis of the entire thing