dabears

8 ms·

1.
by dabears 1y ago
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 talking about. I have no formal education and I am ex
2.
by dabears 2y ago
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 solve these problems: https://github.com/phee
3.
by dabears 3y ago
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 possible only implementing strictly necessary abstractions.
4.
by dabears 3y ago
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 are "smarter" than you now?
5.
Show HN: Fuzzy Ruby Server – Go to Definition for Ruby(github.com)
2 points by dabears 3y ago|0 comments
6.
by dabears 3y ago
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 indexed in an in-memory db with Tantivy. https:/&#
7.
Show HN: Fuzzy Ruby Server, go-to definition for Ruby(github.com)
1 points by dabears 3y ago|0 comments
8.
by dabears 4y ago
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 hit a series of merge conflict while rebasing. Then eith
9.
by dabears 4y ago
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 old branch that has 1500+ changed files then inotify wil
10.
by dabears 4y ago
Just have to say thank you so much for CoffeeScript! It was pivotal in my career and has brought me a lot of joy :)
11.
by dabears 4y ago
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 events and writes to your secondary datastore. Something li