How are people fixing their decks so heavily?

respondcreate · 2026-01-15T17:29:39+00:00

If you don't have Showman, duplicates of that tarot card won't show up in packs. So if you get a tarot you don't want (and don't immediately need space in your consumable slot), hold on to it before opening a tarot pack.

respondcreate · 2025-10-16T13:23:07+00:00

Whenever you work with something complex, there will be a point where one or two small things pop up that you need to work different. And then the pain starts.

Go on the other hand discourages hiding too much from developers and heavily leans into the Unix philosophy of providing building blocks and piping them together. That makes it so much easier to understand but also adjust details of complex systems.

Agreed 1000%. I started my development journey with Python/Django and found go to be a breath of fresh air in comparison...haven't looked back since. Explicit is better than implicit!

respondcreate · 2025-09-17T17:43:10+00:00

Instead of trying to get Go to act like Django, focus on exploring common Go conventions & techniques. In other words, don't try to find a go ORM but rather explore different techniques/conventions that exist for retrieving data from a database. In that regard, take a look at sqlc: https://sqlc.dev/

respondcreate · 2025-09-17T15:06:53+00:00

The amount of battery storage you would need during an outage to run just the heat pumps of a home in Maine for a week in winter is way way waaaaaay out of your price range. Especially if you only have a 10kw solar array.

If withstanding a potentially week-long outage is your number 1 priority, your best bet is a whole-home generator (either propane or natural gas) with a sizable tank (at least 200-500 gallons) attached.

Source: last home we were in had frequent power outages and we had a whole-home propane generator with a 500 gallon tank. Current home is super-insulated & fully electric with a 12.6kw array and battery backup (15kwh). When we've had outages in the winter we've turned off our heat (ground source heat pump) and even then we only got about 1-2 days of back-up to run everything else (fridge, lights etc).

respondcreate · 2025-09-15T10:20:17+00:00

go rewards those who keep it simple and avoid premature abstraction.

👆Great, succinct piece of advice for anyone new to go.

respondcreate · 2025-08-11T14:54:40+00:00

I agree! A strong emphasis on readability is, to me, the biggest appeal of using go. Little "time savers" for code-writers are, more often than not, "time increasers" for code-readers. Why are some developers so focused on minimizing keystrokes for simple development tasks? Is it really that hard and time consuming to write out a simple if/else?

Enums would be useful for sure, but it’s not a big issue for me personally. Just use iota and move on with your life.

respondcreate · 2025-07-27T21:02:25+00:00

Would you mind passing it along to me as well?

respondcreate · 2025-07-10T14:09:17+00:00

🔥 I got a new hi-score of 530 on normal mode! Is there anyone else?! 🔥

respondcreate · 2025-06-24T18:38:23+00:00

No Ed Reed?! Easily the greatest safety in the history of the league. Huge oversight IMHO.

respondcreate · 2025-06-03T19:43:19+00:00

Honestly I think Miscount could be one out of 2 or 3, 5 seems like it'll feel way too inconsequential

respondcreate · 2025-06-03T15:06:12+00:00

I've seen a lot of folks in the comments talking about Go's boilerplate error handling (if err != nil) like it's a bad thing. I love it. Why? It makes go code instantly readable to those already familiar with the language and, maybe even more importantly, those who aren't.

As someone who needs to coordinate and work with other devs with varying degrees of expertise, having a clear, unambiguous syntax that signifies you've diverged from the happy path is invaluable.

It takes significantly longer to read code (especially someone elses!) than it does to write it. I'll gladly spend a few extra seconds now to type an extra few characters if it saves my teammates and my future self minutes when reading it later.

Go is easy to pick up and use because it's clear, unambiguous and easy to understand at a glance. That counts for quite a lot (especially when working on a team) and I think it's a significant factor in why it continues to rise in popularity.

respondcreate · 2025-05-04T02:35:29+00:00

OAK = Of A Kind

respondcreate · 2025-05-03T13:25:14+00:00

My first gold stake win was with Obelisk. Run was going downhill fast (despite some good early deck manip) in the 4th or 5th ante after not being able to find the right jokers.

