1. X
  2. InfoQ
Log inSign up
InfoQ
55.6K posts
Image
user avatar
InfoQ
@InfoQ
Helping dev teams adopt new technologies and practices for 20+ years. Written by software engineers. Read by over 1.5 m devs worldwide. linktr.ee/infoq
infoq.com
Joined March 2008
1,414
Following
57.5K
Followers
RepliesRepliesMediaMedia

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
  • user avatar
    InfoQ
    @InfoQ
    2h
    The jump from senior engineer to technical leader is one of the least-supported transitions in software. InfoQ's Engineering Leadership cohort is built around it, facilitated by Michelle Brush, Engineering Director for SRE at Google. Starts Aug 21:
    Image
    Online Engineering Leadership Cohort with Michelle Brush | InfoQ
    From certification.qconferences.com
    303
  • user avatar
    InfoQ
    @InfoQ
    3h
    #VirtualThreads changed in JDK 24 & 25. JEP 491 fixes monitor pinning, but bottlenecks now shift to connection pools, rate limiters, and ThreadLocal caches. Learn what to audit before adopting them, backed by a public benchmark ➤ bit.ly/3RrpLgB #Java #JDK25 #JEPs
    Image
    466
  • user avatar
    InfoQ
    @InfoQ
    4h
    #TanStackTable V9 is now in beta. The headless table library introduces improved state management, lower memory usage, better extensibility, and an opt-in feature model, so developers only load the functionality they need. 🔗 Read more: bit.ly/4vVkDiL #WebDev #InfoQ
    Image
    617
  • user avatar
    InfoQ
    @InfoQ
    9h
    Ever wonder why PDF generation still feels like it's stuck in 2005? Legacy document generation is slow, tough to scale & painful to maintain. Learn how #RustLang + #Typst can deliver a 10× faster, version-controlled PDF workflow. 🔗 Watch now: bit.ly/4vAPCBj #InfoQ
    Image
    835
  • user avatar
    InfoQ
    @InfoQ
    12h
    Microsoft has published a reference architecture for routing AI agent traffic on Azure Kubernetes Service. The architecture focuses on 3 key decisions: 1️⃣ Which model answers a call 2️⃣ How the call is managed 3️⃣ Which GPU replica handles it 🔗 bit.ly/3Tkqlxj #InfoQ
    Image
    1.1K
  • See @InfoQ's full profile

    Sign up
    Log in
Advertisement
Advertisement