Group items tagged

"There are sufficient videos available in the video repositories provided by YouTube and Vimeo to make it difficult locating the good ones. In addition, not all of them are professionally produced. However, InfoQ.com could identify some pearls which are worthwhile watching. We have reviewed what we found and tried to figure out the interesting ones. But, of course, such activities are always driven by the author's taste."

This is the book I'm currently reading

And? (Quite funny. I was just going through the InfoQ newsletter myself :)

Actually a really good book. Very different topic, more focused on configuration, deployment and operational stuff and not really code.

Sounds like this guy is confuse between enterprise architecture and solutions architecture. Or I am. :)

I think both those roles are evolving quite quickly at the moment. The classic Enterprise Architect is having to find new ways to plan, communicate and check quality as more and more teams explore Agile methodologies. The Solution Architect is suddenly playing a more obvious role as a result of the above. My feeling is, it is not so much about people, but about function. The same person could operate as a Solutions Architect most of the day, but then could get together in some kind of Architect's forum and play the role of an Enterprise Architect. That forum then wrestles through the Enterprise Architect issues and establishes the back-bone on which the Agile Development is done. That's what is probably happening, formally or informally in a lot of dev teams at the moment.

"I'll let you in on a secret: I don't care what letter you put in front of "DD." I don't care so much about how code is written or the ins-and-outs of software development. It's not because I don't realize how incredibly important it is - it's because what I care most about is the value delivered. How can what you do save me time, money and/or frustration? I'm smart enough to know that without you - the incredibly talented member of the development team - my life will go into a tailspin. Nothing will work. I realize and appreciate that what you develop creates value for me."

"We've all seen the statistics[1], and likely experienced first-hand, the reality of project failure. The majority of software projects continue to be classified as failures. In thinking about this situation we can see that there are a few different ways in which a project can fail (clearly this is not an exhaustive list!):"

"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."

" 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. "

" 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?"

"Fixed price contracts are evil - this is what can often be heard from agilists. On the other hand those contracts are reality which many agile teams have to face. But what if we try to tame it instead of fighting against it? How can a company execute this kind of contract using agile practices to achieve better results with lower risk? This article will try to answer those questions."

"Modern business relies on multitasking to get work done. Employees are evaluated on their ability to multitask. IT professionals are routinely assigned to multiple projects. Did we always do this? Does multitasking work? What are the real impacts of multitasking? Is there an alternative?"

" A number of commentators have been talking about the perceived dichotomy between Agile techniques and architectural thinking. In the Agile world architecture is often perceived as BDUF (Big Up Front Design) and as a result is frequently overlooked or delayed in the spirit of "YAGNI" (You ain't gonna need it)."

" Sadek Drobi talks about abstracting the control syntax (glue), giving examples from mainstream and FP languages: Null, propagating errors, events, asynchronous programming, lists, streams, channels, functors, monads, and custom abstractions. "

"When people invent or improve significantly new services or technologies, they are in general focused on their domains (especially software vendors who are tempted to cater to their market first). Cloud computing is no exception. IBM, For example, defines the Rainmaker technology as software and hardware that work together to help enterprises create clouds. And, as usual, the devil lives in the details, and software and hardware will work together in a very proprietary way."

l

" Martin Thompson and Michael Barker talk about building a HPC financial system handling over 100K tps at less than 1ms latency by having a new approach to infrastructure and software. Some of the tips include: understand the platform, model the domain, create a clear separation of concerns, choose data structures wisely, and run business logic on a single thread. "

" In this interview Ryan discusses Clojure with author Chris Houser. They cover Clojure's approach to classes, comparing and contrasting it with Java. Chris delves into they type of programming problem sets Clojure is best suited for, especially in relation to parallelism as the number of cores in computers increases and Clojure's applicability as or research language. "