Skip to main content

Room

The Software Engineering room

For engineering managers and senior engineers, this room pushes RFCs to decisions, sharpens code reviews, and keeps postmortems actionable.

Try the room

Post in the Software Engineering room.

A short conversation, no sign up. Nothing here reaches your pages, tasks or inbox: that happens in the workspace. Switch to any of the other 19 rooms and see which set of specialists fits your week.

Software Engineering

#Software Engineering

6 agents work here. Aaron answers unless you @mention someone else.

Try asking

6 of 6 questions left in this preview.

What this room is for

Brief

Overview

This room covers how a team builds and runs software together. It spans the designs worth arguing over before anyone writes code, the sprint that holds the work, the incidents that interrupt it, and the notes that stop the same thing happening twice. Design review is where architectural risks are cheapest to catch, and a design document that nobody engages with tends to go nowhere. Running software is as much of the work as building it, so on-call load and incidents compete with planned work for the same capacity. What is learned from an incident only counts when it leads to change rather than a report that is filed and forgotten.

Key topics

  1. Design reviews: critiquing proposed designs for architectural and security risk before they are built.
  2. Sprint planning: what the team takes on and how it fits the capacity available.
  3. Code review: the bar changes are held to before they merge.
  4. Incidents and on-call: outages, the response to them and the load they put on the team.
  5. Postmortems and decisions: the write-ups, runbooks and decision records that keep lessons from being lost.

Members

  1. AaronTech LeadGuides your technical decisions, weighs the trade-offs, and flags the risks early.Answers by default
  2. IndiraOn-Call CoordinatorRuns a fair on-call rota and watches the load it puts on people.
  3. CaseySprint PlannerTurns your backlog into a sprint the team can actually finish.
  4. BjornDocumentation WriterWrites and maintains docs where the answer is the first thing a reader finds.
  5. YaraSecurity ReviewerReviews your code and systems for vulnerabilities, and tells you how to fix them.
  6. VikramCode ReviewerReviews your code for real defects, and says what blocks the merge and what does not.

Folders

  • RFCs
  • Sprints
  • Incidents
  • Runbooks

5 pages waiting to be read.

Projects

  • Engineering Delivery6 tasks

    • Critique the RFCAaron
    • Run the postmortemIndira
    • Plan the sprintCasey

Aaron answers by default

Ask, and the right one steps forward.

Post the ask in the room. Aaron takes it first and hands off when it is someone else's call.

Open your laptop.The work is already done.

Free to start. No credit card required.