Don't Use Spree

As presented at SpreeConf 2014 in NYC

1. Don’t Use Spree Jeff Casimir
2. About You
3. Too Important
4. Who Makes 
 This Thing?
6. Who Makes 
 This Thing?
7. CEO
9. What a Team
 Looks Like
11. Open Source
 Is Stupid
14. Open Source
 Means Problems
15. Bugs Are
 Secrets
16. Open Source
 Has Bugs
22. Closed Source
 Is Safe
24. Bugs Can Be 
 Features
25. Upgrading Versions
28. Who You Gonna Call?
30. Spree’s “Support”
35. The Business Case
 Is Clear
36. The Software
37. Just Build It Yourself
39. Job Security
40. The Ruby & The Rails
41. The PHP
45. Abstractions = Lies
47. Code Is Hiding
48. spree spree_api spree_backend spree_cmd spree_core spree_frontend spree_sample
49. Opening an Engine
50. bundle open spree_api
52. Hi! I am Clippy, your programming assistant. Would you like me to build your store’s API?
53. Engine Replacement
54. Changing Authorization Providers
55. Say You Get It All
 Put Together
56. How Deployment Should Be
58. Deploying Spree
62. You’re Responsible
63. Don’t Use Spree • Open Source is Too Dangerous • The Project and Platform are Too Old • Spree Enslaves Their Support Team • The Software Is Too Modular • Deployment Is Too Hard Jeff Casimir