Hacker News: bkolobara

New comment by bkolobara in "Our $445M Series D"

bkolobara — Fri, 09 Oct 2026 13:51:23 +0000

I was interested in applying to Oxide a few months back. They ask candidates who reach interviews to provide at least 9 hours of availability, normally arranged as three separate 3-hour blocks. Each block contains three 1-hour interview slots, so the standard schedule is effectively nine one-hour conversations. Not including the follow ups.

I got another great offer after just 1 interview that I took, so I never went through their process, but it looks very exhausting to me. Being rejected after investing so much time must also feel awful.

New comment by bkolobara in "Our $445M Series D"

bkolobara — Fri, 09 Oct 2026 13:31:39 +0000

- Series B in Jul 2025 $100M

- Series C in Feb 2026 $200M

- Series D now $445M

I expect the next round soon :)

New comment by bkolobara in "Git 3.0's upcoming SHA-256 default will be a costly mistake"

bkolobara — Thu, 01 Oct 2026 17:22:25 +0000

I run a small git/jj forge and for us it's already painful dealing with this. Can't imagine how GitHub is going to handle it.

New comment by bkolobara in "Blizzard Revives 'StarCraft' Franchise with Open-World Sci-Fi Shooter"

bkolobara — Mon, 14 Sep 2026 17:03:11 +0000

Starcraft 2 is the only game I still play from time to time. Yes, you can probably make more money making a shooter, but there is a reason Starcraft is such a cultural phenomenon.

It just makes me sad that every decision nowadays is driven by profit and there is just very little courage left to do something else.

New comment by bkolobara in "Oxide Computer raises $445M (SEC Form D)"

bkolobara — Tue, 04 Aug 2026 21:26:18 +0000

They just raised $200M in February and $100M a year ago.

New comment by bkolobara in "GitHub Down Again"

bkolobara — Mon, 27 Apr 2026 17:42:01 +0000

All the PRs are gone ....

José Valim vs Coding Agent

bkolobara — Mon, 27 Apr 2026 10:55:31 +0000

Article URL: https://twitter.com/josevalim/status/2048698752077025743

Comments URL: https://news.ycombinator.com/item?id=47919993

Points: 3

# Comments: 0

New comment by bkolobara in "We've raised $17M to build what comes after Git"

bkolobara — Fri, 10 Apr 2026 06:36:08 +0000

We are working on something https://lubeno.dev

New comment by bkolobara in "Reinventing the Pull Request"

bkolobara — Thu, 02 Apr 2026 14:51:18 +0000

Lubeno only supports private repositories at the moment, so I can't link directly to one. But that is on my todo list.

New comment by bkolobara in "Reinventing the Pull Request"

bkolobara — Thu, 02 Apr 2026 14:47:32 +0000

Direct links to the images, until I implement popup on click:

https://lubeno.dev/assets/images/blog/lubeno-repository.png

https://lubeno.dev/assets/images/blog/lubeno-pr.png

https://lubeno.dev/assets/images/blog/code-review-before-aft...

New comment by bkolobara in "Reinventing the Pull Request"

bkolobara — Thu, 02 Apr 2026 13:46:03 +0000

... on a website owned by the VC that invested in the developer.

I believe that the ideas in the blog post are novel enough and should spark curiosity and interesting discussions. Also I submitted this last week, someone must have hand-picked and given it another chance because it's a good fit for HN.

New comment by bkolobara in "Reinventing the Pull Request"

bkolobara — Thu, 02 Apr 2026 13:36:59 +0000

Sorry about that! Performance is really important to me, I just didn't get around to configuring CDN caching and optimizing the assets. All the HN traffic hitting our server also didn't help.

New comment by bkolobara in "Reinventing the Pull Request"

bkolobara — Thu, 02 Apr 2026 13:22:17 +0000

You can just start a new branch in parallel if you don't need to build on top of the foundation. But if you are happy with the foundation and the next feature requires it, you can also continue working on something else. Jujutsu's automatic change propagation to children can also help if you need to adjust the foundation. For me work is mostly continues, like a flow.

Reinventing the pull request

bkolobara — Fri, 27 Mar 2026 09:04:29 +0000

Article URL: https://lubeno.dev/blog/reinventing-the-pull-request

Comments URL: https://news.ycombinator.com/item?id=47540441

Points: 109

# Comments: 87

New comment by bkolobara in "Reinventing the Pull Request"

bkolobara — Thu, 26 Mar 2026 17:45:27 +0000

Thank you! Would love to check out what you are working on if you have anything to share at this point.

Reinventing the Pull Request

bkolobara — Thu, 26 Mar 2026 17:20:15 +0000

Article URL: https://lubeno.dev/blog/reinventing-the-pull-request

Comments URL: https://news.ycombinator.com/item?id=47533142

Points: 3

# Comments: 3

New comment by bkolobara in "Migrating to the EU"

bkolobara — Mon, 23 Mar 2026 13:25:07 +0000

Shameless plug. We have been working on building a European GitHub alternative for private repos at https://lubeno.dev.

New comment by bkolobara in "Show HN: Better Hub – A better GitHub experience"

bkolobara — Thu, 26 Feb 2026 11:21:06 +0000

I just noticed that you can uncheck permissions before you clicking continue with GitHub, to reduce the scope.

New comment by bkolobara in "Show HN: Better Hub – A better GitHub experience"

bkolobara — Thu, 26 Feb 2026 11:12:45 +0000

This looks awesome! I remember the Mitchell tweet, it was like a week ago? I'm super impressed how much functionality you managed to push out so fast. Crazy times.

And I very much agree with Mitchell that the repository page needs improvement. If it's a public repository I'm exploring, I scroll always down through the files to see the README. If it's a repository I'm maintaining I'm either clicking on commits, PRs or issues. All this information should be right there on the first page! Most of the realestate is occupied by the file view, something I never cared about.

I have also been working on improving the experience for myself with https://lubeno.dev, and have been thinking for the last year how GitHub can be improved. I started specifically with Pull Requests, borrowing some ideas from other platforms, like stacked PRs. One feature that I'm very proud of is the possibility to see an interdiff when someone changes the code I commented on. You can instantly tell if the issue was addressed instead of getting an tag on the comment and hunting down the latest changes. Would really love to see more innovation when it comes to forges. It looks like GitHub set the standard 20 years ago and everything else is a 1:1 copy of it.

Lubeno.dev – Code hosting and collaboration with stacked PRs and JJ support

bkolobara — Tue, 24 Feb 2026 20:59:12 +0000

Article URL: https://lubeno.dev

Comments URL: https://news.ycombinator.com/item?id=47142945

Points: 2

# Comments: 1