At a glanceExpert's RatingProsEasy to disassemble for cleaningOnly $100 more than the smaller Seagull SEWater drains quicklyConsIneffective at cleaning the poolRan for barely half its promised running timePower switch is stiff and difficult to engageOur VerdictThe Seagull Plus promises extra power and running time, but it didn&rsquo;t deliver either.Aiper is back with another pool-cleaning robot: This one is a variation on its Seagull Plus, but mounted on a larger chassis, with a bigger battery, and providing more suction. You&rsquo;d think that combination would result in a much cleaner pool. Unfortunately, that just didn&rsquo;t pan out in my testing, and I&rsquo;m baffled as to why.Let&rsquo;s start with specs. The 13.8-pound device has the overall look of a small, gray lawn mower, rectangular and utilitarian. Aiper says the 7800mAh battery pack will provide 110 minutes of running time, covering a vast 1,300 square feet of flat-floor pool space. The unit charges via wall power in ab

Aiper Seagull Plus review: This bigger bot isn’t necessarily better. Sure enough, after another hour and a half, I emptied the SE to find that it had more debris inside than the Seagull Plus had had—and that’s after the Plus had had first crack at the job and had spent an hour vacuuming up leaves

TechHive

Sign upSign inSign upSign inSamir SaciFollowTowards Data Science--ListenShareSustainable sourcing is the process of integrating social, ethical and environmental performance factors when selecting suppliers.This includes assessing and evaluating suppliers based on sustainability criteria such as health and safety, environmental impacts or labour rights.The aim is to minimize the negative impacts on the environment and maximize the positive social impacts.As a Data Science Manager, can you develop tools to streamline the process of supplier selection?Supply Chain Network design tools automatically select the best suppliers that minimize costs and meet the market demand while respecting constraints defined by your sustainability team.In this article, we will explore how you can use data science in your organization to support the implementation of sustainable sourcing.Let us take the example used in the previous articles about Life Cycle Assessment.You are the Data Science Manager of an international clothing group that has stores all around the world.The company sources garments, bags, and accessories from suppliers located in Asia.Stores are delivered from local warehouses that are directly replenished by suppliers.Can you automatically select suppliers that minimize your costs while respecting environmental and social constraints?The sourcing team has decided to implement sustainable sourcing on the limited scope of T-shirt suppliers.They want to review their supplier selection process to support the company’s sustainability roadmap.However, they are facing several obstaclesTherefore, they request your help deploying a product to monitor suppliers’ KPIs and automate the selection.Let’s see how data analytics can answer this problem.I will use a simple example with a limited range of indicators for this article.We can quickly review them to understand their definition and how to measure them.Carbon emissionsThe primary indicator that will drive your sustainability roadmap is the carbon footprint of the supply chain.This can be measured by calculating the total emissions of greenhouse gases such as carbon dioxide, methane and nitrous oxide.💡 What should we consider?The first two metrics should be collected from the suppliers, but your team can calculate the third one.The formula is quite straightforwardThe data sources areIf you need more information, I have detailed the process in this articletowardsdatascience.comEnergy consumptionAnother indicator is the amount of energy consumed by the supplier to produce and deliver products.It can be expressed in Joules used per production unit (called functional units in the Life Cycle Assessment Methodology).💡 What should we consider?The sourcing team should collect this metric.Water usageAs it becomes a scarce resource, new regulations are pushing companies to redesign their processes for water consumption reduction.With this indicator, you can focus on suppliers that do not affect the local water supply.💡 What should we consider?Waste generationMeasuring the amount of waste generated during production can help identify areas for adopting more sustainable production methods.💡 What should we consider?Social indicatorsThese indicators assess suppliers’ performance in terms of social sustainability.You can conduct your own audits or use third-party assessments.💡 How to Measure it?Your sourcing team assigns a weight to each criterion in the scorecard below.The auditors calculate a score linked to each criterion to represent the supplier’s performance.The total score is a pondered average of the scores that provide a general supplier assessment.The first support you can provide to your sourcing team is to streamline the data collection and storage process using data analytics tools.A data lake can be a central source of unstructured and structured data (databases, excel files, …).You can implement automated pipelines to extract, process and analyze these data to build reports and provide insights.This can lead to the implementation of data products that can be used for reporting and the optimization models I will present in the next section.For more information on the best practices and methodologies to automate this exercise, look at this article about Life Cycle Assessment.towardsdatascience.comWe can use this data to drive decisions now that we have collected information about suppliers and performed audits with scoring.The sourcing team’s main obstacle was the problem’s complexity considering the number of different metrics and suppliers.They use Excel files with limited automation; this restrains their processing capacity.Therefore, the idea is to use advanced analytics to automatically design sourcing and logistics networks to deliver your stores.I will use an example with dummy data to understand how to implement a data-driven methodology to select suppliers considering environmental factors.You want to redefine the Supply Chain Network of your fast fashion retail company for the next five years.You have stores in 5 different markets worldwide (USA, Germany, Japan, India and Brazil).In each market, you can select a supplier to produce your t-shirts and choose to source from abroad.You would like to select the right set of suppliers to minimize the cost of production and delivery considering.Your overseas suppliers are cheaper, but you must pay high freight costs to deliver to your market with higher CO2 emissions for transportation.Moreover, the sustainability team has implemented constraints on maximum environmental impact per T-shirt produced including water usage, CO2 emissions, energy usage and waste generated.The sourcing team needs linear programming support to manage these complex tradeoffs and decide which suppliers to select.Let me illustrate my point with the example below, in which I will gradually add environmental constraints to see the impact on the footprint.If you define the objective function to minimize the costs without additional constraints, you can easily guess that it will maximize the volume produced in India and Brazil.💡 InsightsWhat if we want to add sustainability constraints?As your company implements a sustainability roadmap, you must add additional constraints limiting the environmental impact per T-shirt produced and delivered.Therefore, your procurement team has contacted local suppliers in your predominant markets (USA, Japan).What would be the impact on your sourcing network?We can start by adding constraints on the average energy and water consumption per unit produced.Your suppliers in Germany and Japan heavily invested in modern equipment to reduce the environmental impact of their operations.💡 InsightsWhat if we add CO2 emissions constraints?Transportation accounts for a considerable part of the CO2 footprint of your Supply Chain.Therefore, you would like to reduce the impact of upstream flows by limiting the CO2 emissions of💡 InsightsWith this simple exercise, you can get the potential of these solutions to accelerate the decision-making process by testing several scenarios.If you want to try it yourself, I have deployed this solution in a web application hosted on the VIKTOR platform.You can upload your dataset or use the sample available in the app to test different scenarios.For more details about this solution, have a look at this article published on Towards Data Science.towardsdatascience.comWhen implementing a green transformation, companies face many challenges related to change management and complex decision-making processes.As a data analytics professional, you can support this transformation by facilitating data collection and partially automating decision-making using optimization models.Sourcing teams can easily add constraints in their supplier selection process to follow the guidance of the sustainability team.By showing the financial impact of each scenario, you facilitate the decision-making process by highlighting the balance between sustainability and cost efficiency.These results can trigger strategic discussions to find the right balance between sustainable sourcing and cost reduction.Let’s connect on Linkedin and Twitter; I am a Supply Chain Engineer using data analytics to improve logistics operations and reduce costs.If interested in Data Analytics and Supply Chain, look at my website.samirsaci.com💡 Follow me on Medium for more articles related to 🏭 Supply Chain Analytics, 🌳 Sustainability and 🕜 Productivity.----Towards Data ScienceTop Supply Chain Analytics Writer — Follow my journey using Data Science for Supply Chain Sustainability 🌳 and Productivity ⌛HelpStatusAboutCareersBlogPrivacyTermsText to speechTeams

