Davertron

> Thing is, it's not even "too much theory".

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.

This is why learning guitar when I was younger was so difficult to me; people just presented things like "you have to learn these 5 scale patterns" but they didn't really go into why, it was just "memorize this stuff and then you'll be good!", but I hate rote memorization without understanding the underlying principles. I'm old and didn't have the internet back then so I was just learning from various books or friends and it was slow going, but I still see things like this presented in tons of Youtube videos today.

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.

Yeah, it was happening on Super Mario Kart. I just tried Super Mario RPG and didn't have any issues. Let me know if I can get you more info or help with a repro.

This looks super awesome! I just tried it in Chrome however, and after a minute of playing the game it just drops me back to the game library screen. Love the idea though!

This. Interviewing is a COMPLETELY different game in the tech industry. Some people spend a lot of time and are very good at this game.

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.

Yeah, this. I don't have any data to support this, but when I was in school, MOST people didn't have close to full-time jobs. I had a job where I probably worked 10 hours during the week at night and some full 8 hour shifts on the weekends. Most of the people I went to school with (and I would assume, maybe wrongly, that most people in better schools than I went to) didn't work AT ALL while they were in school, it was just those of us less than wealthy folk who actually had to work to have spending money and money to pay for books etc. I don't think my work load was overly demanding, but I was a Comp Sci major, fwiw.

Well good luck then, in my experience the most free time I've ever had in my life was during college. I squandered massive amounts of that time doing things completely unrelated to education, and I definitely don't regret doing that. College isn't just about book learning after all. But still, BY FAR, college is the time of my life when I had the most free time to do whatever I wanted.

I just discovered this feature so I haven't played with it enough yet but it seems to tick all my boxes. One thing that I found confusing about the UX though was that I didn't realize at first I could continue searching around and adding content, so when I added my first bit of content and clicked "Create Notebook" and then subsequently navigated somewhere else and wanted to add content I ended up creating another notebook instead of adding it to a pre-existing one. Or sometimes I come back and want to add more content to an existing notebook, but I don't see how to do that.

Ha, that's kind of where I'm leaning now, I thought of the same thing in another response in this thread. It seems like it's lightweight enough to stay out of my way but flexible enough that I can have some control over how I organize things, and being able to quickly add some prose to describe why that particular link is relevant would be great.

Yeah, I also don't really like splits, they just don't feel very scalable. If I just need to open one or two other files they're fine temporarily, but more than that and everything becomes too small. Maybe if there were something that let you zoom in and out, like a Figma canvas, so that you could organize the files spatially in some order that makes sense to you (this is another thing that annoys me about just opening tabs in my editor, they're never really ordered in any meaningful way). If you could do this not just for files but for selected lines / ranges / functions / classes to keep things tightly scoped that would be awesome. I believe this sort of thing was something the original LightTable video explored, but I don't believe it was ever actually implemented.

I use these as well, but maybe something I didn't articulate well is that it's often useful to remember where I've been. One thing that I haven't played with in VS Code but that bites me a lot (and sorry, I don't know the proper name for this setting/feature) is that often when you're navigating you're doing so in the same vs code tab. If I remember to double-click the tab it'll hang around, but that's a pretty janky workflow, and I don't ALWAYS want to do that. Ctrl+- works if I hop into a method/function and want to look at it briefly and hop out, but I find if I go more than a couple levels deep it would be nice to mark certain areas as I go so I can easily get back to them.

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.