Boosted Embeddings with Catboost

Introduction

When working with a large amount of data, it becomes necessary to compress the space with features into vectors. An example is text embeddings, which are an integral part of almost any NLP model creation process. Unfortunately, it is far from always possible to use neural networks to work with this type of data — the reason, for example, maybe a low fitting or inference rates.

I want to suggest an interesting way to use gradient boosting that few people know about.

#330: New Admin Tools

Chris & Marie talk about a big long project that we’ve finished at CodePen: our new Admin Tools. Any web app is gonna need ’em. They do stuff that is unique to customer service on your app. Say you need to manually trigger a password reset email or hand-verify an account. You look them up in an Admin Tool, and perform those specialized actions. Our Admin Tools are heavily focused on users and content. We’ve totally re-built them to focus on the UX of actually doing customer support, as well as to make a clean UI that users the same componentry that the main CodePen app does. We do a lot of spam cleanup in our Admin Tools as well, so getting a chance to re-think those experiences was satisfying.

We dove into this project not just to make customer support better, but because of an alignment of concerns. We got to use a whole new development stack to do this, using technology we wanted to prove out for more of CodePen. We used Next.js on the front end and for server side rendering, and a Go-powered GraphQL API for the data. We made it all work in our monorepo. We build tools for deployment, so in a cool twist of fate, this app can deploy itself.

  • 01:06 Working on internal tools
  • 02:50 How do we pick things to work on?
  • 08:16 Admin tools specific to CodePen support
  • 12:33 Sponsor: Mailpoet
  • 14:31 Benefits of mono repo development
  • 20:27 Figuring the perfect UX with a team
  • 25:25 Early detection of spam users
  • 29:00 Multiple CMS built in

Sponsor: Mailpoet

If you build your website and business around WordPress, you’re in good hands for a lot of reasons. One of which is that you own your site, you own your own data, you own all aspects of what powers your business, and the rug can’t get pulled out from under you entirely. Check out this article and video on how to make a paid subscription newsletter with WordPress + WooCommerce + Mailpoet. That is a business model right there, from which you can grow forever entirely under your control.

The post #330: New Admin Tools appeared first on CodePen Blog.

WordPress Classic Editor Support Extended for at Least Another Year

Last week, I reached out to several members of the core WordPress committers to see if we could get an official word on whether Classic Editor support would continue beyond the mere months it seemingly had left to live. I received a semi-official answer but was asked to hold off on publishing for a more detailed and nuanced response.

Earlier today, WordPress executive director Josepha Haden Chomposy announced the official decision. It was just as expected. The WordPress project would continue supporting the Classic Editor plugin for a while longer.

“At the time, we promised to support the plugin through 2021 and adjust if needed as the deadline got closer,” she wrote. “After discussing this with Matt [Mullenweg], it’s clear that continuing to support the plugin through 2022 is the right call for the project as well as the community.”

As of now, classic users have a one-year extension.

However, the plugin will not suddenly stop working on December 31, 2022. That is merely the current deadline for the “full support” phase. It should continue working well beyond whatever date is set for that support window to close.

Designer Mark Root-Wiley reached out to WP Tavern via Twitter last week, but others had been asking the same question for a while. For some, they needed to know if they could continue supporting specific client needs. For others, it was a bludgeon to use in conversations for all editor-related things. Whatever the reason, before today, the last word had been from a Make Core post in November 2018.

“The Classic Editor plugin will be officially supported until December 31, 2021,” wrote core contributor Gary Pendergast in that three-year-old announcement. It was a shock for many at the time, uncertain whether the new block system would meet their needs.

While three years may have seemed like plenty of time to ditch the classic in favor of the modern WordPress editor, the current stats show that the project still has a few miles yet to go.

Currently, there are over 5 million active installations of the Classic Editor plugin. I am still waiting for a more specific tally, but no one has provided an answer yet. At best, we think the counter turns over at 10+ million, so we can speculate on the floor and ceiling for possible usage.

Active installs are not the entire picture either. For example, we have the plugin installed here at the Tavern for legacy reasons but do not use it in our day-to-day work. We can likely disable it altogether. WordPress has no telemetry system for tracking the usage of such features. While the install total will not always make the picture clear, the current number supports the push for continued maintenance.

“I think it’s important to note that the plugin is not going anywhere,” said core committer Jonathan Desrosiers. “It will continue to be listed on the .ORG repository for the foreseeable future.”

He pointed out that understanding the next phase of the Classic Editor plugin meant looking into the level of effort required to support it since 2018. The overwhelming majority of the changes in that nearly three-year timeframe have come down to keeping up with:

  • Text changes.
  • Adjustments to prevent warnings/errors and promote consistency across supported PHP versions.
  • Changes to deprecated action/filter hook calls.