Data Science for Sustainable Sourcing. The first support you can provide to your sourcing team is to streamline the data collection and storage process using data analytics tools

Towards Data Science - Medium

Data Science for Sustainable Sourcing

Posted on Mar 7                  When creating websites or apps even those, with skills can make common errors.Whether it's overlooking responsiveness or neglecting security issues these missteps can impact performance and user satisfaction.Let's explore some of these traps and how to steer clear of them.NOTE: some analogies have been taken from ChatGPT to make the article more engaging.Just as too much construction can lead to traffic jams, excessive DOM manipulation can slow down your website.Imagine scrolling through a website on your phone, constantly zooming in and out just to read the text or click a button.Frustrating, right?That's why it's essential to prioritize responsiveness in design for a smoother user experience.To ensure your website loads quickly it's important to optimize performance by getting rid of any unwanted elements (like files) and following best practices.Imagine setting sail on a grand sea voyage, only to realize that your ship can't cruise certain waters.Like preparing for a voyage testing your website across browsers is necessary to avoid any compatibility issues.Close your eyes and imagine yourself using a website without being able to see the screen.That's why you should follow accessibility standards for inclusivity.Read more here.Without the right map and compass, your website as a treasure is destined to remain unexplored.So, use semantic HTML and meta tags for better search engine visibility.Without records of your progress, chaos would surely follow.Thus, you should always use version control, like Git, for code management.Sometimes, blindly using spells from a random book you found on the ground will just lead to the worst.So please, understand frameworks, and don't over-rely without comprehension.Neglecting security is like leaving the gates wide open, inviting trouble to come knocking.Accordingly, prioritize front-end security to prevent vulnerabilities.Imagine your code as a toolbox, neatly organized with each function and component designed for a particular task.This approach not only smoothens the development process but also enhances the effectiveness of our website.Avoid duplicating code; use functions or components for reusability.Ever wondered why your website isn't performing as well as it could? 🤔Or why do users seem frustrated with your app? 😠By asking yourself questions like these, you can make progress for smoother web experiences.I hope you liked the article! ❤️Connect with me: linktreeHappy Coding! 🚀Thanks for 18899! 🤗Templates let you quickly answer FAQs or store snippets for re-use.        Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.      Hide child comments as well                  Confirm              For further actions, you may consider blocking this person and/or reporting abuse              fajarriv - Mar 4                          Andrew Bone - Mar 4                          Samuel Lubliner - Mar 4                          Ollie Bannister  - Mar 4                  DEV Community — A constructive and inclusive social network for software developers. With you every step of your journey.    Built on Forem — the open source software that powers DEV and other inclusive communities.Made with love and Ruby on Rails. DEV Community © 2016 - 2024.          We're a place where coders share, stay up-to-date and grow their careers.

