Web Development Notes

Best Practices in API Design (A Practical Guide) APIs are the connective tissue of modern software. A  useful  API is predictable, consistent, and safe to evolve. Below is a concise, hands-on guide—mirroring the structure in the image—covering eight fundamentals with patterns, anti-patterns, and snippets you can drop into your docs. 1) Use Clear Naming Principles Nouns, not verbs  for resources:  /products ,  /orders/123 ,  /users/42 . Plural collections ; singular items:  /products  (list/create),  /products/{id}  (read/update/delete). Use subresources for relationships/actions : Relationship:  /orders/123/items Domain actions (state changes) as subpaths:  /orders/123/cancel ,  /users/42/verify Consistent casing  (kebab-case or snake_case) and predictable errors. Do POST /api/v1/products GET /api/v1/products?category=shoes PATCH /api/v1/products/123 DELETE /api/v1/products/123 Don’t /createNewProduct /getProduc...

When you’re building software—whether it’s a small utility or a full-scale application— performance  plays a critical role. Efficient algorithms are the backbone of scalable systems, and understanding how they behave as the input size grows is essential. This is where  Big O Notation  comes in. Big O is a mathematical notation that describes the  worst-case growth rate  of an algorithm in terms of time or space. It doesn’t measure exact speed but rather gives an upper bound on how an algorithm scales. Understanding it helps you compare solutions and make better design decisions. Below is a breakdown of the most common time complexities, explained with simple examples and real-world use cases. O(1) – Constant Time An operation that takes the same amount of time regardless of the input size. Example:  Accessing an array element by index: const item = arr[5]; Use Cases: Hash table lookups Boolean checks Retrieving values from dictionaries O(n) – Linear Time Th...