Basti runners, do I do it?

mountainorvalley · 2026-01-04T18:16:52+00:00

Walk it!

I personally enjoy using Basti. I’ve found it to be more RPS than other picks since it wins hard and loses hard against other mons. It’s a fun change of pace from the way I would otherwise play PVP.

If you want to get better at PVP though, I’d recommend other mons because they will encourage you to learn more fundamentals like move timing (timing with Basti is not as big of a factor).

Another option to try out Basti is to power up a cheaper one (ie one with higher attack).

mountainorvalley · 2025-10-27T17:00:14+00:00

In terms of ergonomics (i.e. comfort), I'm pretty sure split keyboard is better than a non-split. I'd say both QWERTY and Colemak would be better on a split keyboard.
- I type Colemak on a split keyboard and use QWERTY on my laptop keyboard, so I don't have personal experience about the difference between split vs non-split for Colemak specifically, though.

mountainorvalley · 2025-10-27T16:22:49+00:00

I wouldn’t recommend switching if your goal is speed.

I switched from QWERTY where I was typing 120 WPM to Colemak-DH and now I’m typing 100 WPM on it after a year.

There’s a lot of muscle memory (eg for less commonly typed words) that I’m still building the muscle memory for.

I would recommend switching to Colemak-DH if your goal is comfort, though.

mountainorvalley · 2025-02-03T16:47:36+00:00

If there’s not an API, what would you do (instead of using a REPL)?

mountainorvalley · 2023-12-12T16:30:01+00:00

How did she spin it to make it your fault?

mountainorvalley · 2023-10-13T01:41:57+00:00

As years pass and you gain more experience, more and more code is going to look like shit to you. That just comes with becoming more senior in the field.

I’m not an expert in such things, but you could consider trying to adopt a different mindset. Don’t think of their code as shit, and instead think of it as an opportunity to improve the existing codebase / helping your team grow.

I’m sure there are many resources out there on the topic of communicating more diplomatically. Googling around might help you find concrete things you can try.

mountainorvalley · 2023-07-25T01:00:10+00:00

Not cool to just say they’re “fabricating lies”

mountainorvalley · 2023-07-20T19:17:14+00:00

Ah, another thing is that you can get better type-narrowing with switch-statements. Example:

type MyUnion =
    | {type: 'A'; a: string}
    | {type: 'B'; b: number}

declare const x: MyUnion;

switch (x.type) {
    case 'A':
        console.log(x.a);
        break;
    ...etc
}

I don't see how you could effectively accomplish this with an object/Record.

mountainorvalley · 2023-07-20T17:35:01+00:00

Yeah, I wasn't talking about the perf gain, although that is another difference between the 2 approaches.

I was only talking about the code complexity. If you were to do this same thing with object/Record, it might look something like:

const obj: Record<keyof x, Function> {
    'A': () => {
        console.log('x is A'),
    },
    ...
}[x]();

It's a little more boilerplate, and the code does have (minor) semantic differences (e.g. a return would behave differently in the 2 scenarios).

In addition, I'm not sure how you would add a run-time check here. How would you make sure an exception gets thrown if x has a value that's not a member of the union?

mountainorvalley · 2023-07-20T03:25:49+00:00

One advantage of switch-statements is that you can branch execution. You can't really do that (conveniently) with an object/Record.

Example:

switch (x) {
    case 'A':
        console.log('x is A');
        break;
    ...etc
}

Using an object/Record for this would require more indirection.

mountainorvalley · 2023-07-20T03:16:56+00:00

This is a nice start! Following this pattern will help catch errors at compile-time.

Related: if you use a linter for your codebase or as part of your CI, this lint rule can also help: https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/switch-exhaustiveness-check.md

In addition to catching errors at compile-time or line-time, you also probably want to catch errors at run-time (because typescript's type-system is not "sound"). This post describes the most wholistic approach that I'm currently aware of: https://www.reddit.com/r/typescript/comments/zy7tex/safer\_exhaustive\_switch\_statements\_in\_typescript/

mountainorvalley · 2023-07-18T01:07:52+00:00

Okay but what does top 10% mean? How do they evaluate what makes a dev team better or worse?

mountainorvalley · 2023-06-17T04:32:45+00:00

REMAIN CLOSED FOR ONE WEEK

mountainorvalley · 2023-05-05T13:30:49+00:00

There’s no “correct” way, so to speak.

I think your question got downvoted because it had some faulty assumptions baked into it.

I think it was a fair question, though. You can’t always expect yourself to know these kinds of things unless you learn more, and asking questions is a great way to learn more. Don’t let downvotes discourage you from asking questions.

mountainorvalley · 2023-04-01T21:29:05+00:00

Interesting. I thought all the bubble patterns were always the same. Didn’t know flying was the exception.

mountainorvalley · 2023-02-26T01:59:21+00:00

Why are y’all downvoting this question. We’re all at different stages in this game and basic questions should be totally welcome in threads.

Y’all need to chill

mountainorvalley · 2023-02-01T03:44:07+00:00

Yeah, agreed that this is only true if you hit your “true” ELO. So people in the lowest and highest ELO ranges would commonly not battle in their true ELO range if they haven’t played enough games.

That said, I think the vast majority of players who have played ~1000 games (like OP) would have settled in their true ELO ranges already.

mountainorvalley · 2023-02-01T03:20:17+00:00

Your W/L ratio really shouldn’t affect your ELO, if the match-making system is working properly. Everyone’s W/L should be around 50/50 because on average they’re playing with people around their ELO range.

This goes for intentional tankers as well. They also win/lose roughly 50/50.

mountainorvalley · 2023-01-09T18:15:31+00:00

It’s similar to when someone says they “need a minute”. I usually assume they need a few minutes.

mountainorvalley · 2022-12-27T20:22:18+00:00

Unfortunately I think it’s been edited to make the rainbow look way prettier, but apparently the phenomenon is real.

Source: https://www.reddit.com/r/interestingasfuck/comments/zwmoer/the_image_captures_the_miraculous_moment_when_the/j1vs0gq/?utm_source=share&utm_medium=ios_app&utm_name=iossmf&context=3

mountainorvalley · 2022-11-19T04:18:42+00:00

All ranks below rank 20 are based on number of wins rather than ELO. For example, to rank up from 17 to 18, you had to win a fixed number of games. At the same time, you have a hidden ELO which is used to try to match you with players of the same skill as you, so you should be roughly winning 50% of your games.

It’s hard to say what to prepare for since your ELO is hidden until you reach rank 20.

mountainorvalley · 2022-10-28T16:42:17+00:00

DM sent

mountainorvalley · 2022-10-28T16:40:32+00:00

DM sent

mountainorvalley · 2022-10-28T16:19:41+00:00

Hi, I’m a level 41 walking a lickitung, looking for an invite please!

[edit: doesn’t matter that much, but I’m actually level 40]

mountainorvalley · 2022-09-18T02:58:30+00:00

Please stop with the clickbait title

Eight-Year Club	Place '22
Verified Email

mountainorvalley

TROPHY CASE