The Secrets of Productive Developer Tools | by François Chollet

The Secrets of Productive Developer Tools | by François Chollet | Kaggle Days San Francisco

Рет қаралды 8,284

5 жыл бұрын

François Chollet
"The Secrets of Productive Developer Tools"
Kaggle Days San Francisco held in April 2019 gathered over 300 participants to meet, learn and code with Kaggle Grandmasters, and compete in our traditional offline competition.
This edition is presented by LogicAI with sponsorship from Kaggle and Google Cloud.
Kaggle Days are a global series of offline events for seasoned data scientists and Kagglers created by LogicAI and Kaggle.
About the presenter:
François Chollet is the Creator of Keras (keras.io), a leading deep learning API, and author of the textbook “Deep Learning with Python”. He is also a machine learning researcher at Google Brain and a contributor to the TensorFlow machine learning platform.
About LogicAI:
LogicAI as a creator of Kaggle Days is a sole partner of Kaggle to build global offline community.
LogicAI is a boutique Data Science consultancy company owned by Kaggle fans and Grandmasters. As a global company, they do custom end-to-end AI and Data Science development projects as well as trainings for C-level management and tech teams.
Want help with your AI projects or want to work with LogicAI to create AI strategies? Simply apply at logicai.io!
Follow LogicAI online:
Visit the WEBSITE: logicai.io/
Like LogicAI on FACEBOOK: LogicAI-147154915962100/
Check out our BLOG: logicai.io/blog/
Connect with us on LINKEDIN: www.linkedin.com/company/logicai/
Follow Kaggle Days online:
Visit the WEBSITE: kaggledays.com/
Like Kaggle Days on FACEBOOK: KaggleDays/
Follow Kaggle Days on TWITTER: Kaggle_Days
Connect with Kaggle Days on LINKEDIN: www.linkedin.com/company/kaggle-days/
SUBSCRIBE: kzfaq.info&
About Kaggle:
Kaggle is the world's largest community of data scientists. Join us to compete, collaborate, learn, and do your data science work. Kaggle's platform is the fastest way to get started on a new data science project. Spin up a Jupyter notebook with a single click. Build with our huge repository of free code and data. Stumped? Ask the friendly Kaggle community for help.
Follow Kaggle online:
Visit the WEBSITE: www.kaggle.com/?
Like Kaggle on FACEBOOK: kaggle?
Follow Kaggle on TWITTER: kaggle?
Check out our BLOG: blog.kaggle.com/?
Connect with us on LINKEDIN: www.linkedin.com/company/kaggle?
Advance your data science skills:
Take our free online courses: www.kaggle.com/learn/overview?
Get started with Kaggle Kernels: www.kaggle.com/docs/kernels?
Download clean datasets from Kaggle: www.kaggle.com/docs/datasets?
Sign up for a Kaggle Competition: www.kaggle.com/docs/competitions?
Explore the Kaggle Public API: www.kaggle.com/docs/api?
Kaggle
kzfaq.info

Пікірлер: 4

@drbokka 3 жыл бұрын

Notes from the talk for the benefit of other viewers: One Principle: Every design decision should be made with the user in mind. Three Rules: 1. Deliberately design end-to-end workflows focused on what users care about. 2. Reduce cognitive load for your users 3. Provide helpful feedback to your users Additional Notes for Each of the Rules: 1. Deliberately design end-to-end workflows focused on what users care about. Good APIs are designed as holistic workflows, not as a set of atomic features Good APIs closely map to domain-specific notions that users are familiar with User-centric design is solution-oriented Checkbox-driven APIs are problem-oriented 2. Reduce cognitive load for your users Good software makes hard things simple Poor software makes simple things hard Automate everything that can be automated Minimize the amount of user input: infer what can be inferred Reduce number of steps in each end-to-end workflow Make steps simple to remember, consistent, intuitive Use consistent and standard naming conventions Provide good defaults. Good software works out of the box. Introduce as few new concepts as possible. Litmus test: If the cognitive load of a workflow is sufficiently low, it should be possible for a user to go through it from memory without looking up a tutorial or documentation after having done it once or twice. 3. Provide helpful feedback to your users Have a place where users can ask questions Invest in high-quality documentation Catch user errors early and anticipate common mistakes Provide detailed feedback upon user error A good error message should answer: What happened, in what context? What did the software expect? How can user fix it?