Viewing profile — dabears

Hello! I was curious if you would happen to have any advice or particular comp sci papers you would point as aspiring compiler developer towards. I think I'm sort of who you're tal…

I was tired of feeling slowed down by grepping in large Ruby code, and the artificial boundary gems create requiring a `bundle open` to keep digging. I created my own Ruby LSP to s…

The real trick is doing both. Code that reads like a short story while including error handling and edge cases. This is achieved in a practical way by first keeping it as simple as…

I'm curious what you're really trying to say here and why feel the need to compare yourself to your peers in such a way. Do you feel like you wasted those years because your peers …

Ruby language servers today are largely missing features like Go To Definition because most Ruby code lacks type definitions. Fuzzy Ruby Server accepts that uncertainty and creates…

I made a Ruby LSP because of this problem. It's not perfect but incase it's helpful for you. It can parse a large project with all of its gems in a few minutes. That data is indexe…

Hello! I work in a large Ruby codebase and have had a lot of frustrations with the existing tooling. Solargraph is far too slow, and the rest of the Ruby language servers don't sup…

This is my workflow as well, it's great. Github is configured so merging a PR into master will automatically produce a squashed commit. My rule of thumb, always rebase unless you h…

Inotify can drop events when there is a burst of file changes. You can bump up the max number of queued events though. For example, if you're watching a git repo and switch to an o…

Just have to say thank you so much for CoffeeScript! It was pivotal in my career and has brought me a lot of joy :)

Ideally you have a reliable Change Data Capture (CDC) mechanism like a Binlog Reader. Debezium, for example, can write directly to a queue like Kafka. A Kafka consumer picks up the…