Same thing. "I'm (am/have done/am doing) X therefore I'm right".



Jmanis talks to a mother of five:
J:
I think women fake it when they claim giving birth hurts
M:
hmm... I actually can give you firsthand experience that it does actually hurt
J:
pffff appeal to authority 
🖐
Appeal to authority is a fallacy when you rely on the authority of the person, not on their expertise in the subject. Don't just throw around smart phrases without understanding what they are. Makes you sound like an apologist.
en.wikipedia.org
And when I do, what then? You'll challenge that? Just concede?
Ultimately what I want is to know what the truth is. I'm not here to force my opinion. If I'm wrong, I want to know I'm wrong, and the first step to knowing is becoming convinced. Hence, I'm looking (through provocation, admittedly) for convincing arguments and evidence. Should you convince me, I will be convinced and concede.
Here's a couple questions, just to start with. And I'm deliberately being opaque as to the relevance of these questions.
- Where does Voice Attack comes in to things? Have you even thought about it?
No, I have not. Good point. That said, isn't it just a third party tool that interprets voice and activates in game shortcuts based on them? If the game allows for a shortcut to the function then FDev need not be concerned with whether or not some third party tool takes that into account. It's up to the third party to catch up.
- Are you suggesting Software Developers have full remit to do whatever they want with the UI?
Developers do to the UI what they're told to do by the ticket and what lands on the ticket comes from the PM/PO/SM, depending on team structure. If the right person says "do" you do.
- So when does testing happen? Or are we just going "Passed unit tests, ship it" here?
- Thought about localisation?
Perhaps that's where there's a misunderstanding between us.
- As a software developer, the natural definition of "implementation" to me is the programming definition, meaning that I have an interface or an abstract class and I write the actual class/method that performs the contracted functionality.
- In a project context, I understand "implementation" as the part where the developer "makes it work" and "time to implement" as time required for developer to "make it work". For example, when I get literally asked "how long will it take you implement this?", the person asking me always wants to know how long it will take me to code the feature, not how long somebody else takes later to package it.
- When referring to the entire time required from idea to production, including concept art, deliberation, prioritisation, visual design, scrum activities (i.e. splitting into tasks, estimation, creating tickets and user stories, ceremonies), change management, code review, QA, adding unit tests, localization, user testing, documentation, security check, packaging etc. I would call it "time to release", "time to publish" or "time to production".
From the very beginning I believe I was clear enough that I meant just the developer's work.
Doesn't have to exist, hundreds of functions don't have them. As long as the shortcut exists on the list and is bindable, I consider it case closed. The way I structured shortcut management in my applications would require a total of 1 minute to implement.
Not going to lie, there's traps in those questions. Have fun.
I'm curious to hear what the traps were. Hit me
