Відео

Thank you! What would you like to see next?

I can only grow codebases, but no chest hair.

Absolutely. Even if sagas aren't around that much anymore, the things you can learn from sagas will simplify your code 10x.

Thanks a ton for the compliment! Excited to see what you think by then end of the video 🔥

@@JanHesters Excellent, excellent video. I had to watch it a few times. Subbed! Keep up the good work!

@@JanHesters I don't see a section on Monads. I was hoping that was covered. That's the only thing I'd mention.

@@makerKID5 Will be their own video some day! Thanks for the suggestion.

Thank you for the kind words! Anything specific you want to learn?

Love back from Germany! x3

More fly than seagulls!

@@JanHesters :D

Thank you for the kind words! 🙏 Part two came out today :)

Thanks a ton! 🙏 It released today 🔥

Out today!

I can understand. Many people dislike it, which is why it has gotten unpopular. I made this video because many of my company's clients still use it, and because many jobs still require it from my mentees. But no hard feelings ❤️

Got it. I'm def planning on dedicated videos for each of these technologies. Thank you for sharing your feedback! 🙏

Thank you! 🙏

Thank you for your comment! 🙏 There are tons of alternatives like AWS, DigitalOcean, or Railway. When using Remix, I also often work with Fly.io. In my opinion, Next.js can handle full-stack development with its API routes easily. I'd only break out your backend for complex or special needs. Then separating the backend (e.g., using Node.js, Go, Django, or others) can be a better approach.

It's a metaphor for robust code and the `pipe` function haha Thank you for the kind words! 🙏

Thank you for the kind words! 🙏

1.) Thank you! 2.) Never selling trading courses lol But I might make videos on how the blockchain works in the future because it might become more relevant. 3.) Haha some other people in the park during that day.

Thank you for the kind words! More to come 🔥 And just curious, anything specific you'd like to see?

@@JanHesters If you're on to SaaS, you can share how we can research for SaaS, market and scale. Recently I was trying to build a SaaS project but stuck at some point to find the unique solution I was looking for, for example: do stuffs by pdf selection such as highlight, translate, take notes, explanation via ai, and then get them together in a docs.

Thank you! 🙏

Thank you for the kind words! 🙏

Insert big brain meme 😄 Thanks for the compliment!

That's so kind! Thank you 🙏

Swagger is perfect for API design! 🙏

Hope it helps! 🔥 Curious, what kind of API will you design? 🤔

You're welcome! And you're right. RDD is close to A.I. Driven-Development. Buuut, A.I. isn't there, yet. It still needs a human in the loop.

What? 😄

@JanHesters you're not blinking at all for the whole video for some reason Relax a bit and blink

This is just a fancy way to call a function that preserves the "this" context. Here is a more simple way to write it: const result = fn(...args);

You're welcome!

Thank you! I wanted to try something new haha! 🙏

i use webstorm, i see no reason to use husky 😅

@@devyb-cc I've never used WebStorm, so I don't know how they compare, but I HATE the idea of Git pre-commit hooks in general.

@@jamescbender43081 well, jetbrains products all have something like hook. i usually do it only to analyze my code, in case i left some TODOs or unused imports.

Interesting! How do you do it? Do you just run linting and type checks in CI/CD and let people push even with linting or type errors?

@@JanHesters Yeah, we let developers send PRs up with linting errors. Before anyone even reviews it, it will run through the CI/CD pipeline, so linting, and all tests (unit, E2E, etc.) get run automatically and have to pass before the PR can be approved, no matter how many votes it gets. We do this for a few reasons. First, I want all the long-running/resource-intensive steps to run on the server so they can run faster without blocking the developer from working on something else. This also ensures that the branch will integrate with the existing branch. The other big reason, and why we stay away from pre-commit hooks (like Husky) is that I want my developers to be able to commit (locally) frequenty, even if these commits are "work in process" commits, aka "I want to commit what I have so that if the next thing I try to do totally f's things up, I can go back to the last commit." and making them conform to a bunch of rules designed to protect the main branch causes a lot of friction, and discourages these kinds of commits. As log as the "last" commit that's part of the PR conforms to the rules, as enforced by the pipeline, I don't care what the previous commits in that PR do.

Will create one! 👍

Thanks for the kind words!

Why? 😄

@@JanHesters My guess is because you’re talking really quickly. I get not wanting to be too slow, but people who like to go through content at a quicker pace (such as myself) can set their playback speed quicker. So your normal pace should be slow enough for people to comfortably understand what you’re talking about. But great video other than that minor nit pick

@@tobydixonsmith6126 Thank you for the feedback! 🙏 I'm experimenting with my deliver style in upcoming videos.

​@@JanHesters to be honest it's really fast and loud for me. Btw nice content ❤.

