The Boundary-Control-Entity (BCE/ECB) pattern is a software architecture pattern that organizes code into Business Components. A Business Component is a package or namespace comprising three distinct layers, each with specific responsibilities. Business components adhere to the principles of maximal cohesion and minimal coupling, and are named after their domain responsibilities.

If you're writing for a living, as I do, I think you should be writing in Obsidian.

This session is about practical, no-nonsense coding. We'll explore lean Java 21+ practices and patterns that eliminate bloat and hacks that increase productivity. We will start with structuring and organizing backend monoliths and microservices, cover testing, then move on to decoupling, abstractions, Data Oriented Programming, automation with pure Java and the impact of LLM assistants on design and code structure.

Your questions and scenarios are not only welcome, they're essential.

Adam Bien

TLDR; Sogo est une couche d'intérop et webmail Open source et libre pour entreprise semble améliorer. Elle s'interface par dessus Cyrus et postfix. Utilisé et promu par la ville d'Echirolles.
Ca semble être fait en Objective C.

https://www.sogo.nu/about.html#/overview

SOGo offers multiple ways to access calendaring and messaging data. Your users can either use a web browser, Microsoft Outlook, Mozilla Thunderbird, Apple iCal, or a mobile device to access the same information.

SOGo is a highly interoperable solution due to its adoption and promotion of open standards. Among those, SOGo particularly focuses on:

• CalDAV: The Calendaring Extensions to WebDAV protocol is vastly popular among clients (Apple iCal, Mozilla Lightning, etc.) and allows them to exchange calendar components with servers that support it.
• CardDAV: In its fourth revision, vCard Extensions to WebDAV is to address books / contacts what CalDAV is to calendaring. Less popular than CalDAV, it's nevertheless quickly gaining momentum and is used by the SOGo Connector extension.
• Mail protocols: For messaging, SOGo fully makes use of standard protocols such as IMAP and SMTP.
• Microsoft Exchange ActiveSync: The de facto standard for synchronization of email, contacts, events, and tasks with mobile devices that use Apple iOS, Android, or Windows Phone.
  Supporting open standards provides SOGo with extensive interoperability, scripting capabilities and more.

https://www.sogo.nu/about.html#/why

Ease of deployment

• SOGo reuses your existing services such as Microsoft Active Directory, OpenLDAP, your SQL database, or even your IMAP server. By reusing those, SOGo prevents you from time-consuming data migration or directory services data duplication or synchronization problems
• If you have little or no existing services, ZEG can be used for immediate deployments. ZEG will get you running in minutes
• SOGo provides you with migration scripts from existing solutions and more scripts are being added

https://www.sogo.nu/about.html#/features

Components reusability

SOGo uses existing IMAP, SMTP, database and LDAP services. When not available, best breed ones can be used from the Open Source community such as Cyrus IMAP Server, Dovecot, OpenLDAP, Postfix, MySQL and PostgreSQL.

LLMs have been trained on decades of freely available Java specifications, including JSRs, JEPs, MicroProfile and Jakarta EE. They know the patterns. They know the standards. Now let's put them to work. In this live coding session, we'll use LLM agents to build production-ready Java applications quickly. No slides, no theory - just real code, real prompts, and real results. We'll start with a typical enterprise requirement and demonstrate how to guide LLMs to generate clean, maintainable Java code following BCE/ECB architecture patterns that actually work in production. You will learn how to effectively access the LLM's in-depth knowledge of Java specifications, how to continuously improve the generated code with each iteration, and how to maintain a high velocity without creating a mess. Expect live coding, real-world scenarios from actual projects, and honest discussion about where LLMs excel and where human expertise remains crucial. Bring your questions - we'll solve them with code.

Le collectif regroupe de nombreux acteurs du Grand Est qui oeuvre pour sensibiliser et accompagner les organisations vers un numérique plus responsable.

Nos objectifs

Objectif 1

Recenser et faire connaître les acteurs (des personnes et pas des structures) du Numérique Responsable dans la région.Nous souhaitons nous positionner en centre de ressources NR sur le territoire.

Objectif 2

Fédérer et animer les acteurs pour faire rayonner le Numérique Responsable sur le territoire. Nous souhaitons ainsi créer des opportunités de collaborations (business, appels à projets...)

AI coding agents frequently ignore long rule documents. Asking them to hold on to an entire book's worth of coding advice is at best futile, at worst makes the agent's performance worse by polluting the context window.

Humans don't need to hold the same information in their head because humans can form habits through repetition. However, AI agents can't do this.

Human habits form when an easy-to-detect cue triggers a complex sequence of actions with the desired effect. This is the inspiration for habit hooks.

Linters provide a deterministic metric, but Goodhart's law postulates that a metric ceases to be a good metric if it becomes a target. AI agents are very good at gaming these metrics when they are only provided the metric.

Habit hooks wraps your linter to create the trigger, but instead of providing only the metric, it gives actionable advice on how to fix the issue. This creates AI behaviour that looks like human habits, and has similar effects.

The use of habit hooks:

• Increases code quality
• Improves AI performance ensuring that the AI always starts with good code quality
• Reduces token usage, since good quality code also means the AI doesn't need to read as much context to complete the task.

Guidelines for Agentic development.

"Put your AI on rails."

BCE architecture · Java · Web standards

Adam Bien

Some of you may know Emacs as the rival to Vim, and we know that Vim has been increasing popularity. However, I like to go against the grain, which means I pivoted to Doom Emacs a couple years back, and I haven't looked back. In this video, I’m diving deep into why Doom Emacs has become my go-to choice for coding and productivity. If you’re tired of your current setup or just curious about what Doom Emacs can offer, you’re in the right place!

Doom Emacs is not just another text editor; it’s a powerful framework that enhances the Emacs experience. With its keyboard-centric workflow, you can do everything from coding to managing tasks, all in one place. I’ll share my favourite packages, explore some underutilized features, and even show you how it integrates seamlessly with my Linux distro, Nix.

One of the standout features for me is org-mode, which has transformed how I manage tasks and notes. I’ll walk you through my simplistic workflow and how you can easily adopt it to boost your productivity. Plus, I’ll discuss the benefits of using open-source software and how Doom Emacs supports a variety of programming languages without the hassle of extensive customization.

If you’ve ever felt overwhelmed by the complexity of Emacs, don’t worry! I’ll explain how Doom Emacs simplifies the experience while still allowing for customization. You’ll learn how to become a power user without spending hours reading documentation. And for those of you who have experience with Vim, you’ll be pleased to know that your skills transfer over seamlessly with Doom Emacs’s evil mode.

Join me as I explore the incredible capabilities of Doom Emacs, from its intuitive key bindings to its stability and performance. Whether you’re a seasoned developer or just starting out, this video will provide valuable insights into how you can enhance your coding experience. Don’t forget to like and subscribe for more content on Emacs and coding productivity!