[MAJOR ISSUE] [ALERT] This board is not ready for the postseason. [Mod Update: Now we're ready for the postseason.]

[fnordcircle]

ATTN: IAN - MODS - SELF-APPOINTED MODS

There is a major technical issue impacting this board that will come to a head in a mere matter of hours if not addressed!


When you want to choose a different emoji you click on the right-pointing arrow on the left side:


However, if you click on that the arrow under your mouse now turns to a left-pointing arrow which returns you to the previous emoji selection:


This has caused several issues:

* Inadvertent clicks in the same spot that now return you to the previous emoji selection screen.
* Significant finger strain on my finger due to wasted clicks.
* Imposes unwanted and unwarranted delay in critical emoji response times.

In key game situations we need to be focused not waylaid by technical barriers. The Butterfly Effect clearly implies a potential path where a perfectly timed Ha Ha emoji could translate into a series of events which impacts crucial game outcomes.

Thank you for your attention in this matter. The world is watching.

 

[Huckleberry1]

ATTN: IAN - MODS - SELF-APPOINTED MODS

There is a major technical issue impacting this board that will come to a head in a mere matter of hours if not addressed!


When you want to choose a different emoji you click on the right-pointing arrow on the left side:


However, if you click on that the arrow under your mouse now turns to a left-pointing arrow which returns you to the previous emoji selection:


This has caused several issues:

* Inadvertent clicks in the same spot that now return you to the previous emoji selection screen.
* Significant finger strain on my finger due to wasted clicks.
* Imposes unwanted and unwarranted delay in critical emoji response times.

In key game situations we need to be focused not waylaid by technical barriers. The Butterfly Effect clearly implies a potential path where a perfectly timed Ha Ha emoji could translate into a series of events which impacts crucial game outcomes.

Thank you for your attention in this matter. The world is watching.

You forgot the ALL CAPS!

 

[Pape]

ATTN: IAN - MODS - SELF-APPOINTED MODS

There is a major technical issue impacting this board that will come to a head in a mere matter of hours if not addressed!


When you want to choose a different emoji you click on the right-pointing arrow on the left side:


However, if you click on that the arrow under your mouse now turns to a left-pointing arrow which returns you to the previous emoji selection:


This has caused several issues:

* Inadvertent clicks in the same spot that now return you to the previous emoji selection screen.
* Significant finger strain on my finger due to wasted clicks.
* Imposes unwanted and unwarranted delay in critical emoji response times.

In key game situations we need to be focused not waylaid by technical barriers. The Butterfly Effect clearly implies a potential path where a perfectly timed Ha Ha emoji could translate into a series of events which impacts crucial game outcomes.

Thank you for your attention in this matter. The world is watching.

be quiet or i will ban you!

 

[maust]

 

[Wozzy]

Ca we get rid of the red alert at the top of the page on the pick the score tab?

 

[turkeyneck]

@Ian, I've been meaning to bring up this matter as well. It would be much more ergonomic to have it as @fnordcircle suggests.

I don't know if playoffs is the best time to execute the transition though...

 

[n1997y]

@Ian, I've been meaning to bring up this matter as well. It would be much more ergonomic to have it as @fnordcircle suggests.

I don't know if playoffs is the best time to execute the transition though...

Playoffs are a critical performance period!

As a longtime IT professional I know it is essential to have a mandatory code freeze around critical performance periods. Nothing short of mission essential break fixes will be implemented during the code freeze.

So those of you requesting changes are SOL. Please follow proper procedures for requesting changes.

You must create a change request in the Jira ticketing system, fully describing the desired change and the expected benefits. If the change and benefits are not adequately explained your request will be returned for additional information to be provided. When fully justified it will be queued for review by the Change Committee to prioritize it for submission to the Architecture Review Board and entered into their prioritized queue. After the review the proposed change for potential impacts the ARB can choose to deny it, defer it, or approve it for submission to the Project Planning Committee for review and inclusion in the appropriate upcoming major or minor release cycle plans. Minor changes will be implemented by the Development Team during their next scrum, and queued for the Quality Assurance team post haste. Major changes will be queued for inclusion in the next design sprint, going through a waterfall model of design, implementation, code review, and unit testing before queueing to QA. All QA submissions will be given full regression testing. Changes failing regression testing will be returned to the development team for correction and resubmission to QA. Changes passing QA will be queued for inclusion in the next production deployment push. It is currently expected that the next production deployment will be scheduled after the mandatory change blackout window for the 2026 playoffs.

Thank you for using our new Agile Development process.

 

[fnordcircle]

Playoffs are a critical performance period!

As a longtime IT professional I know it is essential to have a mandatory code freeze around critical performance periods. Nothing short of mission essential break fixes will be implemented during the code freeze.

So those of you requesting changes are SOL. Please follow proper procedures for requesting changes.

You must create a change request in the Jira ticketing system, fully describing the desired change and the expected benefits. If the change and benefits are not adequately explained your request will be returned for additional information to be provided. When fully justified it will be queued for review by the Change Committee to prioritize it for submission to the Architecture Review Board and entered into their prioritized queue. After the review the proposed change for potential impacts the ARB can choose to deny it, defer it, or approve it for submission to the Project Planning Committee for review and inclusion in the appropriate upcoming major or minor release cycle plans. Minor changes will be implemented by the Development Team during their next scrum, and queued for the Quality Assurance team post haste. Major changes will be queued for inclusion in the next design sprint, going through a waterfall model of design, implementation, code review, and unit testing before queueing to QA. All QA submissions will be given full regression testing. Changes failing regression testing will be returned to the development team for correction and resubmission to QA. Changes passing QA will be queued for inclusion in the next production deployment push. It is currently expected that the next production deployment will be scheduled after the mandatory change blackout window for the 2026 playoffs.

Thank you for using our new Agile Development process.

Been laid off for 11 months now. Thanks for triggering my Sprint PTSD.

Please do the needful.

 

[fnordcircle]

@Ian, I've been meaning to bring up this matter as well. It would be much more ergonomic to have it as @fnordcircle suggests.

I don't know if playoffs is the best time to execute the transition though...

I guess some of us just believe in Ian.

We all We got. We all We need.

 

[turkeyneck]

I guess some of us just believe in Ian.

We all We got. We all We need.

Just no hero coding...

 

[Steve102]

Just no hero coding...

@Ian is not the hero we want, he's the hero we need. He's a silent guardian, a watchful protector... the dark knight.

 

[PancakeBlockPaul]

I have faith that @Ian will get this world ending issue resolved soon. He's got a 6 hour SLA to adhere to and certain KPI that are established by, you got it, US! =p

Been laid off for 11 months now. Thanks for triggering my Sprint PTSD.

Please do the needful.

Right there with ya...November myself. Time to skill up I suppose.

 

[Ian]

Ca we get rid of the red alert at the top of the page on the pick the score tab?

Make a prediction and it will go away. Otherwise, if you don't want to play it, open the menu and click on "My Settings" and unclick "Predict the Score" or whatever other contest you don't want to play:

 

[Ian]

@Ian, I've been meaning to bring up this matter as well. It would be much more ergonomic to have it as @fnordcircle suggests.

I don't know if playoffs is the best time to execute the transition though...

You need a button, though, to be able to get back to the previous group. I looked at a few other solutions before I modified that, and that seemed to be the best way to make it easy to jump from one group to the other. I initially had the buttons to the right, with the two buttons next to each other. But that made it easy to accidentally click the wrong one, which is why it ended up the way it is currently.

 

[Ian]

ATTN: IAN - MODS - SELF-APPOINTED MODS

There is a major technical issue impacting this board that will come to a head in a mere matter of hours if not addressed!


When you want to choose a different emoji you click on the right-pointing arrow on the left side:


However, if you click on that the arrow under your mouse now turns to a left-pointing arrow which returns you to the previous emoji selection:


This has caused several issues:

* Inadvertent clicks in the same spot that now return you to the previous emoji selection screen.
* Significant finger strain on my finger due to wasted clicks.
* Imposes unwanted and unwarranted delay in critical emoji response times.

In key game situations we need to be focused not waylaid by technical barriers. The Butterfly Effect clearly implies a potential path where a perfectly timed Ha Ha emoji could translate into a series of events which impacts crucial game outcomes.

Thank you for your attention in this matter. The world is watching.

LOL, and I've been meaning to add another group, so I'm open to whatever suggestions/preferences you might have on this.

 

[Username]

Wait...

There's emoji's?

 

[Ian]

Wait...

There's emoji's?

LOL, I know you're joking, but oddly enough, that question ("There's 'X' on this site?") was essentially the impetus behind the left menu redesign. I looked at a lot of different ones before settling on this one, which hopefully does a better job of making everything on here easier to find.

 

[fnordcircle]

LOL, and I've been meaning to add another group, so I'm open to whatever suggestions/preferences you might have on this.

4th group should just be Dislike/Disagree because those were so popular and did so much for board unity.

 

[Ian]

4th group should just be Dislike/Disagree because those were so popular and did so much for board unity.

I agree - I need to modify that first group and push some of those off to the latter groups. I'll definitely do that.

Any requests for new ones?

 

[Gumby]

I agree - I need to modify that first group and push some of those off to the latter groups. I'll definitely do that.

Any requests for new ones?

Clown? We do have GotoHell, but ?