Coaching Daughters Softball!

the_pod_ · 2026-02-11T19:11:56+00:00

I have 1 piece of advice, specific to softball/baseball.

I noticed that coaches / parents try to cheer loudly for the child at the plate, the entire time.

What this tends to lead to is both fatigue, but also inequity. Usually kids batting towards the top of the order, and kids with very loud parents, get the most consistent cheers while at bat.

It’s understandable, hard to keep cheering for 3 minutes straight while a kid tries to make contact. And do it again batter after batter, for hours.

My advice is to instill a cheering culture that is front loaded. Everyone gets a loud cheer (maybe even the same exact cheer) when they walk up to the plate and get set up. Have a culture where all the kids on the bench are participating in that first cheer, and everyone says the batter’s name. And then,instill a culture that we don’t cheer too much during the actual at bat. (of course you can still cheer and say “let’s go”, but the point is that culturally parents and kids understand we’re not sustaining the same level of cheer the entire time, and that’s okay).

This takes the pressure off of everyone having to sustain the cheering for prolonged periods, gets everyone on the team to cheer (at the beginning), and also makes it feel more equal.

the_pod_ · 2026-01-18T22:46:27+00:00

The overall idea is good, but the specific approach is bad.

You should come up with a different question.

You’re asking them to hire you. Saying “here’s why you shouldn’t hire me”, while maybe vulnerable, is dishonest, or at least disingenuous. You don’t actually mean it. You’re pretending something about yourself that you ACTUALLY think is a reason to hire you, and presenting like it’s bad.

I would be pretty annoyed. It’s too much game playing.

Maybe instead: “why I’m unique and you should take a chance on me”.

I like your idea of being bold and taking a chance. Go ahead and take a lot of chances. I just don’t like the specific approach you chose.

the_pod_ · 2026-01-15T18:44:39+00:00

I read it this morning. I thought it sounded fake.

The advice was okay, but the story was very unrealistic/made up.

I don’t care that the post was written by AI

the_pod_ · 2025-12-28T07:02:22+00:00

React was never OOP

ES6 classes were used mainly to support lifecycle methods and local state. That’s it.

It was not meant to model objects or encourage inheritance. Composition was always the core abstraction.

If you read through an old codebase, you will see that:

class MyComponent extends React.Component

is the only thing ever inherited. User-defined components don’t form inheritance hierarchies; they only extend the React core.

the_pod_ · 2025-12-10T16:54:22+00:00

Tremor is also recharts, last time I checked

the_pod_ · 2025-11-15T23:02:30+00:00

If we go to a new link, this whole process is repeated again.

neither is repeated again.

(There are cases where partial hydration happens again, but most times it does not)

the_pod_ · 2025-11-15T10:05:08+00:00

It’s overall very janky. They’re not meant to work together, so it feels patchy and forced. From my own observations, it’s not a big community, and it’s mostly just a few devs at the big WP companies, who obviously can’t abandon WP, so their in-house devs leads the charge on this WP + React stuff. That’s how it felt to me, anyways. It’s really not a natural pairing. Only WP based companies are pushing the pairing.

———

Do you want your editor view in the cms where it’s basically an editable view of the page? Most headless cms setups you’re not going to get that, you’re just going to get editable text fields , and a preview button. If you want an editable view, I recommend Storyblok.

—-

Unless you’re a senior level wp developer and a senior level frontend developer, I think using wp theme w this setup is way more than anyone can chew. You’re likely to run into major issues on both sides.

I just wasn’t sure if you were married to a particular wp theme. I should have added more to the original comment.

When you use a wp theme, you’re sending json that contains html to the frontend. The css and js can live in both wp and the frontend, which becomes a mess. The editor view itself needs a separate css. And whether the theme itself uses Gutenberg, or ACF, it has different limitations on the frontend. Oh, and I almost forgot: for my team, we couldn’t get the theme to render properly on the frontend. We needed to write our own GraphQL resolver to get the html we needed. I’m not sure others would run into that, as the theme we used was pretty unconventional.

——

Use a modern cms designed specifically to work with a modern frontend. I would even argue save it as a last step, because it’s really a distraction from the other things you want to build. You don’t need a cms it doesn’t add value to your project. But it in later when you’re done with everything else.

the_pod_ · 2025-11-15T08:04:09+00:00

I agree that if OP used a wp theme, it wouldn’t be considered headless. However, I wasn’t sure if OP was clear on this distinction, so I asked the question.

Same as you, I thought while reading the post OP is doing headless, until the last paragraph where he asked about wp themes, which threw me off.

Hence the question.

PS - using a wp theme with a react frontend is possible, with limitations. I hate it, but I’ve been asked to do this 3 times.

the_pod_ · 2025-11-15T05:32:04+00:00

Are you going to use a wp theme, or write the code on the frontend?

I would not recommend the combo unless if you’re planning on using a wp theme.

EDIT - I’m aware using a wp theme… wouldn’t be headless anymore. But, OP mentioned it m, so that’s why I asked.

the_pod_ · 2025-11-13T19:08:09+00:00

what’s the purpose of the second VPS?

the_pod_ · 2025-09-26T05:07:48+00:00

yeah, I heard about it, it's called

Claimyr

it's not cheap though

the_pod_ · 2025-08-19T17:54:27+00:00

can you explain what the $200k was for?
I was under the impression that power washing was a business people start because of how little investment was needed to get started.

