Blog /Technology

Building multifunctional websites and web applications is hardly an easy task. We support ourselves in this process with various programming languages and tools.

We are the largest and best-known company dealing with creating and supporting Drupal-based websites in Poland. Our areas of expertise also include Symfony, PHP, ReactJS and front-end development. In our endeavours, we also use a variety of other software solutions, such as PHPStorm, Jenkins and Docker.

We are happy to share our experiences, describing the process of work on building and developing websites and applications at Droptica. Thanks to SCRUM and the right tools such as Slack and Jira, we ensure seamless communication between the team and the client. We systematically improve or change the software we use in order to automate repetitive actions and speed up the development work.

You can learn more about the ins and outs of our work thanks to our extensive blog articles, or you can find out what benefits we can offer you thanks to our Case Studies.

Many articles have been written about what characterizes good code, how to write good code, and why good code is… good from the programming side. We can easily find them online and on our blog. Today, however, we want to approach the impact of good (or bad) code on software from the business side. Why is it not worth saving money at the beginning of creating a new system and how bad code can generate huge costs in the future?

What do Spotify, Netflix, Twitter, and Adobe have in common? Taking advantage of the benefits provided in the package with Node.js. Netflix has reduced the time it takes to launch its streaming service. Twitter has also achieved better performance, further reducing the cost of maintaining the platform. Do you also want to do this? This article will tell you whether Node.js might be a good solution for you.

Just as tools were created to process materials and build shelters, today, developers are creating tools for themselves to work more efficiently. However, it grew to such an extent that jokes have started to be made among frontend developers about the next frameworks. Why are there so many of them? How are they different from JavaScript libraries? What are frameworks and why developers want to write their projects in them? We'll answer these questions in a moment, but one step at a time...

Today's high traffic websites must handle hundreds of thousands or even millions of simultaneous requests from users or customers and return the correct elements on the web page. They have to do all of that quickly and reliably. For the servers handling a given website, it's a test of whether they'll properly handle the traffic at a given moment so that the end user has uninterrupted and comfortable access to the service.

In this article, we'll discuss the differences, advantages, and disadvantages of both of these solutions. However, before this happens, we'll briefly remind you how websites work and how it’s possible that, regardless of what device we use to surf the web, we only need an internet connection and any device with a browser.

In the process of creating a product, every person working on a given problem may have a slightly different approach to solving it. These don’t necessarily have to be big differences. It's enough to interpret the idea differently for the finished solution to not fully suit the product owner. Establishing clear and transparent acceptance criteria will help streamline your software development, as well as allow for the prevention of possible misunderstandings.

We use multiple environments when developing software. We care most about the production environment which is accessible to all users. In the test environment, we check that the changes we make function as they should. There is also a local environment - we could say it is the most important one. It is where application development and maintenance starts. What exactly is it, what does it provide us with and how do we generate it? Let's get down to specifics.

It would be a strange world if we didn’t use names, but call each other "you" or, even worse, use numbers. In everyday life, we are well aware of the importance of our name. Some even ascribe to it meanings or magical powers that contribute to success in private and professional life. Therefore, it shouldn't be surprising that the name of our website domain is as important as our own name.

In the world of application development, API is a great way to upload and retrieve the data we need. The mechanisms responsible for sharing data in an API can be either simple services providing information on currency exchange rates, or carry out more complicated processes, allowing for creating users or processing larger amounts of data. However, what if we want to test or check what result will be returned to us by a particular API?

MG 1202 Blur

Need a team of Drupal and PHP web development experts?