Why do people start companies? The reasons are different. Some want to get rich and famous. Some think they can do things better than the others. Some just cannot help it not to be creative.
What all the founders have in common is the ignorance. They do not realize yet how hard their journey will get and how many obstacles they’ll have to overcome to build their dream product.
For the founders - ignorance is a bliss.
The world is changing very rapidly. Markets are crashing, money is disappearing, new unions are being created, the old ones are being destroyed.
The investments are not as they were even a year ago. VC’s didn’t get any wiser but they’ve gotten more precautious. On one hand they have to spend the money cause it’s losing its value every day, on the other hand they cannot spend it on the startups that don’t make any profit.
As of today DKB is the third largest direct bank in Germany with more than 3.9 million customers.
After it has introduced the custody fees for the deposits larger than 25.000 Euros and removed its best product - a fee free credit card that could be used abroad free of charge both for payments and withdrawals it’s destined to lose some of its clients.
Startups are all about the speed of execution and iteration. If you don’t have enough financial resources to hire a team to execute on your idea 24/7 for the next 3-6 months, your best bet is to find like-minded people and start working on your pitch-deck.
Everything written below is highly influenced by my personal experience and talks that were given by the people I’m following.
What you will read here is my take on the leadership.
Although the end of PWAs has been proclaimed a while ago, the Progressive Web Apps keep getting better.
Not only the processors have been improving at a rapid rate but also the
V8 is getting better with every iteration.
If you’re long enough in the tech business, you should have heard a tale about 3H that every startup needs. In order for a startup to become successful it needs 3 founders:
If you think about this setup for a bit, this constellation will definitely start making sense.
Let’s see what every one of those 3H actually entails.
Recently we decided to use AWS Amplify for one of the products we’re currently working on.
AWS Amplify promises to provide you with the option to rapidly develop the REST or a GraphQL based backend that’s very well integrated with your frontend development - be it a web application or a mobile app. That’s at least the marketed value proposition.
At Mbanq Cloud we run most of our services on AWS and try to use AWS Lambda as much as possible.
A while ago I’ve been working on the a small npm package that should have helped us to make use of SSM and KMS to manage our system configuration. SSM and KMS play nicely together as the most of the AWS services.
In order to test the newly written npm package, I had to mock the promisified version of the ssm.getParameters(request)
Everyone has its own view on how to organize the routes in a Single-Page Application-we’re not different.
Since we’re using Vue.js in our current project, we’re also using the Vue Router.
Here I would like to describe the approach we took to organize our router and its routes. We will probably change/improve the current state later on but for now I will describe the status quo.