stickperson

Neat! How did you find out (and when) .codes was going to be released?

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?

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.

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?

CDC is slightly different; it depends what type of events you are interested in. This is a pretty good read: https://debezium.io/blog/2020/02/10/event-sourcing-vs-cdc.

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?

Good point

Most people here (including myself) will have the same feeling. Would be great if it was open source.

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.

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.

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.

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.

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.

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.

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?

I really enjoy Discord's blog. Their Cassandra write up was excellent as well. A couple of thoughts and questions:

- Having many clusters and assigning messages to a specific cluster seems like an interesting solution.

- I'm curious how they managed to lazily index messages.

- Since only message, channel and server ids are stored in ES, have there been any problems reindexing data after an index fails?

I'd be interested in attending the talk. Have any more info?

Have the link to Mugsy? Sounds pretty cool.

What methods do people prefer for boots?

A classmate and I did a bit of contract work for a company. We built out some widgets for a dashboard with d3.

Sometimes accepting a shitty job just to get started is the only option. You do what you have to do though.

I think it might be a bit unfair. Don't get me wrong, I have seen people who had the mentality of "I'll just go to a bootcamp and start making good money." There are definitely others who, as others have said, used bootcamps as a lunch pad and just something to get them started. Hard to tell just from a resume though.

That's simply not true. Plenty of students have had success after bootcamps.

I did one back in 2013 and went in with very minimal experience-- I could write simple loops in python but had no idea how to actually build something. At the time I wasn't even sure if that's what I wanted to do for a living. I knew I wanted to try something in tech since it's everywhere in SF. At a bare minimum, the bootcamp would give me an idea of how the engineering process works.

All of the bootcamps I know of focus solely on web dev. That's not necessarily a bad thing. Plenty of places need web people, and you can always keep learning and transition to something else if you want.

Here's the advice I usually have for people that ask me if they should do one:

* what did you do in college? I found that people who did some sort of STEM major caught on much more quickly than those who did something like Art. Basically, if you've had a lot of experience with problem solving and critical thinking things should come easier to you

* go in with a project in mind. Learning with a purpose and intent (I want to build X, what do I need to learn to do that?) is much more effective

* don't believe the job placement numbers. Prepare to be on the hunt for 6 months after you finish

* try to talk to people who did the specific program you're interested in. This is a big one. LinkedIn is your friend.

* if you do go, don't mention it on your resume. Plenty of people just throw bootcamp resumes out. Just say you're self taught.

* you won't learn to code just by simply showing up to class. It takes a lot of effort outside the classroom

That's all I can think of for now. I had a tough time finding my first job, but if I had to do it all over again I'd do it in a heartbeat. Feel free to shoot me an email if you have any questions.

  Grouping of sub-dependency groups (e.g. a testing group).

That seems like an improvement over having multiple requirement files. Then again, I'm perfectly happy with separate dev/testing files.

What was your math background before beginning?

Is this the series you're referring to: https://www.edx.org/xseries/data-science-engineering-apache-...

Do you ever check out the Who's Hiring thread here?

Autocomplete is another good example. Instead of having my autocomplete API call go through the whole dispatch -> reducer flow, I just update my component's state when I get a response.

Yea. I think that's called the NOR chip.