“It’s been almost three whole years, and the plugin has largely required very little maintenance to continue functioning, and the bulk of maintenance has been to limit warnings and notices in debug logs,” he said.

The goal of the Classic Editor plugin was to help ease the transition to the block editor. Thus far, there have been eight major WordPress releases since the switch in version 5.0.

“There’s a theory called the diffusion of innovations that looks to explain how, why, and at what rate new technology spreads,” said Desrosiers. “It separates adopters into several groups based on when they are willing to take the jump: innovators, early adopters, early majority, late majority, and laggards. I truly think that we have seen a good portion of the late majority beginning to move towards using the block editor. This can also be confirmed by the plugin’s install growth, which has been slowing and plateauing this year.”

He had expected the previous deadline to mark the next stage of the Classic Editor plugin, called the “sunset” phase. It would be a time when the WordPress project moved from full support to encouraging late adopters to transition to the current editor to get the plugin’s numbers down.

“The context I gave previously shows that, until now, that the level of effort needed to keep the plugin working on newer versions of WP has been pretty minimal,” said Desrosiers of the potential sunset phase. “I expect that pattern to continue thanks to backward compatibility. If any security issues or major problems are encountered, they’ll, of course, be fixed. Any incompatibilities with the plugin and newer versions of WP will be considered on a case by case basis, but little to no time will be put towards bug fixes.”

However, this sunset phase will have to wait. We will not see it until at least the current support window closes on December 31, 2022. WordPress project leaders will need to reevaluate the plugin’s lifespan at that point.

The other looming question would be whether core WordPress would move specific pieces of its system to the Classic Editor plugin, such as allowing custom post types to support the old editor or the meta box API.

“There are no plans at this time to move any of the underlying ‘classic’ parts from core to the plugin,” said Desrosiers. “I’m sure that removing these parts will be evaluated at some point in the future, but when that will be is not clear.”

Even when official Classic Editor support reaches a hard deadline, it does not mean such a traditional editing experience will cease to exist. Plugins like Disable Gutenberg have promised longer lifespans than the initial support window, and other editor projects will undoubtedly arise if there is wide enough demand.

“The block editor has come a long way, and I encourage everyone that has not yet given it a second chance (late adopters) to do so,” said Desrosiers. “You may be pleasantly surprised.”

Cognitive AI Meets IoT: A Match Made in Heaven

Over the last decade, the Internet of Things (IoT) has caused widespread disruption in every sphere of our life. The evolution of IoT is not influenced by advancement in the unique technology segment; instead, a series of emerging technologies and innovation trends have converged together to create a unified experience of the ubiquitous world. The emergence of Edge computing, the 5G/ 6G revolution, and cloud computing have introduced a set of architectural patterns to minimize latency, network bandwidth requirements and allowed systems to scale beyond the limit. In the world of ‘new normal, the endless opportunities with both business and social transformations will weave IoT applications into our everyday life with billions of sensors seamlessly interacting with each other. Big Data and advanced analytics have transformed the massive volume of sensory signals and multimedia feeds into actionable insights and new revenue streams across the digital value chains.

A rapid expansion in exposing pervasive channels and deploying intelligent automation have brought critical challenges towards the future of digital transformation in the 21st century. The promising applications of AI and ML are mostly executed within the centralized cloud ecosystem, far from the point of action. Such intelligence is not designed to gain situational awareness from within the operating landscape. Harnessing the benefit of capturing and analyzing temporal data and timely interpretation of sensory events within the active window of the operational cycles are emerging as the key imperatives to gain strategic advantage and address cybersecurity concerns. As the diversity of sensors and applications grow exponentially, structured intelligence or prebuilt rule-based automation deployed in the edge runtime will not be efficient and extensible to elevate process automation and autonomic functions.

Microservice Architecture and Agile Teams

Let us glance into the below Principles of Agile

  • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  • Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale.
  • Working software is the primary measure of progress.
  • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  • Continuous attention to technical excellence and good design enhances agility.

When we would like to implement all the principles for the Agile team, how satisfied it would be when a team gets some natural technology booster?

Top 10 Low-Code Articles

Introduction

Creating a business/personal website with little to no technical skills is now easier than you imagined. Low/No Code has been brewing amongst us for quite some time. How awesome would it be to find top trending articles in one place so that you can always stay up to date with the latest trends in technology? We dug into Google analytics to find the top 10 most popular Low/No Code articles at DZone. Let's get started!

