dkulchenko

Joined 15 years ago

Karma
2,153
Submissions
191
Member since
Jul 14
Daniil Kulchenko

Founder of Phenona (acquired by ActiveState in June 2011), then Cloud Engineer at ActiveState, interviewer at Karat, now working on calmbox (https://thecalmbox.com)

http://daniilkulchenko.com/

[email protected]

@dkulchenko

[ my public key: https://keybase.io/dkulchenko; my proof: https://keybase.io/dkulchenko/sigs/cl5s7-RPu-RRimreOlsa5Iyd2mYcV5CNTDI1s4S78b0 ]

View on Hacker News

Recent submissions

Comment · 1 year ago
Have you tried comparing with 3.7 via the API with a large thinking budget yet (32k-64k perhaps?), to bring it closer to the amount of tokens that o1-pro would use?

I think claude.ai’s web app in thinking mode is likely defaulting to a much much smaller thinking budget than that.

Comment · 1 year ago
Every time I read the story of Therac-25 I feel incredibly frustrated AECL never faced real consequences or (criminal) liability for it.

Maybe I'm retroactively imposing modern day safety culture, but reading the timeline and history, it feels like AECL was completely negligent in waving off the issue as more and more fatalities kept piling up.

Can't believe the devices weren't pulled offline to definitively solve the issue after the first death. Instead, they basically went "can't repro, oh well".

Comment · 2 years ago
The T-Mobile experience has gone majorly downhill since the departure of Legere. Now they feel like just any other carrier.
Comment · 3 years ago
This mirrors my experience. Not once did I have a Yellow LTL shipment arrive on time, and typical delays ranged from 2 days to 2 weeks or longer. Shipments would get lost in a terminal, down to staff insisting it never arrived on the trailer, and then spontaneously reappear after a loss claim was filed.

I would've loved to avoid them but vendors would often choose them due to their cost.

Comment · 4 years ago
I had the same issue migrating an app off of Render (they also use Cloudflare for app routing).

Cloudflare would refuse to route to my new IP for hours on end. Incredibly frustrating and I almost pulled my DNS off of CF as a result.

I was able to work around it by disabling the orange cloud for the domain for a couple hours, then turning it back on, which must have reset some sort of cache on CF's end.

Ultimately, it's not a DNS issue, it's an internal CF routing issue - it only happens with CDN (orange cloud) on. It seems CF's just caching the orange cloud's original route (via the SaaS provider) way too long internally somewhere and it's not being cleared when the route is changed off of the SaaS.

Comment · 4 years ago
Maybe a bit unorthodox, but I've been using SquashFS with xz for compression for long-term archival (I generally prefer zstd, but for long-term archival I don't mind waiting longer for better compression with xz).

SquashFS files have file-based deduplication, fast random access, and mountability, all of which are lacking from .tar.* archives without resorting to other indexing tools. And they're mountable on any Linux without installing anything.

Only downside is they're readonly (or more accurately append-only), but for my uses, that's totally fine.

Comment · 5 years ago
Comment · 5 years ago
Personally, I stick to Firefox because of multi-account containers, which Chrome doesn’t have (no, profiles don’t count). It’s a really sticky feature.
Comment · 5 years ago
Agreed. Why is there no Tinder/online dating equivalent for making new friends locally?

Instead of dating-specific qualifiers, it'd ask for your interests, hobbies, values, age and other demos, then match you based on overlap.

Not Meetup - it's not quite solving the same problem, and so it solves things differently (focusing on shared interests and on discrete meetup events).

Comment · 6 years ago
I recently modeled churn for my subscription box calmbox (https://thecalmbox.com) by using an actuarial table (http://www.lifeexpectancy.org/lifetable.shtml, formulas at the bottom) which I found to be a lot more informative than the standard churn formula.

Subscriptions still active at month x are represented as `l(x)` and subscriptions that "die" (cancel/expire) in a given month are represented as `d(x)`.

This gives you a "life expectancy" and a "mortality rate" (so, churn) for any given number of months that a customer has been subscribed. So I can project how long someone will stay subscribed when they're brand new (at month 0) and how long they likely still have when they're at month 8 (longer than at month 0, funnily enough).

With those subscriptions where the month-specific churn will largely decrease the longer someone's subscribed (after passing the initial high-churn first months), this allows measuring/projecting churn on a much more granular level.

Comment · 6 years ago
Comment · 6 years ago
Wow, this is substantial.

All my mail sync is down, Analytics isn't loading, Sheets and Docs are all stuck in "Reconnecting". I wonder what could cause this.

Comment · 6 years ago
Yeah, shockingly enough despite the economic situation. Business-wise, it's been the best quarter yet, outpacing even holiday gifting peaks.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton