Tooling & standard generators
- Development and maintenance of the JoinedWorkz studio
- Standard generators for persistence, APIs and controllers
- Maven plugin and build integration support
- Improvements based on feedback from real projects
About JoinedWorkz & JoinedSystems
JoinedWorkz is developed and supported by JoinedSystems, an independent software engineering practice focusing on model-driven development, backend architectures and developer tooling.
The goal is straightforward: make it easier for teams to keep their architecture consistent while still giving developers room to do their job properly.
Background
JoinedWorkz grew out of practical project work where the same problems kept appearing: repetitive boilerplate, architecture guidelines that were hard to enforce, and documentation that fell behind the actual implementation.
Instead of building yet another “all-in-one platform”, JoinedWorkz focuses on:
- a DSL that is close enough to the code to be useful for developers,
- generators that encode real architecture decisions, not just syntax,
- integration with existing tools like Git, Maven and standard Java stacks.
JoinedSystems develops the toolchain and supports organizations that want to use it in real projects.
What JoinedSystems offers around JoinedWorkz
JoinedWorkz can be used as a tool on its own, but most organizations get the best results when they combine the product with targeted project support.
Project accompaniment
- Clarifying goals and realistic scope for model-driven generation
- Defining modeling conventions and DSL usage in your context
- Designing and implementing custom generators
- Coaching architects and developers during rollout
How cooperation typically looks
There is no single template for introducing JoinedWorkz, but a typical collaboration looks like this:
1
Initial discussion
Short call or workshop to understand your current stack, the size of your teams and where you see the main potential for generators (APIs, persistence, documentation, …).
2
Pilot definition
Select a concrete pilot project or area, define what should be modeled and what should be generated, and agree on how success will be measured.
3
Modeling & generator design
Work together on the model and the first custom generator(s). Align them with your architecture guidelines and coding standards.
4
Implementation & rollout
Use the generators in the pilot project, refine them based on feedback and then decide how to roll them out to further teams and systems.
The concrete scope and mode of collaboration can be adapted to your organization – from a short workshop up to ongoing support over several projects.
Contact
If you want to discuss whether JoinedWorkz fits your projects, or if you are interested in support for defining generators and integrating them into your stack, you can get in touch via:
- E-mail: info@joinedsystems.eu
- Website: joinedsystems.eu
- GitLab: JoinedWorkz on GitLab
A short description of your context (tech stack, team size, main pain points) helps to prepare a meaningful discussion.
Interested in trying JoinedWorkz in your environment?
Start by looking at the documentation and examples, and then reach out if you want to explore a pilot project or need support with custom generators.