I recently reread Ecclesiastes & on the second reading came across what people tend to be trying to get at with that advice. I'll try give it from the Ecclesiastes perspective
Whatever you go out & gather, is ultimately worthless. So if you're in a shit mood & thinking that some day this work will pay off, you'll find that your days are spent in a shit mood & thinking some day this work will pay off. & then you die & everything you did doesn't really matter, & you spent your time in a shit mood. So if instead you find enjoyment in the simple daily toll, that your work today is essentially paying for the food you'll enjoy today, then you'll find your days are spent in a good mood. & then you die & everything you did doesn't really matter, but at least you enjoyed your time while it lasted
So "live it like your last" is a bit hyperbolic, but at least don't justify your suffering on the idea that life gets better
To try make sense of "live it like your last", it might be better said as "go to sleep at peace with your life even if you were to die in the night"
> Over the next 15 days, the school district captured at least 210 webcam photos and 218 screenshots. They included photos inside his home of Robbins sleeping and of him partially undressed, as well as photos of his father. The district also snapped images of Robbins' instant messages and video chats with his friends, and sent them to its servers.
> "Many of the images captured and intercepted may consist of images of minors and their parents or friends in compromising or embarrassing positions, including, but not limited to, in various stages of dress or undress," the lawsuit charges.
Sequence diagrams are very useful. Flow charts and state diagrams are also useful but less so in my experience.
If your inheritance structure is so complicated that you need a class diagram, you are probably in for pain... But class diagrams do their job for sure.
I find UML useful as post-coding documentation. After you figured out how things work, you UML diagram your code to help explain the complicated parts.
UML is also useful for talking with coworkers. As a 'sketch' don't try to get everything right, but coworkers often need to know what your plans are if they are to find work that won't conflict with your plan.
I think another UML post was talking about sketch 'masala' graphs (throw everything into a touchy feely graphic that really doesn't say much). Being absolutely vague and nontechnical is an advantage in some cases, but not useful to engineers. UML, for all of it's faults, is precisely defined. Every symbol means something.
It's physics, not perception. Just make your website fast.
Am currently consulting big ecommerce bussiness on how to improve page load. I made them this 'fastest page in the world' demo:
https://turboeshop.com/fastestpageintheworld/ - kindly please check it out. And here is fastest page with Google Analytics:
https://turboeshop.com/newstackonly/. 325 ms for fully loaded time CSS + images + HTML + JS + GA loaded + Measurement Protocol hits sent.
This is what fast website is: a) inline purged css; b) everything loaded from one domain, 100% cached. c)inlined js(vanilla + web component if you need one); d) inlined images up to 4kb; e) larger images loaded from cache from same domain. f) gtag.js and analytics.js -> from cache; g) Measurement protocol hits sent from async proxy on edge. h) 100% cloudflare cache hits; i) Cloudflare workers for dynamic bits; That's all what it takes. Don't read articles- just make it fast, it's really that simple :)
And as svelte was mentioned - if you want to improve a website that is bigger than your personal blog, you don't use svelte, react, gatsby or any other of that breed as it's impossible to do serious marketing with a website that's hydrated (svelte's web components is a wonderful thing though and is totally nice addition to marketing stack). I mean no insult to anyone with my strong opinions and would be glad to have discussions in comments.
UPD: Added note on Cloudflare & Cloudflare workers.
The best resource I've used for learning dynamic programming and actually having it click is the DP lectures from the OMSCS Graduate Algorithms course.
Rob was running ten simultaneous businesses by himself, (and he has a few kids), diligently managing and tracking his time to run each one as efficiently as possible, and tracking it to make it easy to sell the business to someone some day with a specific intruction manual and estimate of how much time it would take to run that business.
Whatever you go out & gather, is ultimately worthless. So if you're in a shit mood & thinking that some day this work will pay off, you'll find that your days are spent in a shit mood & thinking some day this work will pay off. & then you die & everything you did doesn't really matter, & you spent your time in a shit mood. So if instead you find enjoyment in the simple daily toll, that your work today is essentially paying for the food you'll enjoy today, then you'll find your days are spent in a good mood. & then you die & everything you did doesn't really matter, but at least you enjoyed your time while it lasted
So "live it like your last" is a bit hyperbolic, but at least don't justify your suffering on the idea that life gets better
To try make sense of "live it like your last", it might be better said as "go to sleep at peace with your life even if you were to die in the night"