I would agree with you. I feel like watching videos where someone goes "hey, so here's this pattern that completely unlocks the neck for you, don't be stuck in a box anymore!" and all they're showing you is where the various notes in a key are along the neck (now I know that, but I wouldn't have known that before...) and it's WAY more confusing than if you just learn how the pentatonic scale works and how to find the notes in a key etc. And the funny thing is, the only reason I was stuck in that box in the first place is because of silly rote memorization without understanding why you play the various notes in a scale etc., it just feels like this thing that kind of compounds when you just learn patterns vs. just learning the underlying principles.

But again, I'm completely amateur at this stuff still, and I don't have any experience teaching other folks an instrument, so it's hard for me to say with any certainty that we should be teaching it one way or another I guess.

I've since gone back and learned a bit of music theory as an adult and it's been super helpful understanding the underlying principles so I can work things out vs. having to just memorize things without understanding why they work.

I think then you can go practice the various scale patterns and get good at them with the knowledge that you can always work out the scale from first principles if you need to.

Different strokes for different folks though I guess, I'm sure there's an argument to be made for not overwhelming folks with too much theory out of the gate. Not sure if I had started with a bunch of theory if I would have stuck with it when I was younger.

Also my naïve impression is that the market is pretty flooded right now with candidates with impressive-looking credentials (i.e. ex-FAANG employees) from numerous large layoffs, so I wouldn't be surprised if getting a job right now is more challenging than it was a year ago. I have heard anecdotally though that there's still abundant opportunity, but I'm not sure how that nets out. Maybe it just means that the top tier, most desirable jobs are super hard to get right now, but everything below that is pretty much the same? I'd be curious to hear other folks experiences.

FYI, I originally learned about this stuff via https://haim.dev/posts/2020-07-28-dual-monitor-kvm/.

Edit: Oh and I would normally use the debugger A LOT to trace through the code and understand the call stack and params, but another crappy thing about this project is that it generates a massive JS bundle and it crashes the app I'm testing if I try to put debugger statements in...JS ftw

Sometimes I do this by just adding a comment, and now that file will at least show up in version control as changed and I can get back to it if I need to, but that's also a little bit janky and I have to be careful I don't leave that cruft around on accident when I commit.

I'm trying out a bookmark extension in VS code and we'll see how it goes, I'm already a little bit annoyed by it in that it doesn't seem to let me organize the bookmarks in any way, so it might be somewhat useful for temporary spelunking, but I won't for example be able to save these bookmarks to refer to them later, which seems like it could be useful.

Sourcegraph has this concept of "Notebooks" which allows you to add files and intermix markdown, which feels like a pretty cool idea, and if I'm just reading code in Sourcegraph it's great, but when I'm in my code editor and making changes I don't want to bounce over to another tool. Maybe it's as simple as keeping some sort of Markdown file open that I write into and then add links to file line numbers as I go, I haven't tried that but I suppose it wouldn't be the worst, and allows me to organize the links in any fashion I see fit.

Looking for any tips you all might have for making this easier.

Comments URL: https://news.ycombinator.com/item?id=32567798

Points: 29

# Comments: 36

I know that I could obviously grep the output of the first command, and then use sed or awk to manipulate the line I want to get just the url, but I'm not sure about the best way to go about the rest. In addition, I usually want to see all the output of the first command (in this case, it's not done executing, it continues to run after printing out the url), so maybe there's a way to do that with tee? But I usually ALSO don't want to intermix 2 commands in the same shell, i.e. I don't want to just have a big series of pipes, Ideally I could run the 2 commands separately in their own terminals but the 2nd command that needs the url would effectively block until it received the url output from the first command. I have a feeling maybe you could do this with named pipes or something but that's pretty far out of my league...would love to hear if this is something other folks have done or have a need for.