Podcasts about autofac

Welcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: It's time for a self-reproducing machine, published by Carl Feynman on August 8, 2024 on LessWrong. I've wanted to build a self-reproducing machine since I was 17. It's forty-five years later, and it has finally become feasible. (I've done a few other things along the way.) I'm going to describe one such device, and speculate as to its larger implications. It's a pretty detailed design, which I had to come up with to convince myself that it is feasible. No doubt there are better designs than this. The Autofac Here's a top-level description of the device I'm thinking of. It's called an Autofac, which is what they were called in the earliest story about them. It looks like a little metal shed, about a meter cubed. It weighs about 50 kilograms. There's a little gnome-sized door on each end. It's full of robot arms and automated machine tools. It's connected to electricity and by WiFi to a data center somewhere. It has a front door, where it accepts material, and a back door, where it outputs useful objects, and cans of neatly packaged waste. You can communicate with it, to tell it to make parts and assemble them into useful shapes. It can do all the metalworking operations available to a machinist with a good shop at their disposal. In return, it occasionally asks for help or clarification. One particular thing it can be told to make is another one of itself. This is of course the case we're all interested in. Here's what that looks like. You feed a 60kg package of steel castings, electronics, and other parts, into the door at one end. It starts by building another shed, next to the other end. The two sheds are butted up next to each other, so the rain can't get in. Once it's enclosed, there is no visible progress for about a month, but it makes various metalworking noises. Then it announces that it's done. The second shed is now another Autofac, and can be carried away to start the process elsewhere. There's also a can full of metal scrap and used lubricant, which has to be disposed of responsibly. This process can be repeated a number of times, at least seven, to produce more offspring. Eventually the original Autofac wears out, but by then it has hundreds of descendants. The software The key part of the Autofac, the part that kept it from being built before, is the AI that runs it. Present-day VLMs (vision-language models) are capable of performing short-deadline manual tasks like folding laundry or simple tool use. But they are deficient at arithmetic, long term planning and precisely controlling operations. Fortunately we already have software for these three purposes. First, of course, we have calculators for doing arithmetic. LLMs can be taught to use these. In the real world, machinists constantly use calculators. The Autofac will be no different. Second, there is project planning software that lets a human break down an engineering project into tasks and subtasks, and accommodate changes of plan as things go wrong. We can provide the data structures of this software, initially constructed by humans, as a resource for the AI to use. The AI only has to choose the next task, accomplish it or fail, and either remove it from the queue or add a new task to fix the problem. There are thousands of tasks in the life of an Autofac; fortunately the AI doesn't need to remember them all. The project planning software keeps track of what has been done and what needs to be done. Third, there are programs that go from the design of a part to a sequence of machine tool movements that will make that part, and then controls the machine tool motors to do the job. These are called Computer Aided Manufacturing, or CAM. Using CAM relieves the AI of the lowest level responsibilities of controlling motor positions and monitoring position sensors. This software doesn't do everything, of...

Link to original articleWelcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: It's time for a self-reproducing machine, published by Carl Feynman on August 8, 2024 on LessWrong. I've wanted to build a self-reproducing machine since I was 17. It's forty-five years later, and it has finally become feasible. (I've done a few other things along the way.) I'm going to describe one such device, and speculate as to its larger implications. It's a pretty detailed design, which I had to come up with to convince myself that it is feasible. No doubt there are better designs than this. The Autofac Here's a top-level description of the device I'm thinking of. It's called an Autofac, which is what they were called in the earliest story about them. It looks like a little metal shed, about a meter cubed. It weighs about 50 kilograms. There's a little gnome-sized door on each end. It's full of robot arms and automated machine tools. It's connected to electricity and by WiFi to a data center somewhere. It has a front door, where it accepts material, and a back door, where it outputs useful objects, and cans of neatly packaged waste. You can communicate with it, to tell it to make parts and assemble them into useful shapes. It can do all the metalworking operations available to a machinist with a good shop at their disposal. In return, it occasionally asks for help or clarification. One particular thing it can be told to make is another one of itself. This is of course the case we're all interested in. Here's what that looks like. You feed a 60kg package of steel castings, electronics, and other parts, into the door at one end. It starts by building another shed, next to the other end. The two sheds are butted up next to each other, so the rain can't get in. Once it's enclosed, there is no visible progress for about a month, but it makes various metalworking noises. Then it announces that it's done. The second shed is now another Autofac, and can be carried away to start the process elsewhere. There's also a can full of metal scrap and used lubricant, which has to be disposed of responsibly. This process can be repeated a number of times, at least seven, to produce more offspring. Eventually the original Autofac wears out, but by then it has hundreds of descendants. The software The key part of the Autofac, the part that kept it from being built before, is the AI that runs it. Present-day VLMs (vision-language models) are capable of performing short-deadline manual tasks like folding laundry or simple tool use. But they are deficient at arithmetic, long term planning and precisely controlling operations. Fortunately we already have software for these three purposes. First, of course, we have calculators for doing arithmetic. LLMs can be taught to use these. In the real world, machinists constantly use calculators. The Autofac will be no different. Second, there is project planning software that lets a human break down an engineering project into tasks and subtasks, and accommodate changes of plan as things go wrong. We can provide the data structures of this software, initially constructed by humans, as a resource for the AI to use. The AI only has to choose the next task, accomplish it or fail, and either remove it from the queue or add a new task to fix the problem. There are thousands of tasks in the life of an Autofac; fortunately the AI doesn't need to remember them all. The project planning software keeps track of what has been done and what needs to be done. Third, there are programs that go from the design of a part to a sequence of machine tool movements that will make that part, and then controls the machine tool motors to do the job. These are called Computer Aided Manufacturing, or CAM. Using CAM relieves the AI of the lowest level responsibilities of controlling motor positions and monitoring position sensors. This software doesn't do everything, of...

