This is the key. Ask all the developers for a ranked top-3 list of who they would most prefer to go to for help with a programming problem. Put that data together and you know who your best are.
Before the inevitable protest: I believe the ability and willingness to communicate with other developers is a vital skill in this business.
A nice layout. For fun I attempted to actually print (to PDF) and boy was that messed up badly! Guessing that's not the type of "print" you had in mind. :)
go into the print settings for pdf and set the margins to "none" - that fixed it here. but my workflow was singlefile extension to save as a single html file, then i opened that in another browser and used that to print to pdf - just to make sure i wasn't doing a "but it worked at my house" sort of claim!
We're in the process of migration a large MVC application from Framework 4.8 to .NET 6. It's been....painful. Hopefully at least for a while updating to new LTS versions will be less so.
We did that last year on a 3 million line / 500 person-year investment application. Quite challenging as everything from app domains to remoting, to call contexts and other unsupported things were being used. It was definitely worth it for performance alone as we were also using Mono to run on Linux.
I am moving a personal project with ~50k loc and it has turned into a rewrite of about 2/3 of it. Not fun, but on the plus side the app runs A LOT faster now. So much faster that even non tech people that use it noticed the difference.
Typically wherever you buy it they will have small Styrofoam coolers next to it. It typically comes sealed in thin plastic bags. Get it home, put on a glove, and throw it in your freezer. Any glove is fine as long as you're not standing there with it in your hand. There are several grocery stores that have it available here.
We use WKHTMLTOPDF (https://wkhtmltopdf.org/). In our case it's in the Rotativa package (.NET MVC). There are a few caveats; it uses an older headless WebKit engine that doesn't support everything. We use the QT Web Browser (http://www.qtweb.net) to test/debug when needed. We do design pages to be specific "paper" sizes and lean on SVG a lot for anything fancy. We have some JS that breaks long tables into multiple tables, etc. But the resulting output looks flawless.
Before the inevitable protest: I believe the ability and willingness to communicate with other developers is a vital skill in this business.