Hacker News: coryvirok

New comment by coryvirok in "Ask HN: How can I get better at using AI for programming?"

coryvirok — Sat, 13 Dec 2025 17:44:42 +0000

The hack for sveltekit specifically, is to first have Claude translate the existing code into a next.js route with react components. Run it, debug and tweak it. Then have Claude translate the next.js and react components into sveltekit/svelte. Try and keep it in a single file for as long as possible and only split it out once it's working.

I've had very good results with Claude Code using this workflow.

New comment by coryvirok in "Event Sourcing, CQRS and Micro Services: Real FinTech Example"

coryvirok — Sat, 18 Oct 2025 20:57:46 +0000

For sure. Event logs in a transactional dbs are weird. I was surprised that they weren't using something like kafka for this.

New comment by coryvirok in "Event Sourcing, CQRS and Micro Services: Real FinTech Example"

coryvirok — Sat, 18 Oct 2025 20:42:55 +0000

Not sure why there is so much hate on this thread. I found the post well written, insightful, and pragmatic.

Having built systems that process billions of events and displayed results, triggered notifications, etc in real time (not RTOS level, I'm talking 1 or 2 seconds of latency) you absolutely need to separate reads and writes. And if you can trust db replication to be fast and reliable, you can indeed skip distributed locks and stay on the right side of the CAP theorem.

Event sourcing is how every write ahead log works. Which powers basically every db.

Is the concern on this thread that they preoptimized? I thought they walked through their decision making process pretty clearly.

New comment by coryvirok in "Show HN: DesignArena – crowdsourced benchmark for AI-generated UI/UX"

coryvirok — Sat, 12 Jul 2025 16:28:45 +0000

This is really good! It would be really cool to somehow get human designs in the mix to see how the models compare. I bet there are curated design datasets with descriptions that you could pass to each of the models and then run voting as a "bonus" question (comparing the human and AI generated versions) after the normal genAI voting round.

New comment by coryvirok in "GCP Outage"

coryvirok — Thu, 12 Jun 2025 19:08:11 +0000

Shameless plug for https://rollbar.com

Good luck out there!

New comment by coryvirok in "Hyper Typing"

coryvirok — Sun, 18 May 2025 23:02:52 +0000

Apparently an unpopular opinion, but actually strong types are useful above and beyond editor linting errors.

- Jit optimizations - Less error checking code paths leading to smaller footprints - Smaller footprints leading to smaller vulnerability surface area - less useful: refactorability

Don't get me wrong, I love the flexibility of JavaScript. But you shouldn't rely on it to handle your poorly written code.

New comment by coryvirok in "AI Won't Kill Junior Devs – But Your Hiring Strategy Might"

coryvirok — Sun, 18 May 2025 22:50:07 +0000

This has led me to wonder if this is the last generation of "senior" devs. The thinking goes, if it takes a couple of years to educate and train a junior dev on average and LLMs can increasingly replace junior devs... There is no need for a company to hire junior devs, starving the ecosystem of talent that would have otherwise gone onto becoming senior.

In a world where the average work is the first to be displaced (due to training data availability), the last to be replaced are the ones furthest from distribution mean...

New comment by coryvirok in "Show HN: "Git who" – A new CLI tool for industrial-scale Git blaming"

coryvirok — Wed, 19 Mar 2025 02:10:21 +0000

https://shortlog.io/

New comment by coryvirok in "Show HN: Open-sourced Webflow for your own app"

coryvirok — Tue, 09 Jul 2024 01:22:12 +0000

Ya, that seems about right for my project as well. Although mine won't be OSS so I'm more concerned with finding good ppl with Svelte skills vs React skills. I may need to bite the bullet once I'm closer to hiring. Thanks.

New comment by coryvirok in "Show HN: Open-sourced Webflow for your own app"

coryvirok — Mon, 08 Jul 2024 21:46:58 +0000

Why did you decide to rewrite this in react vs svelte?

As someone who loves svelte and whose been writing a fairly large svelte app but has been jealous of the react ecosystem, I'd love to hear your rationale.

New comment by coryvirok in "Show HN: Errorpush – Minimalist Sentry alternative using PostgreSQL"

coryvirok — Mon, 20 Sep 2021 18:29:18 +0000

Hey! Cory, (Co-Founder/CTO) from Rollbar here.

Just wanted to say I think this is awesome and I love what you're doing here! :D

And to the author, I'd love to chat - drop me a line at cory@rollbar.com

Debugging Node.js Apps in Production

coryvirok — Fri, 19 Dec 2014 20:03:33 +0000

Article URL: https://rollbar.com/blog/post/2014/12/19/Debugging-Node.js-Apps-in-Production-with-PyCharm

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

Points: 12

# Comments: 0

New comment by coryvirok in "Show HN: Startup Utility – Collection of Startup Resources"

coryvirok — Sat, 25 Oct 2014 19:44:28 +0000

Also, check out https://rollbar.com for free error monitoring.

(Ps. I'm one of the founders :)

Ad-hoc error monitoring and reporting

coryvirok — Fri, 09 Aug 2013 18:17:49 +0000

Article URL: https://rollbar.com/blog/post/2013/08/08/ad-hoc-error-reporting-with-rollbar-cli/

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

Points: 2

# Comments: 0

Async node.js API server testing

coryvirok — Mon, 15 Jul 2013 20:54:20 +0000

Article URL: http://rollbar.com/blog/post/2013/07/12/Async-nodejs-API-server-testing/

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

Points: 1

# Comments: 0

New comment by coryvirok in "Node.js error handling"

coryvirok — Sat, 22 Dec 2012 00:28:26 +0000

One of the things I love about node.js is that it forces you to come up with a style and stick with it for things like this. At http://ratchet.io our API servers are written in node.js and we chose the foo(err, callback) method.

I personally love this style even though it makes you write more boiler-plate code, it forces you to write exception-safe code from the start. Also, it forces a structure on all of your code that you can instantly recognize as missing if someone forgets to check for err in the callback.

If you can stick with the style, it's fairly difficult to write code that doesn't deal with errors gracefully.