Happy New Year to all here in 2023. It's going to be a great year. It's a great time to be a programmer. A great time to be building with .NET; you are going to do great things this year. You have what it takes. You are smart, you have great tools, and you have a great team. You are a great leader. This episode is going to be all about remembering what happened this past year at the podcast.   Topics of Discussion:  [1:15] Jeffrey talks about the architect forums he's hosting and facilitating in 2023. You can register here. [1:46] Huge announcement in Microsoft Developer news including: - Android apps on Windows 11 - ARM processors getting big investments - Microsoft Dev Box — in preview — dev workstation in the cloud - Power Pages websites - Large SKU app service; up to 256GB RAM available for those who need it - Azure Arc, the new name of Hybrid Azure. And a single-node Azure Stack for remote locations but the programming model of Azure — looking forward to testing it at the right time. - Azure Container Apps tooling got better, and it became ready for prime time. Every team should be looking at this. - .NET 7 released. [4:11] What might the default application stacks and environments look like on the platform in 2023? - Windows 11 - Visual Studio 2022 w/ ReSharper - .NET 7 - Onion Architecture - Blazor for interactive applications - .NET service workers for back-end jobs and queue listeners - Entity Framework with Azure SQL — add on other storage services as per application. - Azure App Service for hosting while prototyping Azure Container Apps. - Application Insights with the Open Telemetry NuGet packages. - Azure Pipelines paired with Octopus Deploy (keep an eye on GitHub Actions as they fill out support for scenarios you need). - NordVPN for developer workstation work-from-home or remote Wi-Fi. [9:11] When it comes to developer workstations, desktop computers are still giving the most bang for the buck with power, and only a few laptops do the job really well. I have not reviewed all computers, and there are a lot out there. I can vouch for Alienware R series desktops. Liquid-cooled, so they are really quiet, even under full load. Dell Precision laptops are amazing for software engineers. I really wanted to love the Lenovo P1, but the fan was just too loud when it was under load. And we all know that cooling is so important in laptops. When a laptop gets too hot, your BIOS will slow down the processor to keep it from burning up. Then you no longer have a fast processor. And video calls use a good deal of processor, surprisingly — or not. For super mobile laptops that you can use for programming, I really do like the Microsoft Surface Laptop. I wanted to like the Surface Studio laptop, but they inverted the cooling and the battery placement, so it's very uncomfortable on my lap and my wrists unfortunately under load. The wrist wrest gets really hot. Normally the battery is under the wrist rest, but Microsoft swapped it on this one, so it's not fun using it as a laptop on your lap or even on a desk while hot and under load. [13:11] Highlighting some past episodes that will be interesting:  - Highlighting some past episodes over the year that might be interesting. - With Microsoft Orleans providing a new implementation of the Actor design pattern, we have a two-part series interview with Aaron Stannard, the creator of Akka.NET, episodes 172 and 173. - On the IoT front, Wilderness Labs has been trucking along creating system-on-a-chip options that run .NET natively and easily. I interviewed founder and CEO Bryan Costanich. - For those educating themselves for a career in software engineering, my interview with Henry Quillin might be useful. He talks about a programming internship and his education journey, his work earning his Eagle Scout, and how he became a working programmer even as he is just starting university. - More on embedded. Kevin Kirkus was with us in episode 186. He runs a testing team at Intel doing automated testing for their Xeon processor line. The design necessary for testing in this specialized environment gives us all plenty to think about. - For team leaders out there, I interviewed Mark Seemann. He wrote a recent book, Code That Fits In Your Head. He talks about the principles that are in the book. I subsequently bought and read the book, and I wish I had this book earlier in my career. Would have saved me a great deal of time. - On distributed systems, Udi Dahan is always a fascinating gentleman to listen to. Check out episode 192. As the founder and CEO of Particular Software, and the creator of NServiceBus, he is one of the world's leading experts on distributed systems, microservices, and messaging architectures. - Time-tested ideas are continually useful. I had the pleasure of interviewing Philippe Kruchten. He worked at Rational Software back when they were at the forefront of the software process in the 1990s. He published a paper outlining a framework for emergent, agile architecture. He didn't call it that. He called it the 4+1 Architecture, but only because it predated the agile manifesto. If you are an architect, and you aren't aware of this approach to architecture, give episode 195 a listen. - For the Blazor developers, I had Steve Sanderson on in episode 202. Steve is the original designer of Blazor, which has become the new default web application on .NET. He shared about the future of Blazor and WebAssembly. - Because there is so much going on in this space, Daniel Roth also joined me to discuss more Blazor Futures. - GitHub Actions is being talked about quite a bit. While loads of people are using it for builds, people are scratching their heads about where it fits in regarding deployments. Damian Brady, on the GitHub team and a former employee of Octopus Deploy, sheds light on this in episode 206. - Scott Hunter joined me in episode 211. He announced his new role at Microsoft running more of Azure development and .NET. He shared quite a bit behind the scenes regarding Microsoft's strategy there. - For the UX people. Mark Miller is the Chief Architect of DevExpress, the big UI components company. He has a brilliant user experience mind, and I was able to get him talking in episode 212. - Telemetry. We all need it to keep our software stable in production. The Serilog and AutoFac maintainer, Nicholas Blumhardt, joined me to discuss the fundamentals of modern logging and telemetry. Check out episode 217 for that. - More on the testing front, Eduardo Maltez, a software engineer doing some really interesting full system test work shares his thoughts on what makes tests reliable, stable, and fast — and how to fight brittle tests. Episode 224. - We closed out the year on the security front. With LastPass getting hacked and now Rackspace having a hacking-induced major outage, we all need to take action. Troy Vinson, a multi-certified security professional and certified ethical hacker, gave his perspective on the Rackspace breach and what every .NET team should learn from it.   Mentioned in this Episode: Architect Tips — New video podcast! Azure DevOps Clear Measure (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! Jeffrey Palermo's YouTube Jeffrey Palermo's Twitter — Follow to stay informed about future events! Programming with Palermo programming@palermo.network   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Existem grandes erros e grandes acertos nas adaptações dos contos de Philip K. Dick feitos pela Amazon. Neste episódio, comentamos os episódios 1 (Real Life, baseado no conto Peça de Exposição), episódio 2 (Autofac, baseado no conto de mesmo nome) e episódio 3 (Human Is, baseado no conto de mesmo nome). Veja a crítica de todos os episódios no blog: https://tavernadolugarnenhum.com.br/resenha/sonhos-eletricos/

