Disclaimer

This is one person's experience

Everything here is written by me, from what I have learned building on Salesforce. It reflects my own understanding at the time of writing — not a consensus, not an official position, and not the only reasonable way to do things.

I get things wrong sometimes. When I find out, I fix the article and say what changed rather than quietly editing it.

Written in a personal capacity

I work in this industry, which is the reason I have anything useful to say. It is also the reason this section exists.

This site is entirely personal. It is written on my own time, on my own equipment, and published on infrastructure I pay for myself. The views are mine alone and are not those of any employer, client, partner or customer, past or present. Nobody reviews, approves, sponsors or endorses what I publish here, and nothing here should be read as an official statement by any organization I have worked with.

Nothing published here is confidential or proprietary. I do not write about any employer's or client's systems, data, source code, architecture, customers, internal documentation, roadmaps or commercial arrangements. Everything I discuss is drawn from publicly available platform documentation, publicly released features, open-source code, and general professional experience of the kind any practitioner accumulates.

Where an article uses an example — an org shape, a data model, a failure, a code sample — it is constructed to illustrate the point. It is generic, or reconstructed, or invented outright. It is not a description of a real system belonging to anyone I have worked for, and any resemblance to one is a consequence of these problems being common across the industry, not of me describing a specific case.

No employer or client is named anywhere on this site, and that is deliberate.

Not advice

This is technical writing, not professional advice. It is not legal, financial, security, compliance or architectural advice for your organization, because I know nothing about your organization.

Before acting on anything here: read it critically, check it against the current official documentation, and test it in a sandbox. Your governor limits, your data volumes, your licensing, your integrations and your risk tolerance are not mine. A decision with real consequences deserves advice from someone who has actually looked at your situation.

Code comes with no warranty

Code samples are illustrations, not products. They are written to be readable rather than exhaustive, and they routinely leave out error handling, bulkification edge cases, security review and test coverage that production code needs.

Use them, adapt them, learn from them — and take responsibility for what you deploy. I am not liable for what happens when code from an article reaches a production org.

The open-source projects linked from here are separate, and each carries its own licence and its own warranty terms in its repository.

Things go out of date

Salesforce ships three releases a year and the AI tooling moves faster than that. An article is a snapshot of what was true when it was written. Check the publication date, and when it matters, check the official documentation before relying on any specific behavior, limit or API.

Trademarks and affiliation

Salesforce, Apex, Lightning Web Components, Agentforce, Experience Cloud and related marks are trademarks of Salesforce, Inc. Other names belong to their owners.

This site is not affiliated with, authorized by, endorsed by, or sponsored by Salesforce, Inc., or by any other company whose products are mentioned. I use their names to describe what I am writing about, which is the only honest way to write about a platform.

AI assistance

I use AI tooling in my own work, and I write about doing so. Where it helps produce something published here, the thinking, the technical judgement, the testing and the final text remain mine. I do not publish generated content I have not verified myself.

Sponsorship

There is none. No article on this site is paid for, sponsored, or written in exchange for anything, and there are no affiliate links. If that ever changes, it will be disclosed clearly on the article itself, not buried on this page.

External links

Links point at documentation, repositories and other people's writing because they are worth reading. I do not control them and cannot vouch for what they say tomorrow.

Questions

If something here reads as though it crosses a line, tell me — ansukhetskyi@gmail.com — and I will look at it properly.