Solved
You finally did it
You ruined the game
Maxinq signing off
Good luck legends 😔
Lmao, cry more. Bye!
Forum Discussion
16 Replies
Lmao, cry more. Bye!
- @IDTAKEN192000 It's funny as I used to say the same to people who said they are going to leave .
But looks like you are still fresh maybe started in season 3 or something so maybe you don't know how Apex originally was
But with time you will get to the same level of frustration if things is not fixed .
@maximas1986 wrote:
@IDTAKEN192000It's funny as I used to say the same to people who said they are going to leave .
But looks like you are still fresh maybe started in season 3 or something so maybe you don't know how Apex originally was
But with time you will get to the same level of frustration if things is not fixed .Been playing since day one and for the first time it seems they are going in the right direction.
- @apostolateofDOOM Exactly big LOL
So what exactly is wrong? I assume that it's less forgiving.
- @IDTAKEN192000 You mean other than the bugs?
@maximas1986 wrote:
@IDTAKEN192000You mean other than the bugs?Yes, bugs that can be fixed and are to be expected after major updates in live service games. What else is your issue?
That's actually a dismissive attitude. You ignore the problem rather than address it.
Programming is a procedural process. There are things in place, like QA (Quality Analysis) which help to prevent problems going out into production environments (aka "Live"). So "expecting" a drop in QA for the mere fact that an update occurred would not cut mustard at MANY development teams I've seen.
In reality, what is happening here is that the team is being held to a schedule/deadline that forces them to bypass QA measures, which results in (to the stakeholders liking) faster product deployment, but to the community's chagrin, a less stable or qualitative experience.
@Aegis_Kleais wrote:That's actually a dismissive attitude. You ignore the problem rather than address it.
Programming is a procedural process. There are things in place, like QA (Quality Analysis) which help to prevent problems going out into production environments (aka "Live"). So "expecting" a drop in QA for the mere fact that an update occurred would not cut mustard at MANY development teams I've seen.
In reality, what is happening here is that the team is being held to a schedule/deadline that forces them to bypass QA measures, which results in (to the stakeholders liking) faster product deployment, but to the community's chagrin, a less stable or qualitative experience.Right, you go do it then. You are the expert right?