🔟 Things You Must Not Do In Frontend Development. Without the right map and compass, your website as a treasure is destined to remain unexplored

DEV Community

🔟 Things You Must Not Do In Frontend Development

Posted on Mar 7                  Hey there fellow devs! We all know that in the world of software development, productivity is key. Whether you're slinging code on the backend or crafting pixel-perfect UIs on the frontend, finding ways to get more done in less time is a universal goal. So, let's dive into some informal productivity tips that can help you supercharge your workflow, whether you're tinkering with databases or wrangling CSS.Backend Bliss: Making the Most of Your TimeAutomate All the Things: Don't waste time on repetitive tasks. If you find yourself doing something more than once, it's time to automate it. Whether it's setting up deployments with CI/CD pipelines or automating database migrations, automation can save you loads of time and effort.Use the Right Tools: Every backend dev has their favorite tools, whether it's an IDE, a database management tool, or a debugging tool. Find the tools that work best for you and stick with them. Don't be afraid to try new tools, but don't get bogged down in tool paralysis Know Your Services Inside and Out: Whether you're working with AWS, Google Cloud, or your own custom services, take the time to really understand how they work. Knowing the ins and outs of your services can help you troubleshoot issues faster and build more robust applications.Stay Organized: Keep your codebase clean and well-organized. Use consistent naming conventions, modularize your code, and comment liberally. A well-organized codebase is easier to navigate and maintain, saving you time and headaches in the long run.Frontend Finesse: Navigating the Wild World of Web DevelopmentMaster Your Framework: Whether you're a React junkie, an Angular aficionado, or a Vue virtuoso, take the time to really master your chosen frontend framework. Learn all the ins and outs, explore the latest features, and stay up-to-date with best practices.Stay Lean and Mean: Keep your frontend codebase lean and mean. Avoid bloat and unnecessary dependencies, and optimize your code for performance. Remember, every line of code you write is a potential source of bugs, so keep it simple and focused.Embrace CSS Like a Boss: CSS can be a beast, but don't let it intimidate you. Embrace the power of CSS preprocessors like Sass or Less, and explore the latest CSS frameworks and techniques. With the right tools and know-how, you can tame even the wildest of stylesheets.Test, Test, and Test Some More: Don't skimp on testing. Whether you're writing unit tests, integration tests, or end-to-end tests, testing is crucial for ensuring the reliability and stability of your frontend code. Embrace testing as a core part of your development process, and you'll thank yourself later.So there you have it, folks! Some informal productivity tips to help you crush it on both the backend and frontend. Whether you're automating deployments, mastering your favorite frontend framework, or wrangling unruly CSS, these tips can help you stay focused, efficient, and productive. So go forth and code like the wind, my friends!Templates let you quickly answer FAQs or store snippets for re-use.very nice article 😊 short, to the point, and while most of these may seem like common sense, you’d be amazed how often they aren’t used so all are worth stating! keep up the good work, mate!         Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.      Hide child comments as well                  Confirm              For further actions, you may consider blocking this person and/or reporting abuse              Scofield Idehen - Feb 20                          Marcus Ahlfors - Feb 7                          Web Genius - Feb 6                          MK - Feb 6                  DEV Community — A constructive and inclusive social network for software developers. With you every step of your journey.    Built on Forem — the open source software that powers DEV and other inclusive communities.Made with love and Ruby on Rails. DEV Community © 2016 - 2024.          We're a place where coders share, stay up-to-date and grow their careers.

