You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+24-1Lines changed: 24 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ I have contributed to software experiences for **Adobe Systems**, **Zumba Fitnes
15
15
16
16
It's easy to find people with JavaScript experience. It's extremely hard to find JavaScript developers who really understand the craft of building great applications.
17
17
18
-
*99 out of 100 candidates I've interviewed lack the qualifications to hit the ground running.*
18
+
*99 out of 100 candidates I've interviewed lack the qualifications to hit the ground running.* The fact is, [JavaScript Training Sucks](https://medium.com/javascript-scene/javascript-training-sucks-284b53666245). That's the problem we're solving with these courses.
19
19
20
20
To fix that, I wrote a book called [“Programming JavaScript Applications”](http://pjabook.com) (O’Reilly). It's finished and shipping, and it's already helping a great deal... but it's not approachable for novice JavaScript developers-in-training.
21
21
@@ -32,6 +32,29 @@ What we need is a solution that can guide programmers of any skill level from th
32
32
***Collaboration** Create an agile study group to share encouragement and tutoring as you progress.
33
33
34
34
35
+
### JavaScript Software Testing with Sauce Labs *(est launch: before the end of February, 2015)*
36
+
37
+
***The only thing that matters in development is that users love the product.***
38
+
39
+
This course is **a step-by-step guide to building a product that users will love.** These lessons are hard won over a long career, and borrow heavily from many other software development teams who have contributed to the emergence of **lean startup culture** that has transformed Silicon Valley, and **transformed the way large enterprise organizations produce great products, too.**.
40
+
41
+
I have worked at **organizations that failed to test products well.** The common result is that *products took weeks, months, or years to ship software and updates.* I consulted for one firm that shipped a new release about once every two years, and even with all that time to prepare, **integrating code** from several teams into one product without breaking the build **was a nightmare.**
42
+
43
+
Every time we would try to get the build ready somebody would submit a bug fix or a new feature that conflicted with code that somebody else had changed. We had dedicated release engineers on the case to help resolve conflicts and get the build passing QA again. **Broken processes made us miss target date after target date.** I wanted to do something about it, but the root of the problem ran deep, from inward thinking product management to deeply ingrained developer habits. Every process change we managed to implement was a hard battle against the dysfunctional corporate culture.
44
+
45
+
A few years later, I worked at another company —**a five year old startup** at the time that had taken a whole industry by storm and become a global leader. We were growing the business at a very fast clip, hiring as fast as we could get qualified candidates in the door — but we had missed several release date targets already, and **we struggled to implement new processes while we were trying to onboard new recruits.**
46
+
47
+
By way of contrast, I have also worked with **large enterprise organizations who have taken lessons from the lean startup movement** and somehow managed to escape the old corporate culture and embrace working in small, agile teams with tools automating the process of testing and product integration.
48
+
49
+
**We shipped code to production on a daily basis,** and even at a big company with tens of thousands of employees, we were nimble enough to respond quickly to customer needs, ship bug fixes quickly, and integrate important new features dreamed up by the product teams.
50
+
51
+
Good agile teams are effective because they know how to fail fast on a strict budget, and learn lessons quickly. From the customer's perspective they appear responsive to the costomer's needs. A high quality testing process is the cornerstone of good agile developement.
52
+
53
+
In this course, you'll be guided through a product development process that works -- one that I've adapted from my experiences working with companies of all kinds, from tiny startups to market leading enterprise businesses. I've taken the best ideas from each, and distilled that hard won wisdom into ten minute video chunks interspersed with text, exercises, and real-world examples. The course is specifically targeted to JavaScript developers, so all the examples and exercises will be relevant to the things you want to learn how to do.
54
+
55
+
The value of these lessons can't be overstated. The ideas, tools, and techniques in this course will inform your career and help you make confident, data-driven decisions with a real potential to make a strong impact on the bottom line. There is nothing else like this on the market at any price.
56
+
57
+
35
58
## Supporting a Good Cause
36
59
37
60
We launched ["Learn JavaScript with Eric Elliott" on Kickstarter](https://www.kickstarter.com/projects/ericelliott/learn-javascript) and raised 250% of our goal. The campaign went viral after I posted a story on medium: ["Fighting Poverty with Code"](https://medium.com/the-backer-army/fighting-poverty-with-code-d1ed3ebd982d).
0 commit comments