Flutter
Cross-platform mobile apps with a single code base. From the first screens to store publishing, up to the architecture of an app that needs to grow.
- Dart and widgets
- Navigation and state
- Networking and local data
- Testing and publishing
Training
Technical training built around your team
We do not have a catalogue with fixed dates and durations. We have the topics we work on every day and a way of building the course: we start from what the team needs, define the programme together and end with something you can use the following Monday.
The topics
Subjects we have already taught to other teams
These are the courses we have run most often, on technologies we use every day in our projects. Each card lists the aspects usually covered: which ones to go deeper into, and how far, we decide with you.
Angular
Structured web applications, with components, forms and state management that stay readable even as the project and the team grow.
- Components and signals
- Forms and validation
- API calls and RxJS
- Testing and code organisation
Backend with NestJS or Symfony
Well-organised APIs and services, in TypeScript with NestJS or in PHP with Symfony: modules, data access, security and a structure that holds up as the application grows.
- Modules and dependency injection
- REST and GraphQL
- Doctrine and the data model
- Authentication and security
- Testing and maintenance
Software architecture and coding best practices
How to design and write software that withstands change: boundaries between modules, the domain at the centre, readable code and tests that really protect you.
- DDD and domain boundaries
- Hexagonal and layered architecture
- Clean code and refactoring
- Testing and code review
Bringing AI into business processes
For decision makers and for the people working in the processes: what language models really do, where it pays to use them, what it takes to get started and how to evaluate a result.
- Concrete use cases by department
- Ready-made tools and integrations
- Data, confidentiality and limits
- How to measure whether it works
Better coding with AI
For development teams: using assistants and agents in daily work without losing control of the code, from writing to review to testing.
- IDE assistants and agents
- Prompts and context for code
- Reviewing generated code
- Team rules and workflows
How it works
How a course is built
The same topic is not the same course for two different teams. These steps shape the training plan around your needs, instead of fitting you into a programme already written.
Step 01
Introductory call
A first call, with no commitment, with whoever leads the team. You tell us the context, what led you to look for a course and which topic you have in mind. If the topic turns out to be different from how it looked, we say so right away.
Step 02
Requirements analysis
We pin down who takes part and how many, what their roles are, where they start from and what they need to be able to do at the end. From here come the course goals, measurable, and the choice of what to go deeper into and what to leave out.
Step 03
Presenting the plan
We present the training plan: programme, duration, format (on site, remote or mixed), schedule and materials. We discuss it together and adjust it until it meets your needs. Then we start.
Funded training. Many courses qualify for inter-professional funds or for training and digitalisation grants. We help you work out whether there is one you can use for your case and prepare the technical part of the paperwork with you.
The next step? We take it together
Whether you want to build software from scratch or grow a project that is already under way, we want to understand what you are trying to achieve. You do not need to have everything figured out: tell us about your idea, your doubts and the parts still to be defined. We guide you, with the right questions and concrete proposals, to work out where to start and how to move forward.
Let's talk about your project →