Piotr Kliczewski

[Ashesh Badani @asheshbadani]

With over 1 million VMs reviewed and 400,000 migrated, the momentum is real. We are helping our customers take control of their future by unifying virtualization and cloud-native containers on a single, open platform. Learn how we can help you modernize: https://t.co/u5ZRWkynOs.

[Andrew Ng @AndrewYNg]

AI-native software engineering teams operate very differently than traditional teams. The obvious difference is that AI-native teams use coding agents to build products much faster, but this leads to many other changes in how we operate. For example, some great engineers now play broader roles than just writing code. They are partly product managers, designers, sometimes marketers. Further, small teams who work in the same office, where they can communicate face-to-face, can move incredibly quickly.

Because we can now build fast, a greater fraction of time must be spent deciding what to build. To deal with this project-management bottleneck, some teams are pushing engineer:product manager (PM) some teams are pushing engineer:product manager (PM) ratios downward from, say, 8:1 to as low as 1:1. But we can do even better: If we have one PM who decides what to build and one engineer who builds it, the communication between them becomes a bottleneck. This is why the fastest-moving teams I see tend to have engineers who know how to do some product work (and, optionally, some PMs who know how to do some engineering work). When an engineer understands users and can make decisions on what to build and build it directly, they can execute incredibly quickly.

I’ve seen engineers successfully expand their roles to including making product decisions, and PMs expand their roles to building software. The tech industry has more engineers than PMs, but both are promising paths. If you are an engineer, you’ll find it useful to learn some product management skills, and if you’re a PM, please learn to build!

Looking beyond the product-management bottleneck, I also see bottlenecks in design, marketing, legal compliance, and much more. When we speed up coding 10x or 100x, everything else becomes slow in comparison. For example, some of my teams have built great features so quickly that the marketing organization was left scrambling to figure out how to communicate them to users — a marketing bottleneck. Or when a team can build software in a day that the legal department needs a week to review, that’s a legal compliance bottleneck. In this way, agentic coding isn’t just changing the workflow of software engineering, it’s also changing all the teams around it.

When smaller, AI-enabled teams can get more done, generalists excel. Traditional companies need to pull together people from many specialties — engineering, product management, design, marketing, legal, etc. — to execute projects and create value. This has resulted in large teams of specialists who work together. But if a team of 2 persons is to get work done that require 5 different specialities, then some of those individuals must play roles outside a single speciality. In some small teams, individuals do have deep specializations. For example, one might be a great engineer and another a great PM. But they also understand the other key functions needed to move a project forward, and can jump into thinking through other kinds of problems as needed. Of course, proficiency with AI tools is a big help, since it helps us to think through problems that involve different roles.

Even in a two-person team, to move fast, communication bottlenecks also must be minimized. This is why I value teams that work in the same location. Remote teams can perform well too, but the highest speed is achieved by having everyone in the room, able to communicate instantaneously to solve problems.

This post focuses on AI-native teams with around 2-10 persons, but not everything can be done by a small team. I'll address the coordination of larger teams in the future.

I realize these shifts to job roles are tough to navigate for many people. At the same time, I am encouraged that individuals and small teams who are willing to learn the relevant skills are now able to get far more done than was possible before. This is the golden age of learning and building!

[Original text: https://t.co/1pUxNC5UXk ]

[Itamar Heim @itamarheim]

Happy to showcase all our work with partners around AI! https://t.co/GHDXIAuNw4

[FOSDEM @[email protected] @fosdem]

https://t.co/9kAeF0EpXX

[Piotr Kliczewski @pkliczewski]

Reminder about call for participation for Virtualization and Cloud infrastructure devroom at FOSDEM

you can submit your proposals here https://t.co/f0Wdw1ABlc.

#virtualization #cloud

[Piotr Kliczewski @pkliczewski]

Virtualization and Cloud infrastructure devroom at FOSDEM has been accepted and you can submit your proposals here https://t.co/f0Wdw1ABlc. Any topics related to @ovirt @OpenStack @CloudStack KVM qemu @kubevirt OpenNebula Libvirt XEN are welcome.

[KubeVirt @kubevirt]

My my my, how the year has flown. KubeVirt Summit is now less than one week away!

Join us for this fantastic virtual event on June 24 & 25 for 10 hours of talks about all things KubeVirt.

Full schedule and (free) registration:
https://t.co/Cax1bPVwvD

[KubeVirt @kubevirt]

KubeVirt Summit, June 24-25

Registration now open:
https://t.co/Cax1bPVwvD

[KubeVirt @kubevirt]

Huzzah! The CfP for KubeVirt Summit 2024 is open!
If you work on KubeVirt, use KubeVirt, or have an interesting journey into the world of KubeVirt, we want to see your submission.
Check out our blog for all the details: https://t.co/XY7sJFcoZE

[FOSDEM @[email protected] @fosdem]

https://t.co/KYThbcGTj1

[FOSDEM @[email protected] @fosdem]

Presentations - Call for Participation https://t.co/Mha6ZOhYuC

[FOSDEM @[email protected] @fosdem]

Accepted stands for FOSDEM 2024 https://t.co/54s2iJWb6w

[Piotr Kliczewski @pkliczewski]

Virtualization and Cloud infrastructure devroom @fosdem has been accepted and call for participation was announced here https://t.co/p6D5ns0gCO. Please submit your talks about oVirt OpenStack CloudStack KVM qemu KubeVirt OpenNebula Libvirt XEN etc.

[FOSDEM @[email protected] @fosdem]

Accepted developer rooms https://t.co/LOfs7MbRh7

[FOSDEM @[email protected] @fosdem]

FOSDEM 2023 call for devrooms https://t.co/ecN6xFdtbX

[project-flotta @project_flotta]

Would you like to know how to monitor power consumption on the edge. Here you can find more details how to do it: https://t.co/hq08hSSTA9

#EdgeComputing #gsoc

[project-flotta @project_flotta]

Would you like to know how to use ML on the edge? Here is the summary of awesome work done by @singhdpy https://t.co/gPJkdPI5gC and here is the demo: https://t.co/eg2nsdpqPH

#EdgeComputing #MachineLearning #gsoc

[Piotr Kliczewski @pkliczewski]

@MSzynkiewicz Good luck!

[project-flotta @project_flotta]

Here you will find details on how to use flotta pipelines to build edge images: https://t.co/bQoOSNiigh

#Edge #EdgeComputing

[project-flotta @project_flotta]

Did you know how easy it is to use flotta cli? Here is how to use it: https://t.co/jYgCK4Ja9U

#Edge #EdgeComputing