The Original Hypertext Preprocessor

Transcript

1. PHP Community Conference April 2011 Drew McLellan edgeofmyseat.com grabaperch.com -THE ORIGINAL- HYPERTEXT PREPROCESSOR
2. EVERY LINE OF CODE -CAN HAVE A- DIRECT IMPACT ON CUSTOMERS
3. DESIGNING SOFTWARE FOR HUMANS
4. FUNCTIONALITY IS NOT ENOUGH
5. REWIND
6. DUDE, LIKE WHAT ABOUT DRUPAL?
7. With Wordpress (don’t even get me started on Drupal), the learning curve was very high, requiring my clients to learn about posts versus pages versus custom post types.
8. LOTS OF OPTIONS BUT LOTS OF USERS
9. THERE'S ROOM IF YOU CAN BE DIFFERENT
10. YOU DON'T NEED TO CAPTURE THE WHOLE MARKET
11. LIGHTWEIGHT PHP CMS FOR SMALL WEBSITES
12. 9 LESSONS & CAROLS
13. LESSON: THE MOST DIFFICULT PROBLEMS ARE WET ONES
14. Support will kick your ass Jason Fried, 37signals http://www.extractable.com/blog/?p=58
15. Helpspot (help desk software) really saved our ass when it came to support Todd Dominey, SlideShowPro http://5by5.tv/bigwebshow/24
16. SUPPORT INVOLVES A LOT OF ASSES
17. MANY CUSTOMERS ARE INEXPERIENCED
18. THEY NEED A LOT OF SUPPORT
19. EACH LICENSE SOLD = 15 MINUTES OF SUPPORT TIME
20. SUPPORT YOUR OWN SOFTWARE
21. FIND WAYS TO REDUCE SUPPORT
22. EVERY REQUEST SHOULD BE UNIQUE
23. WHEN WILL THIS FAIL?
24. Take pleasure in designing out the weaknesses
25. MAKE ARCHITECTURAL DECISIONS TO MINIMISE COMPLEXITY
26. THERE IS NO ADD NEW
27. <?php perch_content(‘Heading’); ?>
29. KEEP THE BASIC USE-CASE SIMPLE
30. All code breaks. Great code breaks well.
35. NOT ALL ATTEMPTS ARE SUCCESSFUL
37. SPEED OF RESPONSE IS THE MOST IMPORTANT THING
38. NOT ALL SUPPORT REQUESTS ARE YOUR FAULT...
39. LESSON: RUNNING PHP EVERYWHERE IS HARD
40. WE'RE USED TO CONTROLLED PLATFORMS
41. WE'RE USED TO CONTROLLED PLATFORMS
42. ALL BETS ARE OFF.
43. CHEAP HOSTING IS CHEAP
44. WINDOWS IS WEIRD
45. SERVER VARIABLES CAN NEVER BE RELIED ON
46. PERMISSIONS ARE AN UTTER MYSTERY
47. PATHS ARE BACKSLASHTASTIC
48. MIGRATING BETWEEN FILESYSTEMS
49. NEVER MIX CASE IN MYSQL TABLE NAMES
50. LESSON: TECHNICAL PROBLEMS ARE DIFFICULT TOO
51. PHP5 AS STANDARD
52. WE WOULD LOVE TO MOVE TO PHP5.3
53. THE FAILED PROMISE OF SQLITE
54. MARKUP IN FILES CONTENT IN THE DATABASE
55. SCHEMALESS STRUCTURED DATA
56. !<perch:content !!!type=”text” !!!id=”heading” !!!label=”Main heading” !!!required=”true” />
57. <h2><perch:content id="heading" type="text" label="Heading" required="true" title="true" /></h2> <p class="date"><perch:content id="date" type="date" label="Date" format="%d %B %Y" /></p> <perch:content id="body" type="textarea" label="Body" textile="true" editor="markitup" required="true" />
58. 1. TABLE OF KEY/ VALUE PAIRS 2. BIG BLOB OF JSON
59. 1. TABLE OF KEY/ VALUE PAIRS
60. SCALES UP WELL CAN BE FILTERED WITH SQL
61. REQUIRES HOUSEKEEPING INEFFICIENT FOR SMALL VALUES
62. 2. BIG BLOB OF JSON
63. STORE ANY SHAPE IN ONE ROW EXTREMELY SIMPLE
64. CONTENT HAS TO BE FILTERED IN PHP NATIVE JSON LIBRARIES ARE NOT UNIVERSAL
65. CREATE TABLE `perch_contentItems` ( `contentID` int(10) unsigned NOT NULL AUTO_INCREMENT, `contentKey` varchar(255) NOT NULL DEFAULT '', `contentPage` varchar(255) NOT NULL DEFAULT '*', `contentHTML` longtext NOT NULL, `contentNew` tinyint(1) unsigned NOT NULL DEFAULT '1', `contentTemplate` varchar(255) NOT NULL DEFAULT '', `contentMultiple` tinyint(1) unsigned NOT NULL DEFAULT '0', `contentAddToTop` tinyint(1) unsigned NOT NULL DEFAULT '0', `contentJSON` mediumtext NOT NULL, `contentHistory` mediumtext NOT NULL, `contentOptions` text NOT NULL, PRIMARY KEY (`contentID`), KEY `idx_key` (`contentKey`), KEY `idx_page` (`contentPage`) ) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=utf8;
66. SO HOWS THAT WORKING OUT FOR YOU, BIG GUY?
67. NON-NATIVE JSON IS SLOW
68. QUERYING ACROSS TABLE COLUMNS AND JSON VALUES IS A TWO STEP PROCESS.
69. SO WHAT IS GOOD ABOUT IT?
70. { ! “heading”: “Foo”, ! “date”: “2011-04-22 10:00:00” }
71. [ ! { ! ! “heading”: “Foo”, ! ! “date”: “2011-04-22 10:00:00” ! }, ! { ! ! “heading”: “Foo”, ! ! “date”: “2011-04-22 10:00:00” ! } ]
72. [ ! { ! ! “_rev”: 1300447544, ! ! “_content”: { ! ! ! “heading”: “Bar”, ! ! ! “date”: “2011-04-22 10:00:00” ! ! } ! }, ! { ! ! “_rev”: 1293968747, ! ! “_content”: { ! ! ! “heading”: “Foo”, ! ! ! “date”: “2011-04-22 10:00:00” ! ! } ! } ]
73. SIMPLE, EFFECTIVE HISTORY STACK
74. THEORISING IS EASY. NOTHING BEATS EXPERIENCE.
75. LESSON: BE OPINIONATED, BUT NOT DICTATORIAL
76. WYSIWYG IS EVIL
78. BUT MY CLIENTS MUST HAVE AN EDITOR LIKE WORD
79. IT'S NOT OUR PLACE TO TELL PEOPLE HOW TO WORK
81. EDIT IN PLACE IS A FALSE PROMISE
82. LESSON: HELP CUSTOMERS SERVE THEIR CLIENTS
83. IDENTIFY YOUR CUSTOMERS PROBLEMS
84. CONFIDENCE IS EVERYTHING
85. EVERY FIELD CAN BE ANNOTATED
86. help=”Use the teacher’s initials from the timetable.”
88. <perch:help> !<p>Confused? Watch !!!this video:</p> !<video>...</video> </perch:help>
91. DRAFTS PREVIEW UNDO
92. LESSON: FIND OTHERS TO COVER YOUR WEAKNESSES
99. LESSON: BE A MAGICIAN, NOT JUST A DEVELOPER
100. FUNCTIONALITY IS NOT ENOUGH
101. LEARN TO ACCEPT WHEN USERS ARE HAVING TROUBLE
102. REALLY GREAT DEVELOPERS SOLVE PROBLEMS
103. DON'T FEAR REFACTORING
104. LESSON: YOU CAN'T WIN EVERY USER
105. I love the little cms but the one thing I was expecting to get is a license for multiple domain,... if you guys can help with that you will earn a big customer,.. and as of right now I already found 2 more cms just like yours at a lower price but what they take a away is in the interface design,.. (which I could careless about it) but you guys still my number 1 option but if you guys can give me a break on that little part for licensing multiple domains that will be very much appreciated,..
106. NOT EVERYONE WILL GET IT.
107. THANK YOU! grabaperch.com @drewm