BTW this was done in the day when drawing pixels on a screen was all done via the CPU telling the card "draw /this/ pixel with /this/ color". Good times!
761 karma · joined August 5, 2017
BTW this was done in the day when drawing pixels on a screen was all done via the CPU telling the card "draw /this/ pixel with /this/ color". Good times!
Found the GitHub: https://github.com/haykgrigo3/TimeCapsuleLLM
I really enjoy having the flexibility/option of standing or sitting, and IMO a standing desk is one of those purchases that has a 10x payback.
I hate the "everything's a subscription" business model that's taking over everything. We'll achieve peak serfdom when the air we breathe, water we drink, and food we eat is bought on a subscription model.
Then, once I've procrastinated, my fear/anxiousness of the consequences of NOT doing the thing kicks in and I rush to complete it.
It's great! /s
The best solution I've found is to slow down, introspect into and address my fear/anxiety, and reassure myself that most of the time my fears are entirely or mostly unfounded, and that even if something "bad" happens it won't be catastrophic.
I don't practice that enough, and that's the hill I'm climbing now. I'm also trying to learn to lean more into the feeling of accomplishment ahead of time. In a "it will feel so good to get this done, even if it's not great" way.
In the physical world, when we build something complex like a car engine, a microprocessor, or bookcase, the laws of physics guide us and help prevent invalid states. Not all of them -- an upside down bookcase still works -- but a lot of them.
Of course, part of the problem is that when we build the software equivalent of an upside down bookcase, we 'patch' it by creating trim and shims to make it look better and more structurally sound instead of tossing it and making another one the right way.
But mostly, we write software in a way that allows for a ton of incorrect states. As a trivial example, expressing a person's age as an 'int', allowing for negative numbers. As a more complicated example, allowing for setting a coupon's redemption date when it has not yet been clipped.
They might not have "known", but come on, you're selling radiation-hardened chips to NASA. You can sure make an educated guess that they might be used for a probe.
I'm guessing there's a clause missing in the contract that says Infineon must disclose all known problems to NASA regardless of how the chips will be used.
Regardless, there are some people at NASA to whom 'Infineon' is now a curse word.
I don't have experience with it, but some people also recommend jooq.
As far as battling it goes, my experience is that you can get a lot of mileage by just spending an extra minute or three making something a little cleaner, more readable, less prone to failure, etc.
I did see the '---' collapsible and that helps but only if you have one section you want to collapse. I'm perhaps more visually-oriented than most, and being able to hide extraneous material helps me focus.
-- Allow regular expression search. -- Click outside the note to save. (Autosave every N seconds would be nice as well.) -- Customizable CSS. (Yes, I can do this with a local build.) -- Collapse/expand (sub)headings.
I'll give it more of a test drive over the next few days.
Tags could cover most of my need for taxonomy/organization. (I'm hesitant to say 'all'.)
FYI I noticed a typo, "Github falvored markdown".
[0] I try for 'inbox zero' but am okay with leaving things in my inbox for a few days if I'm expecting to need them soon. Sometimes I flag for followup or color-categorize.
If you're implying that the judge was somehow complicit in helping OceanGate ('oversaw', meaning presided over and made decisions concerning), then please provide evidence of that?
I should add we're not doing this because we need to cut costs.
At the technical level, both tragedies were caused by design flaws. Organizationally and culturally, multiple factors contributed, but an attitude of "nothing has happened yet, so this is fine" (normalizing risk) was a major one.
Agreed. The writing style, including adjective/adverb use, is clearly intended to convey an emotional tone of disgust and displeasure.
I'd love to give these people a chance to review a car from the 1900s or 1910s. They'd undoubtedly walk away convinced that the newfangled 'automobile' was a heap of rubbish destined for the dump.
(Of course the successes we have today are built on top of endless heaps of rubbish and a few good ideas.)
What am I missing here?
I ran OS/2 Warp for a couple years as my daily driver and agree, it was a fantastic OS. Stable as heck, preemptive multitasking, just a solid workhorse. I would say Windows got "good enough" with Windows 2000, and pretty decent with the release of XPSP3. Many years later....