Engineer Explains: ERROR handling strategies every developer must know
We've asked experienced engineers to share how they would explain some tech terminology at three levels of experience - from junior developer to CTO.
Engineer Explains: What is DevRel, and why developers should care?
We've asked experienced engineers to share how they would explain some tech terminology at three levels of experience - from junior developer to CTO.
There’s probably no better person to ask to explain Developer Relations than Mary Thengvall, the author of the first book on the matter, “The Business Value of Developer Relations.”
As Mary has already said for ShiftMag – DevRel is not something that people naturally understand. It’s part of the job for people who work in DevRel to explain to developers and their other colleagues the value of their job and that they’re not just “people who travel to a lot of conferences.”
Watch the video to hear how Thengvall explained the value of DevRel at three levels, from a junior developer to a CTO:
This video is a part of ShiftMag’s video series, Engineer Explains.
We’ve asked experienced engineers to share how they would explain some basic and some less basic tech terminology to different tech job titles or at three levels of experience — from junior developer to CTO.
More:
How would you explain APIs, internal developer platforms, software architecture, software testing, scaling infrastructure without breaking the bank, low-code as a dev tool, what is a database or Network APIs at three levels of experience?
