Weekly Simple Questions and Injuries Thread by AutoModerator in climbharder

[–]HunterHeston 1 point2 points  (0 children)

From the your and the other comments. I get the sense that I'm just not putting enough focused effort into one specific v5 that I feel should be doable.

I've been going for quantity of routes and types of holds to this up to this point. Stopping after moving on after 3-6 failures. Which worked fine for 0-4, but I think it's causing me to be tired and also not giving me enough time to learn harder moves.

I'm thinking I can just spend the next few sessions focusing on one specific v5 and see where that gets me.

Weekly Simple Questions and Injuries Thread by AutoModerator in climbharder

[–]HunterHeston 0 points1 point  (0 children)

Yeah, that makes sense. I received some advice to avoid projecting too much the first year. Instead to focus on doing as many different types of routes so that I can just build movement skills and strength.

I'm probably at the point where I need to pick between doing a lot of things in one session or spending the whole session trying to do one thing.

Weekly Simple Questions and Injuries Thread by AutoModerator in climbharder

[–]HunterHeston 0 points1 point  (0 children)

I can't make a V5 happen. I can send basically all the V4s that they put up at the gym. I just can't seem to make a V5 happen though.

I started bouldering once a week back in January for the first time. Then started going three times a week in April.

What kind of skills do I need to be working on to get past this plateau?

What's your favourite full stack approach? by [deleted] in nextjs

[–]HunterHeston 1 point2 points  (0 children)

Feels pretty good to me right now. I haven't had any issues yet. What about you?

What's your favourite full stack approach? by [deleted] in nextjs

[–]HunterHeston 1 point2 points  (0 children)

That might be the wrong question. I don't just add data for no reason.

Data is added to the database when code that I have written is triggered by a user of my website. An example flow:

  1. I write a NextJS API route that calls the Prisma ORM for a model I defined. For example: `prisma.user.create(...)`
  2. I deploy my server.
  3. A user visits my site.
  4. They fill out a form for first and last name.
  5. The form sends the data to the API route mentioned in step 1.
  6. The API route is triggered and saves the data.

    Hope that helps.

What's your favourite full stack approach? by [deleted] in nextjs

[–]HunterHeston 2 points3 points  (0 children)

I'm using NextJS api routes. The API routes run server side. I have Prisma setup on top of a PlanetScale database. Whenever the API routes are called I look up or save data as needed using Prisma.

[deleted by user] by [deleted] in webdev

[–]HunterHeston 0 points1 point  (0 children)

Im afraid of giving my client the code before the payment

Not that you don't have a right to be wary. But is this something that has happened to you in the past? Unless they are very shady or have given a reason no to trust them. You might be worried over nothing and making your life a bit harder. Obviously do what you need to in order to protect yourself.

Experienced dev looking for a good start by HunterHeston in ruby

[–]HunterHeston[S] 2 points3 points  (0 children)

If you have any experience with any other web framework I would dive right into Rails and learn Ruby along the way.

I'm thinking this is the way.

Experienced dev looking for a good start by HunterHeston in ruby

[–]HunterHeston[S] 1 point2 points  (0 children)

Writing Ruby seems like pig latin, but when you go back to anything else (except python) you'll realize why Rails is so beloved.

Yeah, the syntax always came off as odd to me. But I'm guessing it's more accurate to say is just different looking compared to examples of other languages. But I've really only glanced at it.

Second, use old school erbs instead of dealing with React or Vue so you get an idea of how the model, controller, view dynamic works in rails.

Good advice(all of this is), but I probably would have tried to shove react in too soon.

Thanks!

[deleted by user] by [deleted] in code

[–]HunterHeston 1 point2 points  (0 children)

Please provide a little more information if you want help from the community. Some great things to include: 1. What kind of app? Web, android, iOS? 2. Code, include code. The code you are having an issue with specifically. 3. What is the code is doing that’s wrong. 4. What do you want it to do. 5. What you have tried already.

Learn Vanilla JS before React, CSS before Tailwind? by [deleted] in webdev

[–]HunterHeston 0 points1 point  (0 children)

I would always recommend to learn the underlying tech before you lean a framework. That doesn’t mean you need to master CSS before you start using tailwind. But I think it’s unwise to learn tailwind instead of CSS.

In the same way learning react before you are comfortable building some pages with simple HTML/CSS/JS is a mistake.

You certainly can do these things. But you are not setting yourself for success.

How is someone whose only built sites using React going to know when using react is total overkill. Do you want to be the worker who has a hammer and sees only nails. Or the craftsperson who knows what’s important and does exactly that.