Back in the VGA days, I worked for a video card maker, and one of them supported a multi-head configuration. You could stick as many as 16 into one machine, if it had enough slots. Thus driving 16 monitors at once. I was responsible for taking the stock Windows 3.1 display driver for the chipset and modifying it for multi-head support. That was a really fun and challenging project, and ultimately very satisfying. I am pretty sure there were a few customers who needed the full 16-card setup.
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!
Someone tried this, I saw it one of the Reddit AI subs. They were training a local model on whatever they could find that was written before $cutoffDate.
Agreed, I get better design and arch solutions from it. And part of my system prompt tells it to be an "aggressive critic" of everything, which is great -- sometimes its "critic's corner" piece of the response is more helpful/valuable than the 'normal' part of the response!
OP posited SQLite database contention. I don't know enough about this space to agree or disagree. It would be interesting, and perhaps illuminating, to perform a similar experiment with Postgres.
Yes, 100%. Being immobile is bad, whether you're standing, sitting, or lying down. (Too much strain from movement is bad too, hence RSI for many of us.)
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.
Another comment mentioned using a linter to prevent 'console.log' from being mergeable in a PR, and this is exactly the kind of approach I'd take. Preventing an invalid state from existing is a pretty useful principle.
I don't know the first thing about such things, but I'll bet if companies were pushed on this they'd suddenly start asserting that it's a lease, which I think is typically taxed similarly to a sale.
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.
My fear/anxiety causes me to avoid action. Fear of mistakes, failure, reproach/criticism from others, that it's going to take a lot of time/money, that I'll waste a lot of time/money, etc.
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.
I think the only way this gets better is with software development tools that make it impossible to create invalid states.
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.
Every complex piece of software "breaks in weird ways", that doesn't make it terrible. It will also break if you're trying to do 'weird' things it's not really designed for.
From the article: "Infineon did not report the flaw to NASA because the company did not know what the transistors would be used for, Fitzpatrick said."
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.
If you work in the JVM ecosystem, I can recommend (Java/Kotlin) + Quarkus + JDBI with Postgres. Quarkus supports testcontainers out of the box for tests, and it just plain works.
I don't have experience with it, but some people also recommend jooq.
Once you're familiar with friction, you start seeing it everywhere. And then you hate how much of it there is. I'm sure there's a philosophical lesson in there somewhere.
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.
Fair enough on the CSS, and I didn't realize autosave is already done, thanks!
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.
Experimented a few more minutes, and I have a few suggestions I think I'd like to see implemented:
-- 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.
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!