| 18 May 2025 |
 commiterate | AWS also doesn't really use these kind of local mocks much internally. Integration + E2E test suites on real infrastructure is always used instead. | 19:46:54 |
| 19 May 2025 |
 Arian | AKA I should come up with a fix myself :D | 08:57:12 |
| commiterate | basically. As usual per open source, if you want something done you have to do it yourself | 16:44:10 |
| commiterate | * basically. As usual in open source, if you want something done you have to do it yourself | 17:07:47 |
| commiterate | * Most AWS teams are fairly small (maybe 5-10 people) and there's generally no distinction between engineering, QA, and devops/SRE. It's just "software development engineers" (SDEs) who handle all 3 functions which they can get away with because the internal tooling is, IMO, very well done and generally pushes for better designs since you have to consider both the operational burden and testing aspects in designs.
Each organization is basically a big ensemble of a bunch of small teams (e.g. control plane team, data plane team, frontend team for AWS console stuff) as the leaves which roll up into a reporting tree.
That means most teams are actually pretty lean and don't have much extra capacity for other stuff. More important areas like the AWS CLI + SDKs or AWS CDK will have additional dedicated resources beyond SDEs to handle a lot of customer interactions (e.g. support engineers, solutions architects).
As a result, they rely heavily on community contributions with AWS SDEs mostly acting as reviewers. | 17:18:37 |
| 24 May 2025 |
|  fromtheeast710 joined the room. | 05:10:18 |
| 26 May 2025 |
|  @xengi42:matrix.org joined the room. | 08:13:00 |
| 27 May 2025 |
|  matrixrooms.info mod bot (does NOT read/send messages and/or invites; used for checking reported rooms) joined the room. | 15:50:06 |
| 1 Jun 2025 |
|  Sean Thawe joined the room. | 23:48:47 |
