Group items tagged

That dev team must be very motivated and must be doing really great work!

"IDEAL CHALK mnemonic acronym and mnemonic images for Object Oriented Principles"

"SafePeak is a plug-and-play Dynamic Database Caching Solution, designed to improve data access performance for Applications built on SQL Server. It offloads the read queries and stored procedures which perform "Select" by dynamically caching in-memory result sets, thereby reducing read response time and overall database load."

"Kanban represents a unique way of catalyzing the application of Lean product development principles to software development, maintenance and operations. Being a method for driving change Kanban does not prescribe specific roles, practices or ceremonies but instead offers a series of principles to optimize value and flow in your software delivery system. As such, Kanban's focus on context and adaptability has made it increasingly popular for teams working in contexts where traditional Agile methods are not an easy fit and mature Agile teams looking for ways to further optimize their development process."

"If you´ve read my previous posts about why I deem WCF more of a problem than a solution and how I think we should switch to asynchronous only communication in distributed application, you might be wondering, how this could be done in an easy way."

" Don Syme overviews some of the basic features of functional languages, presenting why and when they are useful for parallel programming: simplicity, composability, immutability, lightweight reaction, translations, data parallelism, using F# examples but addressing the larger spectrum of functional languages including Haskell, Erlang, Clojure and JavaScript. "

" Object-oriented programming was supposed to unify the perspectives of the programmer and the end user in computer code: a boon both to usability and program comprehension. While objects capture structure well, they fail to capture system action. DCI is a vision to capture the end user cognitive model of roles and interactions between them. "

" Monitoring-Oriented Programming, abbreviated MOP, is a software development and analysis framework aiming at reducing the gap between formal specification and implementation by allowing them together to form a system. In MOP, runtime monitoring is supported and encouraged as a fundamental principle for building reliable software: monitors are automatically synthesized from specified properties and integrated into the original system to check its dynamic behaviors during execution. When a specification is violated or validated at runtime, user-defined actions will be triggered, which can be any code from information logging to runtime recovery. One can understand MOP from at least three perspectives: as a discipline allowing one to improve safety, reliability and dependability of a system by monitoring its requirements against its implementation at runtime; as an extension of programming languages with logics (one can add logical statements anywhere in the program, referring to past or future states); and as a lightweight formal method. "

"Jason Baragry from the Norvegian Computing Center asked me to comment on the relationship bettween MOP and DCI. I originally threw a few comments here. I wanted to go back and comment some more after watching James Coplien's latest video from QCon. James really ticked me off. He embodies -like so many self-proclaimed gurus- what is so wrong with our industry."

" Dan North talks about the tendency developers-becoming-architects have to create bigger and more complex systems. Without trying to be simplistic, North argues for simplicity, offering strategies to extract the simple essence from complex situations. "

" In this interview from the Erlang Factory event in London, three creators of modern functional languages -- Martin Odersky, creator of Scala; Joe Armstrong, a creator of Erlang; and Don Syme, creator of F# -- discuss the similarities and differences of their creations. They also discuss their languages' common thread -- that they integrate object-oriented features in functional languages. "

"Just Enough Software Architecture book, by author George Fairbanks, focuses on a risk-driven approach to software architecture development. RelatedVendorContent Got fires in production? Find root cause in minutes. FREE Java performance tool The Agile Business Analyst Experience Java EE! 600 page Redbook Testing Platforms Analyst Comparison: IBM, Microsoft, Coverity, MKS, and more Transform IT Complexity to Achieve IT System Vitality George explains the Architecture Modeling process from different perspectives such as Engineering Use Models, Conceptual Model, Domain Model, Design Model and the Code Model. He also discusses the various architecture styles including Big ball of mud, Pipe-and-filter, Batch-sequential, Map-Reduce and talks about the distinction between architectural patterns and architectural styles. The discussion also includes topics like evolutionary design, architecture refactoring and how to analyze, test and validate the architecture models."

"The results of software estimation are important for stakeholders to take care of team allocation and budgeting. A widely prevalent technique to estimate in Agile has been Planning Poker, which is a consensus based. Does this way of estimating take too much time? Are there other methods which can be employed by experienced practitioners?"