Like many other events, DrupalCamp Oslo went virtual this year. In person events are still my favorite, but this did give me the chance to participate in the event for the first time! I joined in to provide an update on the state of the API-First work in the Drupal Commerce ecosystem. We were excited to take part in the event, as we've often collaborated with the Norwegian Drupal team at Ny Media on Drupal Commerce contributions and on the occasional client project. One of our favorite outcomes was the Commerce Pricelist port to Drupal 8 developed as part of the Akademika.no case study. We've been busy developing Centarro Commerce, our headless commerce SaaS, which means expanding the API-First capabilities of Drupal Commerce. For instance, we just added support for on-site payment gateways over our Commerce API. We also expanded our shipping integration with the ability to trigger shipment notifications in the latest Commerce Shipping release. DrupalCamp Oslo was live-streamed on YouTube, so you can catch my talk about "API Driven Drupal Commerce" on the recording. Read moreOriginally from Drupal.org aggregator https://ift.tt/3ei0D3F
0 Comments
The German and Austrian Splash awards took place yesterday. The yearly event that was virtual this year, turned out to be a lot of fun, with great hosts and guests.
Originally from Drupal.org aggregator https://ift.tt/3kX0vcF Share your vision on the business side of Drupal in 2020! Agencies One Shoe, Exove and the Drupal Association are calling all Drupal agency leaders to take part in the annual and already the fifth Drupal Business Survey. The Drupal Business Survey aims to gain insight into the key issues that Drupal agency leaders nowadays face. It includes questions about the business strategy of Drupal companies, the impact of Covid-19, Drupal community contribution and about the future of Drupal. Read the 2016, 2017, 2018 and 2019 reports for previous analyses. Now it’s time to contribute to a new overview of the state of Drupal business in a year that’s influenced by so many factors. Your response will be used to generate an anonymized, aggregate report about the state of the Drupal business ecosystem. The survey is open until Monday, November 16th. The results and insights of this survey will be shared with you, officially published on Drupal.org and discussed on the Drupal CEO Virtual Drinks on December 9 at DrupalCon Europe. Take part in this survey and contribute to the Drupal project: your opinion is of great value! Originally from Drupal.org aggregator https://ift.tt/2THbgDy
The Collaboration Between Designers And Developers During Code Review Tuba Ayyubi Sat, 10/31/2020 - 01:15
Code reviews help in identifying bugs before the testing phase. Many people skip this step and think of it as an ongoing practice during the development stage but code reviews have proven to be a great assurance strategy. Getting your work reviewed and reviewing other people’s work is an excellent way to learn and grow. A collaborative environment among different teams is the need of the hour. Today, when things have gone digital, collaboration and communication gaps need to be given more importance to keep the workflow consistent. A happy and smooth collaboration between the designers and developers is important but is a little difficult. The idea of someone else reviewing your work might sound scary. For a designer, having someone not as creative review their work is like a threat to their creativity. And likewise, for a developer, getting their codes and programs reviewed by a designer is not easy to take. But if you think of it as many ideas coming from different sources and collaborating together to make something bigger and better, it will be easier for you to let other people look into your work. So how do we get the two teams to get along? We will get to it, but first, let’s look at why and how code review is important. Why do a code review?When you have someone who reviews your work, and also when you know someone is going to review your work, helps in increasing the quality of your code and makes it an error-free one. According to The 2018 State of Code Review by SmartBear, 73% of people said that code review helps share knowledge across their team and 53% said that code reviews help in mentoring less experienced developers. Code review plays an important role in building a collaborative culture among the team members. When more than one person is involved in a code review process, it should not just be 'my code' or 'your code', it should become 'our code'. A few principles that need consideration are as follows:
These principles, if followed, make code review a positive force instead of a negative and disappointing one. The teams must allow each other to ask questions and clear their doubts without any hesitation and keep motivating each other to build something great together. If doing a review holds such advantages, why only do it for code? For a business to run efficiently, the design and development teams need to come together. And to truly maximize the outcomes, the teams should be able to work as teams. Collaboration, communication, and consistency have to be a part of the process. If this is not done, you will have to deal with frustrated team members, unhappy clients, lengthy rants, many missed deadlines, and whatnot. To stop such things from happening, let’s look at these steps that will help in strengthening the collaboration between designers and developers. Learn more about the importance of code review here. Steps to consider for the designers for the code review process
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
April 2023
Categories |