I'd be surprised if this topic hasn't been covered on HN in the past, if not I'm sure it'll show up one day. When your role is "non-technical" (not my favorite term but using it for clarity), UI, CMS, and dialogue menus seem like the best solution. Why wouldn't I want to just point and click?
But the day I learned how to run a GET request, parse data, save it somewhere, analyze it later; my outlook completely flipped. Whenever I google "[organization] api" and get 0 official results I become irrationally angry. All this to say, I hope they approach the topic before it becomes a hard requirement, because it's a fun and useful skill to have even outside of work.
I don't mind wrangling data in the CLI, and I have written a few scripts that do utilise some APIs, like a dynamic dns type script that runs on my home server and updates Netlify's DNS to point a list of subdomains to my home network, but I'm hesitant to build anything too complex for work because when I do leave, it'll all come tumbling down :)
I try to build our processes so that our non-tech HR/management department can keep everything running eventually. Spinning up a Docker image or deploying builds to a CI pipeline is a bit out of their job description and skill set hah.
aamoscodes|3 years ago
But the day I learned how to run a GET request, parse data, save it somewhere, analyze it later; my outlook completely flipped. Whenever I google "[organization] api" and get 0 official results I become irrationally angry. All this to say, I hope they approach the topic before it becomes a hard requirement, because it's a fun and useful skill to have even outside of work.
httpsterio|3 years ago
I try to build our processes so that our non-tech HR/management department can keep everything running eventually. Spinning up a Docker image or deploying builds to a CI pipeline is a bit out of their job description and skill set hah.