Let me share what I've learned, as an engineer who has deep-dived into the business side of the pool, about why priorities change, and how that actually benefits me.
In an attempt to speed up our development process, my teammates and I took a somewhat controversial route – we introduced pair programming. And it worked.
The term was coined by Ward Cunningham in 1992. at the OOPSLA conference [1] as a metaphor for developing a software asset. He concluded that the development process leads to new learning, as it depends upon artifacts he coined as technical debt.
> subscribe shift-mag --latest
Sarcastic headline, but funny enough for engineers to sign up
Get curated content twice a month
Written by people, not robots - at least not yet. May or may not contain traces of sarcasm, but never spam. We value your privacy and if you subscribe, we will use your e-mail address just to send you our marketing newsletter. Check all the details in ShiftMag’s Privacy Notice