- Working on my two papers about a new unifying theory of software architecture based on the "Independent Variation Principle" (IVP) (one paper for IEEE ICSA 2026 conf, Research track - I hope it will be accepted, and a long-form paper already on Zenodo: https://doi.org/10.5281/zenodo.17677316).
- Today I have started vibe-coding a frontend framework called wickeTS based on Apache Wicket's concepts, but for TypeScript. According to an analysis I made of various frontend frameworks (Java, JavaScript, dotnet, php...) using the IVP, Apache Wicket is the one that presents the highest compliance level with the IVP (the best decoupling of constructs that have different change driver assignments). I'll use it for my website (a knowledge base) about the IVP, and if it works, also for other things. I'd say that for SSR, I'm at least halfway there after half a day. For CSR, I haven't tested yet. I also plan to support Static Site Generation. And I plan to support accessibility standards.
- Organizing the creation of my company to start working as a freelance software consultant (mostly for archi & dev).
Hey I see that you are in Belgium, do you have some introductory material on IVP? Or recorded seminars? I'm always interested in learning more about arch
You might want to read "Chapter 8. Applying IVP: A Practical Framework" of the long-form paper.
It's difficult to have introductory stuff right now, I've only recently started publishing about it, and I've been busy with the very formal ICSA paper.
Nevertheless, I plan to publish a web site which would serve as the knowledge base about IVP in a near future (few weeks time).
There's actually so much to say about it, and I'm having new ideas every day... Latest one: use IVP to compare open-source software with proprietary software under the lens of their change drivers in various contexts.
