So, the one advantage to being out of ADHD meds is that I can have a drink without worrying about drug interactions.
I'll take my victories where I can.
Okay, sqlitebrowser (from the #Debian repositories) is actually a pretty decent tool. It provides a nice point-and-click interface that makes working with #sqlite3 databases a little bit nicer. Knowledge of how to write an #SQL query is still a requirement, but it makes creating/editing tables more convenient. Maybe it's well known, but I just discovered it yesterday.
Edit: sqlite browser, not mysqlbrowser
like this
reshared this
like this
So, I get that #KiCad can't have symbols and footprints for every component ever in their default library, but some of the things they've chosen to include can be a little confusing when compared against what they haven't chosen to include. Here's an example:
There are symbols for the TC74HC00 (quad NAND gate) and TC74HC08 (six channel inverter) series of chips, but none for the TC74HC04 (quad AND gate). Sure, the 74HC00 symbol can fairly trivially be edited into a 74HC04, but still... Am I missing something here?
Fortunately, for this particular board I was able to do some boolean magic with a single 74HC00, so it's a moot point.
I'd try this out on a breadboard, but I don't currently have the necessary parts so I'll just ask instead.
What happens on a 555 timer if you simultaneously drive the trigger low and the threshold high? Is this an error state that could vary from chip to chip?
πππ reshared this.
Q and ~Q outputs of the SR latch to be driven low.
Woo! Got my clock module down to two chips total (plus resistors, capacitors, and such).
Really basic stuff, but I'm still learning #KiCad.
like this
reshared this
~HLT instead of +5V. No additional logic gates required.
Decided to look into Nostr since everyone here seems to hate it (so I can figure out why).
From their website, they tout that it's "censorship-resistant"* while also complaining that traditional social media is overrun by bots and spam.
How does one go about solving the bot/spam problem without resorting to censorship? This feels rather mutually exclusive to me.
* frequently a fascist dog whistle
R. L. Dane reshared this.
8bitdo makes bluetooth receivers that plug into an nes controller port, been thinking about getting one of those.
And there are plenty of no name 3rd party nes controllers on websites like aliexpress
Jonathan Lamothe likes this.
Here's the funny thing about propaganda:
It gets started by someone (or a group of someones) with an agenda, but when it's effective, it gets swallowed and spread by well-meaning individuals who simply don't know any better. When this happens, it becomes even more effective, making it a vicious cycle.
Not everyone who spreads it is doing so for nefarious reasons (though many are).
...and I've officially let myself run out of my ADHD meds.
Shit.
screen for many years. I somewhat recently switched to tmux. Both are solid options, though tmux seems more popular.
Adam Hunt likes this.
Jon's Friendica Node Notices reshared this.
Well shit.
I got the parts I ordered from DigiKey. I didn't realize how small they were. I've soldered SMT parts before, but I don't know if I have a steady enough hand to do these ones by hand. π
Good thing I only ordered a few.
like this
To those who argue "my VPN can't track me because I pay them in bitcoin":
You know they have your IP address, right?
like this
So, I was bemoaning the fact that finding chips in a DIP format is getting harder and harder because everything's moving to SMT. I don't hate SMT chips, but they make it rather difficult to play with them on a breadboard before using them in a project.
It just occurred to me that if I'm going to the trouble of designing a PCB in the first place, nothing stops me from sticking a single chip on a PCB with a bunch of pin headers to turn it into a quick and dirty "DIP chip" for experimenting with on a breadboard. I can even do this with a bunch of different chips on a single PCB that breaks out into multiple different units.
I'm sure I'm not the first person to have thought of this, but it was definitely an "aha" moment for me.
like this
Justin To #ΠΠ΅ΡΠΠΎΠΉΠ½Π΅ reshared this.
I love it when the photo of a component and the schematic drawing on the data sheet disagree with each other.
(e.g.: digikey.ca/en/products/detail/β¦)
Guess I'll have to wait 'till I have the physical component in my possession to find out for sure.
For all the filtering options that DigiKey has on their web site, I wish you could filter based on minimum order quantity.
No, I do not want to buy 3000 voltage regulators.
When a bear attacks you, you generally die and then it's over. When a man attacks, you live with that trauma for life.
like this
The great thing about being an adult is that if you want to have candy for dinner, nobody is going to stop you.
The terrible thing about being an adult is that if you want to have candy for dinner, nobody is going to stop you.
πππ reshared this.
Maintenance and Release Schedule
βοΈ Nextcloud server, a safe home for all your data - nextcloud/serverGitHub
@BjΓΆrn SchieΓle I think I figured out my problem. I'm running an older version of PHP that is no longer supported by later versions.
Edit: It irks me that it didn't warn me about this before now though.
Something that's been bothering me about lifetimes.
When I got to this section in the book, I couldn't (and still can't) understand why it's necessary to specify lifetimes for the references a struct holds. I mean, if I have:
struct Foo<'a> {
bar: &'a String,
}Shouldn't it just be assumed that the data referenced by Foo::bar should have to live at least as long as the Foo object itself? Why does this have to be explicitly stated? Is there some scenario where you would want this to not be the case?
Edit: formatting fix
Adam Hunt likes this.
Lifetime elision only applies on function signatures. It might be because no one has done the work? Though I think it's nice to be explicit that the struct holds a reference to something.
Explicit lifetimes would be necessary for a struct with multiple references (or I guess a rule that says they're either all the same or all unique). These are not the same:
struct Foo<'a> {
bar: &'a String,
baz: &'a String,
}
struct Foo<'a, 'b> {
bar: &'a String,
baz: &'b String,
}More info on the elision rules is at the Rustonomicon.
Lifetime Elision - The Rustonomicon
The Dark Arts of Advanced and Unsafe Rust Programmingdoc.rust-lang.org
Jonathan Lamothe likes this.
&self and return a reference.
like this
So you'd put up with the sound of crickets to spite them all. Good luck with that.
I need to know what is going on. I don't have cable tv (a real corporate problem) and my "social media" include my local weather info (via Youtube) as does a lot of my news sources etc.
And ALL my interests are in things that no longer have magazines or newspapers exclusive to them, instead them have Podcasts, Youtube Channels, etc. Same with most of the folks I communicate with in my life (since I lost so many friends and relatives to the Pandemic).
It's not the 1990s anymore.
@Joseph Teller That's not really likely to happen though, is it? At least not in the near future. Besides, if everyone jumped ship, there would be no content there to miss out on to begin with.
My original point though was that singling out TikTok as the only problem is rather silly.
Reading up on NES ROM programming.
For some reason, memory addresses 0x0000-0x07ff are mirrored three times (for a total of four identical regions of memory). In a system with such a small amount of addressable memory, why would anyone do that??
like this
@Jonathan Lamothe Depending on the specific system, complex asynchronous code via timer interrupts (or raster interrupts, or I/O interrupts) is possible, but only one "thread" should use the stack.
For example, by default the Commodore 64 has a timer interrupt to trigger code to handle keyboard scanning, blinking the cursor, and other stuff. It's a non-trivial amount of code, but it does not mess with the stack.
God damned #ADHD brain.
I either get super hyper-focused on one project, to the detriment of other things (like eating and sleeping) or I'm so scattered between twenty things that I don't get anything meaningful accomplished on any of them.
A thing that's been stuck in my brain for a while:
A couple weeks ago, @Cory Doctorow wrote this blog post about how AI shouldn't be used to write code (edit: among other things). I agree with his rationale, but I can't help but be reminded of a (perhaps apocryphal) story I once heard about a similar argument being made against compilers in the early days of computing. The same kinds of arguments could've been made back then.
Building a small personal project in #Rust to teach myself the language. As I was looking over my code, I noticed a mistake I'd made that technically worked, but was kind of silly so I fixed it.
This got me to wondering if Rust had a linter (it does) because surely I'd made other similar rookie mistakes. I found the linter and ran it on my project. It came back with one result that I already knew about: a value in a struct that doesn't get read because I haven't written that code yet. That was it.
I was surprised. It's still a very small project, but perhaps I'm a more competent developer than I give myself credit for.
ragectl reshared this.
Jonathan Lamothe likes this.
fedops ππ
in reply to Jonathan Lamothe • • •Jonathan Lamothe
in reply to fedops ππ • •