tkachenko1503 · April 21, 2020 10:35 · Apr 28, 2018 · Apr 28, 2018 · Apr 28, 2018 · Apr 28, 2018
diff --git a/why-do-we-need-types-in-javascript.md b/why-do-we-need-types-in-javascript.md
@@ -1,4 +1,4 @@
-### This is my lightning talk submission for ReactiveConf 2018 https://reactiveconf.com/
+### This is my lightning talk submission to ReactiveConf 2018 https://reactiveconf.com/
 
 
 In this talk, I want to share my experience gained during the development of frontend applications in several programming languages.

diff --git a/why-do-we-need-types-in-javascript.md b/why-do-we-need-types-in-javascript.md
@@ -2,6 +2,10 @@
 
 
 In this talk, I want to share my experience gained during the development of frontend applications in several programming languages.
-I think it's not a secret for anybody that developing large JavaScript applications is not so easy as it seems at first glance. We all want something simpler and more reliable. Therefore, many developers and even entire companies switch to different, compiled in JavaScript, programming languages. The bulk of such transitions is accounted for TypeScript and flow, and often, developers faced with more problems than they were before.
+
+I think it's not a secret for anybody that developing large JavaScript applications is not so easy as it seems at first glance. We all want something simpler and more reliable. Therefore, many developers and even entire companies switch to different, compiled in JavaScript, programming languages. The bulk of such transitions is accounted for TypeScript and flow, and often, developers faced with more problems than they were before.
+
 I wasn't the exception. Moving to a new project, I started using TypeScript and was disappointed.
-Luckily in my next project I used ClojureScript and it was like everything is illuminated! Since then, I know exactly what the recipe for simple and reliable code (even in plain old JavaScript). And I want to share this recipe with you.
+Luckily in my next project I used ClojureScript and it was like everything is illuminated! 
+
+Since then, I know exactly what the recipe for simple and reliable code (even in plain old JavaScript). And I want to share this recipe with you.
diff --git a/why-do-we-need-types-in-javascript.md b/why-do-we-need-types-in-javascript.md
@@ -1,19 +1,7 @@
-### This is my lightning talk submission for ReactiveConf 2018 https://reactiveconf.com/  
+### This is my lightning talk submission for ReactiveConf 2018 https://reactiveconf.com/
 
-Plan:
-- Intro (1m)
-- Problem (1m)
-- Solution (2m)
-- Recipes (1m)
 
-Problems with types:
-- UI development cycle should be as fastest as it can be
-- Hiding problems, but not solving them
-- Trying to recreate whole universe (always from skratch)
-
-Alternatives to types:
-- Separate behavior from data structures
-- Use immutable data structures
-- Use better abstractions (generic methods, functors and monads)
-- Don't overuse design patterns
-- Use TDD
+In this talk, I want to share my experience gained during the development of frontend applications in several programming languages.
+I think it's not a secret for anybody that developing large JavaScript applications is not so easy as it seems at first glance. We all want something simpler and more reliable. Therefore, many developers and even entire companies switch to different, compiled in JavaScript, programming languages. The bulk of such transitions is accounted for TypeScript and flow, and often, developers faced with more problems than they were before.
+I wasn't the exception. Moving to a new project, I started using TypeScript and was disappointed.
+Luckily in my next project I used ClojureScript and it was like everything is illuminated! Since then, I know exactly what the recipe for simple and reliable code (even in plain old JavaScript). And I want to share this recipe with you.
diff --git a/why-do-we-need-types-in-javascript.md b/why-do-we-need-types-in-javascript.md
@@ -13,6 +13,7 @@ Problems with types:
 
 Alternatives to types:
 - Separate behavior from data structures
+- Use immutable data structures
 - Use better abstractions (generic methods, functors and monads)
 - Don't overuse design patterns
 - Use TDD
diff --git a/why-do-we-need-types-in-javascript.md b/why-do-we-need-types-in-javascript.md
@@ -1,5 +1,11 @@
 ### This is my lightning talk submission for ReactiveConf 2018 https://reactiveconf.com/  
 
+Plan:
+- Intro (1m)
+- Problem (1m)
+- Solution (2m)
+- Recipes (1m)
+
 Problems with types:
 - UI development cycle should be as fastest as it can be
 - Hiding problems, but not solving them

diff --git a/why-do-we-need-types-in-javascript.md b/why-do-we-need-types-in-javascript.md
@@ -1 +1,12 @@
-This is my lightning talk submission for ReactiveConf 2018 https://reactiveconf.com/
+### This is my lightning talk submission for ReactiveConf 2018 https://reactiveconf.com/  
+
+Problems with types:
+- UI development cycle should be as fastest as it can be
+- Hiding problems, but not solving them
+- Trying to recreate whole universe (always from skratch)
+
+Alternatives to types:
+- Separate behavior from data structures
+- Use better abstractions (generic methods, functors and monads)
+- Don't overuse design patterns
+- Use TDD
diff --git a/why-do-we-need-types-in-javascript.md b/why-do-we-need-types-in-javascript.md
@@ -0,0 +1 @@
+This is my lightning talk submission for ReactiveConf 2018 https://reactiveconf.com/
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		This is my lightning talk submission for ReactiveConf 2018 https://reactiveconf.com/