Benny JooandDevin AI
ab21c7f805
* feat: Cal.diy — community-driven MIT-licensed fork of Cal.com This squashed commit contains all Cal.diy changes applied on top of calcom/cal.com main: - Rebrand Cal.com to Cal.diy across the entire codebase - Remove Enterprise Edition (EE) features, license checks, and AGPL restrictions - Switch license from AGPL-3.0 to MIT - Remove docs/ directory (migrated to Nextra at cal.diy) - Remove dead code: org tests, EE tips, platform nav, premium username, SAML/SSO, etc. - Clean up .env.example for self-hosted Cal.diy - Update Docker image references to calcom/cal.diy - Update README, CONTRIBUTING.md, and issue templates for Cal.diy community fork - Add PR welcome bot for Cal.diy contributors - Fix API v2 breaking changes oasdiff ignore entries - Replace Blacksmith CI runners with default GitHub Actions 3893 files changed, 20789 insertions(+), 411020 deletions(-) Co-Authored-By: benny@cal.com <sldisek783@gmail.com> * refactor: remove org-specific /organizations/:orgId endpoints from API v2 atoms controllers (#1701) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> * fix: revert Cal.diy Inc to Cal.com, Inc. in license files, copyright notices, and package metadata (#1702) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> * rip out org related comments in api v2 --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
44 lines
1.3 KiB
Markdown
44 lines
1.3 KiB
Markdown
---
|
|
title: Prioritize Clarity Over Cleverness
|
|
impact: HIGH
|
|
impactDescription: Reduces cognitive load and improves maintainability
|
|
tags: quality, simplicity, readability
|
|
---
|
|
|
|
## Prioritize Clarity Over Cleverness
|
|
|
|
**Impact: HIGH**
|
|
|
|
The goal is code that is easy to read and understand quickly, not elegant complexity. Simple systems reduce the cognitive load for every engineer.
|
|
|
|
**Questions to ask yourself:**
|
|
- Am I actually solving the problem at hand?
|
|
- Am I thinking too much about possible future use cases?
|
|
- Have I considered at least 1 other alternative for solving this? How does it compare?
|
|
|
|
**Incorrect (clever but hard to understand):**
|
|
|
|
```typescript
|
|
// Clever one-liner that's hard to parse
|
|
const result = data.reduce((a, b) => ({...a, [b.id]: (a[b.id] || []).concat(b)}), {});
|
|
```
|
|
|
|
**Correct (clear and readable):**
|
|
|
|
```typescript
|
|
// Clear, step-by-step approach
|
|
const groupedById: Record<string, Item[]> = {};
|
|
|
|
for (const item of data) {
|
|
if (!groupedById[item.id]) {
|
|
groupedById[item.id] = [];
|
|
}
|
|
groupedById[item.id].push(item);
|
|
}
|
|
```
|
|
|
|
**Important note:**
|
|
Simple doesn't mean lacking in features. Just because our goal is to create simple systems, this doesn't mean they should feel anemic and lacking obvious functionality.
|
|
|
|
Reference: [Cal.diy Engineering Blog](https://cal.com/blog/engineering-in-2026-and-beyond)
|