10. Can Low-Code Really Solve the Problem of Technical Debt?

Technical debt is the topic of debate when developing any application. Should the team follow the guidelines and code quality or take a quicker route to delivery and result. Code cannot be called a quality code unless all of its debt is settled. As Low-code allows the developers to create applications with minimal code, can it resolve the problem of technical debt? Read this article to know more about Low-code and if it is a way to overcome technical debt.

Will AGI take jobs or will it evolve jobs and create new industries?

Hi Guys,

Will AGI take all jobs that are currently done by humans? Maybe it will eliminate most jobs that don't have a technical background or most low-medium skilled jobs?

I am not talking about A.I as it is today or ASI but in the future lets say 2060

Or humans will be able to adapt to AGI and find new sorts of work in an emerging industry or re-skill and change their nature of their work or AGI may even complement humans but not replace them

Or AGI is over-hyped and it will only ever slightly increase unemployment rate from the current percentage now to 20%-40% worldwide

Or there will be a utopia in 2060 where people get a universal basic income and where people do whatever they want such as travel, gaming etc and let AGI take all the jobs and everyday will be like a weekend/public holiday.

Many Thanks

What Is Functional Programming? | The Easy Way

Hey everyone, I am Ryan Roy. In this blog, I’m going to explain what functional programming is and I promise you that after watching this blog, it’s going to be absolutely simple and a breeze to understand what functional programming is.

In every single functional programming blog, you’re going to see that it says in functional programming, we treat functions as first-class citizens. To the point, it is absolutely 100% accurate. Sometimes, these phrases get so much popularity that you start wondering what it means and whether someone can tell you in plain, simple language.

Emitting Vue.js events in Typescript

Vue.js allows users to emit an event from a child component and react to it in parent component via this.$emit('event-name') . While this works like a charm when being used directly in components, it does create an issue when working with TypeScript.

Understanding the Issue

Let’s assume (based on my private code) that:

How Do You Test Your Tests

Software today has shifted far from the monoliths of the past towards microservices. Microservices have many benefits over monoliths. They are more flexible, scalable and generally enable developers to add features more quickly. Unfortunately, testing cloud platform microservices is more complicated than it was in the monolithic ancestors. 

For cloud services, functional, integration, and unit tests are performed by creating a lower-level version of your function and plugging in inputs. The outputs from the function can show how your logic and infrastructure performed during the test. 

How To Improve Website Loading Speed

Website Speed Optimization is always an important job that a Marketer cares about to optimize the user experience and improve rankings on the Google search results page, as well as other aspects in Digital Marketing. Is your website experiencing slow loading? Severe customer loss? Then the following 10 tips on how to increase website speed are for you!

Apply AMP and PWA To Optimize Your Website

This is one of the ways to increase the speed of outstanding websites that Professional Web Development Companies often apply. To help you better understand the two terms above, the next content will explain in detail the two terms above.

Localization in Android

What Is Localization?

Localization is more than just the translation of the strings in your application in other languages. The locale is a combination of the language and the country.

In this tutorial, we will walk through the basic steps for Android localization with Android Studio.

How To Convert an OST File to PST File Manually

In offline (Cached Exchange) mode, Microsoft Outlook stores all Exchange mailbox data in a local file termed OST file. When the Exchange connection is re-established, the modifications made by the user in offline mode are updated to the server mailbox. Exchange Server failures and catastrophes, Exchange mailbox deletions, and other events have no effect on the OST file because it is stored on the user's PC. As a result, in the case of a disaster, Exchange administrators and end-users can use OST files to restore user mailbox data.

Scenarios in Which Converting an OST File to a PST File Is Beneficial:

  • A small number of Exchange mailboxes are removed from the server.
  • A couple of Exchange mailboxes need to be backed up. 
  • An Exchange user wishes to rebuild his OST file, however, there is some data in the OST file that has not been preserved.
  • Due to Exchange corruption, server crashes, and other factors, OST files are unavailable, and users require immediate access to their emails.

If you can log in to Outlook with the same Exchange profile, you can convert any OST file to PST using one of many techniques. Here are several natural techniques for converting OST to PST:

How To Implement and Design Twitter Search Backend Systems using Java Microservices?

Twitter is the largest and one among the most important social networking service where users can share photos, news, and text-based messages. In this article, I have explained in this blog about designing a service which, will store and search user tweets.

What do you mean by Twitter Search and how this functionality works?

Twitter users can update their status whenever they want to update irrespective of time. Each status or we can say it as Tweets consists of a plain string or test, and I intend to design a system that allows searching over all the user tweets. In this blog, I have given importance to the Tweet Search Functionality.