How to Build a Commission Attribution Engine in Google Sheets

·2 views

Commission disputes in sales teams are rarely caused by calculation errors — nearly 95% stem from payments being matched to the wrong sales rep in the first place. A key challenge is that buyers often check out using personal email aliases, Gmail dot variations, or unregistered addresses, making attribution unreliable. The proposed solution involves normalizing email addresses by stripping tags and Gmail-specific dots before attempting to match payments to rep accounts. Domain-based matching is also supported, but deliberately excludes free providers like Gmail and Outlook to prevent bulk misattribution. The system returns a confidence score alongside each match, allowing high-confidence results to be auto-approved while lower-confidence ones are routed for manual review.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Artificiety Launches as a Persistent Fantasy World Run Entirely by AI Agents

Developer Artificiety has launched a persistent fantasy simulation where every character is an AI agent powered by large language models, a concept its creator spent over a decade trying to make technically feasible. Each agent independently observes its local environment, decides on an action, and stores memories that persist across sessions, without any scripted behavior or central coordination. The underlying engine uses a single-writer tick loop, an entity-component system, and immutable world snapshots to handle concurrency, with state durably saved to S3. Emergent behavior is encouraged through designed-in conditions such as finite resources, use-based skill progression, dynamic weather and seasons, and autonomous wildlife routines. The platform runs on a Java and Spring backend with PostgreSQL, and the world server and platform services share no database, communicating only via authenticated REST.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Legacy Code Never Dies: The Web Runs on Layers of Technical Debt

A developer reflecting on Lea Verou's 16-year-old rgba.php workaround argues that the entire web is built on accumulated technical workarounds rather than clean architecture. The original script was created to help older browsers render CSS colors by bridging old and new technologies via a PHP-based API layer. The author notes that critical institutions such as banks, hospitals, and governments continue to rely on outdated systems, requiring ever more costly workarounds instead of fundamental fixes. Legacy code, the piece contends, never truly disappears — it simply gets buried under new layers of compatibility patches. The key takeaway is that good engineering is not about perfect code, but about responsibly isolating inherited chaos so that existing systems remain functional.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

45% of Developers Face Weekly Knowledge Silos Due to Outdated Documentation

A recurring problem across software teams is that internal documentation quickly loses its usefulness, even when it was accurate at the time of writing. New hires are routinely directed to tools like Confluence or Notion, only to find pages that lack the context behind key decisions. The core issue is that documents are rarely linked to the incidents, debates, or Slack threads that originally shaped them. Over time, this critical context disappears while the documentation itself remains, creating a misleading sense of completeness. A developer who surveyed multiple teams found the root causes to be fewer than expected and has outlined the recurring patterns behind these knowledge gaps.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds Nightly Batch Job to Auto-Generate Claude AI Skills From Chat Logs

A software developer has built an automated shell script that runs every night at 3:30 AM to extract reusable procedures from Claude AI conversation logs and save them as structured SKILL.md files. The system has so far generated 104 skills from a library of 3,349 accumulated conversation logs without manual intervention. To avoid excessive token costs, the script uses two controls: a watermark mechanism that skips already-processed files, and a hard budget cap of $1.20 per run. These constraints limit each nightly run to processing just three logs and roughly 45KB of content, keeping the operation efficient and cost-controlled. The script also filters out system noise before passing content to the AI model, ensuring only procedurally relevant information is extracted.

0 comments Read more at DEV Community