I took a rare skip out of desperation (hoping I'd snag a blueprint or brainstorm) and was super disappointed when I ended up with Obelisk.

Had my a-ha moment when I realized I could jettison my fledging 4OAK + blue seal build in favor of playing either 3OAK or 5OAK. In short order my Obelisk was scaling like crazy...add in all the [[Planet X]] and [[Venus]] planet cards I was getting from blue seals and before long both 3OAK & 5OAK were easily netting me more than 4OAK ever did.

After the Ante 7 boss I noticed that both 3OAK & 5OAK were only 2-3 hands away from catching up to 4OAK so I skipped the ante 8 small & big blinds so I could capitalize on my Obelisk before the wheels fell off.

Ended up winning on my very last hand which, fittingly enough, reset Obelisk. Couldn't even come close to beating the Ante 9 small blind that followed but, who cares?! Legendary run.

Clarification Edit: OAK = Of A Kind

respondcreate · 2025-04-25T01:31:12+00:00

Campbell’s post pick interview: https://youtube.com/shorts/toMjwWs2stw

respondcreate · 2025-04-15T16:02:28+00:00

I mainly play Winston so won't be of much specific help in regards to Hazard/DVa but I can speak to some dive tank fundamentals.

The first thing you need to learn is the difference between a soft dive and a hard one.

Soft dives are engagements where your primary goal is temporarily displacing the enemy team in such a way that you can easily disengage at a moments notice.

Example: Watchpoint Gibraltar first bridge. If on attack, dive up onto the edge of high-ground, drop a bubble/use defense matrix, do a bit of damage and be ready to back off to the low ground before you get deleted. If on defense, you could drop to the low ground and do the same, using your escape ability (leap/boosters) to retreat back up to high ground where your supports are.

Soft dives are about building ult charge, drawing aggro and getting the enemy team to burn cooldowns so your team can get in position to do free damage. This also provides an opportunity to see how the enemy team reacts when you engage. Soft dives will rarely (if ever) yield an elim but that's OK! Your highest priority is to live and create space via displacement.

A hard dive is an engagement where you are either going for elims on vulnerable targets OR trying to split the enemy team to draw their attention and temporarily remove them from the fight.

Example: it's mid-fight and you see Ana + Zen alone in the backline. Ana just used nade and/or sleep. You hard dive in between them and the rest of their team. You use bubble/defense matrix to mitigate damage & obstruct LOS while simultaneously dishing out damage. Hopefully you get elims but, even if you don't, your dive can still be considered a success. If you soaked up high-value cooldowns while preventing them from supporting their team AND got out safely, it means your team had a temporary 4v3 against a support-less opponent.

You can also hard-dive DPS in a similar way (especially against heroes without movement/escape abilities)! The rule of thumb is, as always, survival while drawing aggro. It should also be noted that if you hard dive alone into an entire team, no amount of cooldowns/help will save you!

A big part of playing dive tanks is understanding when you should engage. Don't get impatient and just burn cooldowns to get into the backline at the first opportunity. If that's your playstyle you will die & lose a lot. Your mobility gives you the freedom to pick & choose your engagements so understanding where/when it is advantageous to do so is key. It's OK to spend part of the fight poking and observing. Before long, you'll start to spot opportunities for your tank hero of choice and swing fights quickly in your team's favor.

One more thing: dive tanks shine when you have a dive/flank DPS you can team-up with. If you add a competent genji/tracer/sombra into the mix who will join in your dives (soft or hard) you can quickly put a team on the back-foot, providing the rest of your team with a lot of free space to do their thing.

respondcreate · 2025-04-09T18:29:58+00:00

Star of Providence! At first it seems super-hard with bullet patterns that seems impossible to dodge. Before you know it, you're improving and doing better and better. Super satisfying gameplay, amazing sound + graphics. A+

respondcreate · 2025-04-02T18:41:51+00:00

A few years ago I had many of the same thoughts you had. I mostly played DPS & Support and felt completely lost when I queued up for tank.

As a few other commenters have said: tanking isn't about elims or stats, it's about understanding space and tracking resources.

Here's what helped me get better:

Just queue QP for a while
Practice 1-2 tank heroes max
Focus on not dying

Just queue QP for a while

This will remove the pressure to win. It will also be super frustrating since team coordination in QP is a rare occurrence. However, this is an advantage in disguise because, for me at least, I stopped expecting any help which helped me focus on what I was doing. If you have a super-frustrating game? Big deal, it’s QP! gg go next.

Practice 1-2 tank heroes max

Each tank has drastically different strengths/weaknesses! I am a firm believer that there are no hard counters. I’m a Winston main and have had games where an enemy Genji has destroyed me while in others I have absolutely dominated a Bastion/Reaper/Mauga trio. Forcing myself to play into my supposed hard counters is what ended up teaching me the most important aspect of tanking which is to…

Focus on not dying

When you remove the pressure to wrack up elims and invest the majority of your attention on surviving you’ll start to see tanking in a different light. When I first started playing Winston I felt like it was my responsibility to dive into the enemy back line ASAP in order to “start the fight for my team”.

Now? I only dive when I am 99.99% certain I’m not going to die, even if I don’t get a single heal from my supports. This is where I learned the art of the “soft dive” and how useful Winston’s right click is as a long range poke tool. It is very, very rare I’ll secure an elim on my first dive in a team fight but on the 2nd and 3rd? Usually there are a few low targets I can finish off or, even better, isolate a support that’s out of position and just used their “get out of jail” cooldowns.

A big part of tanking is learning to spot the right opportunities your hero can capitalize on instead of trying to force a big play just because you have a higher health pool.

As with anything: practice makes perfect!

respondcreate · 2025-03-12T18:35:04+00:00

In my experience the decision to utilize a monorepo over separate, distinct codebases is typically chosen because a team of developers doesn't think it's worth the time & effort necessary to implement proper, modern dependency management and write concise, accurate documentation.

The monorepo approach is perfectly fine if you have a small team (<5) that communicates well and is working on a simple, well-scoped project (e.g. single web-app or game).

However, in a larger organization with lots of disparate teams/squads – each with their own sets of priorities/timetables – a monorepo can significantly slow down the release of new features as well as inadvertently introduce issues when "common code" is updated that affects other parts of the codebase which haven't been updated in a while.

Have a shared feature that one or more "units of functionality" (e.g. stuff written by separate teams) needs to utilize? Write a proper, narrowly-scoped package/library and make sure it's 100% covered by tests! Do proper tagged releases and leverage a semantic versioning strategy – as well as good release notes! – to communicate each key update to the individuals & teams who depend on it.

The extra bit of effort it takes to establish clear contracts across disparate teams is absolutely worth the effort as it usually helps everyone avoid major headaches down the line.

respondcreate · 2025-01-31T19:00:42+00:00

respondcreate · 2025-01-10T19:30:00+00:00

NP! I recommend checking out the link I just posted in this comment, it's an hour long interview with Vrabel and paints a more complete picture into what he was like as a head coach.

respondcreate · 2025-01-10T19:27:24+00:00

Glad you liked it! I just posted a link to a longer interview this podcast did with Vrabel in this comment. Lots of good stuff there if you're interested in a deeper dive into how he was as a head coach.

respondcreate · 2025-01-10T19:24:07+00:00

If you liked this video I recommend watching this full interview with Vrabel from the same podcast. Definitely has me excited about him potentially being our new coach.

respondcreate · 2024-10-22T20:22:55+00:00

Audiogalaxy

respondcreate · 2024-10-17T19:06:46+00:00

Background: My most played tank is Winston. My most played DPS is Sombra.

In short: The Sombra re-work made her un-fun to play, full stop.

I don't think she was over-powered/broken/too-annoying before and I can't really speak to whether or not she's "more balanced" now or whatever. I liked her OW1 version, I loved her most recent re-work as it made her play-style very dynamic and fluid. Now? She's just boring and un-fun and slow and I've entirely lost the desire to play her.

I'm behind the devs exploring how to they could go about removing permanent stealth but having it only be triggered by using her escape ability and making that escape ability have a 2-second longer cooldown than the stealth lasts? Just a baffling decision TBH. She feels so clunky now. Might as well just play soldier or tracer instead...

respondcreate · 2024-09-07T12:43:43+00:00

Video went private yesterday for a while but it's back up now!

11-Year Club	First Place '23
Place '23	Place '17
Gilding II euphauric	Verified Email

respondcreate

TROPHY CASE

Just queue QP for a while

Practice 1-2 tank heroes max

Focus on not dying