coryvirok

6 ms·

1.
by coryvirok 9mo ago
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&#x2F
2.
by coryvirok 11mo ago
For sure. Event logs in a transactional dbs are weird. I was surprised that they weren't using something like kafka for this.
3.
by coryvirok 11mo ago
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 lev
4.
by coryvirok 1y ago
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
5.
by coryvirok 1y ago
Shameless plug for https://rollbar.com Good luck out there!
6.
by coryvirok 1y ago
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 vulnera
7.
by coryvirok 1y ago
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
8.
by coryvirok 2y ago
https://shortlog.io/
9.
by coryvirok 2y ago
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.
10.
by coryvirok 2y ago
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.
11.
by coryvirok 5y ago
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
12.
Debugging Node.js Apps in Production(rollbar.com)
12 points by coryvirok 12y ago|0 comments
13.
by coryvirok 12y ago
Also, check out https://rollbar.com for free error monitoring. (Ps. I'm one of the founders :)
14.
Ad-hoc error monitoring and reporting(rollbar.com)
2 points by coryvirok 13y ago|0 comments
15.
Async node.js API server testing(rollbar.com)
1 points by coryvirok 13y ago|0 comments
16.
by coryvirok 14y ago
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 persona