Skene
Product
Pricing
Docs
Blog
About
Log In
ProductPricingDocsBlogAbout
Log In
Resources / Glossary

Side effect

Code that affects something outside the function it lives in. Analytics calls are side effects. So are logs, emails, and metric increments.

Coding agents

About this term

This page is part of the Skene analytics instrumentation glossary. Use it as a reference when writing specs, dashboards, or playbooks.

Canonical glossary index: /resources/glossary

Glossary

Glossary

Analytics callEvent namePayload (event properties)Identify callEvent taxonomyInstrumentation surfaceBaseline manifestInstrumentation driftSemantic diffRemoved eventRenamed eventMoved eventAltered payloadConditional firing changeCustomer Data Platform (CDP)Schema registryMCP (Model Context Protocol)Coding agentSide effectFunnelConversion eventActivation eventCohort

Definition

In programming, a side effect is any code that changes state outside its local scope. Writing to a database is a side effect. Calling an external API is a side effect. Emitting an analytics event is a side effect.

Why side effects matter here

When an AI agent refactors a function, it reasons about the function's inputs, outputs, and logic. The side effects in the middle are not part of that reasoning. They can be moved, dropped, or modified without breaking the function's contract - and so they often are.

Related terms

  • Coding agent
  • Analytics call
Skene

Product

How it worksFeaturesArchitectureIntegrationsSecurityPricing

Resources

DocumentationGlossaryPlaybooksBlog

Company

AboutOpen sourceContactPrivacyTerms
© 2026 Skene. All rights reserved.
Privacy PolicyTerms of Service
Skene