Lightning Talk: What we can learn from Tailwind

[ckcherry23]

Talk Structure

• Intended impact
  • Know: How some tools that do not follow best practices are the most popular
  • Believe: Best practices are not always good
  • Do: Do not follow best practices blindly
• WIIFY
  • Questioning best practices can lead to more maintainable code if you do it “the right way” for your OSS projects.
• Key points
  • Challenge assumptions about best practices
  • Do not use cryptic names
  • Consider approaches that promote code reusability
  • Ship less code, do more
  • Don’t blindly follow frameworks
• Call-to-action
  • "Best practices" and just considerations. Think critically about your approach for better code in the long run.
• Roadmap
  • What is Tailwind CSS
  • 5 things we can learn from Tailwind
• PUNCH
  • (C: Challenging) "Best practices" don't actually work.

Slides

• PDF download: Charisma-LightningTalkB3-Tailwind.pdf
• Animated slides link: Canva: What can we learn from Tailwind?

[ckcherry23]

Round C Slides

• PDF download: Charisma-LightningTalkC2-Tailwind.pdf
• Animated slides link: Canva: What can we learn from Tailwind?

Updated Talk Structure

• Intended impact
  • Know: How Tailwind can level up frontend development and why it is good at it
  • Believe: Tailwind makes frontend development better because of its different design choices
  • Do: Use Tailwind and make software design decisions thoughtfully
• WIIFY
  • Faster UI development and prettier designs, even if you’re a backend dev with no design experience
  • How Tailwind questions 'best practices' and other software engineering principles it follows, for a fresh perspective
• Key points
  • What
  • Tailwind CSS is a popular utility-first CSS framework
  • How
  • Allows designing within markup which reduces context-switching
  • Defines clear naming conventions for self-documenting code
  • Why
  • Atomic classes for code reusability and design consistency
  • Tailwind + PurgeCSS to remove unused styles and for scalability
  • When
  • Bootstrap for rapid prototyping
  • CSS for maximum control
  • Tailwind for a balance of both
  • 5 things we can learn from Tailwind
  • Challenge traditional practices
  • Use good naming conventions
  • Strive for code reusability
  • Ship less code, do more
  • Always consider trade-offs
• Call-to-action
  • Challenge your assumptions when designing software
  • Next time you develop a frontend, try out Tailwind CSS!
• Roadmap
  • What Tailwind is
  • How it works
  • Why it is good
  • And when you should use it
  • Alongside, 5 things that we can learn from Tailwind itself
• PUNCH
  • (C: Challenging) "Best practices" don't actually work.