[Abstract]: Stop abstracting away your deps

[MatthijsvdVeer]

1. Who do you think this talk is for?

Developers

2. What do you think you'll learn from this talk?

• How to structure your application code
• What abstraction is right
• What you should abstract, and what should just depend on your infrastructure
• All .NET

3. What's something you'll be able to accomplish with the information gained from this talk?

You will know

• how to build maintainable code
• Simple code
• When something is overengineering

4. What is the two-sentence summary of the talk?

You will learn when to abstract dependencies like the database or services and when not. This is all to keep things simple, as .NET developers have a tendency to overengineer the solution.

[github-actions[bot]]

Mastering .NET Application Architecture: Avoiding Overengineering

In this session, you'll discover how to effectively structure your application code, determine the right level of abstraction, and discern what should be abstracted versus what should depend on your infrastructure. Gain insights into building maintainable and straightforward code while avoiding the common pitfall of overengineering prevalent among .NET developers.

This session is tailored for developers looking to refine their coding practices and achieve simplicity in their .NET applications. Expect practical strategies and examples to streamline your development process.

[github-actions[bot]]

✅ 1. Who do you think this talk is for?

Yes, this was covered in the abstract: "This session is tailored for developers..."

✅ 2. What do you think you'll learn from this talk?

The abstract mentions:

• "how to effectively structure your application code,"
• "determine the right level of abstraction,"
• "discern what should be abstracted versus what should depend on your infrastructure."
• "Gain insights into building maintainable and straightforward code while avoiding the common pitfall of overengineering prevalent among .NET developers."

✅ 3. What's something you'll be able to accomplish with the information gained from this talk?

Yes, this was covered in the abstract: "Gain insights into building maintainable and straightforward code while avoiding the common pitfall of overengineering..."

✅ 4. What is the two-sentence summary of the talk?

Yes, the information is effectively summarized in the abstract:

• "Gain insights into building maintainable and straightforward code while avoiding the common pitfall of overengineering prevalent among .NET developers."
• "Expect practical strategies and examples to streamline your development process."

---

Opinion about the quality of the abstract:

The abstract is well-crafted and covers all the key points outlined in the questions and answers. 🎉 It clearly identifies the target audience (developers), specifies the learning outcomes, and summarizes the talk effectively. The focus on practical strategies and examples adds value, making it appealing to attendees. 🌟 Overall, this abstract sets clear expectations and aligns perfectly with the provided answers. Excellent job! 👍

[github-actions[bot]]

✅ Perfect abstract!