Getting Stuff Done: Productivity Tips for Backend and Frontend Devs. Frontend Finesse: Navigating the Wild World of Web DevelopmentMaster Your Framework: Whether you're a React junkie, an Angular aficionado, or a Vue virtuoso, take the time to really master your chosen frontend framework.

Getting Stuff Done: Productivity Tips for Backend and Frontend Devs

Posted on Mar 7                      • Originally published at browsercat.com                   Visual tests are a powerful tool, but they're hell to work with in CI/CD. They're slow, flaky, a pain to debug, and difficult to maintain.Getting them going is no easy task. After all, you need some way to store the snapshots between runs, and you need some way to let your pipeline know when it's OK to update the snapshot cache.Thankfully, I took care of all this for you. :)This article solves all of these problems, and lays the foundation for you to take your visual tests to the next level.If you get value here, you'll love my Ultimate Guide to Visual Testing in Playwright. It covers advanced testing techniques, fine-tuning your snapshot configuration, and more.Let's get started...Your CI/CD environment is not like your local environment, and we should account for that in our Playwright configuration.Update your playwright.config.ts with the following options. Feel free to merge these with any other options you've set so far:Here's what's going on:Next, let's create a basic pipeline. It doesn't do everything (yet), but it's a solid foundation to work from.Create a file at .github/workflows/visual-tests.yml:Notice that we're running our tests with the --ignore-snapshots flag. Since we have no way to store snapshots between test runs, this is literally the only way to get our tests to pass.If you push your repo to Github now, this workflow will run, and it will pass, but it won't guarantee anything about your app.Let's remedy that...For our visual tests to work, we'll need to store snapshots between runs. For this, we'll cache them using Github's "artifacts" feature.Second, let's also write a step that generates new snapshots if they don't exist. This will solve the problem of our tests failing the first time they run on a branch.Third, let's stop ignoring our snapshot assertions.Here's the updates:Notice that our cache key includes the current branch as well as a fallback to the master branch. That way a new branch has some material to work from on the first push.If you trigger the pipeline now, on the first run, you'll see snapshots generated, the tests pass, and the cache updated. On subsequent runs, you'll see the cache hit, no new snapshots generated, and the tests still pass.Not bad, but what happens when the snapshots need to be updated?Now that we have visual tests that really work, let's change our workflow so that we can update snapshots on demand.First, let's parameterize our workflow...workflow_call allows us to manually trigger the workflow with or without updating snapshots. workflow_dispatch allows other Github workflows the same set of options.Here's what the manual widget looks like:Let's also update "Initialize snapshots" to trigger an update when this parameter is enabled:Lastly, let's upload our HTML report as an artifact, so that we can reference it before deciding if we should ask the workflow to update snapshots... or if we need to debug the problem:Notice that our "Test" step now enables continue-on-error, so that we can upload our report even if the tests fail.The new "Upload test report" step uploads the report as an artifact. In the workflow results, you'll see a direct link to a zip file containing our report.Things are going great, but there's one more thing we can do to make visual tests even better: make them blazingly fast!You've probably noticed two steps are slowing your pipeline down:Thankfully, we can fix both of these issues, and most-likely for free!BrowserCat hosts a fleet of Playwright browsers in the cloud that you can connect to with just a few lines of code.If you do so, you won't have to install browsers in your CI/CD environment, and you'll be able to run your tests entirely in parallel.And the best part? BrowserCat has an awesome forever-free plan. Unless you're running a huge team, you'll probably never have to pay a dime.So let's get started!First, sign up for a free account at BrowserCat.Second, create an API key and store it as a secret named BROWSERCAT_API_KEY in your Github repository. You can do this by navigating to your repository, clicking "Settings," then "Secrets," then "Actions," then "New repository secret."Third, let's update playwright.config.ts to use BrowserCat:In the updates above, you'll notice we've increased parallelization to 10 workers when using BrowserCat. This is a good starting point, but you can increase it significantly more without issue.Notice that this config connects to BrowserCat whenever BROWSERCAT_API_KEY is defined. This is useful for running tests locally, as well as in CI/CD.OK, now here's the last bit of magic... Let's stop installing Playwright's browsers every time we run our pipeline:If you run your pipeline now, you'll witness a dramatic speed-up, even with just a single test in your suite. And with 1000 free credits per month, you can run your pipeline for hours on end with plenty of time left over.You've got your CI/CD pipeline working. Now it's time to write some tests!Be sure to check out my Ultimate Guide to Visual Testing in Playwright for advanced snapshot testing strategies and ready-made solutions for running visual tests in CI/CD.In the meantime, happy testing!Templates let you quickly answer FAQs or store snippets for re-use.        Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.      Hide child comments as well                  Confirm              For further actions, you may consider blocking this person and/or reporting abuse              Karen Payne - Feb 24                          Clifton Beale - Feb 1                          Gregor Schafroth - Feb 1                          Mohamed Jubair - Feb 29                  DEV Community — A constructive and inclusive social network for software developers. With you every step of your journey.    Built on Forem — the open source software that powers DEV and other inclusive communities.Made with love and Ruby on Rails. DEV Community © 2016 - 2024.          We're a place where coders share, stay up-to-date and grow their careers.

