[airflow-site] branch aip-11 updated: Add new sample blog post (#127)

[ka...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

kamilbregula pushed a commit to branch aip-11
in repository https://gitbox.apache.org/repos/asf/airflow-site.git


The following commit(s) were added to refs/heads/aip-11 by this push:
     new 82148f0  Add new sample blog post (#127)
82148f0 is described below

commit 82148f01f2b3cb86a928f2469e8c84d92e2c3dd2
Author: Kamil Breguła <mi...@users.noreply.github.com>
AuthorDate: Wed Nov 6 12:52:13 2019 +0100

    Add new sample blog post (#127)
---
 ...Its-a-breeze-to-develop-apache-airflow.md => Grumpy-cat.md} | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/landing-pages/site/content/en/blog/Its-a-breeze-to-develop-apache-airflow.md b/landing-pages/site/content/en/blog/Grumpy-cat.md
similarity index 97%
rename from landing-pages/site/content/en/blog/Its-a-breeze-to-develop-apache-airflow.md
rename to landing-pages/site/content/en/blog/Grumpy-cat.md
index cf7c326..233741a 100644
--- a/landing-pages/site/content/en/blog/Its-a-breeze-to-develop-apache-airflow.md
+++ b/landing-pages/site/content/en/blog/Grumpy-cat.md
@@ -1,6 +1,6 @@
 ---
-title: "It's a breeze to develop Apache Airflow"
-linkTitle: "It's a breeze to develop Apache Airflow"
+title: "Grumpy cat"
+linkTitle: "Grumpy cat"
 author: "Jarek Potiuk"
 description: "Working on an Open Source project such as Apache Airflow is very demanding but also equally rewarding when you realize how many businesses use it every day."
 tags: ["Community"]
@@ -30,9 +30,15 @@ How do you define productivity though? And how can you measure it? I have a poss
 
 I could think of a number of projects where I followed that philosophy of work and where it boosted the productivity of my team. Today, however, I’d like to focus on Apache Airflow.
 
+{{< youtube 8IHLQxOghUQ >}}
+
 ##### The Apache Airflow project’s setup
 Initially, we started contributing to this fantastic open-source project with a team of three which then grew to five. When we kicked it off a year ago, I realized pretty soon where the biggest bottlenecks and areas for improvement in terms of productivity were. Even with the help of our client, who provided us with a “homegrown” development environment it took us literally days to set it up and learn some basics.
 
+{{< gist spf13 7896402 >}}
+
 Apache Airflow is a thoroughly tested project—it has almost 4,000 tests with around 80% coverage and varying complexity (from simple unit tests to end-to-end system tests). Airflow follows a modern software project philosophy: every single Pull Request can only be merged if all the tests pass. But that creates another problem—having to run all the tests for all the backends (there are 3 of them) and different python versions. At the time of starting the project we still supported 2.7, 3. [...]
 
 This is hardly acceptable to any developer. Usually you can work on several issues in parallel. Such waiting is not the worst thing that can happen, but there are always costs of context-switching, distractions, getting out of the flow and the good old “I already forgot what I was doing” phase by the time the build is completed. It’s even worse when you want to make a small Pull Request. For example, when you find a bug and have just one line of fix for it. You submit the Pull Request an [...]
+
+{{< tweet 1189242550403653632 >}}