Recently we visited Budapest to attend EuRuKo2017. I decided to share some insights from this trip.
Employing dozens of software engineers doesn’t necessarily mean you can build a demo MVP in-house… especially when you need it yesterday.
There are a few simple rules that help to write good code: it stays maintainable, it is stable, and it solves a problem. When one of those attributes is missing, you are not doing a good job.
What I found from my experience at Vertalab is that even a junior software engineer can show good performance by following those rules.
This article aims to explain the cost of web app development. Many fixed-cost projects underestimate the costs in terms of money and time. And while there are many reasons for this (e.g. poor judgment, requirements that were not clear, and salesmen trying to win your bid at all costs), the main reason for underestimations is that it is hard for humans to think in exponential terms.
The more complex an application, the more time it takes to implement changes in functionality. A feature that could have been implemented in just one day at the beginning of the project could require several days six months after the project starts.
Let’s take a look at this process from a scientific perspective. Systems theory tells us everything is a system consisting of various elements at different levels of complexity.
Deployment is one of the most important technical steps in building a Ruby on Rails application. When communicating with developers, there are several steps and options you should be aware of. This short guide will help you to understand the workflow of the deployment process and help you to understand its main components.
At Vertalab, we invest part of our working time in self-improvement. Usually, it happens on Fridays. We use this time to play around with our own startup ideas, improve our internal tools, or learn new things.
Technology is not the first thing we talk about with our clients. We talk about business, ideas, and problems that we can help to solve. But when we understand the problem, when user stories are clear and wireframes are ready – we start writing the code. In most of the cases it’s Ruby code.
Here I will try to explain what Ruby on Rails is for people who do not have programming experience to help them understand the tool we use to build web applications. Continue reading Ruby on Rails 101. What is Ruby on Rails?
It’s obvious that every idea has a set of preconditions determining whether it will become a successful product, and your ability to react fast to customers’ feedback is one of the keys to attracting paid customers and igniting growth.
In order to make the customer development process smoother and more dynamic, I recommend using Ruby on Rails to build your product prototype (minimum viable product). Continue reading 10 Reasons to Choose Ruby on Rails for Prototyping Web Apps