# Development Philosophy

Our development philosophy is centered around three core Pillars

**User Friendliness First**

Our merchants come first and if it's not friendly for them, it needs to be changed

**Right Tool for the Right Job**

We build with what we think is the right tool for the right job, we don't go in for the newest craze and we don't adopt technology to make your life harder.

**It's gotta be&#x20;*****Fast***

We know that conversion rate is directly impacted by response times, our internal goal is to make sure that any request to our public endpoints meets the following goal

95% of requests served within 100ms

As of June 2024 - we've served <mark style="background-color:green;">98.71%</mark> of public requests in under 100ms

**What it means to you and our Merchants**

* No GraphQL for you to deal with
* Our widgets only use JS frameworks if the app is complex (Mercury)
* Otherwise, we write plain javascript (Juno, Cupid)
* Our apps public endpoints are geo-distributed near the end consumer


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.plutocracy.io/plutocracy/working-with-plutocracy/development-philosophy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
