hey, your content is very informative, I think it could be even better if you had smooth transitions to where you add lines of code, since it may be a bit hard to follow when you’re jumping between different lines
This makes sense! Still figuring this format out. I think the issue is that the _camera_ moves too fast: i.e. the line of code that my editor is on. This means that it gives the impression that it's snapping back and forward too much. Will work on it, thanks for the feedback!
Hi! This is hopefuly a constructive critic since I like the channel. This video editing style of removing spaces and silences may work for content such as Fireship's, which are mainly small snippets of info/jokes, but (for me at least) don't work for long code explanation like yours; pauses matter, they give emphasis and structure to speech. Keep up the good work!
One suggestion is to slow it down alittle bit. I don’t mind the fast pace, but as others pointed out, it’s just too hard to follow the code with many camera jumps. Thanks for the content, I’m getting up to speed with typescript and I feel like your content has helped the most.
Hey, Matt. Great vid as always! But yeah, it was a little hard to follow with all those sudden transitions and jumps around the code. If those could be a little smoother, this video would be an absolute banger! Really love your videos - they’ve helped me massively improve my own development and understanding of TS. Leaving this comment as a fan of your content who just wants to see you put the best stuff out there.
I think that's good feedback, I definitely find the same. Playback at half speed and having a lightning finger on the pause button is always helpful. 😅 I do like the fast speed as reference though when I come back later after letting it sink in.
This guy is just showing off , does he speak so fast in everyday life, does he speak so fast at work , just imaging he's trying to explain a complex concept to a junior dev, nightmare
Agree with previous comments that although those videos aim to be as condensed as possible, at this point, it's really hard to focus watching them. With so many jump cuts, it's very hard to keep track where in the codebase you currently are, as eyes need few seconds to figure it out. Maybe you could experiment more with typing instead of copy/pasting, and scrolling, rather than jumping between sections?
To fest transition hard to to keep up and a little bit annoying. That how I feel when watching this video. Love your content because of this give a comment hope that help.
Hey Mat! Amazing video content, one thing that I could suggest is to zoom-out a little when showing code, I personally find a bit hard to follow when the code is too large like this. Amazing content nonetheless!
I can't believe how many videos of yours I've gone through in the last few days because you manage to distill so much information into 4-minute videos. I've been looking for reasons why Zod will solve some problems for us and this has sold me.
Hey Matt, are you trying to do a lot like Fireship? Dont get me wrong his videos are great, but I think your content had a different format which in many ways I found that it suit best your approach. But hey, keep rocking and experimenting if that's whats happening. I am glad and thankful you are doing all this effort in making great content. Cheers
Zod is now at the center of a project I've been working on. I use a single schema to validate form inputs, database writes, requests from the browser, and to apply types going back to the browser responding to requests! One question... Zod has a .describe() method that only accepts strings. I've been using it to add data dictionary descriptions so I know the purpose of a particular field in the database. I'd love for it to accept objects so I could add things like: { dictionary: "Address line 1, formInputLabel: "Address 1", formInputId: "address1", formInputPlaceholder: "Enter your address", formInputHelperText: "" } The use case is simply that I could identify a single source for these things as part of the original schema. So, for example, if I have a new user form and and edit user form, and I want to change any of these items, I could change it in one spot and have it update across the forms. At runtime, nothing stops this, but Zod throws type errors in the editor if you add an object into the .describe() method. Any ideas on how this could be extended without updating the core library?
ah i really should get over your beginners ts to get a hang of your style. the information is too much and too beautiful for me to be lazy about the basics. thank you a lot for your content man. you really are a wizard
so happy its not just me that can't follow this, i felt so stupid for not being able to lol. what's the philosophy behind ruthlessly trying to optimize shortening the video length? i got time don't worry
This is so great. Small bit of feedback: could have used an extra second or two to read each code snippet before you moved to the next thing. I ended up just watching at 0.75 and pausing as needed. Thanks for the great content as always!
Damn had to freeze frame a lot to grasp everything, really informative video btw. It would be great if you could start with some code then try to show how it’s flawed and then fix it.
Lol, okay I feel a bit better seeing others not being able to follow along, I'll have to watch this a few times to grasp it...I felt like I had it on 1.5x anyway, I wouldn't change too much, I like all your videos
Thanks for posting this! I just started using Zod (dropped Yup), and I'm having a hard time with some simple stuff, and your tips are very welcome. I like the videos are short and easy to watch on a quick break, and I understand you're trying to figure out the format to improve your views and channel growth. This is my perception based on your tweets and community posts on YT. I think the pace is a bit too fast on this "blazing fast" series. Maybe you can type the important changes instead of the hard cuts? That would add some breath time to digest everything.
very good video, but you should try to not jump all over the place like you did here 2:40. If possible show the entire script and highlight where you want the viewer to focus.
You can use 'bootpress' on npm, i coded it for backend with the similar approach but i coded the 'zod part' my own too so it doesnt have dependency to it.
you can use `as never` there you never really have to use `as any` for anything. you can just ban `: any` and `as any` from typescript literally, you never need it. if you think that you need `any` as a value type, you either need `unknown` or `never` every time.
working with Zod and Prisma has been really hard, not sure if my logic is wrong but Zod + Mongoose was a lot easier. I'm having all sorts of issues with Prisma and models relations, it has been hard and I'm even using a generator to generate the Zod schemas.
For the form example, I would actually recommend using Formik and Yup. Yup is very similar, but being able to use a form library where you can create forms entirely declaratively is pretty nice. It even does error handling automatically. Really recommend looking at Formik at least. There is an adapter to use Zod with Formik, but cant attest to its reliability.
Great content. VERY hard to follow with the jump cuts. Just post a normal video where you're typing the code out with the VO. The jump cut thing is not conducive to learning.
The video is directed at high level TS established wizards, making it difficult for me, a baby mage, to follow along and understand the magic that’s going on to fully appreciate it… 😔
Hi Matt, congratulations on the video! So imagine that my schema is a z.object with 70 properties and I create a type alias from the z.infer of this object, so when I hover over this type vscode won't be able to show me the complete structure of type in your hover tooltip, it will show me something like ... 60 more ... Do you have any suggestions on how I can visually check the structure of the type alias that z.infer would generate for me when I have a schema with many properties?
I ran into this issue yesterday. There's no VScode specific solution, but adding "noErrorTruncation": true under the "compilerOptions" block in the tsconfig.json fixes it for me.
Matt, I️ love your videos and maybe it’s just me but you seem to move way too fast. I️ can understand your perfectly but I’m constantly pausing and rewinding. Other than that, your awesome. Keep it up!
Too hard to follow honestly I only understood first half, but the express part i had no idea what was going on xD. I love you and your content, but there's some work to do about the editing etc yet ;D
Hey Matt, I like the content, it is very informative but it could be better if pace of the explanation, flow of the code would have been taken care of! Hope you'll consider feedback and will deliver such nice content ahead!
Let’s say I have a generated type from gql-gen, and we are storing that data elsewhere, what’s the best way to then use zod to verify that the data confirms to that gql generated type? Also have to assume that type can change so it needs to update the zod scheme automatically if it does (ideally)
You can’t do that. Zod only validates at runtime. At build time the types only work if they are inferred from your Zod schema. What you’ll end up doing is having two sources of types.
I'm sorry man, I *really* tried, but I feel like this video is like drinking from a firehose, to the point where I couldn't even pause fast enough. and it's *really* hard to follow what is going on. plus, there's not even any kind of code or github repo in the description so one can try to find their own context, which is a shame because the express/zod pattern is *exactly* what I'm hoping to use, and this is not helpful.
Love the content but for me it’s just not consumable. I cannot follow what you’re doing. Too many cuts. Taking too fast. Too many quick transitions. Even pausing, thinking, resuming video doesn’t work for me. Is it just me?
I know a lot your videos like this are intentionally just scratching the surface of a topic, and are at least partially meant to refer people to your full guides, but I'd still recommend slowing down a little on the info-per-time-ratio. Even for me, who knows most of the things you talked about in this vid, it was pretty hard to follow.
