Nikita Melkozerov (@meln1k) 's Twitter Profile
Nikita Melkozerov

@meln1k

ID: 92554921

linkhttps://nikita.melkozerov.dev calendar_today25-11-2009 16:15:56

573 Tweet

1,1K Followers

222 Following

Nikita Melkozerov (@meln1k) 's Twitter Profile Photo

HTMX tip: if your backend is fast enough (e.g. written in go with templ), then you can aggressively preload template fragments on mouseover and your UI will feel as responsive as an SPA in most cases.

Nikita Melkozerov (@meln1k) 's Twitter Profile Photo

folks, let's say you bought a domain and want to receive emails on your new shiny email address. How do you do that? Email forwarding from a service like mailgun? Something else?

Nikita Melkozerov (@meln1k) 's Twitter Profile Photo

how to use v0 with htmx: generate the desired result, open browser inspector, and copy the outerHTML. then split into templates, and fill it with htmx attributes. done!

Nikita Melkozerov (@meln1k) 's Twitter Profile Photo

when setting up your VPS, don’t forget 4 simple things: 1. disable ssh authentication via passwords 2. enable firewall and close unnecessary ports 3. enable unattended security updates 4. create a non-root user to run your project

Nikita Melkozerov (@meln1k) 's Twitter Profile Photo

going to dive into the latest and greatest AI-enhanced hipster tech stacks to get out of my Go backend bubble. What should I try out first? TS + cursor + nextjs?

Nikita Melkozerov (@meln1k) 's Twitter Profile Photo

worked on performance optimization at my 9-5 today. running a profiler and getting things 650% faster in the first hour feels good.

Nikita Melkozerov (@meln1k) 's Twitter Profile Photo

I tried remix and liked their approach of having controllers and views together. So I did the same with go, templ and HTMX. Thoughts?

I tried remix and liked their approach of having controllers and views together. So I did the same with go, templ and HTMX. Thoughts?
Nikita Melkozerov (@meln1k) 's Twitter Profile Photo

Noticed a funny trend in the JS ecosystem. Want database - subscribe here, k/v store - subscribe there, background jobs - another subscription. Sounds like a disaster for latency. What happened to a good old postgres+redis+app running on a single server via docker-compose?