Inis dom faoi thréimhse amháin inar bhreathnaigh tú ar do chur chuige a ghlacadh ag do fhoireann.

Question

Accepted Answer

Déanann sé seo tástáil ar **bhreithniú theicniúil**: an féidir leat cás a dhéanamh le fianaise agus daoine a bhreacadh ar do thaobh, agus gan a bheith oscailte don bhéasa a bheith mícheart? Ní bhreathniú a bhaint an bhreithniú.

## Conas é a bhualadh

```text
1. State the problem and the criteria for a good solution first
2. Present options fairly, including the team's preferred one
3. Back your choice with data, a spike, or a small benchmark
4. Invite critique — adjust if they find a real flaw
```

## Sampla oibrithe

```text
S: The team planned to build a custom job queue; I thought we should use an
   existing tool.
T: I had to make the case without dismissing their work.
A: I listed our actual requirements, built a one-day spike with the off-the-shelf
   tool, and showed it met every need with far less code to maintain.
R: The team agreed, and we shipped two weeks earlier. I noted the one case where
   their concern was valid and we documented the workaround.
```

## Maith vs lag

```text
✓ Evidence + fair comparison + open to critique
✗ "I argued until they gave up"
✗ Pushing your idea with no proof
```

## Cén fáth go bhfuil sé tábhachtach

Téann gealltanais ar an gcuid ar bhreithniúcháin maithe; níl dada athruithe ag smaoineamh breá nach nglacann duine ar bith air.

An tosú le critéir agus fianaise a choinníonn an fócas ar an toradh is fearr, ní ar cé an smaoineamh a bhuann.

A bheith oscailte i ndáiríre don bhéasa a bheith mícheart is é atá ann a chuireann daoine muinín i do bharúlacha an chéad uair eile.