<h1 id="request-endpoint-response">Request Endpoint Response<a aria-hidden="true" class="anchor-heading icon-link" href="#request-endpoint-response"></a></h1>
<h2 id="rationale">Rationale<a aria-hidden="true" class="anchor-heading icon-link" href="#rationale"></a></h2>
<h3 id="addresses-swollen-controller-problem">addresses “Swollen Controller Problem.”<a aria-hidden="true" class="anchor-heading icon-link" href="#addresses-swollen-controller-problem"></a></h3>
<ul>
<li><strong>Simplifying Concepts</strong>: It provides a clear structure for REST API endpoints, focusing on the essential components.</li>
<li><strong>Reducing Controller Complexity</strong>: Unlike traditional MVC controllers, which can become bloated, the REPR pattern encourages smaller controllers dedicated to specific endpoints.</li>
<li><strong>Enforcing Clarity</strong>: By adhering to the REPR pattern, developers maintain a clear separation of concerns, leading to more maintainable and extensible APIs.</li>
</ul>
<h2 id="references">References<a aria-hidden="true" class="anchor-heading icon-link" href="#references"></a></h2>
<ul>
<li><a href="https://blog.stackademic.com/the-repr-pattern-simplifying-api-development-dd58a5be476f">https://blog.stackademic.com/the-repr-pattern-simplifying-api-development-dd58a5be476f</a></li>
</ul>

addresses “Swollen Controller Problem.”

Request Endpoint Response

public-notes


Welcome! And beware!  

## Purpose

This vault is the "[[learning-in-public|ar.swyx.learn-in-public]]" part of my Second Brain. If you share some of my interests, please [reach out](https://djradon.github.io)! 

## Contents

- [[t]] my personal wikipedia
- [[idea]] (not necessarily mine)
- Resource Notes, including highlights, thoughts and metadata, for various things:
  - [[ar]] mostly articles, papers and web pages
  - [[book]]
  - [[community]]
  - [[course]]
  - [[event]]
  - [[game]]
  - [[loc]]
  - [[org]]
  - [[user]] 
  - [[prdct]] mostly software products, but also ontologies
  - [[recipe]]
  - [[video]] movies, tv episodes, youtube, etc
- [[vs]]
- [[wanted]]
- Some "Metadata Notes":
  - [[tags]] which may refer to any and multiple (or none) of the above
  - [[c]]: ways to categorize resources
  - [[p]]: ways to assert things about resources (mostly abandoned)

In terms of the [[t.km.zettelkasten]] method, this wiki is a commingling of literature notes with something @Sönke-Ahrens warned about: a "personal Wikipedia or a database" [^1]. 

In terms of [[t.tm.getting-things-done]], it's references, someday-maybe, next actions, and public projects.

## Beware!

This is a cluttered cupboard of jumbled jottings riddled with inaccuracies, confusion, and mistakes.

## What This Is Not

- evergreen-notes/digital-garden: for "synthesized" / original-ish publishable big-idea notes that should evolve over time, props to @andy-matuschak and @maggie-appleton
- blog: for "point-in-time" items to be shared: personal news, articles, etc.
  - e.g., [[ar.substack.carpe-noctem]]


[^1]: [[book.how-to-take-smart-notes]]  