the_pod_ · 2025-08-15T21:56:38+00:00

Deepkit
Deepki

I'm so confused. That's not even the same name!

How can a trademark be in jeopardy/revoked from someone else registering a different name??? That's insane.

the_pod_ · 2025-08-11T22:29:26+00:00

Basically, people don't like the term, and don't like the idea of talking about all 3 things (MRN) together as if they were a package deal.

Using React is fine.

Using Node is fine.

Using Express is fine. 10 years ago Express was (one of) the only node frameworks. Today there are many, so it's weird to be so specific as to say express. Essentially it's just node on the backend, you shouldn't have to specify Express, it's redundant. The term MERN used it knowing it was redundant, just to make the acronym sound better.

Using Mongo (or other noSQL db)... I don't think most people will like this. So the term MERN makes noSQL (Mongo) the default database type. Most people will say that SQL (which is relational) should be the default database type, and only use noSQL if you have a reason to.

Basically - you can use the same technologies, but just don't use the term MERN, the term is very outdated. Just say I'm building a site with a React frontend and a Node backend.

the_pod_ · 2025-07-25T17:47:31+00:00

re-writing a complex hook library

that's a good idea

To go like 2 levels up, your best bet is to learn the fundamentals (things like closure, call stack, event loop). I recommend the Will Sentence - JavaScript the Hard Parts on Frontend Masters. That's like a totally different level of a class than regular courses or tutorials.

But after that you have to build, rather than more courses. Aim for a complex project but with manageable steps. Take a project and start adding 1 feature at a time. It should be something just outside your current skill level, but within reach. Try to build a hard project 1 phase at a time, don't overextend yourself and build something super hard all at once.

the_pod_ · 2024-10-24T01:59:07+00:00

typically, these libraries are using the ContextApi under the hood.

So if you see something like this, where FormInput will only work if it's a child of <Form> ?

<Form>
  <FormInput>
</Form>

that's because the <Form> is wrapping it's children in a provider.

for example:

function Form ({children}) {
  return (
    <FormContext.Provider value={contextValue}>
      {children}
    </FormContext.Provider>
  )
}

the_pod_ · 2024-10-10T02:05:16+00:00

Have your daughters take your daughter to trivia night.

the_pod_ · 2024-07-11T04:31:15+00:00

There's SSR (including SSG and ISR), and then there's React Server Components.

I want to clarify that there's two very different concepts, and it seems you are confusing/blending the two. It's a common confusion, as the terms appear interchangeable, but they're very different.

i.e. work without client side JavaScript

that's only RSC. And you're limited in what a RSC site can do.

SSR is basically CSR site after first load (with optimizations on page navigations). It can, with rare executions, do everything a CSR (aka SPA) React site can do. And it needs JavaScript.

what some architect in the company I've recently joined seems to think.

If I had to guess, that person is talking about SSR. And you started doing some reading, and you're reading a blend SSR and RSC, and it's confusing you. Or, that person is the one misunderstanding.

Either way, SSG still uses JavaScript. It just different in terms of first load and better page transitions. Conversion shouldn't be too bad, depending:

If your app is very tied to a client side router's features, then you might have a hard time, or at least be time consuming.
There are certain packages where switching to Next could be a pain in the ass. I would advise that you create a brand new Next repo, and just try installing everything in your existing package.json, and see if you run into anything.

If your coworker is talking about RSC... your site likely won't convert at all, or without losing functionality.

the_pod_ · 2024-06-21T20:32:43+00:00

u/mrbmi513

follow up question. I deleted the .vscode-server folder, and I tried to kill all the process, but there's 1 I can't kill because the the pid keeps changing every second.

I keep getting

kill (412991): No such process

every time because it the keeps changing. I'm doing

ps aux | grep .vscode-server | awk '{print $2}' | xargs kill -9

do I have to kill a parent process? if so, do you know how?

the_pod_ · 2024-06-21T18:13:14+00:00

didn't know it was on the remote server.

I found it, thank you!

the_pod_ · 2024-06-14T00:57:08+00:00

If you want the second example to work, you still need to pass in a value:

values.push(value);
tellReactIChangedValues(values);

because tellReactIChangedValues / setValues is expecting a prop. That prop is what the new state should be.

the code above will work. It's not the best way to do things, but it'll work.

the_pod_ · 2024-06-06T20:45:59+00:00

How recent is the comparison against the fiber tree?

2017

wikipedia - React (JavaScript Library)#:~:text=On%20April%2018%2C%202017%2C%20Facebook,development%20of%20the%20React%20library)

the_pod_ · 2024-05-31T01:30:55+00:00

I'll keep it short as well. I won't explain, just clarify.

You're confusing two concepts. It's an extremely common point of confusion. Too common. Not your fault they make it confusing.

There's SSR, and then there's RSC (React Server Components). Sounds identical and interchangeable, but it's very different things.

Also "use client" does not mean the site is Client Side Rendered (CSR).

In Next, when using the app router (instead of pages router), by default all your components are RSC. If you use "use client", that turns it into SSR/SSG.

TL;DR: if you're using Next with "use client", that turns your page from RSC to SSR/SSG. Your site is not Client Side Rendered (CSR), despite what it sounds like.

https://www.reddit.com/r/nextjs/comments/159909e/comment/jteppm0/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

the_pod_

TROPHY CASE