home.social

Search

1000 results for “infoq”

  1. The real consequential decisions in engineering aren't made in sprint planning. They're hidden in the 'invisible choices': metrics, defaults & everyday behaviors.

    The industry is focused on the wrong things. The choices that truly shape systems & culture are the ones that go unnoticed and unexamined.

    Read the full insights: bit.ly/43Ajl1y

    #InfoQ #QConSF #ADRs #TechLeadership #Culture

  2. The real consequential decisions in engineering aren't made in sprint planning. They're hidden in the 'invisible choices': metrics, defaults & everyday behaviors.

    The industry is focused on the wrong things. The choices that truly shape systems & culture are the ones that go unnoticed and unexamined.

    Read the full insights: bit.ly/43Ajl1y

    #InfoQ #QConSF #ADRs #TechLeadership #Culture

  3. The real consequential decisions in engineering aren't made in sprint planning. They're hidden in the 'invisible choices': metrics, defaults & everyday behaviors.

    The industry is focused on the wrong things. The choices that truly shape systems & culture are the ones that go unnoticed and unexamined.

    Read the full insights: bit.ly/43Ajl1y

    #InfoQ #QConSF #ADRs #TechLeadership #Culture

  4. The real consequential decisions in engineering aren't made in sprint planning. They're hidden in the 'invisible choices': metrics, defaults & everyday behaviors.

    The industry is focused on the wrong things. The choices that truly shape systems & culture are the ones that go unnoticed and unexamined.

    Read the full insights: bit.ly/43Ajl1y

    #InfoQ #QConSF #ADRs #TechLeadership #Culture

  5. The real consequential decisions in engineering aren't made in sprint planning. They're hidden in the 'invisible choices': metrics, defaults & everyday behaviors.

    The industry is focused on the wrong things. The choices that truly shape systems & culture are the ones that go unnoticed and unexamined.

    Read the full insights: bit.ly/43Ajl1y

  6. #AWS has released an analysis of the major October outage, highlighting key lessons on:
    ⇨ cloud redundancy
    ⇨ multi-region architectures
    ⇨ considerations for moving workloads out of the public cloud

    Triggered by a failure in Amazon #DynamoDB, the outage affected a wide range of services in its busiest region, Northern Virginia.

    Learn more: bit.ly/4raUs6E

    #InfoQ #CloudComputing

  7. #AWS has released an analysis of the major October outage, highlighting key lessons on:
    ⇨ cloud redundancy
    ⇨ multi-region architectures
    ⇨ considerations for moving workloads out of the public cloud

    Triggered by a failure in Amazon #DynamoDB, the outage affected a wide range of services in its busiest region, Northern Virginia.

    Learn more: bit.ly/4raUs6E

    #InfoQ #CloudComputing

  8. #AWS has released an analysis of the major October outage, highlighting key lessons on:
    ⇨ cloud redundancy
    ⇨ multi-region architectures
    ⇨ considerations for moving workloads out of the public cloud

    Triggered by a failure in Amazon #DynamoDB, the outage affected a wide range of services in its busiest region, Northern Virginia.

    Learn more: bit.ly/4raUs6E

    #InfoQ #CloudComputing

  9. #AWS has released an analysis of the major October outage, highlighting key lessons on:
    ⇨ cloud redundancy
    ⇨ multi-region architectures
    ⇨ considerations for moving workloads out of the public cloud

    Triggered by a failure in Amazon #DynamoDB, the outage affected a wide range of services in its busiest region, Northern Virginia.

    Learn more: bit.ly/4raUs6E

    #InfoQ #CloudComputing

  10. has released an analysis of the major October outage, highlighting key lessons on:
    ⇨ cloud redundancy
    ⇨ multi-region architectures
    ⇨ considerations for moving workloads out of the public cloud

    Triggered by a failure in Amazon , the outage affected a wide range of services in its busiest region, Northern Virginia.

    Learn more: bit.ly/4raUs6E

  11. Code that drifts and projects that fail often aren’t technical failures - they’re organizational ones.

    Introducing #HolisticEngineering ⇨ the practice of designing technology by understanding and shaping all the intrinsic parts of the organic system.

    A holistic approach views projects as Organic #SocioTechnicalSystems, influenced by:
    ⇨ External forces: world events, tech trends, market shifts
    ⇨ Internal forces: organization, product, people, engineering

    Read the #InfoQ article by Vanessa Formicola to learn how to master this approach: bit.ly/43Ed7O1

    #SoftwareArchitecture #SociotechnicalArchitecture #Agile

  12. Code that drifts and projects that fail often aren’t technical failures - they’re organizational ones.

    Introducing #HolisticEngineering ⇨ the practice of designing technology by understanding and shaping all the intrinsic parts of the organic system.

    A holistic approach views projects as Organic #SocioTechnicalSystems, influenced by:
    ⇨ External forces: world events, tech trends, market shifts
    ⇨ Internal forces: organization, product, people, engineering

    Read the #InfoQ article by Vanessa Formicola to learn how to master this approach: bit.ly/43Ed7O1

    #SoftwareArchitecture #SociotechnicalArchitecture #Agile

  13. Code that drifts and projects that fail often aren’t technical failures - they’re organizational ones.

    Introducing #HolisticEngineering ⇨ the practice of designing technology by understanding and shaping all the intrinsic parts of the organic system.

    A holistic approach views projects as Organic #SocioTechnicalSystems, influenced by:
    ⇨ External forces: world events, tech trends, market shifts
    ⇨ Internal forces: organization, product, people, engineering

    Read the #InfoQ article by Vanessa Formicola to learn how to master this approach: bit.ly/43Ed7O1

    #SoftwareArchitecture #SociotechnicalArchitecture #Agile

  14. Code that drifts and projects that fail often aren’t technical failures - they’re organizational ones.

    Introducing #HolisticEngineering ⇨ the practice of designing technology by understanding and shaping all the intrinsic parts of the organic system.

    A holistic approach views projects as Organic #SocioTechnicalSystems, influenced by:
    ⇨ External forces: world events, tech trends, market shifts
    ⇨ Internal forces: organization, product, people, engineering

    Read the #InfoQ article by Vanessa Formicola to learn how to master this approach: bit.ly/43Ed7O1

    #SoftwareArchitecture #SociotechnicalArchitecture #Agile

  15. Code that drifts and projects that fail often aren’t technical failures - they’re organizational ones.

    Introducing ⇨ the practice of designing technology by understanding and shaping all the intrinsic parts of the organic system.

    A holistic approach views projects as Organic , influenced by:
    ⇨ External forces: world events, tech trends, market shifts
    ⇨ Internal forces: organization, product, people, engineering

    Read the article by Vanessa Formicola to learn how to master this approach: bit.ly/43Ed7O1

  16. #DomainDrivenDesign (DDD) elevates sociotechnical design.

    Change Smuggling offers a pathway: launch small, safe-to-fail probes to nudge change organically.

    📝 Great interview with Xin Yao on DDD & Change Smuggling on #InfoQ!

    👉 Read now: bit.ly/449nx8x

    #SociotechnicalArchitecture #Agile #InfoQ

  17. #DomainDrivenDesign (DDD) elevates sociotechnical design.

    Change Smuggling offers a pathway: launch small, safe-to-fail probes to nudge change organically.

    📝 Great interview with Xin Yao on DDD & Change Smuggling on #InfoQ!

    👉 Read now: bit.ly/449nx8x

    #SociotechnicalArchitecture #Agile #InfoQ

  18. #DomainDrivenDesign (DDD) elevates sociotechnical design.

    Change Smuggling offers a pathway: launch small, safe-to-fail probes to nudge change organically.

    📝 Great interview with Xin Yao on DDD & Change Smuggling on #InfoQ!

    👉 Read now: bit.ly/449nx8x

    #SociotechnicalArchitecture #Agile #InfoQ

  19. #DomainDrivenDesign (DDD) elevates sociotechnical design.

    Change Smuggling offers a pathway: launch small, safe-to-fail probes to nudge change organically.

    📝 Great interview with Xin Yao on DDD & Change Smuggling on #InfoQ!

    👉 Read now: bit.ly/449nx8x

    #SociotechnicalArchitecture #Agile #InfoQ

  20. (DDD) elevates sociotechnical design.

    Change Smuggling offers a pathway: launch small, safe-to-fail probes to nudge change organically.

    📝 Great interview with Xin Yao on DDD & Change Smuggling on !

    👉 Read now: bit.ly/449nx8x

  21. Tired of stress & burnout dragging down your engineering performance? This #InfoQ video is for you!

    Holly Cummins & Trisha Gee bust the biggest myths of Developer Productivity: activity metrics like lines of code, commit counts, and constant “busy-ness” actually destroy business value.

    Learn how “Developer Joy” & strategic “Boredom” can unlock 31% higher efficiency and massive engineering throughput.

    🎥 Watch now: bit.ly/3XxMNBD

    #EngineeringLeadership #DevEx #Productivity #TechCulture #TechCareer

  22. Unlock precision in GenAI by moving beyond traditional #RAG#AgenticRAG.

    In this #InfoQ video, Adi Polak dives into Agentic RAG architectures, emergent agent design patterns, and the crucial feedback loops (including LLM-as-a-judge) that drive continuous refinement.

    ▶️ Watch now: bit.ly/481f4FD

    📄 #transcript included

    #RetrievalAugmentedGeneration #AI #SoftwareArchitecture #GenAI

  23. #ReverseProxies live at the busiest, most fragile point in modern infrastructure.

    ⇨The real lessons❓ Hidden costs, mundane failures, human factors at scale.
    ⇨ The solutions❓ Keep the common path lean. Validate assumptions. Design for humans under stress. Aim for both resilient & boring - the ideal state for any production system.

    🔗 Read the #InfoQ article by Mitendra Mahto: bit.ly/4nZJTR3

    #DevOps #Performance #Scalability #LoadBalancing

  24. Busy week in the #OpenJDK ecosystem! Check out the key updates:
    • 3 JEPs elevated to Targeted: JEP 529, JEP 516, JEP 500
    • 3 JEPs elevated to Proposed to Target for JDK 26: JEP 530, JEP 526, JEP 524
    • The proposed release schedule for JDK 26 has also been finalized.

    Read the details here: 🔗 bit.ly/4oY0bKY

    #Java #JEP #JDK26 #InfoQ

  25. Busy week in the #OpenJDK ecosystem! Check out the key updates:
    • 3 JEPs elevated to Targeted: JEP 529, JEP 516, JEP 500
    • 3 JEPs elevated to Proposed to Target for JDK 26: JEP 530, JEP 526, JEP 524
    • The proposed release schedule for JDK 26 has also been finalized.

    Read the details here: 🔗 bit.ly/4oY0bKY

    #Java #JEP #JDK26 #InfoQ

  26. Busy week in the #OpenJDK ecosystem! Check out the key updates:
    • 3 JEPs elevated to Targeted: JEP 529, JEP 516, JEP 500
    • 3 JEPs elevated to Proposed to Target for JDK 26: JEP 530, JEP 526, JEP 524
    • The proposed release schedule for JDK 26 has also been finalized.

    Read the details here: 🔗 bit.ly/4oY0bKY

    #Java #JEP #JDK26 #InfoQ

  27. Busy week in the #OpenJDK ecosystem! Check out the key updates:
    • 3 JEPs elevated to Targeted: JEP 529, JEP 516, JEP 500
    • 3 JEPs elevated to Proposed to Target for JDK 26: JEP 530, JEP 526, JEP 524
    • The proposed release schedule for JDK 26 has also been finalized.

    Read the details here: 🔗 bit.ly/4oY0bKY

    #Java #JEP #JDK26 #InfoQ

  28. Busy week in the ecosystem! Check out the key updates:
    • 3 JEPs elevated to Targeted: JEP 529, JEP 516, JEP 500
    • 3 JEPs elevated to Proposed to Target for JDK 26: JEP 530, JEP 526, JEP 524
    • The proposed release schedule for JDK 26 has also been finalized.

    Read the details here: 🔗 bit.ly/4oY0bKY

  29. #GitHub introduces #AgentHQ - a new feature that enables devs to create & deploy #AIagents directly within GitHub’s development environment.

    The feature expands the company’s ongoing efforts to integrate AI into the software development lifecycle, building on previous Copilot releases.

    🔍 Learn more: bit.ly/4p33BMA

    #InfoQ #AI #LLMs

  30. #GitHub introduces #AgentHQ - a new feature that enables devs to create & deploy #AIagents directly within GitHub’s development environment.

    The feature expands the company’s ongoing efforts to integrate AI into the software development lifecycle, building on previous Copilot releases.

    🔍 Learn more: bit.ly/4p33BMA

    #InfoQ #AI #LLMs