Month: July 2023
Abundant opportunities for founders at TechCrunch Disrupt 2023
“Founders first” is the TechCrunch credo — this is the way — and you’ll find the very best and brightest minds in the startup ecosystem gathered at TechCrunch Disrupt 2023, taking place September 19–21 in San Francisco. This year, our programming spans nine stages, seven industries and dozens of breakout sessions and roundtable discussions (for
“Founders first” is the TechCrunch credo — this is the way — and you’ll find the very best and brightest minds in the startup ecosystem gathered at TechCrunch Disrupt 2023, taking place September 19–21 in San Francisco.
This year, our programming spans nine stages, seven industries and dozens of breakout sessions and roundtable discussions (for starters). Disrupt is where founders go to grow, collaborate, network and find inspiration — and, who knows, maybe a term sheet.
Founder opportunities at TechCrunch 2023
Let’s take a look at just some of the founders-first sessions and opportunities waiting for you.
The Builder Stage
Head to the Builder Stage for panels and interviews focused on the nuts and bolts of building and funding new tech enterprises — including these:
What Do You Need to Raise a Series A Today?
How to Build Intelligent Startup Ops that Will Scale with Your Business
Seven new industry stages
In addition to the Disrupt Stage (more on the folks you’ll see there coming soon), we’re filling seven stages with salon-like programs that focus on the industries that matter most to the tech world today. It’s a rare opportunity to explore cross-sector collaborations under one roof. Check out just some of the sessions on each stage below — click the stage link to see the individual agendas.
A Deep Dive on DeepMind, Google’s Premiere AI Lab
Bias, Toxicity and Hallucination: Can AI Be Ethical?
Plaid’s Zach Perret Opens up on Open Banking
The Future of Payments
Mixed Reality Finds Its Focus
What’s Next in Robotics?
What’s Next for GitHub?
AI for SaaS
Signal and the Future of Encrypted Messaging
The Spyware Industry Is Out of Control. Now What?
Doing Something Concrete on Climate
The Upside (and Downside) of Cultured Meat
Wait (we hear you cry) — that’s only six. Ah, you don’t miss a trick. We’re in the process of adding the Space Stage, which is gonna rock-et! Check back for updates and the agenda — coming soon!
Breakout sessions and roundtable discussions
This is your chance to learn more about specific topics, engage with the startup experts leading the conversations and get your burning questions asked and answered. Roundtables are 30-minute discussions. Breakouts are 30-minute presentations followed by a 20-minute Q&A. Here are a couple examples of each.
How to Build a Team for a Growing Startup
The Art of Choosing the Right Investor: A Guide for Startup Founders
AI for Social Good: How Technologists and Nonprofits Can Partner to Deliver Lasting Impact
Building Early-Stage Products as a Nontechnical Founder: What to and Not to Do
Networking at TechCrunch Disrupt 2023
Disrupt is no ordinary tech conference: Our audience spans the most influential corners of the startup community, from visionaries and prominent funders to cutting-edge innovators in the Fortune Global 500. My point? Disrupt is prime networking territory.
Connecting starts with the Disrupt event app — an essential connection and scheduling tool. But that’s just the beginning. We’re creating more organic networking opportunities where you can experience moments of magic in a variety of settings.
Get your network mojo moving on Disrupt eve, September 18, at the Women in Tech (Crunch) reception.
Head to the Deal Flow Café, our brand-new investor-to-founder networking area.
Enhance your trip to San Francisco at After-Hours Events happening during Disrupt week throughout the city.
Meet like-minded travelers in the many engaging workshops, discussions, meetups and Q&A sessions in the expo.
Recharge and reconnect at the TechCrunch+ Lounge, where TC+ subscribers can network and chat with our writers and other special guests.
TechCrunch Disrupt 2023 runs September 19–21 in San Francisco. Founders, put yourself first. Buy your pass before prices go up on August 11, and you’ll save up to $600. This is the way!
Is your company interested in sponsoring or exhibiting at TechCrunch Disrupt 2023? Contact our sponsorship sales team by filling out this form.
Deal Dive: Cutting through the noise in a category clouded by catastrophic failure
The startup is building a machine, VitalOne, that can perform more than 50 blood tests and get patient results back in 20 minutes.
Building a startup is hard enough but growing one in a category marred with Theranos-sized stigma is a new level of challenge. Vital Bio seems up for the test.
The Toronto-based startup is building a machine, VitalOne, that can perform more than 50 blood tests — covering nearly all of those considered routine — and get patient results back in 20 minutes, not multiple days. Co-founder and CEO Vasu Nadella said that he got interested in the space because he and his co-founders have watched family members deal with chronic illness and know that being able to get quick diagnostic results is crucial for treatment.
Plus, Nadella wanted to know why companies couldn’t seem to get the solution to this problem right. While Theranos failed for a variety of reasons, the other companies trying to build these quicker blood diagnostic tools had yet to ship products. He thought maybe he could crack the code.
The startup launched in 2019 and built quietly until it debuted its device at the American Association of Clinical Chemistry’s annual meeting — the industry’s “Super Bowl” — last Monday. Vital Bio also announced that it had raised $48 million in venture funding from Labcorp, Inovia Capital, Lachy Groom and Sam Altman, among others.
Nadella said the company has focused on making sure that its device produces accurate results and that when it does drift, they know how to prevent it from impacting the final diagnosis. He said the company waited to start talking about what it was up to until it felt it had enough to back up its claims.
Leaked guidelines reveal more details about Amazon’s controversial ‘voluntary resignation’ program for remote workers
submitted by /u/thebelsnickle1991 [link] [comments]
submitted by /u/thebelsnickle1991
[link] [comments]
U.S. Hunts Chinese Malware That Could Disrupt American Military Operations
American intelligence officials believe the malware could give China the power to disrupt or slow American deployments or resupply operations, including during a Chinese move against Taiwan.
American intelligence officials believe the malware could give China the power to disrupt or slow American deployments or resupply operations, including during a Chinese move against Taiwan.
New Orleans police use of facial recognition nets zero arrests in nine months
submitted by /u/anascapensis [link] [comments]
submitted by /u/anascapensis
[link] [comments]
Python’s Steering Council Plans to Make Its ‘Global Interpreter Lock’ Optional
Python’s Global Interpreter Lock “allows only one thread to hold the control of the Python interpreter,” according to the tutorial site Real Python. (They add, “it can be a performance bottleneck in CPU-bound and multi-threaded code.”)
Friday the Python Steering Council “announced its intent to accept PEP 703 (Making the Global Interpreter Lock Optional in CPython), with initial support possibly showing up in the 3.13 release,” reports LWN.net.
From the Steering Council’s announcement:
It’s clear that the overall sentiment is positive, both for the general idea and for PEP 703 specifically. The Steering Council is also largely positive on both. We intend to accept PEP 703, although we’re still working on the acceptance details…
Our base assumptions are:
– Long-term (probably 5+ years), the no-GIL build should be the only build. We do not want to create a permanent split between with-GIL and no-GIL builds (and extension modules).
– We want to be very careful with backward compatibility. We do not want another Python 3 situation, so any changes in third-party code needed to accommodate no-GIL builds should just work in with-GIL builds (although backward compatibility with older Python versions will still need to be addressed). This is not Python 4. We are still considering the requirements we want to place on ABI compatibility and other details for the two builds and the effect on backward compatibility.
– Before we commit to switching entirely to the no-GIL build, we need to see community support for it. We can’t just flip the default and expect the community to figure out what work they need to do to support it. We, the core devs, need to gain experience with the new build mode and all it entails. We will probably need to figure out new C APIs and Python APIs as we sort out thread safety in existing code. We also need to bring along the rest of the Python community as we gain those insights and make sure the changes we want to make, and the changes we want them to make, are palatable.
– We want to be able to change our mind if it turns out, any time before we make no-GIL the default, that it’s just going to be too disruptive for too little gain. Such a decision could mean rolling back all of the work, so until we’re certain we want to make no-GIL the default, code specific to no-GIL should be somewhat identifiable.
The current plan is to “add the no-GIL build as an experimental build mode, presumably in 3.13… [A]fter we have confidence that there is enough community support to make production use of no-GIL viable, we make the no-GIL build supported but not the default (yet), and set a target date/Python version for making it the default… We expect this to take at least a year or two, possibly more.”
“Long-term, we want no-GIL to be the default, and to remove any vestiges of the GIL (without unnecessarily breaking backward compatibility)… We think it may take as much as five years to get to this stage.”
Read more of this story at Slashdot.
Python’s Global Interpreter Lock “allows only one thread to hold the control of the Python interpreter,” according to the tutorial site Real Python. (They add, “it can be a performance bottleneck in CPU-bound and multi-threaded code.”)
Friday the Python Steering Council “announced its intent to accept PEP 703 (Making the Global Interpreter Lock Optional in CPython), with initial support possibly showing up in the 3.13 release,” reports LWN.net.
From the Steering Council’s announcement:
It’s clear that the overall sentiment is positive, both for the general idea and for PEP 703 specifically. The Steering Council is also largely positive on both. We intend to accept PEP 703, although we’re still working on the acceptance details…
Our base assumptions are:
– Long-term (probably 5+ years), the no-GIL build should be the only build. We do not want to create a permanent split between with-GIL and no-GIL builds (and extension modules).
– We want to be very careful with backward compatibility. We do not want another Python 3 situation, so any changes in third-party code needed to accommodate no-GIL builds should just work in with-GIL builds (although backward compatibility with older Python versions will still need to be addressed). This is not Python 4. We are still considering the requirements we want to place on ABI compatibility and other details for the two builds and the effect on backward compatibility.
– Before we commit to switching entirely to the no-GIL build, we need to see community support for it. We can’t just flip the default and expect the community to figure out what work they need to do to support it. We, the core devs, need to gain experience with the new build mode and all it entails. We will probably need to figure out new C APIs and Python APIs as we sort out thread safety in existing code. We also need to bring along the rest of the Python community as we gain those insights and make sure the changes we want to make, and the changes we want them to make, are palatable.
– We want to be able to change our mind if it turns out, any time before we make no-GIL the default, that it’s just going to be too disruptive for too little gain. Such a decision could mean rolling back all of the work, so until we’re certain we want to make no-GIL the default, code specific to no-GIL should be somewhat identifiable.
The current plan is to “add the no-GIL build as an experimental build mode, presumably in 3.13… [A]fter we have confidence that there is enough community support to make production use of no-GIL viable, we make the no-GIL build supported but not the default (yet), and set a target date/Python version for making it the default… We expect this to take at least a year or two, possibly more.”
“Long-term, we want no-GIL to be the default, and to remove any vestiges of the GIL (without unnecessarily breaking backward compatibility)… We think it may take as much as five years to get to this stage.”
Read more of this story at Slashdot.
Montana train derailment renews calls for automated systems to detect track problems
submitted by /u/MicroSofty88 [link] [comments]
submitted by /u/MicroSofty88
[link] [comments]