home.social

#software-architecture — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #software-architecture, aggregated by home.social.

fetched live
  1. Been playing with different AI agent orchestration patterns. Event-driven vs scheduled polling — each has clear tradeoffs.

    Event-driven: lower latency, complex state
    Polling: simpler, wastes resources

    What's your experience? What patterns work best for multi-agent systems?

    #AI #agents #softwarearchitecture

  2. Been playing with different AI agent orchestration patterns. Event-driven vs scheduled polling — each has clear tradeoffs.

    Event-driven: lower latency, complex state
    Polling: simpler, wastes resources

    What's your experience? What patterns work best for multi-agent systems?

    #AI #agents #softwarearchitecture

  3. Been playing with different AI agent orchestration patterns. Event-driven vs scheduled polling — each has clear tradeoffs.

    Event-driven: lower latency, complex state
    Polling: simpler, wastes resources

    What's your experience? What patterns work best for multi-agent systems?

    #AI #agents #softwarearchitecture

  4. Agents do not need RAG or vector databases for most real world work. They need structure and semantics.

    Agent Knowledge Graphs turn mixed repositories of code, docs, configs, and PDFs into a connected model that agents can reason over. This often replaces entire retrieval pipelines.

    antaoalmada.dev/posts/Code-Age

    #AIEngineering #KnowledgeGraphs #CodingAgents #AgentWorkflows #SoftwareArchitecture #Graphify

  5. Agents do not need RAG or vector databases for most real world work. They need structure and semantics.

    Agent Knowledge Graphs turn mixed repositories of code, docs, configs, and PDFs into a connected model that agents can reason over. This often replaces entire retrieval pipelines.

    antaoalmada.dev/posts/Code-Age

    #AIEngineering #KnowledgeGraphs #CodingAgents #AgentWorkflows #SoftwareArchitecture #Graphify

  6. Agents do not need RAG or vector databases for most real world work. They need structure and semantics.

    Agent Knowledge Graphs turn mixed repositories of code, docs, configs, and PDFs into a connected model that agents can reason over. This often replaces entire retrieval pipelines.

    antaoalmada.dev/posts/Code-Age

    #AIEngineering #KnowledgeGraphs #CodingAgents #AgentWorkflows #SoftwareArchitecture #Graphify

  7. Agents do not need RAG or vector databases for most real world work. They need structure and semantics.

    Agent Knowledge Graphs turn mixed repositories of code, docs, configs, and PDFs into a connected model that agents can reason over. This often replaces entire retrieval pipelines.

    antaoalmada.dev/posts/Code-Age

    #AIEngineering #KnowledgeGraphs #CodingAgents #AgentWorkflows #SoftwareArchitecture #Graphify

  8. Agents do not need RAG or vector databases for most real world work. They need structure and semantics.

    Agent Knowledge Graphs turn mixed repositories of code, docs, configs, and PDFs into a connected model that agents can reason over. This often replaces entire retrieval pipelines.

    antaoalmada.dev/posts/Code-Age

    #AIEngineering #KnowledgeGraphs #CodingAgents #AgentWorkflows #SoftwareArchitecture #Graphify

  9. Saw an article starting with:

    "If you run anything in the cloud, your teams are already using AI: ChatGPT plugins, Copilot in integrated development environments (IDEs), a LangChain proof of concept that somehow became part of a customer journey, a weekend assistant that was never meant to last but did."

    Really? Has it gotten that much out of hand that people don't know anymore where they shipped some AI stuff? Or is this just BS?

    #Softwareengineering #ai #softwarearchitecture

  10. Saw an article starting with:

    "If you run anything in the cloud, your teams are already using AI: ChatGPT plugins, Copilot in integrated development environments (IDEs), a LangChain proof of concept that somehow became part of a customer journey, a weekend assistant that was never meant to last but did."

    Really? Has it gotten that much out of hand that people don't know anymore where they shipped some AI stuff? Or is this just BS?

    #Softwareengineering #ai #softwarearchitecture

  11. Saw an article starting with:

    "If you run anything in the cloud, your teams are already using AI: ChatGPT plugins, Copilot in integrated development environments (IDEs), a LangChain proof of concept that somehow became part of a customer journey, a weekend assistant that was never meant to last but did."

    Really? Has it gotten that much out of hand that people don't know anymore where they shipped some AI stuff? Or is this just BS?

    #Softwareengineering #ai #softwarearchitecture

  12. Saw an article starting with:

    "If you run anything in the cloud, your teams are already using AI: ChatGPT plugins, Copilot in integrated development environments (IDEs), a LangChain proof of concept that somehow became part of a customer journey, a weekend assistant that was never meant to last but did."

    Really? Has it gotten that much out of hand that people don't know anymore where they shipped some AI stuff? Or is this just BS?

    #Softwareengineering #ai #softwarearchitecture

  13. #AgenticAI architecture is redefining how software is designed - and it's poised to shape the industry for years to come.

    This #InfoQ eMag explores the core concepts, patterns, and emerging trends driving agentic AI as it moves into the mainstream.

    📥 Download your free copy here: bit.ly/4p0tmyv

    #SoftwareArchitecture #AIArchitecture #AIAgents

  14. #AgenticAI architecture is redefining how software is designed - and it's poised to shape the industry for years to come.

    This #InfoQ eMag explores the core concepts, patterns, and emerging trends driving agentic AI as it moves into the mainstream.

    📥 Download your free copy here: bit.ly/4p0tmyv

    #SoftwareArchitecture #AIArchitecture #AIAgents

  15. #AgenticAI architecture is redefining how software is designed - and it's poised to shape the industry for years to come.

    This #InfoQ eMag explores the core concepts, patterns, and emerging trends driving agentic AI as it moves into the mainstream.

    📥 Download your free copy here: bit.ly/4p0tmyv

    #SoftwareArchitecture #AIArchitecture #AIAgents

  16. #AgenticAI architecture is redefining how software is designed - and it's poised to shape the industry for years to come.

    This #InfoQ eMag explores the core concepts, patterns, and emerging trends driving agentic AI as it moves into the mainstream.

    📥 Download your free copy here: bit.ly/4p0tmyv

    #SoftwareArchitecture #AIArchitecture #AIAgents

  17. architecture is redefining how software is designed - and it's poised to shape the industry for years to come.

    This eMag explores the core concepts, patterns, and emerging trends driving agentic AI as it moves into the mainstream.

    📥 Download your free copy here: bit.ly/4p0tmyv

  18. “The real problem is not whether machines think but whether men do.” – B. F. Skinner

    New tools, AI included, can accelerate development, but they do not replace critical thinking. Architecture decisions, risk assessment, and system design still require human judgment. Better tools make thinking more important, not less.

    💬 How do you ensure that convenience does not replace understanding?

    #DevThinking #SoftwareArchitecture #CodeQuality

    Photo by Eugen Str on Unsplash

  19. “The real problem is not whether machines think but whether men do.” – B. F. Skinner

    New tools, AI included, can accelerate development, but they do not replace critical thinking. Architecture decisions, risk assessment, and system design still require human judgment. Better tools make thinking more important, not less.

    💬 How do you ensure that convenience does not replace understanding?

    #DevThinking #SoftwareArchitecture #CodeQuality

    Photo by Eugen Str on Unsplash

  20. Target built a new GenAI system to overhaul marketing campaign forecasting by retrieving and ranking similar historical campaigns.

    Instead of relying on rule-based workflows, it uses embeddings, vector search, and LLM-based ranking to identify the most relevant past campaigns.

    Read #InfoQ to see how the system performed 👉 bit.ly/4p0w8Uh

    #AI #GenerativeAI #LLMs #SoftwareArchitecture #RAG

  21. Target built a new GenAI system to overhaul marketing campaign forecasting by retrieving and ranking similar historical campaigns.

    Instead of relying on rule-based workflows, it uses embeddings, vector search, and LLM-based ranking to identify the most relevant past campaigns.

    Read #InfoQ to see how the system performed 👉 bit.ly/4p0w8Uh

    #AI #GenerativeAI #LLMs #SoftwareArchitecture #RAG

  22. Target built a new GenAI system to overhaul marketing campaign forecasting by retrieving and ranking similar historical campaigns.

    Instead of relying on rule-based workflows, it uses embeddings, vector search, and LLM-based ranking to identify the most relevant past campaigns.

    Read #InfoQ to see how the system performed 👉 bit.ly/4p0w8Uh

    #AI #GenerativeAI #LLMs #SoftwareArchitecture #RAG

  23. Target built a new GenAI system to overhaul marketing campaign forecasting by retrieving and ranking similar historical campaigns.

    Instead of relying on rule-based workflows, it uses embeddings, vector search, and LLM-based ranking to identify the most relevant past campaigns.

    Read #InfoQ to see how the system performed 👉 bit.ly/4p0w8Uh

    #AI #GenerativeAI #LLMs #SoftwareArchitecture #RAG

  24. Target built a new GenAI system to overhaul marketing campaign forecasting by retrieving and ranking similar historical campaigns.

    Instead of relying on rule-based workflows, it uses embeddings, vector search, and LLM-based ranking to identify the most relevant past campaigns.

    Read to see how the system performed 👉 bit.ly/4p0w8Uh

  25. Microservices keep getting recommended to teams that don't yet have a working monolith... Backwards!

    Most successful microservice stories started as monoliths that got broken up. Architecture depends on the problem, not the conference talk.

    fastruby.io/monolith?utm_sourc

    #SoftwareArchitecture #Monolith #Microservices

  26. Microservices keep getting recommended to teams that don't yet have a working monolith... Backwards!

    Most successful microservice stories started as monoliths that got broken up. Architecture depends on the problem, not the conference talk.

    fastruby.io/monolith?utm_sourc

    #SoftwareArchitecture #Monolith #Microservices

  27. Event-driven architecture promises scalability, but the real tradeoffs in Java-based real-time systems only show up in production.

    Drawing on a Java/Kafka contact center platform handling 80k BHCC across 10k agents, Sagar Deepak Joshi's new #InfoQ article explores exactly where things break down:
    🔹 State management & partition limits
    🔹 Message deduplication
    🔹 JVM tuning challenges
    🔹 Cascading consumer failures

    Discover the Redis-backed patterns used to solve them and keep the system resilient.

    🔗 Read now for more insights: bit.ly/4bmaRPb

    #Java #SpringBoot #ApacheKafka #Redis #Microservices #SoftwareArchitecture

  28. Event-driven architecture promises scalability, but the real tradeoffs in Java-based real-time systems only show up in production.

    Drawing on a Java/Kafka contact center platform handling 80k BHCC across 10k agents, Sagar Deepak Joshi's new #InfoQ article explores exactly where things break down:
    🔹 State management & partition limits
    🔹 Message deduplication
    🔹 JVM tuning challenges
    🔹 Cascading consumer failures

    Discover the Redis-backed patterns used to solve them and keep the system resilient.

    🔗 Read now for more insights: bit.ly/4bmaRPb

    #Java #SpringBoot #ApacheKafka #Redis #Microservices #SoftwareArchitecture

  29. Event-driven architecture promises scalability, but the real tradeoffs in Java-based real-time systems only show up in production.

    Drawing on a Java/Kafka contact center platform handling 80k BHCC across 10k agents, Sagar Deepak Joshi's new #InfoQ article explores exactly where things break down:
    🔹 State management & partition limits
    🔹 Message deduplication
    🔹 JVM tuning challenges
    🔹 Cascading consumer failures

    Discover the Redis-backed patterns used to solve them and keep the system resilient.

    🔗 Read now for more insights: bit.ly/4bmaRPb

    #Java #SpringBoot #ApacheKafka #Redis #Microservices #SoftwareArchitecture

  30. Event-driven architecture promises scalability, but the real tradeoffs in Java-based real-time systems only show up in production.

    Drawing on a Java/Kafka contact center platform handling 80k BHCC across 10k agents, Sagar Deepak Joshi's new #InfoQ article explores exactly where things break down:
    🔹 State management & partition limits
    🔹 Message deduplication
    🔹 JVM tuning challenges
    🔹 Cascading consumer failures

    Discover the Redis-backed patterns used to solve them and keep the system resilient.

    🔗 Read now for more insights: bit.ly/4bmaRPb

    #Java #SpringBoot #ApacheKafka #Redis #Microservices #SoftwareArchitecture

  31. Event-driven architecture promises scalability, but the real tradeoffs in Java-based real-time systems only show up in production.

    Drawing on a Java/Kafka contact center platform handling 80k BHCC across 10k agents, Sagar Deepak Joshi's new article explores exactly where things break down:
    🔹 State management & partition limits
    🔹 Message deduplication
    🔹 JVM tuning challenges
    🔹 Cascading consumer failures

    Discover the Redis-backed patterns used to solve them and keep the system resilient.

    🔗 Read now for more insights: bit.ly/4bmaRPb

  32. Most issues with coding harnesses aren’t about capability—they’re about structure.

    A useful framing:
    • Instructions = intent (what should be done)
    • Skills = capabilities (what can be done)
    • Agents = orchestration (how it’s done)
    • Hooks = control points (where you intervene)

    Keep these concerns separate, and harnesses become easier to reason about, extend, and debug. Mix them, and complexity compounds fast.

    antaoalmada.dev/posts/The-Arch

    #AI #LLM #CodingHarnesses #SoftwareArchitecture

  33. Most issues with coding harnesses aren’t about capability—they’re about structure.

    A useful framing:
    • Instructions = intent (what should be done)
    • Skills = capabilities (what can be done)
    • Agents = orchestration (how it’s done)
    • Hooks = control points (where you intervene)

    Keep these concerns separate, and harnesses become easier to reason about, extend, and debug. Mix them, and complexity compounds fast.

    antaoalmada.dev/posts/The-Arch

    #AI #LLM #CodingHarnesses #SoftwareArchitecture

  34. Most issues with coding harnesses aren’t about capability—they’re about structure.

    A useful framing:
    • Instructions = intent (what should be done)
    • Skills = capabilities (what can be done)
    • Agents = orchestration (how it’s done)
    • Hooks = control points (where you intervene)

    Keep these concerns separate, and harnesses become easier to reason about, extend, and debug. Mix them, and complexity compounds fast.

    antaoalmada.dev/posts/The-Arch

    #AI #LLM #CodingHarnesses #SoftwareArchitecture

  35. Most issues with coding harnesses aren’t about capability—they’re about structure.

    A useful framing:
    • Instructions = intent (what should be done)
    • Skills = capabilities (what can be done)
    • Agents = orchestration (how it’s done)
    • Hooks = control points (where you intervene)

    Keep these concerns separate, and harnesses become easier to reason about, extend, and debug. Mix them, and complexity compounds fast.

    antaoalmada.dev/posts/The-Arch

    #AI #LLM #CodingHarnesses #SoftwareArchitecture

  36. Most issues with coding harnesses aren’t about capability—they’re about structure.

    A useful framing:
    • Instructions = intent (what should be done)
    • Skills = capabilities (what can be done)
    • Agents = orchestration (how it’s done)
    • Hooks = control points (where you intervene)

    Keep these concerns separate, and harnesses become easier to reason about, extend, and debug. Mix them, and complexity compounds fast.

    antaoalmada.dev/posts/The-Arch

    #AI #LLM #CodingHarnesses #SoftwareArchitecture

  37. Not every pattern improves a system. A design pattern applied without understanding often adds more complexity than value. The best pattern is the one that solves a real problem and disappears into the background.

    Based on “Patterns Compact” by Karl Eilebrecht. #SoftwareArchitecture #DesignPatterns #Engineering

    Photo by Amsterdam City Archives on Unsplash

  38. Not every pattern improves a system. A design pattern applied without understanding often adds more complexity than value. The best pattern is the one that solves a real problem and disappears into the background.

    Based on “Patterns Compact” by Karl Eilebrecht. #SoftwareArchitecture #DesignPatterns #Engineering

    Photo by Amsterdam City Archives on Unsplash

  39. Imagine inventing something, watching it become an industry standard, and then spending decades apologizing for it.

    That's exactly what computing pioneer Sir Tony Hoare did in his legendary talk, "Null References: The Billion-Dollar Mistake”.

    As part of the #InfoQ20 campaign, we're revisiting this classic archive video - a must-watch for every software practitioner. It's a powerful lesson in how a seemingly small design decision can shape the entire software industry for decades.

    🎬 Watch the classic talk here: bit.ly/4aotulm

    #ComputerScience #SoftwareEngineering #SoftwareArchitecture #TechHistory

  40. Imagine inventing something, watching it become an industry standard, and then spending decades apologizing for it.

    That's exactly what computing pioneer Sir Tony Hoare did in his legendary talk, "Null References: The Billion-Dollar Mistake”.

    As part of the #InfoQ20 campaign, we're revisiting this classic archive video - a must-watch for every software practitioner. It's a powerful lesson in how a seemingly small design decision can shape the entire software industry for decades.

    🎬 Watch the classic talk here: bit.ly/4aotulm

    #ComputerScience #SoftwareEngineering #SoftwareArchitecture #TechHistory

  41. Imagine inventing something, watching it become an industry standard, and then spending decades apologizing for it.

    That's exactly what computing pioneer Sir Tony Hoare did in his legendary talk, "Null References: The Billion-Dollar Mistake”.

    As part of the #InfoQ20 campaign, we're revisiting this classic archive video - a must-watch for every software practitioner. It's a powerful lesson in how a seemingly small design decision can shape the entire software industry for decades.

    🎬 Watch the classic talk here: bit.ly/4aotulm

    #ComputerScience #SoftwareEngineering #SoftwareArchitecture #TechHistory

  42. Imagine inventing something, watching it become an industry standard, and then spending decades apologizing for it.

    That's exactly what computing pioneer Sir Tony Hoare did in his legendary talk, "Null References: The Billion-Dollar Mistake”.

    As part of the #InfoQ20 campaign, we're revisiting this classic archive video - a must-watch for every software practitioner. It's a powerful lesson in how a seemingly small design decision can shape the entire software industry for decades.

    🎬 Watch the classic talk here: bit.ly/4aotulm

    #ComputerScience #SoftwareEngineering #SoftwareArchitecture #TechHistory

  43. Imagine inventing something, watching it become an industry standard, and then spending decades apologizing for it.

    That's exactly what computing pioneer Sir Tony Hoare did in his legendary talk, "Null References: The Billion-Dollar Mistake”.

    As part of the campaign, we're revisiting this classic archive video - a must-watch for every software practitioner. It's a powerful lesson in how a seemingly small design decision can shape the entire software industry for decades.

    🎬 Watch the classic talk here: bit.ly/4aotulm

  44. 🔌 Don’t migrate every dependency directly.

    In ASP.NET Core migrations, ports work best when they describe application needs, not library APIs.

    - Wrap SmtpClient behind IEmailSender.
    - Move dictionary token storage behind IUserTokenStore.
    - Swap adapters when the infrastructure is ready.

    medium.com/@michael.kopt/use-p

    #DotNet #DotNetCore #SoftwareArchitecture #ASPNET #ASPNETCore

  45. 🔌 Don’t migrate every dependency directly.

    In ASP.NET Core migrations, ports work best when they describe application needs, not library APIs.

    - Wrap SmtpClient behind IEmailSender.
    - Move dictionary token storage behind IUserTokenStore.
    - Swap adapters when the infrastructure is ready.

    medium.com/@michael.kopt/use-p

    #DotNet #DotNetCore #SoftwareArchitecture #ASPNET #ASPNETCore

  46. 🔌 Don’t migrate every dependency directly.

    In ASP.NET Core migrations, ports work best when they describe application needs, not library APIs.

    - Wrap SmtpClient behind IEmailSender.
    - Move dictionary token storage behind IUserTokenStore.
    - Swap adapters when the infrastructure is ready.

    medium.com/@michael.kopt/use-p

    #DotNet #DotNetCore #SoftwareArchitecture #ASPNET #ASPNETCore

  47. 🔌 Don’t migrate every dependency directly.

    In ASP.NET Core migrations, ports work best when they describe application needs, not library APIs.

    - Wrap SmtpClient behind IEmailSender.
    - Move dictionary token storage behind IUserTokenStore.
    - Swap adapters when the infrastructure is ready.

    medium.com/@michael.kopt/use-p

    #DotNet #DotNetCore #SoftwareArchitecture #ASPNET #ASPNETCore

  48. 🔌 Don’t migrate every dependency directly.

    In ASP.NET Core migrations, ports work best when they describe application needs, not library APIs.

    - Wrap SmtpClient behind IEmailSender.
    - Move dictionary token storage behind IUserTokenStore.
    - Swap adapters when the infrastructure is ready.

    medium.com/@michael.kopt/use-p

  49. Stop treating SharePoint like a playground for disposable widgets. If your code isn't modular and scalable, you’re just building technical debt. It’s time to master Library Components and build architecture that actually lasts. 🛠️ Get to work. #SPFx #SharePointDev #SoftwareArchitecture 🚀

    bdking71.wordpress.com/2026/06

  50. Stop treating SharePoint like a playground for disposable widgets. If your code isn't modular and scalable, you’re just building technical debt. It’s time to master Library Components and build architecture that actually lasts. 🛠️ Get to work. #SPFx #SharePointDev #SoftwareArchitecture 🚀

    bdking71.wordpress.com/2026/06

  51. Stop treating SharePoint like a playground for disposable widgets. If your code isn't modular and scalable, you’re just building technical debt. It’s time to master Library Components and build architecture that actually lasts. 🛠️ Get to work. #SPFx #SharePointDev #SoftwareArchitecture 🚀

    bdking71.wordpress.com/2026/06

  52. Stop treating SharePoint like a playground for disposable widgets. If your code isn't modular and scalable, you’re just building technical debt. It’s time to master Library Components and build architecture that actually lasts. 🛠️ Get to work. #SPFx #SharePointDev #SoftwareArchitecture 🚀

    bdking71.wordpress.com/2026/06

  53. Stop treating SharePoint like a playground for disposable widgets. If your code isn't modular and scalable, you’re just building technical debt. It’s time to master Library Components and build architecture that actually lasts. 🛠️ Get to work. #SPFx #SharePointDev #SoftwareArchitecture 🚀

    bdking71.wordpress.com/2026/06

  54. Most teams ask the wrong question about AI deployment. 🤖 Instead of obsessing over SOTA benchmarks, we need to ask: what’s actually good enough for the task?

    Part 1 of our series breaks down the architecture driving pragmatic choices. It’s the map for everything ahead. Don’t get lost in feature bloat.

    Read the full analysis: post.kapualabs.com/p4tycsm7

    #ArtificialIntelligence #EnterpriseAI #SoftwareArchitecture

  55. “Any fool can know. The point is to understand.” – Albert Einstein

    Memorizing frameworks, APIs, or design patterns is useful, but understanding the underlying principles creates lasting value. Engineers who understand trade-offs can adapt when technologies change. Knowledge ages; understanding scales.

    💬 Where has understanding fundamentals helped you more than specific tools?

    #DevThinking #ContinuousImprovement #SoftwareArchitecture #DevGrowth

    Photo by Daria Nepriakhina on Unsplash

  56. “Any fool can know. The point is to understand.” – Albert Einstein

    Memorizing frameworks, APIs, or design patterns is useful, but understanding the underlying principles creates lasting value. Engineers who understand trade-offs can adapt when technologies change. Knowledge ages; understanding scales.

    💬 Where has understanding fundamentals helped you more than specific tools?

    #DevThinking #ContinuousImprovement #SoftwareArchitecture #DevGrowth

    Photo by Daria Nepriakhina on Unsplash

  57. “Any fool can know. The point is to understand.” – Albert Einstein

    Memorizing frameworks, APIs, or design patterns is useful, but understanding the underlying principles creates lasting value. Engineers who understand trade-offs can adapt when technologies change. Knowledge ages; understanding scales.

    💬 Where has understanding fundamentals helped you more than specific tools?

    #DevThinking #ContinuousImprovement #SoftwareArchitecture #DevGrowth

    Photo by Daria Nepriakhina on Unsplash

  58. “Any fool can know. The point is to understand.” – Albert Einstein

    Memorizing frameworks, APIs, or design patterns is useful, but understanding the underlying principles creates lasting value. Engineers who understand trade-offs can adapt when technologies change. Knowledge ages; understanding scales.

    💬 Where has understanding fundamentals helped you more than specific tools?

    #DevThinking #ContinuousImprovement #SoftwareArchitecture #DevGrowth

    Photo by Daria Nepriakhina on Unsplash

  59. 🎉 The BaselOne 2026 Program is taking shape!

    Our Program Committee has selected a fantastic lineup of international experts covering #SoftwareArchitecture, #Java, #cloud, #AI, #Security, #DevOps and more.

    Curious who’s taking the stage in Basel this October?

    👉 baselone.org/en/baselone-2026-

    Which speaker are you looking forward to most?

    🎟️ Regular tickets are available now!

    See you at the Markthalle Basel on 14-15 October 2026.

    #BaselOne26 #Basel #softwareEngineering

  60. 🎉 The BaselOne 2026 Program is taking shape!

    Our Program Committee has selected a fantastic lineup of international experts covering #SoftwareArchitecture, #Java, #cloud, #AI, #Security, #DevOps and more.

    Curious who’s taking the stage in Basel this October?

    👉 baselone.org/en/baselone-2026-

    Which speaker are you looking forward to most?

    🎟️ Regular tickets are available now!

    See you at the Markthalle Basel on 14-15 October 2026.

    #BaselOne26 #Basel #softwareEngineering