<commit_before>+++
title = "Epic first post: open sourcing Vamp!"
tags = ["first", "launch"]
category = ["news"]
date = "2015-03-31"
author = "<NAME>"

+++

From today onwards, we are open sourcing the development of Vamp, the *Very Awesome Microservice Platform*. Yay!
For me and the team this is quite a milestone and a very exciting next step in how we build Vamp and who contributes
to it. We are still in alpha, so things might still be somewhat rough around the edges, but what Vamp can do 
already surpasses what I had imagined over a year ago! Big up for the team!

![](/img/team_launch.jpg)
      
So, what can you expect from Vamp and its development?

- Open development on all fronts: open design, open code, easy extending.
- Focus on usability: good documentation, helpful error messages and clear API design.
- Standard where possible: No reinvention if not necessary!

Over the coming weeks and months we will be releasing a lot of write-ups, reference docs and cookbook-type
tutorials on how to use Vamp and what tricks it can do.

<NAME>, CTO
 
 
<commit_msg>add alias after permalink change<commit_after>+++
title = "Epic first post: open sourcing Vamp!"
tags = ["first", "launch"]
category = ["news"]
date = "2015-03-31"
author = "<NAME>"
aliases = ["/blog/epic-first-post/"] 

+++

From today onwards, we are open sourcing the development of Vamp, the *Very Awesome Microservice Platform*. Yay!
For me and the team this is quite a milestone and a very exciting next step in how we build Vamp and who contributes
to it. We are still in alpha, so things might still be somewhat rough around the edges, but what Vamp can do 
already surpasses what I had imagined over a year ago! Big up for the team!

![](/img/team_launch.jpg)
      
So, what can you expect from Vamp and its development?

- Open development on all fronts: open design, open code, easy extending.
- Focus on usability: good documentation, helpful error messages and clear API design.
- Standard where possible: No reinvention if not necessary!

Over the coming weeks and months we will be releasing a lot of write-ups, reference docs and cookbook-type
tutorials on how to use Vamp and what tricks it can do.

<NAME>, CTO
 
 

{'fraction_non_alphanumeric': 0.0741745816372682, 'fraction_numerical': 0.007236544549977386, 'mean_word_length': 4.073394495412844, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '903655', 'n_tokens_mistral': 644, 'n_tokens_neox': 588, 'n_words': 344}