Yan Cui talks about the advantages of using F# to build DSLs and using the actor model. Also: why and how to use graph databases to model (game) economies.
Eric Evans (Creator of Domain-Driven Design), and Brian Foote (Big Ball of Mud, Patterns Languages of Program Design), discuss the current state of software design, reminisce about the Small talk good old days, explain patterns from Domain-Driven Design, UML, Big Balls of Mud, and more.
Markus Völter explains the concepts of the MPS Language Workbench, how it enabled the mbeddr project, approaches to DSLs and how to combine them, programs vs models, formal verification, and more.
Vaclav Pech and Alexander Shatalin explain creating DSLs with Jetbrains MPS, the projectional editor, language extensions and much more.
Mike Williams, co-creator of Erlang discusses the history of and influences on Erlang as well as languages and paradigms used at Ericsson for large scale development and embedded programming.
Larva is a runtime monitoring system that uses AspectJ to weave monitoring into Java code and can check the correctness of the program using an FSM; Elarva is an Erlang version of the tool.
Debasish Gosh talks about Domain Specific Languages: how to build DSLs with Scala or XText, real world DSLs, parser combinators and monads. Also: how Akka brings actor-based programming to the JVM.
In this interview Alec Sharp, an expert on modeling, discusses the importance of modeling, particularly Business Process Modeling and BPMN (Business Process Modeling Notation) to app development. Sharp says that although building complex models can be contradictory to what Agile is about, building simple models is not. Sharp also refers to BPMN as a “visual programming language.”
In this interview Joseph Yoder talks about the Adaptive Object Model (AOM) architecture, a software architecture for easily adapting to changing business requirements.
In this interview, InfoQ’s Chief Editor, Floyd Marinescu, interviewed Scott Ambler, Practice Lead for Agile Development at IBM, on the current status of the Agile community and practices having a look at the perspective of the Agile’s future.
During OOPSLA 2007, InfoQ interviewed Markus Voelter asking him about creating software architecture documentation. Many people mention UML when they are asked about software design documentation, but Markus has a different take on that. He thinks that we should be using models which can be processed with tools which can validate or invalidate them.
Erik Doernenburg has worked in the field of enterprise applications for more than ten years. He is now employed by ThoughtWorks, and his latest interest is software visualization. In this interview he talks with InfoQ about different software visualization strategies using a combination of free tools and custom development.