InfoQ - Ask an editor

QCon London 2023

Session

InfoQ - Ask an editor

Tuesday Mar 28 / 04:10PM BST, Windsor (5th Fl.)

Abstract

An informal session for InfoQ editors and QCon attendees to connect, ask questions, and share ideas.

  • Do you have any questions about InfoQ? 
  • Would you like to meet the InfoQ editors attending QCon London 2023?
  • Do you have ideas to improve InfoQ?
  • Are you passionate about innovative technologies and want to contribute?

Then this session is for you!

InfoQ has been helping software development teams adopt new technologies and practices for over 17 years. Senior software developers rely on QCon and InfoQ to keep ahead of the adoption curve. One of the main reasons senior software engineers, software architects, and team leads tell us they keep coming back to QCon and InfoQ is because they trust the information provided and selected by their peers.

76% senior dev or higher
1:11 speaker ratio
60+ practitioners

QCon London 2023 is a three day conference for senior software engineers, architects and team leads. An international program committee of working engineers selects every session. Patterns and practices, not products and pitches.

Share

From the same track

Tuesday 28 March

10:35 Westminster (4th Fl.) Sponsored Streaming Events? You Should Be Storing Them Yves Lorphelin, Matt Macchia 11:50 Westminster (4th Fl.) Sponsored ChatGPT is Fun, but the Future is Fully Autonomous AI for Code Mathew Lodge CEO @Diffblue 13:40 Westminster (4th Fl.) Sponsored How ING Accelerated Kubernetes Deployments Across 500+ Applications: Challenges & Lessons Learned Wouter Ligtenberg Sr. Engineering Manager @ING Hubs Romania 14:55 Mountbatten (6th Fl.) Sponsored Pipeline Patterns for Platform Teams Zan Markan Senior Developer advocate @CircleCi 16:10 Windsor (5th Fl.) Session InfoQ - Ask an editor Daniel Bryant Platform Engineer, Co-Author of "Mastering API Architecture", Java Champion, and InfoQ News Manager 17:25 Churchill (Ground Fl.) Sponsored It's time to talk about your Big Code problem! Mark McCauley Field CTO @Sourcegraph