How to Run Snapshot Tests in CI/CD with Playwright. If you run your pipeline now, you'll witness a dramatic speed-up, even with just a single test in your suite.

How to Run Snapshot Tests in CI/CD with Playwright

Posted on Mar 6                  The web evolves, so does the art of building web applications. Front end architecture in 2024 is about creating efficient, scalable, and user-friendly platforms. Let's cut straight to the chase and explore the seven pillars that are currently shaping the world of front end development.Front end architecture is now a complex field, with an emphasis on modular design, performance, and automation. The traditional ways of coding are being replaced with strategies that reflect the dynamic nature of the web. I'll guide you through these essentials, which are not merely trends but necessities for any modern web application.Gone are the days when design systems were a nice-to-have. In 2024, they're the blueprint for digital product design. A robust design system transcends mere component libraries, embodying a comprehensive design language that both designers and developers can speak fluently. From the simplicity of buttons to the complexity of widgets, a design system encompasses theming, typography, and icons, ensuring consistency and coherence throughout the application. Documentation is key here—each component meticulously explained for effortless reuse and extension.Imagine building with Lego blocks—each piece should snap together seamlessly, forming structures both simple and intricate. This is the essence of component reuse. By crafting components that can be reused across various segments of an application, we achieve a harmonious user interface with reduced development time. Transitioning to a composable platform means each independent block can be assembled into numerous configurations, providing the flexibility and scalability necessary for modern web applications.The performance of a web application can captivate or repel users. Optimizing assets is not just a technical duty; it's a user-centric mantra. From the compression of images to the minification of JavaScript and CSS, asset optimization directly influences user experience and search engine rankings. The key to mastery? Utilize performance tools that offer strategic insights, ensuring that every image, script, and stylesheet is a sprinter, not a jogger, in the race for efficiency.Caching is not just a technical process; it's an art that enhances the responsiveness of a web application. By storing pieces of information across different levels—from browsers to networks—we can deliver content at lightning speed. Service workers, CDN caching, and browser caching are the unsung heroes here, quietly working behind the scenes to ensure users access content swiftly and smoothly.Tools such as the Chrome Developer Console are the telescopes through which we observe the performance universe of our applications. They provide critical insights into asset impact and application behavior. By employing strategies like CSS minification and leveraging modules, we can not only improve load times but also enhance the user's perception of speed—a crucial factor in the user experience equation.As architects of the digital domain, we must write code that grows with our ambitions. Scalable and maintainable code ensures our applications can expand without crumbling under their own weight. It's about embracing best practices and patterns that have stood the test of time, like MVC or Flux, to structure our applications in a way that future-proofs them against the relentless tide of change.CI/CD pipelines are the conveyor belts of our deployment factories. They automate the mundane but critical processes of building, testing, and deploying applications, ensuring that new features and fixes are delivered rapidly and reliably. Tools like Jenkins, GitLab CI/CD, and GitHub Actions are the workhorses of this operation, driving the relentless march towards improvement and innovation.What is a design system and why is it crucial?A design system is a collection of reusable components guided by clear standards that can be assembled together to build any number of applications. It's crucial because it creates a shared language for teams and ensures consistency across products.How does component reuse benefit frontend architecture?Component reuse streamlines development, ensures UI consistency, and accelerates the development process by allowing developers to leverage existing elements rather than creating new ones from scratch.Why is asset optimization important?Asset optimization enhances user experience by speeding up load times and improving performance, which can also positively impact search engine optimization (SEO).What does caching do for a web application?Caching stores copies of files and data to speed up retrieval on subsequent requests, which reduces server load and improves application responsiveness.How can performance measurement tools impact frontend architecture?Performance measurement tools provide insights into how well an application is running, allowing developers to identify bottlenecks and optimize code for better performance.What makes code scalable and maintainable?Scalable and maintainable code is well-organized, follows best practices, and is built using patterns that accommodate growth and facilitate easy updates and maintenance.What's the purpose of continuous integration and deployment in frontend architecture?Continuous integration and deployment streamline the development process by automating the integration of code changes, ensuring that the application is tested and ready to ship at any moment, thus reducing manual errors and speeding up release cycles.In conclusion, the essentials of front end architecture in 2024 revolve around creating systems that are not only efficient and robust but also adaptable to future demands. As technology advances, these principles serve as a compass in a developer's toolkit, guiding them to build applications that are not only functional but also poised for growth and innovation.Check out our agency site, Cox Code: https://www.coxcode.ioDialogue with me on X: @benajaeroTemplates let you quickly answer FAQs or store snippets for re-use.        Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.      Hide child comments as well                  Confirm              For further actions, you may consider blocking this person and/or reporting abuse              Apostrophe - Feb 16                          Himanshu Gupta - Feb 28                          Hritam Shrivatava - Feb 29                          Méschac Irung - Feb 15                  DEV Community — A constructive and inclusive social network for software developers. With you every step of your journey.    Built on Forem — the open source software that powers DEV and other inclusive communities.Made with love and Ruby on Rails. DEV Community © 2016 - 2024.          We're a place where coders share, stay up-to-date and grow their careers.

7 Essentials for Front End Architecture in 2024. From the compression of images to the minification of JavaScript and CSS, asset optimization directly influences user experience and search engine rankings.