Metrics using MetaFactory for in-house projects
The new MetaFactory IntelliJ plugin
At Metafactory we are using the MetaFactory tool continuously for coding our projects. Therefore we think as critically as anyone when it comes to identifying any nuisance that might stand in your way of smooth development. The continuous switching windows between IDE and the MetaFactory application when generating the code is one of those issues. Or ‘was’, because MetaFactory has now been extended with an IntelliJ IDE plugin! This allows you to generate your entire project (or a buildset of your code instructions) from within IntelliJ and view all the debug information in a run window.
Code generator quadrant
Code generators come in many flavors. In this article a code generator quadrant is presented based on the black-box versus white-box x-axis and the non developers versus developers y-axis. As there is no code generator that suits all purposes optimally, choosing the best one is a matter of properly anticipating its application and actual user.
Angular 2 Tour of Heroes and MetaFactory
As I was curious about the new Angular 2 with TypeScript I worked myself through the Tour of Heroes tutorial. The first thing I noticed is how modular Angular 2 actually is. Angular has a base application and a module ‘Hero’ that defines what we can do with our heroes. Now imagine that we would want to extend the functionality of our application by introducing a list of ‘Losers’ that can be interacted with in the same way as with our heroes.
How to write custom generated code?
MetaFactory is a tool that generates code. The software developer writes patterns in which the code to be generated is defined. The patterns are applied to the domain model.
In this article I touch several software developer preconceptions against code generation. Are those preconceptions still valid when using MetaFactory, and if not how does MetaFactory hand you the possibilities to overcome these general well known code generation shortcomings?
Making automated testing even more intelligent
Working in a software development project becomes increasingly interesting when the result that you’ve achieved as a team gradually approaches the final requirements. However, while delivering new features is a step forward in progress it is also of vital importance to verify that existing functionality keeps working as it should. Unfortunately, a speedy detection of breaking functionality requires extensive and frequent testing of all possible paths in the application. This process is a time consuming and monotonous task whereas most developers would rather design new functionality.
Start your sprint with a new delivery
At MetaFactory, we work on two different projects with the same architecture: AngularJS, and Java with Spring etc. After each two-week sprint our small team switches between projects. We use the same MetaFactory patterns for both projects. This allows us to start and end each sprint with a delivery.
Why take an SDA course?
Earn your certificate in software development automation with MetaFactory’s SDA courses.
In MetaFactory’s software development automation (SDA) courses you will learn two things:
- How to use an SDA tool. (We use the MetaFactory SDA tool.)
- How to recognize software patterns and the variations within these patterns.
Software Development Automation
Software Development Automation (SDA) turns programming into an automated process. Why is that a good thing for a developer?
Software engineers are proud of their code and the applications they develop. The applications do what they must do and the code is a feast for the eyes. No wonder that developers are reluctant to use code generators or Model-Driven Architecture tools. There are situations where generators or MDA tools are useful, but they rarely meet the norms and standards of an outstanding developer. MetaFactory is not a generator or MDA-tool.
Code Quality SAFe
MetaFactory supports Code Quality in SAFe (Scaled Agile Framework)
MetaFactory helps enterprise and system architects improve the Code Quality within SAFe by storing SAFe’s Architectural Runway in patterns and transferring these between individual Agile teams.