Web development (or web programming as I like to call it) is filled with illusions. These illusions, masquerading as common sense, are things like attempting to be "time saving" and tidbits like "don't re-invent the wheel" that are widespread among programmers and web developers. Though good intentioned, these illusions mislead us as web programmers to take the wrong path when building a website. In this talk, I want to bust some of these illusions and mistakes; like using content management systems for single page websites when a simple HTML page will suffice, or installing ultra heavy CSS frameworks when just 500 lines of CSS will be needed, or using a standard shopping cart that your cousin's best friend's sister uses and you want it for your ecommerce shop when you are selling just one product and don't need it (true story). I want to talk about things like that. I see websites being built in a horrible fashion daily and this is not how web development was supposed to be.

1. Illusions of Web Development
and How They Are Destroying
the Industry
By Stefany Newman
www.stefanywebdesign.info
stefany@stefanywebdesign.info

2. About Stefany Newman
● Entrepreneur
● Programmer
● Historian
● Swimmer

3. Illusion: Content Management
Systems trim development time

4. “ [...] Conventional wisdom is
usually a bunch of B.S. ” - Surge
by Mike Michalowicz

5. Web developers are constantly using
complex systems for simple projects!

7. Do not use a CMS
for a simple project.

8. Because: ● Adds unnecessary complexity

9. Because: ● Adds unnecessary complexity
● Slows down development

10. Because: ● Adds unnecessary complexity
● Slows down development
● Increases security risks

11. Because: ● Adds unnecessary complexity
● Slows down development
● Increases security risks
● Changes become a nightmare

12. Because: ● Adds unnecessary complexity
● Slows down development
● Increases security risks
● Changes become a nightmare
● Bottlenecks the website

13. CMS for a complex
project?

15. Because: ● Slows down development

16. Because: ● Slows down development
● Horrible UI

17. Because: ● Slows down development
● Horrible UI
● Numerous security risks

18. Because: ● Slows down development
● Horrible UI
● Numerous security risks
● Plugins will be a pain to write

19. Because: ● Slows down development
● Horrible UI
● Numerous security risks
● Plugins will be a pain to write
● Flouts the CMS’s purpose

20. Content
Management
Systems can be
useful

21. For: ● Middle sized projects

22. For: ● Middle sized projects
● When content will be regularly
changed/added/edited

23. For: ● Middle sized projects
● When content will be regularly
changed/added/edited
● Blogs

24. For: ● Middle sized projects
● When content will be regularly
changed/added/edited
● Blogs
● Projects without unique
requirements

25. For: ● Middle sized projects
● When content will be regularly
changed/added/edited
● Blogs
● Projects without unique
requirements
● … And without confidential
information

26. CSS frameworks can be evil...

27. ...as can anything trendy!

29. Thank you!
Any Questions?