News for hackers. Stuff that matters.

vtemian

vtemian on Hacker News

Make HN great again: Neovim vs. IDEs

Posted by vtemian on Thursday April 30, 2026 @06:39AM
from the self-post dept.

I'm missing the good old never ending debates over nerdy stuff.I used vim for a long time, i3wm fanboy, but 8 years ago I switch to MacOS and PyCharm.I know why I switched, but now, with the entire AI race, new tools popping in and out, I want just to relax and go back to my initial love.So, can neovim still compete with any IDE out there?

( Read More... | 3 comments | 3 points | on HN )
Re:Intent-Based Commits on Tuesday March 03, 2026 @03:31AM (#47229748)
Git was designed for humans. Commits, branches, and the entire model works really well for human-to-human collaboration, but it starts to be too much for agent-to-human interactions.

A better alternative is to share the entire session, the entire flows of ideas, changes and decisions. For that, the export needs to be in a human, readble way, offering a rich experiences to other humans to understand, is way better then having git annotations.

That's why we built https://github.com/wunderlabs-dev/claudebin.com. A free and open-source Claude Code session sharing tool, which allows other humans to better understand decisions.

Those sessions can be shared in PR https://github.com/vtemian/blog.vtemian.com/pull/21, embedded https://blog.vtemian.com/post/vibe-infer/ or just shared with other humans.

Re:If AI writes code, should the session be part of the commit? on Monday March 02, 2026 @02:34AM (#47214900)
Git was designed for humans.

Commits, branches, and the entire model works really well for human-to-human collaboration, but it starts to be too much for agent-to-human interactions.

Sharing the entire session, in a human, readble way, offering a rich experiences to other humans to understand, is way better then having git annotations.

That's why we built https://github.com/wunderlabs-dev/claudebin.com. A free and open-source Claude Code session sharing tool, which allows other humans to better understand decisions.

Those sessions can be shared in PR https://github.com/vtemian/blog.vtemian.com/pull/21, embedded https://blog.vtemian.com/post/vibe-infer/ or just shared with other humans.

Re:LLMs Are Not Fun on Monday December 29, 2025 @03:13PM (#46425003)
why was this post removed? it was #1
Re:LLMs Are Not Fun on Monday December 29, 2025 @02:44PM (#46424644)
> For me, the joy of programming is understanding a problem in full depth, so that when considering a change, I can follow the ripples through the connected components of the system.

100%. The fun is in understanding, creating, exaplaining. Is not in typing, boilerplating, fixing missing imports, and API mismatch etc.

Re:Show HN: Vibe coding a bookshelf with Claude Code on Monday December 29, 2025 @08:59AM (#46420827)
This nails what vibe coding actually is. The model handles execution, but intent and taste stay human. That’s where the real leverage is.
Re:Is Google Down? - EU networking issue on Thursday September 04, 2025 @03:13AM (#45124476)
PING google.com (172.217.17.142): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Re:I so hate the phrase "vibe coding" on Tuesday May 06, 2025 @09:31AM (#43904916)
I'm still searching for successful vibe coding examples.

Each time I tried it, with custom rules, git, and all the best practices I found, it went amazingly well initially, and garbage afterward.

Using the same technique, after a while, it generates a lot more shitty code than helpful.

> So, it’s shit and you’ll spend a long time fixing it.

It just takes more time overall to make it functional. Fixing, debugging and improving vibed code takes more mental resources and time than just writing it from scratch.

Also, there's the flow aspect. Each time you let it "vibe", you're losing the flow state that is important while creating and thinking about complex work.

Re:Windows Bluescreen and Boot Loops (update: caused by a Crowdstrike ... on Friday July 19, 2024 @07:21AM (#41005084)
What's the actual magnitude of this outage? Is there a way to estimate how many machines were down?
Re:Ask HN: What's your choice for the classic web app stack? on Thursday January 12, 2023 @01:17PM (#34358016)
Serverless all the way. There are a lot of good options out there, with AWS being quite flexible.

The onboarding for other developers is also painless. I've recently experiment with AWS Amplify and even if is not quite there yet, is pretty close.

Lambda, cloudfunctions, https://supabase.com/, https://hasura.io/, AWS Amplify, https://aws.amazon.com/serverless/.

For frontend, I would go with either React or Vue, both with a huge community and already a lot of builtin solutions. I would 100% start with a design system, maybe material UI.

Nothing fancy, low maintenance and painless onboarding/development experience.

Older »