BUSINESS

Weekly programmers report 28/09/2023

blogpost

Hi there!

Join us for our weekly roundup of the solutions and technologies we've implemented.

The content for this report was extracted from our internal standup meetings, and ChatGPT has provided clear and concise report text.
The automation of data aggregation is made possible through a custom Slack plugin integrated with make.com, which communicates with OpenAI on our behalf.

Radek:

  • What functionalities were delivered?

Initially, a map was added to the route form, but it was not fully functional. Then, Google Maps was replaced with Leaflet from Openrouteservice, which improved the appearance and functionality of the form. It became possible to add points on the map and calculate routes between them. In the final stage, adjustments suggested by Mehdi were implemented.

  • What problems were resolved?

The initial problem was that there was only one location search field when we needed to have two - one for the starting point and one for the destination. Another issue was disabling the automatically appearing instructions, which was resolved by adding show: false. Additionally, Radek addressed several minor issues when integrating with Leaflet and Openrouteservice. Issues like automatically adding unwanted extra markers. Lastly, he delved into adding additional fields to the form using buttons and calculating routes between multiple points.

  • What technologies, solutions, or tools were used?

Initially, Stimulus and Google Maps API were used, and later, the switch was made to Leaflet from Openrouteservice. Stimulus is still used, along with RSpec.

Maciej:

  • What functionalities were delivered?

Many new functionalities were delivered, including adding locals to the modal, which are passed to Stimulus through the target. The organizer type was added to the ISO file in the invitation email. Work was also done on survey controllers, making them more efficient by using a service. Code adjustments were made, and unused code fragments were removed. Functions for unsubscribing were added to the newsletter, and naming conventions were changed. Correct answers in the test received a green background, although attempts to add a switch encountered issues.

  • What problems were resolved?

Minor issues were addressed, such as unnecessary commented-out code and unused fragments, as well as issues related to names in the case of multiline text. Attention was given to removing the "first" add-on from email names in the newsletter.

  • What technologies, solutions, or tools were used?

Tools used during these tasks included GitHub, Spina, Mailer, Turbo, and Stimulus.

Szymon:

  • What functionalities were delivered?

In the initial reports, Szymon deepened his knowledge of Leaflet map configuration and technologies like Stimulus and Tailwind. The next step was to use this newly acquired knowledge to replace paid Google maps with cheaper alternatives using free requests.

  • What problems were resolved?

A significant problem that was resolved was replacing paid maps with cheaper ones using free requests. The next challenge was adding Google maps to the API and displaying them on the website. This functionality became crucial for the project.

  • What technologies, solutions, or tools were used?

Szymon utilized various technologies and tools. He mentioned technologies like Stimulus and Tailwind, and he used Leaflet, a JavaScript library for creating interactive maps.

Mariusz:

  • What functionalities were delivered?

The functionality of drawing a grid representing the chosen door wing glazing style was delivered. This process was initiated with a button that triggered Stimulus code with Canvas. Scalability and dynamism were achieved by redesigning the JavaScript code, which is no longer based on events (in the context of drawing structures) but on target values with the 'selectedValue' option. Comprehensive cleaning and code separation were also carried out. The choice of door layout and glazing layout was moved to a separate tab in the configurator. Links to the repository related to this task are also available.

  • What technologies, solutions, or tools were used?

In the work, technologies such as Stimulus and Canvas, RSpec, and View Components were used. Utilizing these tools allowed for organizing and optimizing tasks. Additionally, it was valuable for the rest of the team, enabling code repository accessibility and shared use of specialized tools.

Mateusz:

  • What functionalities were delivered?

The first improvement was in testing public profiles, which underwent code review. Privacy settings were also worked on, approved, and planned to be integrated into the main codebase in the near future. The work did not involve specific actions related to tickets. There are plans to add the option of attaching files to the first forum post as it currently only works for replies. Minor adjustments were made to the accessibility mode. Evaluation of a new project began in collaboration with the project manager, but the process is not yet completed.

  • What technologies, solutions, or tools were used?

Technologies used during the work primarily included Simplecov, RSpec, active admin, and DigitalOcean on the Dokku platform. The solutions presented encompass code refactoring, using tests to check new functionalities, and utilizing the gsub function to address an issue with the mailer. In the subsequent project, mailers, SendGrid, and JSONAPI-Serializer were also employed.

Krzysiek:

  • What functionalities were delivered?

Several minor functionalities were delivered for the project. Together with Ark, the installation of version 1.0.3 was carried out. A meeting with the client was held, and only two minor comments were received. No specific actions related to tickets were taken. There are plans to add the option of attaching files to the first forum post; currently, this feature only works for replies. Minor adjustments were made to the accessibility mode. The evaluation of a new project began with the project manager, but it is not yet completed.

  • What technologies, solutions, or tools were used?

Technologies used during the work included SpinaCMS, Tailwind, Stimulus, Ruby, Dokku, and Docker.

Karolina:

  • What functionalities were delivered?

There was a strong focus on testing during this reporting period. Numerous tests were conducted, and various issues were identified, which were then documented using individual tickets. Among the identified issues were the lack of translations in the forum, problems with styling emails in the newsletter, and incorrect display of images in industry events. Following a colleague's suggestion, a strategy of documenting errors and creating tickets from them was adopted instead of informing developers of each issue separately, with the aim of increasing team focus and efficiency.

  • What problems were resolved?

This report did not include information about specific problems resolved during the work. However, significant efforts were made to identify and document issues, which are now being addressed by developers.

  • What technologies, solutions, or tools were used?

During the work, tools such as ClickUp were used for task management and issue documentation, and Slack was used for team communication.

Mehdi:

  • What functionalities were delivered?

During this reporting period, various functionalities were implemented, with a primary focus on resolving issues related to tax amounts stemming from irregularities in financial flows. It was necessary to generate a detailed report aimed at explaining the situation. This process consumed most of the programmer's time.
Simultaneously, work was conducted to address issues related to the Dokku platform. Some improvements were made to it, although work on it is still ongoing.

  • What problems were resolved?

The main problem successfully resolved was inconsistencies. After a prolonged battle with the issue, a satisfactory outcome was ultimately achieved. The discrepancies were mainly related to calculation errors, but they were identified and corrected.

  • What technologies, solutions, or tools were used?

The primary tool that expedited the work was Kubernetes. Thanks to it, the programmer could easily fetch files, greatly facilitating the report generation process.
Additionally, various SQL techniques were employed to address the data problem, particularly in the realm of data filtering and grouping, allowing for effective data management.

Read more on our blog

Check out the knowledge base collected and distilled by experienced
professionals.
bloglist_item
Business

Ruby is great. Python is also great. C# and java are obviously great too.
Even PHP can be great.

So why so many companies struggles with projects written in those languages?
And more important...

bloglist_item
Business

Since I helped about 50-60 people to start their journey with Ruby and I still have to answer for the same questions like
- "What do people find attractive about ruby language?"
- "What is it d...

bloglist_item
Business

INTRODUCTION

In the first part of the cycle, we talked about initial estimations (in our case project concept) and characteristics o...

Powstańców Warszawy 5
15-129 Białystok

+48 668 842 999
CONTACT US