Right now at work I’m the lead on a project to establish a new vendor API. Unfortunately there were decisions made on key specifications of how the API was to be developed before it was handed to me. Where I work there is a lot of legacy standards and so it’s challenging to introduce new technologies as a standard. I do see that there is a constant struggle between what APIs are needed internally versus externally, for B2B integrations. I’m always looking to try to balance this out whenever I can.
A Christ-follower, husband, father, and WordPress Developer with Forum One.
As a developer and, in some areas, a perfectionist I’m always after better #development practices when working collaboratively. An I personally find value in the #commit history. As a #git user I appreciate detailed case from @ecampidoglio on the proper way to keep a clean commit history. The Case for Pull Rebase
Why Talk To Other Sites? Ask them questions – Getting Data Tell them things – Process Requests. How is This Done? GET – wp_remote_get() POST – wp_remote_post() HEAD – wp_remote_head() Cache API Content WordPress Sites (/wp-json) – pull public WordPress site data