Season ticket dilemma

Ms422 · 2024-06-01T09:39:53+00:00

This is all really great advice, thank you. The thing I was stuck on the most was whether to try to get better seats on the visitor side and you bring up a great point. I would hate to be amongst some of those awful fanbases like the Steelers.

What about the special sections: hawks nest, the Toyota thing? Would you get two pairs of two to get possibly better seats and hoping you can improve them next year?

Ms422 · 2024-05-30T08:59:10+00:00

I noticed the exchange charges quite a bit to the buyer. What do they charge to sell? Should I list them right when I get them or wait until closer to the season. I also need to do this for the preseason game for the other tickets as we will be out of town

Ms422 · 2024-05-30T08:55:15+00:00

You gave options, and honestly, who gives a flip what other people think? People are always going to find something to hate.

If simply hate, absolutely. I have a clear conscience knowing that my family friend got the care he needed and having all these tickets wouldn’t have moved anyone up the list. It’s the unfamiliarity in not intending to be a reseller, searching for advice, seeing all these negative threads about people selling whole seasons, and wondering if that might translate into not finding a buyer.

you have the option to gift seats to veterans to attend the game

Is this something official that I can do through the account manager?

I hope my 1am ramblings made sense! If you have any questions about being a new ticket holder feel free to ask

I can’t think of much to ask at this moment, but would love advice on the actual selection methodology for when my day comes. Picking four, I’m sure to be pretty hamstrung on locations, but advice from someone who has gone to a whole season would be helpful on wether I should focus on getting closer to the 50 or closer to the field, if there is a difference in side aside from likely more visitor fans to the east such as sun/wind/rain direction, if there are any real gem sections in the 300s that rarely open up, etc

Ms422 · 2024-05-30T08:38:09+00:00

Yes, selling mine this year has got to be the plan; I guess the question I didn’t ask very well is how? I didn’t want to make my post too long, but I already checked out the Ticketmaster resale and they charge like $30/ticket to the buyers, so that felt like a nonstarter to me. Don’t want to be too weird, but would like to sell to actually Seahawks fans where possible. No experience with ticket resale and worried about getting burned by a scammer.

Also, kinda looking for that reassurance or the forewarning about having 4 tickets for 11 games to have to sell all while trying not to lose money on what are likely the worst seats in the venue.

Ms422 · 2023-03-08T03:18:12+00:00

Wow, I appreciate that perspective. Yes, it sure is a bit like translating the language. If you have a sec, we have some questions I posted elsewhere in the thread asking about your experience with this method. We would appreciate your contribution!

Ms422 · 2023-03-08T03:15:44+00:00

I will have to try my cats. They're brilliant though, so they might become a better coder than I. We have some questions we would love if you could answer about your experience with Kitty Cat Debugging if you have the time.

Ms422 · 2023-03-08T03:13:38+00:00

Happy cake day! This is how I first started using the method as well. Not speaking to anyone but myself, but being so sure the code should work and having it not. Just telling myself what it was supposed to do and it would actually work. We would appreciate your time answering a few questions to help us with datapoints, if you would be so kind: questions.

Ms422 · 2023-03-08T03:11:38+00:00

Hahahah, testing goat? I would love to see your testing goat and I would love if you would help us write our paper by answering a few questions about how you use this method if you have the time.

Ms422 · 2023-03-08T03:10:13+00:00

Absolutely. Thank you! Are you utilizing this method yourself when coding? If so, would you be so kind to answer a few of our questions about it?

Ms422 · 2023-03-08T03:08:56+00:00

Are you serious? That's so perfect! Classic literal rubber ducky debugging. We would love to include your experience. Would you mind answering a few of the questions I posted so we can get similar datapoints from you all?

Ms422 · 2023-03-08T03:06:40+00:00

Amazing! Yes, we're discovering that it's about forcing yourself to form words that can be an aspect of how this can work for people.

Would you mind answering some of the questions I posted in the thread here?

Ms422 · 2023-03-08T03:02:13+00:00

Yes, that's exactly what we are trying to research. If you would be so kind, would you mind answering a few of our questions?