Dopo aver letto il post di Syncfusion a riguardo della loro "Top 10 .NET Core Libraries Every Web Developer Should Know" (https://www.syncfusion.com/blogs/post/top-10-net-core-libraries-every-web-developers-should-know.aspx) ho deciso di fare la mia classifica, in base alle librerie che maggiornmente utilizzo.

Puntata dedicata alla Dependency Injection. Vediamo come poter migliorare la scrittura del codice nelle nostre applicazioni ASP.NET Core andandolo a semplificare disaccopiando le dipendeze. Un modo semplice e a gratis di scrivere buon codice da subito.

Steven van Deursen is building maintainable software with dependency injection. This episode is not sponsored! Want to be a sponsor? You can contact me or check out my sponsorship gig on Fiverr Show Notes: .NET Junkie - Steven’s blog Book: Dependency Injection Principles, Practices, and Patterns Check out episode 94 with Jeremy Miller on Lamar Book: Domain Driven Design Simple Injector Autofac Some free excerpts from the book: Writing Maintainable, Loosely-Coupled Code Understanding the Composition Root Abuse of Abstract Factories What’s wrong with the ASP.NET Core DI abstraction? Steven van Deursen is on Twitter Want to be on the next episode? You can! All you need is the willingness to talk about something technical.

"The future comes, and now my watch begins. It shall not end until my death. I shall miss no game, withhold no news, report all rumors. I shall wear no jerseys and plead allegiance to no side. I shall live and die on my webpage. I am the word in the darkness. I am the watcher of the tv. I am the megaphone that informs the realms of geek. I pledge my hands and name to the Geek's Watch, for geeks and all the geeks to come." John and Mitch give a spoilerful review of 'Ant-Man And The Wasp' and then continue with 'Phillip K. Dick's: Electric Dreams' season 1 episode 2 on Amazon Video.

Podcast Delivery Contents: 1 mediocre Philip K. Dick adaptation by Amazon: https://www.amazon.com/Philip-K-Dicks-Electric-Dreams/dp/B075NTXMN9   1 Brilliant Philip K. Dick short story that you need to read:  https://archive.org/stream/galaxymagazine-1955-11/Galaxy_1955_11#page/n71/mode/2up  2 Philosophical readings on the risks of AI: https://nickbostrom.com/ethics/ai.html https://hackernoon.com/the-parable-of-the-paperclip-maximizer-3ed4cccc669a 1 Mind blowing youtube video on self-replication: https://www.youtube.com/watch?v=V-96C4ExhWM   If any of the contents of this podcast leave you pizzled, please contact us through the following automated systems: Support us at Patreon: https://www.patreon.com/0G  Follow us on Twitter: https://twitter.com/0gPhilosophy Join our Facebook discussion group (make sure to answer the questions to join): https://www.facebook.com/groups/985828008244018/  Email us at: philosophersinspace@gmail.com Sibling shows: Serious Inquiries Only: https://seriouspod.com/ Opening Arguments: https://openargs.com/  Embrace the Void: https://voidpod.com/ Recent appearances: Check out Aaron co-hosting on This Week In News with Kevin and Benedict. Contact us to come on your show. We promise not to Borg you...much...

https://mwge.orgAre you really what you think you are? Is this world really what you think it is? Or maybe it's all just data...In this recording, David and Jason give a pre-movie talk which lasts 9 minutes and 3 seconds. At this point, we recommend you watch Philip K. Dick's Electric Dreams episode "Autoflac" (you can find Electric Dreams on Amazon Prime Video) and then resume the audio to listen to the commentary from during and after the movie.Themes/topics included in this talk: The Real World, artificial intelligence, the fear of redemption, defenselessness, no hierarchy of illusions, the ego's god, the addiction to linear time, and more!Recorded at a public Saturday night movie gathering at La Casa de Milagros in Chapala, Mexico on the 7th of April, 2018. For more information about these public Mexico gatherings with David Hoffmeister, go to http://www.acim-mexico.info/For more enlightening movie reviews, videos, audios, and much more, subscribe athttps://mwge.org

Finally we come to Philip K. Dick's clearest expression of one of his long running concepts, the "Autofac", as important today as it ever was.

Hello, PKD Fans! What happens to a world designed for pure automation when that world finally ends? Read more... The post EDP08 – S1 – Autofac appeared first on Golden Spiral Media- Entertainment Podcasts, Technology Podcasts & More.

Hello, PKD Fans! What happens to a world designed for pure automation when that world finally ends? Read more... The post EDP08 – S1 – Autofac appeared first on Golden Spiral Media- Entertainment Podcasts, Technology Podcasts & More.

"Blade Runner", "Minority Report", "The Man in the High Castle", "Total Recall", "A Scanner Darkly" oder "Der Plan": All das verdanken wir Philip Kindred Dick. Doch der wahre Schatz des Chicagoer Science-Fiction-Autors sind seine rund 120 Kurzgeschichten Mit der Anthologie-Serie "Philip K. Dick's Electric Dreams" will Amazon jezt diesen Schatz heben und dem Netflix-Rivalen "Black Mirror" Konkurrent machen. Wir diskutieren nicht nur, inwieweit das miss- oder gelingt (1:30), sondern bewerten alle zehn Episoden der ersten Staffel und ihre Vorlagen von gut nach schlecht: Crazy Diamond (2:46) Menschlich ist... (13:39) Fosters neue Welt (20:18) Das wahre Leben (27:32) Der unmögliche Planet (36:54) Das Vater-Ding (43:35) Tötet alle anderen (49:03) Der Haubenmacher (1:00:20) Autofac (1:09:25) Der Pendler (1:17:02) Musik: „Please Listen Carefully“ von Jahzzar

The .NET dudes talk to Nicholas Blumhardt about Autofac, an IoC container that uses lambda expressions in C# 3.0 to create components.Support this podcast at — https://redcircle.com/net-rocks/donations