▸ NOW PLAYING · WEEK 17
Shipping kind.events v2 — calendar view, email digests, and a cleaner map.
started
Apr 10
ships
Fri, Apr 30
progress
68%
progress
● recordingdesign: donebackend: donemobile: in progress
← hi, i'm your host.
the cat's called deploy.
the cat's called deploy.
▸ CH.01 — WELCOME ABOARD
a tiny software studio, broadcasting from limassol
one human · three live products · no agency, no decks. mostly code, coffee, and honest copy. pull up a chair.
▣ CHANNELS / LIVE● REC
—
…something new
02
agent-monorepo
03
kind.events
04
matchpro.io
tune in → hi@evgentus.group
or drop a postcard · tg / @evgentus
or drop a postcard · tg / @evgentus
— hello, i am
Evgeniy Kuznetsov — founder, dev, dad.
I run a small group of live products on my own — sometimes with friends. I design them, build them, run them, and occasionally write about it. No agency. No pitch deck.
Writing code since ~2012, shipping products of my own since 2019. Based in Limassol, Cyprus since 2022. Sea is a 12-minute walk.
- ▸ based in
- limassol, cy · since '22
- ▸ shipping since
- 2019 · seven years in
- ▸ group count
- 3 live products, 1 cooking
- ▸ headcount
- 1 (+ friends, sometimes)
- ▸ stack
- ts · next · postgres · rust (when brave)
- ▸ moods
- early mornings, decaf, amber light
▸ self-portrait● REC
P.S.
don't call me a founder —i just make things 🛠
—
▸ CH.04 / cooking · quiet mode
…something new
a note-taking tool for operators of small internet companies. still an idea. writing not yet on sale.
progress
~10%
public
no
investors
none, thx
role
just me, for now
draftOPEN ↗
02
▸ CH.04 / agent-monorepo · oss tooling
agent-monorepo
a boilerplate for teams who let agents write most of the code. contracts first, humans second, agents third.
runtimes
nest · nuxt · flutter
contracts
openapi + asyncapi
license
mit
role
author · maintainer
oss · toolingOPEN ↗
03
▸ CH.04 / kind · recently launched
kind.events
a calm map of what's happening this weekend. curated, no paid placements, no noise.
events
320/mo
cities
3
waitlist
2.4k
role
solo + 1 friend
consumerOPEN ↗
04
▸ CH.04 / matchpro · currently shipping v3
matchpro.io
a niche job-board that actually matches people, not keywords. rebuilt the matching engine this spring.
jobs
1.2k/mo
placements
~180
revenue
profitable
role
solo · design + code + ops
featuredOPEN ↗
¶ case study — 01·shipped spring '26·timeline: 11 weeks·team: 1tags: matching · search · postgres
The old engine matched keywords . The new one reads the whole résumé .
F or three years matchpro matched candidates to jobs the lazy way — a tf-idf over titles, with a sprinkle of rules. It was fine. Not great. Recruiters kept emailing me screenshots of obvious matches it missed. So this spring I sat down and rebuilt the whole thing.
"Matching is not search. Search rewards precision. Matching rewards being interestingly close."
- 01throw away the rankerkept the data, dropped the model. started from a blank ipynb.
- 02embed everythingrésumé + job text → small multilingual model, cached in pg_vector.
- 03re-rank with signalslocation, seniority, years-in-stack. boring features still win.
- 04shadow-run for 3 weeksa/b on recruiters' clicks. watched dashboards more than family.
match-quality (recruiter 👍)41%→ 78%+37 pp
time-to-first-click9.2s→ 3.1s−6.1s
weekly placements12→ 28×2.3
latency (p95)640ms→ 180ms−72%
w01w04w08w11
› bench --cohort=q1-recruiters
running 2,140 matches…
✓ v3 beats v2 on 78% of pairs
! 4 regressions — investigating
› deploy prod
№ 014long read2026-04-18 · 8 min№ 013notebook2026-04-02 · 4 min№ 012notebook2026-03-20 · 3 min
see all posts →case study
Rewriting matchpro's matching engine
What I learned from watching recruiters click for three weeks.
operations
Why I still answer every support email myself
A short defense of doing customer support on purpose.
process
On shipping things when no one is watching
Slack notifications off. Keyboard on. Trust the calendar.
A Philosophy of Software Design
by John Ousterhout · 2nd time
▸ p. 140 / 190
Boards of Canada — on repeat
Music Has the Right to Children
♪02:14 / 06:18
calendar UIs that don't
pretend a week has
8 symmetrical days 🗓
pretend a week has
8 symmetrical days 🗓
— this week · shipped / broken / learned
monshipped kind.events v2 beta to 80 userstuebroke the ICS export for 40 minutes (sorry, karolis)wedwrote notebook #14 · answered 23 emailsthulearned pg_timetz is a lie · slept on itfriwriting this now · planning to take saturday off
typescript★
5.4the default
next.js★
15web framework
postgres★
16only database
rust
1.78for the risky parts
tailwind
4.xwhen lazy
neovim★
0.10editor · lua config
ghostty★
1.0terminal
linear
—one project board
figma
—design, reluctantly
raycast
1.xlauncher
macbook pro★
m3 · 14”work machine
hhkb pro★
hybridclicky keys
moleskine
pocketmorning notes
kinto mug
330mldaily driver
fly.io★
hobbyhosting
resend★
—email
stripe★
—money
cloudflare
—cdn · dns
tailscale
—private net
Drop me a line — I read every one.
Best for work inquiries, kind.events partnerships, and folks curious about matchpro.io. Worst for cold sales.
▸ email
hi@evgentus.group
▸ telegram
@evgentus
▸ github
github.com/evgentus
▸ mastodon
@evg@hachyderm.io
if it's 3am your time, i might be asleep. otherwise i'll reply within a day.
▸ CH.09 — COLOPHON
the site you're on was designed out loud — here's the transcript.
no framework templates, no Figma-to-code handoff. i sketched everything in the browser, talking to an AI collaborator like a junior designer across the desk. two weeks, ten channels, one ASCII cat that wouldn't sit still.
every pixel you see
was argued about.
was argued about.
— timeline · 14 days of signal
d 01–02
tuning the dial
picked the voice (broadcast, warm, honest). chose 4 fonts. drew deploy. ditched 3 directions before locking 'Cozy CRT'.
d 03–06
channels live
hi-fi on every section: hero, about, work, case, writing, now, uses, signal, 404, footer. iterated in-browser, not in a mockup.
d 07–10
paper mode
light theme that isn't just 'dark theme inverted'. re-tuned amber, green, shadows, scanlines so it reads like sun-bleached paper.
d 11–14
handoff & polish
responsive specs, tokens locked, a11y audit, dev handoff notes. wrote this very page. deploy got a nap.
▸ 10 routes · 3 primary entry-points
/ home · you are here
/about who & why
/work four channels, three live
/work/:slug case study
/writing the journal
/writing/:slug one post at a time
/now what's cooking this week
/uses the stack · right here ↓
/signal say hi
/* the lost channel
FRAMEWORK
next.js 15 · app router
RSC by default, static where it fits
STYLING
plain CSS · tokens.css
every value is a var. no Tailwind.
CONTENT
MDX · frontmatter
writes like a notebook, ships like a site
FONTS
Space Grotesk · Fraunces · JetBrains Mono · Caveat
display / serif italic / mono / hand
HOSTING
fly.io · edge · CDN images
fast enough that you don't notice
ANALYTICS
plausible · self-hosted
no cookies, no banner, no tracking
— five rules, taped to the monitor
RULE 01
one signal per screen
red is never decorative. if it's red, tap it.
RULE 02
warm, not cold
dark mode that smells like coffee, not a server rack.
RULE 03
type does the heavy lifting
four typefaces. one job each. no decoration.
RULE 04
motion carries meaning
blink = now. pulse = live. everything else sits still.
RULE 05
deploy everywhere
if a screen felt lonely, the cat moved in.
10
channels
4
breakpoints
47
design tokens
12
section files
1
cat