Application development is conducted like an orchestra

A score written before playing, sections with clear remits, a conductor holding the baton without playing an instrument: the metaphor structuring Maestro, embraced all the way to its logo.

Nine musicians, one baton: Maestro organises application development like an orchestral rehearsal. The score is written before playing, each agent holds a section with a clear remit, and the conductor, you, decides when the note is held. The metaphor extends to the logo: a fermata.

The score is written before playing

An orchestra does not discover a work by playing it: the score precedes performance and outlives the musicians. A directed project follows the same order: the brief, then requirements, then a breakdown into stages, each approved before construction begins. The resulting code is an interpretation; the score, your specification, remains. Musicians can change; the work can be performed again. This journal has explained elsewhere what that score is worth: your specification will outlive the tools performing it, ours as well as others.

Sections, never a soloist

A rehearsal holds together because everyone knows their part. At Maestro, Margaux scopes the need, Victor writes the specification, Maurice lays foundations, Amélie builds and Félix verifies with evidence. Constance reviews everything before construction; Marcel divides the work into playable movements, short enough to repeat until right. A narrowly defined section plays its line better than a soloist charged with the entire work: an agent entrusted with everything loses focus, forgets a constraint and covers the errors in its own part. Separating sections also makes work readable: you know who is playing and where the piece has reached.

The cadence: play, stop, resume

A rehearsal advances through cadences: a passage is played, the conductor stops it, corrections are made and playing resumes. Directed development follows this rhythm: each constructed stage is checked, each document stops before you and waits. Nothing runs itself from start to finish, deliberately: an orchestra playing the whole work without stopping would repeat all its mistakes too.

The fermata, our logo

In music, a fermata is the sign above a note that the conductor holds as long as they judge appropriate: the orchestra suspends its playing and awaits their gesture. We made it our logo because it states our central rule: at every stage, work stops and waits for your ‘Looks good to me’. The note lasts until you release it. No agent decides the next step for you. The gesture is the same for a brief, requirements document or constructed stage: nothing important passes without you.

The conductor plays no instrument

A conductor touches neither violin nor timpani during the concert; nobody concludes that they are not directing. They know the work, hear what sounds wrong and set the tempo, while the orchestra plays each instrument better than they do. Directing a product without coding takes the same position: you do not write code; you know what you want, recognise it when shown and make decisions. The baton cannot be delegated; everything else can. This whole journal develops that sentence: from idea to product, directed by you.