"developer gets a great idea - let's push an update to the API as a GET request so we can cache this on the CDN... forgetting that the JWT token is potentially returned in the call. Now, whoever makes the call first gets their JWT token stored for everyone else to load instead when the API call is made."
I wholeheartedly disagree with this entire statement.
If you want to grow as a programmer (in my case), then side projects are going to get you the skills to advance your career and get you a better job over "buddying up" with recruiters. Sure, you can be a 9-5 kinda person and then "switch off" when you get home, but you will be the one stuck wondering where it all went wrong and write a blog article complaining about it.
easily a 4 - Co-Founder felt embarrassed trying to show it to clients but it worked and people could give us money. knocked it out in like 2 months. - now we're 2 years in, still here.
i voted for and still use sass but inside vue/nuxt - i have no desired to write css inside js, why? because I don't have time to relearn the wheel and I choose vue over everything else because I get to write code faster, not just css but html and javascript at the same time. I use the tools that work well for me so I can move prototypes to production faster.
In a similar boat; I switch between multiple AWS, Gmail, Digital Ocean, GCP, etc accounts and it just didn't handle a 'full on power user'. I dev everything in Chrome and just utilize pinned tabs still.
The autolaunch was also very annoying. Having user profiles or personas to handle all my logged in states for that user would be awesome. let me know when that's in there and I will get it another try.
I host a few services for family/friends/clients and am also working on a couple of projects at a time so I am forever switching accounts on a weekly basis.
My team uses AWS for all of our servers, CDN, SQL and cache boxes but use BQ for all of our telemetry data - about 20 billion metrics a month.
Not having to manage a redshift cluster and just let BQ do all the work for us is worth the query time; even then, most of our complex queries run sub 30 seconds over hundreds of GB. If your data can be queried using a date-range then use date-partitioned tables. There is a 1000 table query limit so there are some pit-falls but BQ makes it easy for you to aggregate data into weekly and monthly tables to query against.