Add section to README on working with the code

Author: Photonios

README.rst

@@ -1,17 +1,27 @@
 django-postgres-extra
 ---------------------
 
-.. image:: https://scrutinizer-ci.com/g/SectorLabs/django-postgres-extra/badges/quality-score.png
-    :target: https://scrutinizer-ci.com/g/SectorLabs/django-postgres-extra/
+=================  ===================
+**Quality**           |QualityBadge|_
+**Test coverage**     |CoverageBadge|_
+**License**           |LicenseBadge|_
+**PyPi**              |PyPiBadge|_
+=================  =================== 
 
-.. image:: https://scrutinizer-ci.com/g/SectorLabs/django-postgres-extra/badges/coverage.png
-    :target: https://scrutinizer-ci.com/g/SectorLabs/django-postgres-extra/
+.. |QualityBadge| image:: https://scrutinizer-ci.com/g/SectorLabs/django-postgres-extra/badges/quality-score.png
+.. _QualityBadge: https://scrutinizer-ci.com/g/SectorLabs/django-postgres-extra/
 
-.. image:: https://img.shields.io/:license-mit-blue.svg
-    :target: http://doge.mit-license.org
 
-.. image:: https://badge.fury.io/py/django-postgres-extra.svg
-    :target: https://pypi.python.org/pypi/django-postgres-extra
+.. |CoverageBadge| image:: https://scrutinizer-ci.com/g/SectorLabs/django-postgres-extra/badges/coverage.png
+.. _CoverageBadge: https://scrutinizer-ci.com/g/SectorLabs/django-postgres-extra/
+
+
+.. |LicenseBadge| image:: https://img.shields.io/:license-mit-blue.svg
+.. _LicenseBadge: http://doge.mit-license.org
+
+
+.. |PyPiBadge| image:: https://badge.fury.io/py/django-postgres-extra.svg
+.. _PyPiBadge:  https://pypi.python.org/pypi/django-postgres-extra
 
 ``django-postgres-extra`` aims to make all of PostgreSQL's awesome features available through the Django ORM. We do this by taking care of all the hassle. As opposed to the many small packages that are available to try to bring a single feature to Django with minimal effort. ``django-postgres-extra`` goes the extra mile, with well tested implementations, seamless migrations and much more.
 
@@ -21,6 +31,7 @@ With seamless we mean that any features we add will work truly seamlessly. You s
 
 Major features
 --------------
+
 * Native upserts
     * Single query
     * Concurrency safe
@@ -49,15 +60,16 @@ Desired/future features
 
 Installation
 ------------
+
 1. Install the package from PyPi:
 
    .. code-block:: bash
 
-        $ pip install django-postgres-extra
+        λ pip install django-postgres-extra
 
 2. Add ``postgres_extra`` and ``django.contrib.postgres`` to your ``INSTALLED_APPS``:
 
-   .. code-block:: bash
+   .. code-block:: python
 
         INSTALLED_APPS = [
             ....
@@ -85,16 +97,60 @@ FAQ - Frequently asked questions
 
 1. Why do I need to change the database back-end/engine?
 
-    We utilize PostgreSQL's `hstore` data type, which allows you to store key-value pairs in a column.  In order to create `UNIQUE` constraints on specific key, we need to create a special type of index. We could do this without a custom database back-end, but it would require everyone to manually write their migrations. By using a custom database back-end, we added support for this. When changing the `uniqueness` constraint on a `HStoreField`, our custom database back-end takes care of creating, updating and deleting these constraints/indexes in the database.
+   We utilize PostgreSQL's `hstore` data type, which allows you to store key-value pairs in a column.  In order to create `UNIQUE` constraints on specific key, we need to create a special type of index. We could do this without a custom database back-end, but it would require everyone to manually write their migrations. By using a custom database back-end, we added support for this. When changing the `uniqueness` constraint on a `HStoreField`, our custom database back-end takes care of creating, updating and deleting these constraints/indexes in the database.
 
 2. I am already using a custom database back-end, can I still use yours?
 
-    Yes. You can set the ``POSTGRES_EXTRA_DB_BACKEND_BASE`` setting to your current back-end. This will instruct our custom database back-end to inherit from the database back-end you specified. **Warning**: this will only work if the base you specified indirectly inherits from the standard PostgreSQL database back-end.
+   Yes. You can set the ``POSTGRES_EXTRA_DB_BACKEND_BASE`` setting to your current back-end. This will instruct our custom database back-end to inherit from the database back-end you specified. **Warning**: this will only work if the base you specified indirectly inherits from the standard PostgreSQL database back-end.
 
 3. Does this package work with Python 2?
 
-    No. Only Python 3.5 or newer is supported. We're using type hints. These do not work well under older versions of Python.
+   No. Only Python 3.5 or newer is supported. We're using type hints. These do not work well under older versions of Python.
 
 4. Does this package work with Django 1.X?
 
-    No. Only Django 1.10 or newer is supported.
+   No. Only Django 1.10 or newer is supported.
+
+
+Working with the code
+----------
+
+**Prerequisites**
+
+* PostgreSQL 9.6 or newer.
+* Django 1.10 or newer.
+* Python 3.5 or newer.
+
+**Getting started**
+
+1. Clone the repository:
+
+   .. code-block:: bash
+    
+        λ git clone https://github.com/SectorLabs/django-postgres-extra.git
+
+2. Create a virtual environment:
+
+   .. code-block:: bash
+    
+       λ cd django-postgres-extra
+       λ virtualenv env
+       λ source env/bin/activate
+
+3. Install the development/test dependencies:
+
+   .. code-block:: bash
+    
+       λ pip install -r requirements/test.txt
+    
+4. Run the tests:
+
+   .. code-block:: bash
+    
+       λ py.test
+    
+5. Run the benchmarks:
+
+   .. code-block:: bash
+    
+       λ py.test -c pytest-benchmark.ini