There's a color, gray95, that is the recommended black and white color for watermarks in a few books I've read on the topic. Honestly the best way to do it right is to ask the court (politely) what their stated requirements for watermarking are and if you get shrugs, you go for the bare minimum.
there is no court where I have ever practiced that would accept a watermark of any kind at whatever percentage or color. And he didn't need to ask, it's right there in the rules (state and local). Every court has extremely detailed requirements for font, size, line spacing, line numbering, color of cover for printed "chambers copies," size of margins, how the name of the court should be set out and where, and so on. Literally no excuse for this, he's lucky he didn't get sanctioned
What a fascinating cultural difference. In my corner of the world there's a Facebook page, the name of which translates to "Half-assed court documents" and it showcases badly made documents issued by courts.
I remember seeing a simple setup very similar to this, but the operator adjusted the camera (and a single screen was used for feedback) but the effect felt like a zoom-in / flyover of terrain. I can't find that video any more, could someone point me to it?
There is nothing stopping node from running on mobile and IIRC quite a few apps embed it as a part of electron or similar frameworks.
If i understand correctly bare can instead use much smaller engines like quickjs (and maybe libjs), but I'm not sure how the stdlib situation is for those.
I know it isn't the point you are trying to make, but I can't think of a better way to re-enforce OP's point of "mediocrity will be even more available" than a mid-00s style, pop country song about eating hamburgers. "Toby Keith but with less to say" might be the gold standard of mediocrity.
Typescript/Javascript, C#, HTML/CSS, Vue, SQL, noSQL, Bootstrap, Azure Devops/Github Actions, Kubernetes, Docker, Node.js, functional programming, CQRS, unit and automated testing
Résumé/CV: upon request via email
Email: michael[dot]goeke[plus]yc[at]gmail[dot]com
Laser focused Principal Software Engineer adept at delivering best in class solutions on time, on budget, while building a kick ass team in stride. Fearless and empathetic communication - break down walls, find and create alignment, empower those around me. Technical genius. Polymath and autodidact. Clear and concise communicator.
I've appreciated a lot of parts of this book and was wondering if I could share it with others in some way.
I like to see the actual content of a book before I buy it to know if it resonates with me.
I found the book's table of content with links to the content is available, so I linked that here. Hopefully you get something out of it, and buy either the digital or paper copy if it speaks to you.
I have a very different set of problems/concerns in my current project and when I walk through the website most of it isn't mapping into my current problem+solution space.
The problem this is solving may be obvious from your perspective, but it isn't from mine, and maybe others.
I don't know I need your solution unless I see I have a problem.
Perhaps there are a few simple, general problem cases this solves.
If so you could characterize those in context+problem+solution brief narratives.
That could help others get on the same page as your solution.
