Concurrency: Past and Present
Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.
Tracking change and innovation in the enterprise software development community
Posted by Mark Pollack on Mar 07, 2008 10:42 AM
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
Six Free Project Management Certification Training Courses
The End of Middleware: Freedom from IT Stacks as we know it
Gamma's Jazz platform's first implementation: Rational Team Concert (Trial Download)
The Agile Business Analyst: Skills and Techniques needed for Agile
I would like to understand everything said in the presentation. I know how to write English, but I am not a native speaker, and I am learning English these days and a transcription as you used to make would be a hit (ok, it on screen it cannot be present the offer a link or better, Closed Caption for the service). You name it.
I have used Spring.NET and tried to compare it to a typical 'anemic domain' architecture you might build in ASP.NET. I love it. I especially like using the Spring.Web (MVC) tools over the ASP.NET controls. Much easier to use. I wish this was the industry standard. Microsoft are moving to LINQ as their ORM, and I think you are seeing or will see Spring.NET copies also coming from Microsoft. (Of course you will eventually see a Grails copy too ;-) Thanks to Mark !! .paul
Very interesting presentation. There are many aspects that became clear to me. I think another presentation is necessary which compares Spring.NET to other similiar frameworks. I think that kind of presentation will clarify the decision of choosing appealing AF.
I would have loved to see the whole presentation all the way through, but the example code was difficult to read in the video and the camera shaking made me ill. The presentation is not for online viewing.
I only see or read about technologies ported over from other worlds to .NET, particularly from the Java/JEE world. Are there any original ideas in the .NET space? It seems like these folks are content w/ just standing on the shoulders of giants. Maybe I'm wrong. Is there anything that these folks have contributed to the development ecosystem?
play or work with others on IRC networks around the world, either in multi-user group conferences or in one-to-one private discussions. It has a clean, practical interface that is highly configurable and supports features such as buddy lists kurye motorlu kurye kurye motorlu kurye kurye kurye motorlu kurye kurye gavurlar adult forum sex kıralık araba kıralık araç araç kiralama oto kiralama araba kiralama minibüs kiralama kiralık oto rent a car porno haber büyütücü seks vprx erotik google kayıt web tasarımı web tasarım web yazılım web hosting e-ticaret e-ticaret e-ticaret e-ticaret sistemi sanal mağaza e ticaret akıllı e ticaret eticaret paketi bayilik file transfers, multi-server connections, SSL encryption, proxy support, UTF-8 display, customizable sounds, spoken messages, tray notifications, message logging, and more. mIRC also has a powerful scripting language
Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.
Often the hardest part of changing technologies is language syntax differences. This new article provides Java developers with a transition guide to Actionscript which forms the foundation of Flex.
Neal Ford talks about having multiple languages running on one of the two major platforms: Java and .NET. He also presents the advantages offered by Ruby compared to static languages like Java or C#.
David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile consists in finding ways to implement its principles.
Nick Sieger talks about the future of JRuby, Java Integration, and his work on JEE deployment tools for Ruby on Rails like Warbler.
Rustan Leino and Mike Barnett of Microsoft Research discuss the technology in Spec# and its futures.
Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.
This article outlines 9 principles Marc Lammers discovered while building the world’s best field hockey team, mapping them to software development practices.
6 comments
Reply