Presenter, Brad Czerniak caught my eye with a blog post (https://www.commercialprogression.com/post/10-things-i-learned-using-drupal-hackathon) about using Drupal at a hackathon. This presentation is goes through the "rapid version" of the Drupal development process at Commercial Progression that he used at the hackathon. Session description There are lots of hooks, templates, and other development avenues in Drupal — "more than one way to skin a cat." Often choosing a particular method can affect the operation of a site, lock you into a particular way of doing things, have implications on future work, and get the notice of fellow developers; all for either better or worse. This presentation explains different endpoints for developing, and introduces a mindset for making the best choice given the circumstances. Takeaways - A list of helpful 'Do' tips, including some of the best lesser-known contrib modules - A list of 'Don'ts', with lots of "code smells" to watch out for - Theming and development methodology best practices — with helpful graphics

15. Do’s and Don’ts

16. Don’ts

17. Don’t php in your
database

18. Don’t contemplate, and
avoid building fences

19. Don’t install panels
“just because”

20. Don’t commit
viewsception

21. Don’t rush the
module review process

22. Don’t use
redundant modules

23. Don’t hack core
or contrib for that matter

24. Don’t litter

25. Don’t litter
[seriously]

26. Don’t create your
own coding standards

27. Don’t assume your
templates are lonely

28. $output = ‘<p>’;
$output .= ‘Don’t hard-code<br />’;
$output .= ‘anything more than a line’;
$output .= ‘</p>;

29. Do’s

30. Do split
your module folders
(contrib, custom, features)

31. Do use
semantically-correct fields

32. Do blockify

33. Do install
easy wins

34. Do let contrib
lead the way

35. Do use smtp and
reroute_email on local

36. Do strive for
reusable custom modules

37. Do name themes and
glue-code modules for reuse

38. Do <front>
with a blank page callback

39. Do theme
in the right place

40. Do make buttons
into <button>s

41. Do render entities
in Views [sometimes]

42. Do use chosen

43. Do call_user_func_array()
in some overrides

44. Do hook_custom_access_paths()
for your eck entities

45. Do keep an eye on
page titles in dynamic views

46. Do label
your entities

47. Do tokens
when about to php your db

48. Do hook_field_extra_fields()
for multi-field formatters

49. Do features by entity type
(careful with field bases!)

50. Do .views-field-excluded {color: #888; }
in your admin theme

51. Do same-origin source
your webfonts

52. Do class
your view and blocks

53. Do make little
media queries

54. Do .first, .last, etc.
for blocks, rows, everything

55. Do run
coder

56. Do rtfm