Recent submissions

Comment · 1 year ago
Neat! How did you find out (and when) .codes was going to be released?
Comment · 3 years ago
This looks super cool! I just tried it out and am having a hard time following the README.

> The blue circle shows your breathing control

What does this mean?

What should I be looking at?

What should I be aiming for with HRV?

Comment · 3 years ago
Using setups like this is a great way to get into neovim. Over time you'll start tweaking it and then realize you can just read the source code and implement your own version. That's what my journey over the past ~8 months has been, at least.

Here's to hoping we get a nice way to play with containers in neovim. I'm sorely missing devcontainers from vscode.

Comment · 3 years ago
How did this work exactly? Twilio would answer the call, listen for a number, and "press" 9 if the number was in an allow list?
Comment · 3 years ago
Comment · 9 years ago
Since most people responding here have some sort of technical job, what sort of stuff are you working on? All of the bootcamps I'm aware of focus on web development. Do you still do strictly web stuff? Frontend or backend? Anything else?
Comment · 9 years ago
Good point
Comment · 9 years ago
Most people here (including myself) will have the same feeling. Would be great if it was open source.
Comment · 9 years ago
I really want to use VSCode, but the one HUGE thing holding me back is lack of a hot key to show/hide VSCode. I use iTerm and am used to opening/closing it with Ctrl + `. Having to use Cmd + Tab and then making sure I actually choose VSCode and note another application that I was just in really slows me down.
Comment · 9 years ago
I tried switching to VSCode earlier this week and am really having a hard time with it. I'm coming from iterm/vim/tmux. The most painful part has been the lack of a hot key to bring up VSCode. Besides that, I've found that switching between open files in vim (which I use <leader> and buffer number for) is much easier than VSCode (ctrl + number).

edit: Just opened VSCode again and noticed one other major thing that has been driving me crazy. In vim I often have files open in different panes and then make one pane full size while editing. Can't do that with splits in VSCode as far as I know.

Comment · 9 years ago
Exactly. When I was in high school, two other classmates and I would go to our English teacher's class during homeroom for SAT prep. We did this for 10 minutes a day for maybe a month. Outside of that, the only prep I did was studying for the SAT IIs the night before.

I did well in high school only studying on the train into school on the days of exams. That formula worked for me, and I figured everybody else did something similar. I knew I had to "study" for the SAT if I wanted to better than average, and practicing vocabulary during homeroom seemed like more than what everybody else was doing.

I happened to get into a good college and really struggled the first year. I studied harder than usual, but it wasn't until I started studying with some friends that I saw how much more work other people put into school.

Comment · 9 years ago
I tend to place engineers in one of two buckets-- those who make tools and those who use the tools. Most people fall into the latter bucket and can get by without hardcore CS knowledge.
Comment · 9 years ago
The small message results from only storing message, channel, and server ids as opposed to the entire message. How efficient is ES at storing the rest of the message data in the inverted index? No clue, but apparently pretty good.
Comment · 9 years ago
Got it. I was under the impression that all messages were lazily indexed. After reading the article again it's pretty clear that's not the case. Thanks for the clarification.
Comment · 9 years ago
Oh, I think I get it now-- is it that the _initial_ indexing is lazy, but all indexing after that is done automatically by the historical index workers? Basically when a user searches for something do you check that ES has something for that user, if it doesn't start off the initial indexing process, and from there the workers do their thing?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton