HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
alteryx
featuretools
Python2017–2023
alteryx / featuretools

featuretools

An open source python library for automated feature engineering

7Distinct people
38Mentions
1Explicit recommenders
7.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An open source python library for automated feature engineering

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

To get started, I'd pick the most important business problem you have and then solve it using the simplest machine learning approach. You mentioned using Pytorch. Instead, I…

kmax12 used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year38 dated mentions

Observed mentions: 2017-11-06 14:51:21 UTC to 2023-09-20 21:40:24 UTC.

051015202017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 19 mentions; 0 submissions, 19 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC716
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC19019
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC707
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC404
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC110

What Hacker News says

7 sources
I worked on building a python library for automated feature engineering called Featuretools (https://github.com/featuretools/featuretools/). I had been working on it for 2 years, but in 2017 we separated it from the rest of the codebase and made it open source. Even though feature engineering is crucial for building machine learning pipelines, there are few formal methods for performing feature engineering. We see Featuretools filling a missing component in the software engineering stack for data science. It has already been put to the test with our customers at my company, but we have also begun to release demos so that others can pick it up https://www.featuretools.com/demos.
In Ask HN: What did you work on in 2017?
This is absolutely correct! After spending a lot of time trying to understand why building machine learning models is so difficult, I came to the same conclusion that "feature engineering" is the key to building high performing models. While feature engineering's importance is generally recognized [0], it's unfortunate that there aren't more tools and formal methods for applying it. Personally, I am a developer of an open source python library called Featuretools (https://github.com/featuretools/featuretools/) that is trying to change this for tabular and multi-table datasets. We are working hard to make automated feature engineering available to everyone and have a list of demos for people to try here: https://www.featuretools.com/demos. It's also worth noting that deep learning is changing the need for feature engineering. However, it p
Read the rest
rimarily works in cases where you don't need interpretable features and you have plenty of data. This means that it's biggest success have been in images, audio, and text problems. For all other use cases feature engineering is still a necessary step for applying machine learning. [0] https://bit.ly/things_to_know_ml
In Machine Learning for Dummies
As someone who works with a lot of people new to machine learning, I appreciate guides like this. I especially like the early slides that help frame AI vs ML vs DL so that people can have a realistic understanding of what these technologies are for. For my part, one of the biggest realization I had after many years of applying machine learning was that I got too caught up in the machine learning algorithms themselves. I was often way too eager to guess and check across different algorithms and parameters in search of higher accuracy. Fortunately, there are new automated tools today that can do that automatically. However, the key piece of advice I'd give someone new to machine learning is not to get caught up in the different machine learning techniques (SVM vs random forrest vs neural network, etc). Instead (1) spend more time on transla
Read the rest
ting your problem into terms a machine can understand (i.e how are you defining and generating your labels) and (2) how do you perform feature engineering so the the right variables are available for machine learning to use. Focusing on these two things helped me build more accurate models that were more likely to be deployed in the real world. Feature engineering in particular has become a bit of a passion of mine since that realization. I currently work on an open source project called Featuretools (https://github.com/featuretools/featuretools/) that aims help people apply feature engineering to transactional or relational datasets. We just put out a tutorial on building models to predict what product a customer will buy next, which is a good hands on example to learn from https://github.com/featuretools/predict_next_purchase for beginners.
In Machine Learning 101 slidedeck: 2 years of headbanging, so you don't have to
It somewhat depends on if you are looking to build AI to address business problems or if you are more interested in the type of AI work you see companies like Google discussing. I can speak to what "AI" means for most businesses outside Top Tech which more frequently work with tabular, relational, or log data rather than image and text. For these companies, this is what you need to learn how to do 1. Define a prediction problem and extract labels 2. Organize and clean the data for prediction 3. Perform feature engineering by applying domain expertise 4. Apply an off-the-shelf open source machine learning algorithm like a random forest Assuming you have access to data and programming skills to clean your data, defining prediction problems and performing feature engineering are the most important skills you have to pick up.
Read the rest
For machine learning you can you use open source libraries like scikit-learn or tensorflow. At my company, we've noticed a lot of programmers are intimated by the feature engineering step in particular, so we tried to make it easier by creating an open source library called Featuretools [0]. [0] https://github.com/featuretools/featuretools
In Ask HN: Best way to get started with AI?
I think this highlights the disconnect between AI researchers and industry. This research focuses on image data and then makes the claim that they want to use it to enable millions of businesses to solve problems with machine learning. However, image data isn't what most businesses are using for machine learning. They use relational datasets. If you look at the recent "State of Data Science" by Kaggle, relational data is ~3x more common than image data in every industry besides academia and the military [0]. While Google wants to 1000x the number of organizations using AI, they aren't focusing on the problems companies actually have. Basically, academics love building AI for images, but what companies really need are better ways to build AI systems on tabular and relational data. Images will be a piece, but shouldn't be the focus. Disclai
Read the rest
mer: my company develops an open source library called Featuretools [1] to automate feature engineering for data with relational structure. [0] https://www.kaggle.com/surveys/2017 [1] https://github.com/featuretools/featuretools
In Building A.I. That Can Build A.I

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.