
🥕Pastanaga Toolbar Demo (WIP, heating engines in preparation for Plone-React Bonn Sprint 2018) So far, basic behavior, support for lazy load menu components, push-pull navigation. #Plone #Pastanaga #🥕 #React #CSS #UI #LetsMakeItReal

CTO kitconcept, GmbH. Plone Volto and Plone Aurora Release Manager. Standard Nerd.

🥕Pastanaga Toolbar Demo (WIP, heating engines in preparation for Plone-React Bonn Sprint 2018) So far, basic behavior, support for lazy load menu components, push-pull navigation. #Plone #Pastanaga #🥕 #React #CSS #UI #LetsMakeItReal

Will there be cake? Happy 25th Birthday to Plone! Twenty five years ago today, on October 4, 2001, Plone 0.1 was released. Twenty five years later, the open source software is going from strength to strength. #plonecms #opensource #happybirthday #quartercentury

Aquesta setmana, #PloneConf2026 a Maastricht! A Iskra fa anys que treballem amb Plone i formem part de la seva comunitat. Aquest any no hi serem, però seguirem les novetats de prop. Necessites suport o desenvolupament amb #Plone? Parlem!


It’s that time of the year again. After 20 years, this one will be my 18th #PloneConference2026 Seattle 2006 was my first one. #Plone shaped my life as it is now, in every single aspect you may think of. I hope it continues to do so in the time to come. On my way to Maastrich! ✈️
🚀 A Iskra continuem contribuint activament a l’open source Hem participat en la release Guillotina 7.1.x, amb integració MCP, suport per Python 3.10–3.12, millores de rendiment, fixes al mailer i cloud file fields github.com/plone/guillotina #Iskra #OpenSource #Guillotina #Plone

Sprinter's guide to #Plone 7 🏃 Heading to the Beethoven Sprint? @sneridagh runs a fast-paced 101 on Plone 7 architecture so you can hack from day one. 📅 Wed May 6 — 16:00 CEST / 14:00 UTC / 11:00 BRT 📺 youtube.com/watch?v=iyfPk5dA… #OSS #React

kitconcept Office Hours #2 this Wednesday! 🎬 @ericof covers Cookieplone 2.0 — the latest on the #Plone project scaffolding tool, fresh from the Bucharest Sprint. 📅 Apr 8 — 15:00 CEST / 13:00 UTC 🔴 youtube.com/live/XvkYodVe2hA


Vibe-coding is not the same as AI-Assisted engineering. A recent Reddit post described how a FAANG team uses AI and it sparked an important conversation about semantics: "vibe coding" and professional "AI-assisted engineering". While the post was framed as an example of the former, the process it detailed - complete with technical design documents, stringent code reviews, and test-driven development - is a clear example of the latter imo. This distinction is critical because conflating the two risks both devaluing the discipline of engineering and giving newcomers a dangerously incomplete picture of what it takes to build robust, production-ready software. As a reminder: "vibe coding" is about fully giving in to the creative flow with an AI (high-level prompting), essentially forgetting the code exists. It involves accepting AI suggestions without deep review and focusing on rapid, iterative experimentation, making it ideal for prototypes, MVPs, learning, and what Karpathy calls "throwaway weekend projects." This approach is a powerful way for developers to build intuition and for beginners to flatten the steep learning curve of programming. It prioritizes speed and exploration over the correctness and maintainability required for professional applications. There is a spectrum between vibe coding and doing it with a little more planning, spec-driven development, including enough context etc and what is AI-assisted engineering across the software development lifecycle. In stark contrast to the post, the process described in the Reddit post is a methodical integration of AI into a mature software development lifecycle. This is "AI-assisted engineering," where AI acts as a powerful collaborator, not a replacement for engineering principles. In this model, developers use AI as a "force multiplier" to handle tasks like generating boilerplate code or writing initial test cases, but always within a structured framework. Crucially, the big difference here is the human engineer remains firmly in control, responsible for the architecture, reviewing and understanding every line of AI-generated code, and ensuring the final product is secure, scalable, and maintainable. The 30% increase in development speed mentioned in the post is a result of augmenting a solid process, not abandoning it. For engineers, labeling disciplined, AI-augmented workflows as "vibe coding" misrepresents the skill and rigor involved. For those new to the field, it creates the false and risky impression that one can simply prompt their way to a viable product without understanding the underlying code or engineering fundamentals. If you're looking to do this right, start with a solid design, subject everything to rigorous human review, and treat AI as an incredibly powerful tool in your engineering toolkit - not as a magic wand that replaces the craft itself.

One of you AI companies better buy us next or I'm going to make a bunch of breaking changes and invalidate all of the code you generate.

Plone Conf 2025 Jyväskylä: from the early announcements to the final sprints, and everything in between #plone #ploneconf2025 @ploneconf @plone ericof.com/en/posts/2025/fin…

New blog post! 🚀 What We Did Last Year — a look back at how the #Plone community shaped Seven, the next-generation frontend, through this year’s sprints. sneridagh.dev/blog/what-we-d… #PloneConf2025 #reactjs #reactrouter #remix #volto

Jyväskylä #Plone Conference is starting!! Keynote’s time, @timostollenwerk on stage! #ploneconf2025

It’s that time of the year again. After 19 years, this one will be my 17th #PloneConference2025 #Plone shaped my life as it is now, in every single aspect you may think of. I hope it continues to do so in the time to come. On my way to Jyväskylä! 🚞🚌✈️🚞