GLA Summit 2020/Abstract This, Not That.: Difference between revisions
Appearance
Added page |
m Update with infobox and presentation template |
||
| Line 1: | Line 1: | ||
{{infobox | |||
|category=presentation | |||
|icon=GLASummitButton.png | |||
|presentation-conference=GLA Summit 2020 | |||
|presentation-presenter=Paul Ross | |||
}} | |||
{{presentation | |||
|presenters=Paul Ross | |||
|abstract=Using abstractions in our code provides many benefits - increasing testability and modularity while reducing coupling, but it isn't always clear when and where to use abstractions. In this presentation, I will discuss the importance of creating abstractions at the right layers, and how you can properly identify those layers. Come see why your actor queues should probably be wrapped in another class, and why you may never need to create another abstract message! | |||
|youtube-id=VO8T2pvNtLI | |||
}} | |||
==External links== | |||
*[https://www.glasummit.org/presentation-list/2020 GLA Summit 2020 Presentations] | |||
* [https:// | |||
[[Category:GLA Summit 2020]] | [[Category:GLA Summit 2020]] | ||
Latest revision as of 18:51, 21 August 2024
| Abstract This, Not That. | |
|---|---|
| Conference | GLA Summit 2020 |
| Presenters | Paul Ross |
Abstract This, Not That. by Paul Ross
Using abstractions in our code provides many benefits - increasing testability and modularity while reducing coupling, but it isn't always clear when and where to use abstractions. In this presentation, I will discuss the importance of creating abstractions at the right layers, and how you can properly identify those layers. Come see why your actor queues should probably be wrapped in another class, and why you may never need to create another abstract message!