Good session. Gonna use that with a team I'm coaching. From the content, we here in my dev group (The Guild from Spain) do like how maaany names in early stages of its naming process end up vanished, like inlined or the whatnot. That's why we came up with the most satisfying and writing-pleasant alternative to appleasauce: jitanjaphores!
ever find yourself moving words out of the function name and into a parameter with a default value you'd never change e.g. `fn SendTpsReport_WithCoverSheet(TpsData)` becomes `fn SendTpsReport(TpsData, CoverSheet = true)` (or could be into a parameters object with a default value)
Interesting! I'm a little skeptical of boolean arguments but I think the point you're making would still stand with a more complex type too. The idea of the final steps of naming as a process is to make domain objects with encapsulation of their data, so probably something more like TpsReport.GenerateFrom(data).SendWithCoverSheet() ?
Too bad, I had to pause this vid. Will return later. But what I've seen so far was awesome. :) You're awesome, Emily!
Glad you liked it! Hope you enjoy the rest too.
Really useful video thanks Emily !
Glad it was helpful!
Thats good !!! I will think how to implement this in our team.
Happy to hear that!
Good session. Gonna use that with a team I'm coaching.
From the content, we here in my dev group (The Guild from Spain) do like how maaany names in early stages of its naming process end up vanished, like inlined or the whatnot. That's why we came up with the most satisfying and writing-pleasant alternative to appleasauce: jitanjaphores!
It's a cool name, jitanjaphores!
So long as everyone recognizes obvious nonsense then do whatever your team prefers.
ever find yourself moving words out of the function name and into a parameter with a default value you'd never change
e.g. `fn SendTpsReport_WithCoverSheet(TpsData)` becomes `fn SendTpsReport(TpsData, CoverSheet = true)`
(or could be into a parameters object with a default value)
Interesting! I'm a little skeptical of boolean arguments but I think the point you're making would still stand with a more complex type too. The idea of the final steps of naming as a process is to make domain objects with encapsulation of their data, so probably something more like TpsReport.GenerateFrom(data).SendWithCoverSheet() ?