Even software engineers now have to think about the proactive steps they can make to limit the impact of a possible layoff.
> subscribe shift-mag --latest
Sarcastic newsletter headline, but funny enough for developers to sign up for it
Regular digest of our best engineering content for engineers.
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
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.