This is good advice and tracks pretty well to my recent experience. I applied almost exclusively to startups though. 7 YoE full stack web.
I did two take home assignments but zero white-boarding, just a few general language/framework questions. Some very casual system design questions also. This was for mid-level to senior full stack web dev roles.
I had a minimum salary but beyond that do not need more, so I didn't bother with FAANG or large enterprise stuff. Very happy where I landed.
I was actually really surprised at how smooth and relatively simple the whole search was compared to the almost horror story level experiences some people have. It is mentally exhausting but I was lucky to have polite and professional interviewers.
webpack can be made use-able relatively easily if you do not mount node modules over the shared file system.
I've been doing this for quite awhile with a volumes declaration in docker-compose that looks like this (running nextjs, assuming /usr/src/app is where your dockerfile has your node stuff):
(on service definition):
volumes:
- .:/usr/src/app:cached
- node_modules:/usr/src/app/node_modules/
- next_artifacts:/usr/src/app/.next/
and then in the top level volumes key defining node_modules and next_artifacts as blank/default.
That means I mount everything except node modules and the build artifacts so the shared filesystem does a LOT less work trying to sync stuff.
The downside, of course, is that I need to run npm commands both inside the container and outside if i want them in my IDE. A fair trade for decent performance.
That setup is still not as fast as native but definitely usable and does not send my machine into space header mode much more than normal usage.
Interesting. I have always had the same docker-compose setup with a separate node_modules volume inside Docker, but I've always still had the jet engine space heater issue.
Birding is great for relaxing. I recently picked up a camera to go with my binos and it's been awesome.
I go out to a park or my backyard for an hour or so and sit while looking for birds and taking photos.
Then when I get back I spend a little while editing them and posting to ebird.
It's not 100% free, but you can get into the hobby with some 8x42 binos (Nikon Prostaffs are ~$100 and great, but you can go cheaper). Cameras can really eat budget - there is a $300 lumix that would be fine and even a cheaper point and shoot will work.
It's like fishing. If you are patient, you can see a lot of unexpected kinds of birds wherever you are. You can bird anywhere and have a nice time. Migration is a fascinating time where tiny birds wander by, popping in your area for a day and moving on.
I recently re-platformed my personal site onto Hugo, and it's really nice. You can easily use GitHub to host, and posts are in markdown.
Templating is pretty simple and as close to plain html markup as I think you can reasonably get. Outputs flat files that you could put anywhere.
Totally reduced friction to post, no server processes or database to babysit and the binary to build it is one versioned package. I will be able to build it for years without worrying too much. Can't recommend enough.
Jetbrains is really really good and checks all of your boxes, op. Aside from having great coverage out of the box, there are plugins supporting nearly everything, especially web stuff. Bash, helm charts, docker, database tooling and all kinds of JavaScript stuff like webpack, react, eslint and prettier.
Ultimate edition is worth it if you're bouncing all over the place and has been my ide for several years after switching from sublime.
The only thing ultimate didn't cover super duper good was golang, but they have a separate edition for that which works great. Been a bit since I've done go work so ultimate may cover it well now too.
Vscode is really close behind in many places but the depth of coverage in jetbrains is unmatched in any of the free offerings I've used.
Organize or offer to host a local Meetup group. Totally expected that hosts say what they do and that they're hiring, and everyone going will probably be a developer.
Nothing stopping you from explaining your opinion as an expert on the tech, and if it's extra time (==money) also communicating that. If that is ignored and you're getting paid for your time, that's the best you can do.
This is usually what happens, though in my case my boss (Lead Dev) is already telling them what isn't possible and what doesn't make sense. Some clients just insist for months until we finally give them what they want and they see we're not talking out of our rears. But yeah I understand all that, it's just silly to me to waste time and money doing things that will not be useful for the end-product. I guess I'll be numb to the silliness eventually...
It appears that they used the massive influx of capital they got from the hype pre-launch to continue building their vision that was entirely too big to deliver in any timely manner. They might be able to turn this around riding that into something that generates enough interest to continue to make plenty.
Putting it on sale on steam has it back at the top, which is actually kind of incredible considering the launch outrage.
The hype wasn't for nothing, people are craving the kind of game that was described before this launched. This is potentially Minecraft all over again.
I did two take home assignments but zero white-boarding, just a few general language/framework questions. Some very casual system design questions also. This was for mid-level to senior full stack web dev roles.
I had a minimum salary but beyond that do not need more, so I didn't bother with FAANG or large enterprise stuff. Very happy where I landed.
I was actually really surprised at how smooth and relatively simple the whole search was compared to the almost horror story level experiences some people have. It is mentally exhausting but I was lucky to have polite and professional interviewers.