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.
You're probably imagining the aforementioned mentor as a wise white-haired sensei one step away from retirement, but here's the kicker - it's a colleague 20 years my junior.
More than half of developers, 51%, said they mainly assemble code written by others, and 58% don’t feel that writing code from scratch will be required as part of their roles in the future, says Atlassian’s State of the Developer report.
Want to hear a first-hand recollection of on-call engineers' worst nightmare? Come to Infobip’s Shift conference in Miami to hear Paige Cruz of Chronosphere speak of ”the time that her deployment brought down production in a big way”.
Privacy isn’t a feature, or an afterthought once you've built and scaled everything. It should be a day 1 priority; privacy needs to be part of the culture of a company.