At my last company, when we were building a greenfield application, we leveraged this pattern, at a time when GraphQL was not yet available. In my new company, I look at GraphQL and realize that this solves the BFF pattern in a standardized way
I went through the exact same thing with Google. The interview was very impersonal, never going into if I'd be a great culture fit and it was simply on the basis of if I knew how to do this algorithms problem that doesn't show if I'm a good engineer or not. Ended up in a much better company culturally, and I've never looked back
I used to be a big supporter and user of Sublime, using it for my day to day. Unfortunately, even though it still has faster boot time than VSC, the community around VSC is so much richer that it becomes a case of too little too late.
I'm also using it as my default. I also find it great that with every release, they are pushing features that promote immutability; ReadonlyArray, and const assertions, to make developer workflow better and safer.
Interesting article. Though, the article should provide alternatives and speak to how use other types of programming paradigms might solve the issues that the person in the article is stating.
I ended up leveraging multi-stage building with Docker and have a gradle image as my builder image, build the jar, and copy that to the image that is going to get deployed.
I know that there are many backend solutions to this such as using a headless browser to generate the page and create a PDF, and Wkhtmltopdf, but I'm looking for a way to circumvent this with a full frontend solution.