Assignment, Pair vs Solo Programming

saas.txt

I truly enjoyed the assignment as it immediately layed down the foundational rules for modern software development. 
TDD before production! Red-Green-Refactor! Also enjoying the steady increase in pace and technical knowledge, 
and how the assignment brought the knowledge (lectures) to bear. If it's not obvious, I like that the assignment was "practical"
and not theoretical alone.

Pair programming is done frequently in my time and I don't like it. It makes me uncomfortable. But I see it's value. We are using scrum
and given I have a low attention to detail and can possibly rabbit hole, having pair programming at points where I hit stumblingblocks
has proven rather helpful, allowing to move what is blocking the pathway.

Solo programming is what I do best, but over the past year I've come to realise how dangerous that is.
It comes back to verification and validation. Did I build the thing right? (If it works, doesn't mean it's right). 
Did I build the right thing? Oh look the customer changed their mind. An immature solo developer is prone to not 
delivering or going out of budget and having an extra pair of eyes helps maintain focus and accountability.
Darn it, I'm going to say it, a TEAM is better than ONE.