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.
Engineer Explains: Network as Code in under 3 minutes
We've asked experienced engineers to share how they would explain some tech terminology at three levels of experience - from junior developer to CTO.
“You are able to pick up an API, and in 10 to 15 minutes, you can already tell a network to give you better quality of service, to create a dedicated network for you, check the location of a device, or to check if a SIM has been swapped by a hacker”.
That’s what Network as Code does – it abstracts all the complexity of a network API for developers, automates all the mundane work, and exposes the good stuff.
Navigating the network for 5G or Industry 4.0 applications no longer requires developers to understand network technical details deeply. With Network as Code, developers can easily access and integrate network capabilities without ever touching the underlying complexities.
As Nokia’s Akin Akintola explains, junior developers can now focus on what they do best instead of diving deep into network technology; senior developers can geek out and look at the same APIs in up to 26 languages. CTOs, of course, can let their teams focus on creating features and products for their users instead of re-engineering and spending a lot of resources to compensate for a network’s deficiencies.
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 or what is a database at three levels of experience?
