Browse by type

Explainer reads

Explainer posts on Yomu, summarised newest first.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Heroku
Retrospectives
Retrospectives are presented as a way for software engineering teams to review operational incidents, investigate root causes, create remediation tasks, and improve teamwork. Beyond technical review, the process can focus on emotional and human aspects of projects, including interactions and ways to work better together. The suggested timing includes post-incident or post-project sessions, mid-project course corrections, and weekly meetings; a 90-minute Friday session one week after a project ends is described as effective, while next-day and three-week delays are discouraged. An active, neutral facilitator should prepare an agenda and guest list, state a clear purpose, involve everyone, and use one or two activities such as a timeline, five whys, or Start Doing / Stop Doing / Keep Doing brainstorming.

Heroku
Using force.com from your Heroku apps
Force.com and Heroku, both part of the Salesforce1 platform, can be connected from Heroku applications through data synchronization or direct API access. Heroku Connect provides point-and-click, two-way synchronization between Force.com and the Postgres database attached to an app, allowing reads and writes in Postgres while changes are copied asynchronously; that latency makes it unsuitable when an immediate Force.com response is required. For synchronous access, open-source client libraries cover Force.com’s SOAP, REST, Streaming, Bulk, and Metadata APIs across languages including Java, Ruby, Node.js, PHP, Python, Objective-C, and Go. The article maps libraries and packages to supported APIs, including restforce and salesforce_bulk for Ruby, nforce for Node.js, simple-salesforce for Python, mobile SDKs, and ForceCLI for scripting SOAP and Metadata operations.

Weekly digest

The best engineering reads, once a week.

Browse by type

Explainer posts on Yomu, summarised newest first.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Heroku
Retrospectives
Retrospectives are presented as a way for software engineering teams to review operational incidents, investigate root causes, create remediation tasks, and improve teamwork. Beyond technical review, the process can focus on emotional and human aspects of projects, including interactions and ways to work better together. The suggested timing includes post-incident or post-project sessions, mid-project course corrections, and weekly meetings; a 90-minute Friday session one week after a project ends is described as effective, while next-day and three-week delays are discouraged. An active, neutral facilitator should prepare an agenda and guest list, state a clear purpose, involve everyone, and use one or two activities such as a timeline, five whys, or Start Doing / Stop Doing / Keep Doing brainstorming.

Heroku
Using force.com from your Heroku apps
Force.com and Heroku, both part of the Salesforce1 platform, can be connected from Heroku applications through data synchronization or direct API access. Heroku Connect provides point-and-click, two-way synchronization between Force.com and the Postgres database attached to an app, allowing reads and writes in Postgres while changes are copied asynchronously; that latency makes it unsuitable when an immediate Force.com response is required. For synchronous access, open-source client libraries cover Force.com’s SOAP, REST, Streaming, Bulk, and Metadata APIs across languages including Java, Ruby, Node.js, PHP, Python, Objective-C, and Go. The article maps libraries and packages to supported APIs, including restforce and salesforce_bulk for Ruby, nforce for Node.js, simple-salesforce for Python, mobile SDKs, and ForceCLI for scripting SOAP and Metadata operations.

The best engineering reads, once a week.