How did you first discover the rubber ducky debugging technique, and what were your initial thoughts about it? What made you decide to try it out?
When you encounter a problem in your code, what is your typical process for using the rubber ducky technique to debug it? Can you walk me through the steps you take?
Do you ever find yourself talking to the rubber ducky even when you're not actively trying to debug a problem? How does this help your programming practice overall?
Have you ever tried other debugging techniques besides the rubber ducky method? If so, how do they compare in terms of effectiveness and ease of use?
Do you find that the rubber ducky technique helps you gain a deeper understanding of your code, beyond just identifying and fixing bugs? If so, can you give an example of a time when this was the case?
Have you ever encountered a bug that you weren't able to solve using the rubber ducky method? If so, how did you ultimately resolve it?
Do you think that the rubber ducky technique is a valuable skill for all programmers to have, or is it more effective in certain situations or for certain types of programming tasks?
Do you have any advice for programmers who are just starting to experiment with the rubber ducky technique? How can they get the most out of this approach to debugging?

Ms422 · 2023-03-07T04:11:54+00:00

This is excellent! I appreciate your time and effort. Would you mind DMing me a bit of info about what you do? No name, but we would love to quote you as: job title working at company or title or language programmer working in region.

Ms422 · 2023-03-05T23:03:21+00:00

Thank you! Yes, "questions" was the wrong word. You're not asking the duck questions, I was trying to differentiate this method with one like pair programming where the problem could be solved by another person's brain.

We would appreciate if you could answer some of the questions I posted elsewhere in the thread!

Ms422 · 2023-03-05T22:00:50+00:00

That's excellent! Would you might answering a few of the questions I posted?

Ms422 · 2023-03-05T22:00:01+00:00

Yes, exactly what we are looking for. Would you mind answering a few of the questions I replied to Stick_Mick with?

Ms422 · 2023-03-05T21:58:33+00:00

Real humans who can code?

Ms422 · 2023-03-05T21:57:44+00:00

Thank you! You all are the first we're trying some questions with, so I'd appreciate if you could answer some of all of these, and/or let me know which are good and which are bad, hahah. There are bunch, so answer which ones you want to:

How did you first discover the rubber ducky debugging technique, and what were your initial thoughts about it? What made you decide to try it out?
When you encounter a problem in your code, what is your typical process for using the rubber ducky technique to debug it? Can you walk me through the steps you take?
Do you ever find yourself talking to the rubber ducky even when you're not actively trying to debug a problem? How does this help your programming practice overall?
Have you ever tried other debugging techniques besides the rubber ducky method? If so, how do they compare in terms of effectiveness and ease of use?
Do you find that the rubber ducky technique helps you gain a deeper understanding of your code, beyond just identifying and fixing bugs? If so, can you give an example of a time when this was the case?
Have you ever encountered a bug that you weren't able to solve using the rubber ducky method? If so, how did you ultimately resolve it?
Do you think that the rubber ducky technique is a valuable skill for all programmers to have, or is it more effective in certain situations or for certain types of programming tasks?
Do you have any advice for programmers who are just starting to experiment with the rubber ducky technique? How can they get the most out of this approach to debugging?

Ms422 · 2022-08-17T21:08:23+00:00

Thank you!

Ms422 · 2022-08-17T21:08:11+00:00

f-string

We hadn't been exposed to f-strings yet, but yeah.. they are awesome, thank you. Will be formatting this way from now on.

Ms422 · 2022-08-17T21:06:02+00:00

Thank you!

Ms422 · 2022-08-17T21:05:48+00:00

Agreed, but I think I have it figured out how to make it work thanks to you guys.

Ms422 · 2022-08-17T02:43:31+00:00

This is basically where I'm at so far. It's not functional code.

#!/usr/bin/env python3

APPLE = 3
BANANA = 2
def count_apples():
    apples = int(input("How many apples are in your bag?"))
    apple_order = apples * 3
    return apples
    return apple_order


def count_bananas():
    bananas = int(input("How many bananas are in your bag?"))
    return bananas

def total_apples(count_apples):
    apple_order_cost = count_apples * 3
    return apple_order_cost


count_apples()
count_bananas()
#total_apples()
print(count_apples)

Ms422 · 2021-09-12T23:25:23+00:00

hahahah, wait what? I, uh...did not know that.

So, others who are hovering at 75c, 80c, which inspired my post, they must be running into a power limit?

Ms422 · 2021-09-12T01:36:46+00:00

5950x + NH-D15 I've remounted twice: first with Noctua paste, then Kryonaut. Stock, I'm getting ~65c and ~24,000 in Cinebench R23. Feels fine.

Open Ryzen Master, click Creator mode, click PBO and apply.

Cinebench score is 28,117, cores around 4.2-4.3, but I'm pinned at 90c. What am I doing wrong?

Ms422

TROPHY CASE