Quickly getting a prototype/MVP up and running is key to customer feedback and engagement. Only a customer that collaborates in the development process of the product gives precise and informed feedback.

Based on that premise the following technologies are my default choice to cover most cases:

  • Python
  • JavaScript
  • HTML, CSS
  • VueJS / Quasar Framework
  • PHP
  • SQL
  • Node.js / ExpressJS
  • MongoDB
  • Docker

Supporting methodologies:

  • Agile - Incremental advances reduce risk,
  • DevOps - Packaging software with OS-wrapper eases deployment and reproducibility
  • and Functional programming - building larger solutions from well testable smaller ones


Heavy-lifting after you know what you lift

Premature optimization is a problem I want to avoid so I avoid optimized languages until the mission is clear.

C/C++ and Java would cover those cases for me.


Creating tools to support creating tools

As scripting languages like CPython have access to anything from high-level Web-API’s to low-level C or serial interfaces information can easily be obtained and visualized via HTML5, CSS and Javascript.

Understanding your project on a higher level may suddenly be possible beyond buildin functionality of common tools. A Python script I made helped in understanding the state of a Jira project that was overly fragmented because connecting issues were retired without propagating the changes and realizing the implications on other issues.

Jira issue graph snapshot of project Digitale Weiche 2 visualized via HTML5, Jinja2, Python and Jira-REST-API