• F your Foobar

    As the famous Phil Karlton quote goes: "There are only two hard things in Computer Science: cache invalidation and naming things". This talk focuses on one of those things: naming! Why is naming so difficult? How do we craft concise, clear, and consistent variable names? What makes a variable name concise, clear, and consistent? In this talk, I'd like to discuss the importance of naming, walk through examples of variable names and improve them, and set some clear guidelines and tips on how to name things. By the end of this talk, you'll leave with the indispensable skill of effectively naming things!

  • Looks GREAT To Me (CFE Dev)

  • Looks GREAT To Me (beyond tellerand)

  • Looks GREAT To Me (J on the Beach)

  • Variables of the Veracious Variety (Stir Trek)

    As the famous Phil Karlton quote goes: "There are only two hard things in Computer Science: cache invalidation and naming things". This talk focuses on one of those things: naming! Why is naming so difficult? How do we craft concise, clear, and consistent variable names? What makes a variable name concise, clear, and consistent? In this talk, I'd like to discuss the importance of naming, walk through examples of variable names and improve them, and set some clear guidelines and tips on how to name things. By the end of this talk, you'll leave with the indispensable skill of effectively naming things!

  • Variables of the Veracious Variety (VSLive)

    As the famous Phil Karlton quote goes: "There are only two hard things in Computer Science: cache invalidation and naming things". This talk focuses on one of those things: naming! Why is naming so difficult? How do we craft concise, clear, and consistent variable names? What makes a variable name concise, clear, and consistent? In this talk, I'd like to discuss the importance of naming, walk through examples of variable names and improve them, and set some clear guidelines and tips on how to name things. By the end of this talk, you'll leave with the indispensable skill of effectively naming things!

  • Looks GREAT To Me (VSLive)

  • Looks GREAT To Me (Symetri Kickoff 2024)

    "Unlock the secrets to effective code reviews with Adrienne Tacke. Learn how to go beyond the bare minimum and create a positive environment for reviewer and author collaboration. Discover common mistakes and how to fix them."

  • Looks GREAT To Me (DecompileD)

    "Unlock the secrets to effective code reviews with Adrienne Tacke. Learn how to go beyond the bare minimum and create a positive environment for reviewer and author collaboration. Discover common mistakes and how to fix them."

  • Looks GREAT To Me (VoxxedDays Thessaloniki)

  • Looks GREAT To Me

  • Variables of the Veracious Variety

    First presented at Copenhagen Developers Festival (August 2023) As the famous Phil Karlton quote goes: "There are only two hard things in Computer Science: cache invalidation and naming things". This talk focuses on one of those things: naming! Why is naming so difficult? How do we craft concise, clear, and consistent variable names? What makes a variable name concise, clear, and consistent? In this talk, I'd like to discuss the importance of naming, walk through examples of variable names and improve them, and set some clear guidelines and tips on how to name things. By the end of this talk, you'll leave with the indispensable skill of effectively naming things!

  • Conducting Humane Code Reviews

  • One Serverless Principle to Rule Them All: Idempotency

  • Serverless Socializing

    Serverless Socializing: How I Built a Quick Multi-Player Serverless Game Working with a fully remote team, it's been hard to develop some team camaraderie. To help with this, we played various multiplayer, cloud-based games! And of course, I tried to build my own. In this talk, we'll play the game and understand how it is built with a serverless architecture in mind!

  • Documentation: The Missing Pieces

    Most documentation, technical tutorials, and quick demos are written in a certain way. But for the true beginners, the career-transitioners, or those crossing domains? That technical content is certainly not written for them! Funnily enough, these same shortcomings affect “technical” people too, especially when it comes to learning something new. In this talk, I’d like to explore the ways we can make our documentation better by considering more kinds of people. We’ll discover common oversights and assumptions most documentation has built-in by default and learn how to fix them. We’ll also strengthen our technical writing skills to ensure, to the best of our ability, that every anticipated reader of our documentation never feels lost or frustrated. By the end of this talk, you’ll leave and never write documentation in the same way again…and that’s a good thing!

  • There is NO Developer Uniform!