Thank you!

Right into the feels! 💔😄 Wear whatever you want 😉

Absolutely! But it will take a few months, I have a bunch of other topics planned first. Thank you for the compliment and the suggestion! 🙏

Appreciate it! I like shooting outside because we are inside enough as developers haha

You're welcome! 🙏

Thank you! 🙏

I have the privilege of working with the best when it comes to style 😉 Thanks!

Thanks so much!

A few of me were, yes 😉

Absolutely agree. I said at the end of the video that the examples in this video are contrived and optimized to be understandable. I disagree that OOP coder is easier to test because by default class inheritance is the tightest form of coupling and frequently requires mocking. But if you have good examples for OOP code that is easier to test than pure functions, please kindly point me to it 🙏 And regarding performance, IMO you should favour readability over performance UNTIL performance becomes a bottleneck. I can't speak to those other languages you mentioned because I'm specialized in JavaScript.

​@@JanHesters Easily testable OOP code honestly follows the same guidelines. Given the same input, you should get the same output. The thing that tends to get people thrown off is that with OOP and stateful classes, you'll have adjusted one of the inputs if you run the same method twice. In order to replicate the same thing you also need to replicate the class instance. Just with a really basic class (pure garbage I'd never write normally, so sorry about it being a bad example): class Addition { value; constructor(initial) { this.value = initial; } execute(value) { this.value += value; return this; } } assert(new Addition(2).execute(2).value, 4) would be 4, every single time you run it; same as FP. If you chain it like new Addition(2).execute(2).execute(2).value then you've fundamentally changed what it does, just like FP. Same principle, different execution. The class example is extremely stupid though, wouldn't write code like that normally, state is best stored in DB regardless. One of the benefits to using classes in JavaScript is that while it looks as if the objects all have their own methods, they are all only allocated once, which is a major benefit to anonymous functions added to objects which need to be allocated every time. This is not as important now with imports and exports being a thing, but look into how stupidly much memory is used in a regular application due to all of the object nonsense JavaScript injects since it needs to treat everything like a nondescript object. That's not the case in Java or C# for example, where they only keep the bare minimum to identify the class. As for why I think a lot about performance, it's because I work with larger datasets frequently, so I have to walk the tightropes of readability and performance a lot. This is true for both backend and frontend things; where updating/inserting 50k DOM elements is hell and takes ages even in a best case scenario, whereas remaking the entire HTML structure as a string and replacing all of it takes a few seconds. However, it only takes a few seconds under the assumption that I reuse memory through not allocating anything extra. This means reusing variables and pre-allocating memory as much as possible. I do enjoy FP though, I reach for it whenever possible, but only when I can afford doing so. I never do anything particularly crazy with it either, but the idea of passing functions to other functions is something I use regardless of FP or OOP. Command pattern is just that. The Addition class I gave as an example would be one of the classes one would pass to something that processes it. Somewhat unreadable, but with enough complexity in the business logic, it's totally worth it. Sorry about the long reply, not sure if you're going to read it either, but I hope my sleep-deprived brain didn't spew out too much nonsense.

@@CottidaeSEA Thanks for the long reply! I for sure read it 🙏 Got it. As you said, the code you gave as an example is different from how you'd write it, but let me still address it because it demonstrates one of the problems I had with testing (and reading / understanding classes) as opposed to FP - even in production codebases with "real" code examples: You need to set up the internal state to run the different functions, and it's hard to understand a method in isolation. For example, if you had another method on that class, that would only do something if `value` was three, you'd need to either call `execute` three times, complicating the test. Or you'd need to manipulate the class directly, which then would obfuscate the test so it resembles the real usage less. With FP and pure functions, they usually map one input to an output, making it trivial to write tests for them and truly test them in isolation. And thank you for clarifying where you come from. Totally makes sense that you think about performance so much! 👍 I've been a fullstack dev for most of my career and over time I learned the best approach to browser performance is "fix it if it breaks, otherwise favor good DX (testability, readibility etc.)". (Most) Browsers are so fast nowadays that it doesn't matter if you take up extra memory. > I reach for it whenever possible, but only when I can afford doing so This pretty much sums it up! 😊 And in my experience, in most JS server and browser codebases, you don't need to optimize for performance so granularly. (Especially on the backend, if performance mattered, the teams switched to Rust or another fast language haha) Thanks again for your thoughtful reply!

The examples in this video are NOT meant to be production code, but just to teach the concepts of FP. (I mention it at the end of the video.) But your comment is good advice, I hope more people read it!

Thank you for the kind words! 🙏 That's exactly the target audience. So far, this video received less views than my other ones, but I hope people who really need to find it, find it through SEO :)

Thank you!🙏

Thank you and you're welcome! What topic would you like to see covered next?