A lot of watches now have Bluetooth music playback, both smart watches and sport watches.
I can also still manage to fit an iPhone 12 Mini comfortably in many running shorts in the small rear key pockets or back zipper pockets. Some running waistbands also work well. But it's hit and miss vs old mp3 players that weighed next to nothing.
Fully 3D online game engine with multiplayer. Most of the game is made in the interactive click and drag mode, but has modes for extra logic and ultimately a full JS scripting engine if needed. Kind of like Roblox but far simpler on the dev side.
When Web Sockets were still not finalized, I was writing a C# program using them but there wasn't a functional library available. There was however a nice open-source Java implementation. I copied it into Visual Studio, changed all the file extensions, and spent half an hour hitting build then fixing syntax and import red squigglies. It eventually built successfully and happily sent data to a NodeJS front end for years.
Cool. I did something similar with an old C program from the 80s by Peter Langston called Riffology, which was the algorithm used to generate the procedural music in Ballblazer.
I pasted the C files into Eclipse, deleted some `register` keywords, made a bunch of tweaks, and it ran fine as Java.
My favorite front end interview did this exact thing. The interview started with an issue taken straight from the Preact GitHub codebase. The interviewer provided the issue text and the commit right before it was fixed to pull down onto my machine. I had an hour to figure out how to build and reproduce the issue, Take in the high level structure of the code base, figure out how to drill down in a debugger to find where the issue itself was occurring, then propose a fix for it. Took the whole hour but was both extremely satisfying for me, and I imagine very insightful for the interviewer.
I've worked at two different FAANG companies, and have a different view than some of the other commenters here. It sounds like you want to grow, learn, and advance, and I don't think you'll be happy kicking back and coasting.
The first piece is that mobility is high between teams at almost every FAANG company. At my first one, I moved 3 months later because the initial team wasn't a great fit for me maintaining a lot of slow moving legacy systems. I moved to a team working on much more greenfield projects with more attention on the products themselves, and I thrived for several years. See what your options are to talk to other teams and move to one that aligns better with what you want to work on.
The other related piece to this is that because mobility is so high, there do tend to be certain teams or areas with higher turnover and lower quality hires in some cases. No one wants to work on hard to maintain and neglected products, most good engineers that start there move on, and so it becomes a self-perpetuating cycle.
There are likely some extremely brilliant people to learn from at the company (even if not in your team), so try to seek out and find them in teams with openings. I agree it's easier to move after a year, but if the fit is really not right you can likely get an exception going to a team with an understanding manager (who you would enjoy working for anyways). Set up some non-formal meetings based on the internal job board and be open with all these experiences and concerns.
Finally, the internal toolset is a real challenge, but I've come to take a slightly less pessimistic view on it. First off, the internal tooling tends to be worse on an individual workflow level, but accepting it has largely been better for me than fighting it (in most but not all cases). It's slower than a modern toolset, but still usually productive once you embrace what it's good at. The flip side is there are usually good reasons it's evolved to where it is today. Some of these reasons have to do with the scale of how many teams are working together, and understanding that will help explain why it is what it is. The other reasons are just that some of these companies have now been around a long time, and shifting to something better would be quite painful organizationally, meaning it's not ideal but the alternative would also be painful for the organization at a whole. You're new to it, so are at the opposite end of that.
This is in line with the point of the original comment, which wasn’t just about investing money. That comment mentions self-development but it’s the general principle of reinvesting gains in something that is increasing in value.
In your case you are reinvesting gains from your music career back into your music career which is currently increasing in value. The principle is that this will let your career grow at increasing rates.
Presumably it comes from a combination of things, e.g.
1. Streaming higher quality video.
2. Using mobile more often instead of needing to find WiFi.
3. Changing behavior to do things that you couldn’t before on a slower connection.
4. Faster rate of consumption due to faster load times.
I do all those things, and in two months I’ve used 17 gigs on my iPhone XR. I’ve got eight devices on a Verizon unlimited plan with 25G soft cap, and I’ve never come up to the point where I’ve been throttled.
I can also still manage to fit an iPhone 12 Mini comfortably in many running shorts in the small rear key pockets or back zipper pockets. Some running waistbands also work well. But it's hit and miss vs old mp3 players that weighed next to nothing.