hermanradtke

Joined 13 years ago

Karma
989
Submissions
310
Member since
Aug 7
CTO of Trove. I continue to write software both professionally and in my personal time. My personal work uses Rust and focuses on the HTTP networking stack.

Blog - http://hermanradtke.com Bluesky - https://bsky.app/profile/hermanradtke.com Github - https://github.com/hjr3

View on Hacker News

Recent submissions

Comment · 1 month ago
feels more like an ngrok competitor
Comment · 1 month ago
As I understand it, the author was sharing the story to convince the audience he was a good writer and, thus, we should value his opinions on how to write non-fiction.
Comment · 3 months ago
Are there any other?

Namespaces are heavily discouraged. Some teams still use enigma but most people in the know us unions of strings.

I know the TS team regrets enums and I have not seen any plans for adding additional keywords that break type stripping.

Comment · 7 months ago
Comment · 11 months ago
> we end up with a mix of both Zod and types and sometimes types that need to be converted to Zod

In my code, everything is a Zod schema and we infer interfaces or types from the schemas. Is there a place where this breaks down?

Comment · 11 months ago
> it expects a level of correct-design-up-front which isn't realistic for most teams

It requires a business that is willing to pay the maintenance cost of event sourcing in order to get capabilities needed capabilities (like an audit trail or replayability).

Comment · 1 year ago
Comment · 1 year ago
Comment · 1 year ago
New Relic, Datadog, etc are selling their original offering but now with otel marketing.

I encourage the author to read the honeycomb blog and try to grok what makes otel different. If I had to sum it up in two points:

- wide rows with high cardinality

- sampling

Comment · 1 year ago
Comment · 1 year ago
Many do. In their GitHub repos right next to the code.
Comment · 1 year ago
In what cases is your join causing a table lock?
Comment · 1 year ago
That is a feature. Compose instead of extending.
Comment · 1 year ago
Yes, there are bad places to work. There are also places that require detailed time tracking, do not allow any time to write tests, have very long hours, tons of on-call alerts, etc.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton