gajus

Somewhat related to your ask https://github.com/gajus/pg-dump-parser

We use it internally to create folder-like structure representation of our database schema.

https://github.com/gajus/pg-dump-parser?tab=readme-ov-file#r...

Very handy when reviewing changes in version control, etc.

Zod is the default validator for https://github.com/gajus/slonik.

Zod alone accounts for a significant portion of the CPU time.

Surprised not to see more people ask about performance profile of v4.

Zod is great in terms of API, but a no-go in terms of performance.

We ended up writing babel plugins (https://github.com/gajus/babel-plugin-zod/) and using it along with zod-accelerator, which improves performance, but breaks in various edge-cases.

What's a relatively small dataset?

For someone that could be 1m records for others that could be 1bn records

TLDR

> So, we now focus on the new NIST standards of FIPS 203 (ML-KEM), FIPS 204 (ML-DSA) and FIPS 205 (FLH-DSA).

That’s a lot longer post than I anticipated on the subject.

Just so I understand the other side of the argument: where is the purported inefficiency of keeping DST coming from?

What’s better/different/same from many tools in this space like langfuse etc

The idea of llm generating flashcards is kinda neat. Not an area I am personally exposed, but I can see use cases for this

All fair insights and learnings. Good luck with your next one

All interesting and rational points. Thanks!

What's the SQL equivalent of this?

What does free with unlimited tokens mean?

Heads up that the article is open source in case you wanted to contribute an edit.

https://github.com/gajus/gajus-com/blob/main/src/blogPosts/2...

I fixed the typo though. Thanks!

Thanks for the anecdote. I've included it in the article.

Updated the article. Thanks for the context

Thanks. Fixed

I never ran into into this situation, but I plan to update the article based on aggregated feedback. A few good suggestions have been made.

Makes sense. I am just curious about the logic behind the algorithm, more than anything else.

Out of curiosity, anyone knows why would this post be removed from the front page?

I was excited see that the post is getting engagement. I saw it in 3 position. Then checked an hour later and it is nowhere to be seen.

I am assuming this is some sort of opportunistic algorithm at play that gives a chance to a post, but removes it if it is not performing, but curious if anyone has more details.

Yikes. Well, less of fan now!

Both are visually ambiguous, so we are good.

Somewhat related, I always liked the concept of https://what3words.com/

Yay! A new joke. I've been collecting jokes for several years. Pretty rare to run into a new one after a while.

CAPTCHA is not a bad suggestion, but my hesitation is that if someone has gone through the hoops to setup residential proxies to do this, then CAPTCHA is just another nuisance to bypass (there are many services readily available to do that), and the people that will suffer the most will be the real users.

Customize the CV with an intro that's directly addressing the company and the role requirements for which you are applying.

Interested to know as well

Hello HN,

It's hard to believe, but it's been three years already. If you're unfamiliar with Contra, let me introduce it. Contra is a freelancer marketplace designed to stand out in an industry filled with restrictive platforms, high commission fees, and competitive bidding that often results in race to the bottom. We've created an open marketplace without commission fees, aiming to attract and keep both high-quality clients and talented freelancers.

I'm excited to unveil something we've been passionately working on: Contra for Companies. This all-in-one platform revolutionizes how you hire, manage, and pay freelancers and contractors.

Ever juggled a spreadsheet to track your talent pool, their contact info, rates, deliverables, and projects? That's exactly what motivated us. After hiring hundreds of freelancers, I've experienced firsthand the challenges of managing talent. That's why Contra for Companies is a game-changer, integrating talent discovery, management, and project oversight into one seamless platform. It's designed to empower companies to scale their teams effortlessly with a skills-based workforce.

Take a moment to watch our demo video for a sneak peek of what we're bringing to the table.

https://www.youtube.com/watch?v=b34a7eUPI-g

A heartfelt thank you to our incredible team for turning this vision into reality, especially as we celebrate Contra's 3rd anniversary. It's a proud moment for us, but truly, it's just the start. The best is yet to come.

I'd say sadly it is almost the inverse.

It's the companies that hire really high volumes that I see resort to leet code tests as sort of a great filter.

I rarely see small companies use leet code interviews, but that does not say much about the rest of their interview quality.

I agree with this.

I see a lot of benefits in advocating this style of interview. However, I am struggling to think of what good does a SaaS bring here.

For one, we use GitHub for all code reviews, and we'd want interview to be as close as possible to the environment that the engineers are familiar with. Any time we tried bringing another tool to the process, it only causes additional stress/friction for everyone involved.

Also, I found that constructing example code for interview produces worst insights than using your actual codebase. We have a few codebases that are of lesser importance that we use for interviews. The extra benefit of this is that the candidate gets to see approximation of how your actual codebase is structured.

As someone who hires a ton of engineers, I wholeheartedly disagree with this.

I actually really like this concept. The main benefit is that this approach allows a more conversational interview and also allows to cover a broader range of real-world problems.

There is almost 0 correlation between candidates ability to be effective collaborator and their ability to solve leet code problems. The former is a lot more important to us than your ability to chew out code.