Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

The sorry state of frontend code

49 vues

Publié le

It's time to be honest with ourselves and admit that we do not treat our frontend code the same way we treat our backend code. And it shows.

But what's wrong with our frontend code, you ask? Well, not surprisingly, the same things that we usually recognize as Bad Things™ for backend: duplication, coupling, clutter, lack of unit tests, bad naming, etc. Let's take a closer look at some of these anti-patterns showing up in our frontend code and how we can avoid them.

Publié dans : Technologie
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

The sorry state of frontend code

  1. 1. THE SORRY STATE OF FRONTEND CODE
  2. 2. DISCLAIMER Frontend code written by frontend developers is fine, most of the times. Frontend code written by backend developers is NOT fine, most of the times.
  3. 3. SKIPPING ALL THOSE RULES THREE SMALL TIPS TO HELP YOU DO WHAT YOU LOVE EVERYDAY Quick and dirty will do it. We'll revisit it later when things aren't so hectic.
  4. 4. THREE SMALL TIPS TO HELP YOU DO WHAT YOU LOVE EVERYDAY BUT WE NEVER DO, DO WE?
  5. 5. BOYSCOUT RULE: LEAVE THE PLACE CLEANER THAN YOU FOUND IT!
  6. 6. LACK OF S
  7. 7. HIGH COUPLING
  8. 8. 3RD PARTY DEPENDENCIES
  9. 9. GLOBAL  NAMESPACE POLLUTION
  10. 10. SIDE  EFFECTS
  11. 11. THANK YOU Alin  Pandichi @alinpandichi alin.pandichi@mozaicworks.com

×