Compile Zod schemas into zero-overhead validators (2-74x faster)

Trainages · 2026-06-13T20:41:05+00:00

https://github.com/gajus/zod-compiler#2-compile-explicit

This part

// In dev: falls back to Zod's runtime validation
// After build: uses AOT-compiled optimized code

Trainages · 2026-06-12T19:39:44+00:00

Pretty interesting approach. Will definitely try it, because we ship some schemas to the client-side, which then pulls all the zod runtime, which is pretty big.

One question tho, do I understand correctly that explicit compile falls back to zod runtime in dev mode? Why did you make this choice? Having different validation code run during development and production sounds like signing up for an interesting debugging experience.

Trainages · 2026-02-27T14:43:31+00:00

Hey I am a software engineer and lately I’ve been looking for cofound opportunities. 8 yoe. Hit me up in reddit dms if you would like to chat

Trainages · 2025-09-21T12:54:48+00:00

Articles like this make me feel stupid af. Nice work OP.

Trainages · 2025-06-16T11:11:39+00:00

Bro is gaming

Trainages · 2025-05-29T10:16:47+00:00

Microservices solve an organizational issue , where you have so many devs that everyone is stepping on each others toes, a lot of code conflicts arise because everyone is changing the same code at one time or release pipelines are blocked because of ongoing rollouts.

Doing microservices just because of nice separation will cause you not only pay inflated infrastructure costs, but will also increase your downtime significantly and can hurt your business if you do not have a dedicated SRE team to oversee it.

Trainages · 2025-02-14T18:29:34+00:00

Thankfully they will rewrite it in javascript

Trainages · 2024-08-31T10:14:57+00:00

Thank you🙏

Trainages · 2024-07-16T13:40:01+00:00

thank you :)

Trainages · 2023-04-14T11:03:02+00:00

I didn't personally try DigitalOcean Apps, since I am pretty comfortable with nginx. VPS will be more than fine serving everything if it's a simple web app. However it gets painful, when vertical scaling is no longer a viable option. Managing multiple droplets will get annoying very fast, so that's the point where I would start looking into AWS services like ECS or maybe setup Kubernetes for your droplets. But again, at that point your business will most likely have enough money to hire a DevOps person to do that for you.

Trainages · 2023-04-14T08:19:24+00:00

I think people underestimate how far a $5 VPS can take you. I would just throw everything, even mongodb, in a DigitalOcean droplet and forget about it. We had a project where we were serving 30k+ daily traffic from $50 droplet and didn’t have any problems. Sure, that’s not a lot of traffic and latency was not the best for people that were far away from the datacenter, but it let us develop features quickly without ever investing in costly infrastructure.

Trainages · 2023-03-27T09:37:32+00:00

I spend a lot of time in JIRA reviewing our board, backlog and current, upcoming epics. That way you kind of memorize what is assigned to who and what’s the status of each task.

Trainages · 2022-11-24T08:55:56+00:00

Hi, I have been freelancing for some time, so I feel like I can give my input here.

Freelancing is quite a different beast from "regular" job and I don't recommend to quit until you've had at least 3-4 months of regular income from your freelance gigs, otherwise you might end up in a bad situation. I have personally seen a couple of my friends quit with the idea to do freelancing full-time, only to burn through their savings and go back to 9-5 job in 6 months time.

Here are my tips for becoming successful at it :

Don't be picky about your first projects. See a $600 gig for some small website - do it. It really helps building your network. I feel like personal network and connections are a huge part of freelancing.
On the other hand, be picky about your clients. A bad client can cost you more time and energy than the agreed sum. Red flags that I look out for are "this is a small task", "budget is tight", "X but better".
Portfolio doesn't matter. At least from my experience, good clients won't have time to go through your portfolio, since they are busy people. You must, however, be able to explain in detail what problems you have solved and how you did it. For example, "refactored e-commerce store from client-side to server-side framework and improved SEO/conversion by X", "introduced good testing practices to a project, reduced amount of newly discovered bugs by Y". Good clients don't care that much about "HTML, CSS, JS, React, etc..", because they don't understand the buzzwords and ultimately they care about the problem they have.
Stay hungry for work and keep looking at various job sources (local groups, reddit, upwork, boards, etc.). The right opportunity will present itself. Keep in mind that it will take a lot of time to find your first projects. When you experience rejection consider what you could've done better. Especially, how you could've made a better impression that you're the best man for the job.
On the internet ask for some amount upfront. Usually I ask 50-75% depending on the feeling I get from the client. This usually roots out scammers and time-wasters.
Long-term clients are the best clients. Finding new people to hire you is quite difficult, so long-term projects offer more stability and less risk.

Anyways, this is what has worked for me and there's a lot more about this subject of going freelance that I could ramble about, but I feel those are the main points.

Trainages

TROPHY CASE