<center>
![](https://cl.ly/0F0o3M2y002V/Image%202017-09-18%20at%209.59.52%20PM.png)
</center>

---

It's not easy to write apps for the STEEM blockchain.  It depends on the language you're comfortable with and what level of development you're doing.  Sometimes, it's downright impossible to figure out without a fully defined set of API docs.

<center>
  [![](https://cl.ly/2F1w2j2q0y0p/Image%202017-09-18%20at%209.34.53%20PM.png)](https://steemit.com/steemit/@andrarchy/re-williambanks-re-steemitblog-crowdsourced-marketing-protocol-ideas-proposals-projects-20170418t184727463z)
</center>

---

I know this is not a trivial task.  In fact, it's not a new problem.  It's a problem as old as software development.

> "By documenting a design, the designer exposes himself to the criticisms of everyone, and he must be able to defend everything he writes. If the organizational structure is threatening in any way, nothing is going to be documented until it is completely defensible." - **The Mythical Man-Month by Frederick P. Brooks, Jr.**

While the above paragraph is absolutely true, we should keep in mind it's not an excuse for lack of documentation.  It's merely an observation as to *why* docs get the back seat in priority.  In other words, it's *descriptive*, not *prescriptive*.

I would like to help.  But I encountered a roadblock.

> Is this repo the correct place to expand on the developer api documentation? I only ask because it seems dead in here and I have gotten conflicting responses in rocket chat.

![](https://user-images.githubusercontent.com/494368/30315296-48cf4470-9758-11e7-89bb-057417f5f13b.png)

See: https://github.com/steemit/steemit-docs/issues/8

The roadblock is that I'm not sure if this is the correct repository to make pull requests from.  In addition to that, I'm not sure if my additions would be authoritative.

Anyway, @andrarchy.  What have you found during your 5 month hard look at the API docs?