The keyboard stops working after a while of inactivity like watching a movie or playing a game. The keys light up, and the 2.4ghz indicator on the keyboard shows it's connected, but my pc doesn't detect any keystrokes. Only after I unplug and plug the dongle again, does it start working. How do I fix this? Is this an issue on the linux side, or should I return the keyboard and get a Keychron v6 max?

cross-posted from: https://programming.dev/post/51247328

I use speckit, and while I like the spec/clarify/plan/task/analyze/implement loop (although it can get a bit overwhelming at times), I don't like that I have to start with writing a spec and implement it to begin with. I am looking for a more of a design phase before the spec phase, where I can talk about the overall application architecture, and then start writing specs for implementing pieces of it.

For instance, let's say I want to build a github repo provisioner that 1. creates repos with desired setup, and 2. bulk edit repos with secret updates, yaml updates, etc. I don't want to build both the features at the beginning. I want to first build only the create portion, and then do the bulk edit feature later on. With speckit, I can do this by only telling it to create the spec for the build portion, but later if I want to build the bulk edit portion, the whole application might need to be changed in important places, because it wasn't a 'planned' feature when it was first designed. I want instead to have a design phase where I describe and maintain a doc with the whole application, and when I start the spec for the create portion, the agent can understand that this create portion is only part of a bigger application and can design/implement the create portion accordingly.

Have you come across a situation like this? how do you handle your big applications? Please advise.

I use speckit, and while I like the spec/clarify/plan/task/analyze/implement loop (although it can get a bit overwhelming at times), I don't like that I have to start with writing a spec and implement it to begin with. I am looking for a more of a design phase before the spec phase, where I can talk about the overall application architecture, and then start writing specs for implementing pieces of it.

For instance, let's say I want to build a github repo provisioner that 1. creates repos with desired setup, and 2. bulk edit repos with secret updates, yaml updates, etc. I don't want to build both the features at the beginning. I want to first build only the create portion, and then do the bulk edit feature later on. With speckit, I can do this by only telling it to create the spec for the build portion, but later if I want to build the bulk edit portion, the whole application might need to be changed in important places, because it wasn't a 'planned' feature when it was first designed. I want instead to have a design phase where I describe and maintain a doc with the whole application, and when I start the spec for the create portion, the agent can understand that this create portion is only part of a bigger application and can design/implement the create portion accordingly.

Have you come across a situation like this? how do you handle your big applications? Please advise.

cross-posted from: https://programming.dev/post/49896390

Keeps alerting me to empty boxes of 'person' detected with 90+% confidence. So frustrated right now.

She's an only child, and we didn't grow up in America, so she's a bit naive on a lot of things. Her teacher advised us the other day that she's such a sweet girl, but middle school could be brutal for her because of that. What are some wholesome shows I can watch with her that helps her get ready for the world?

EDIT:

This is an astounding collection of shows. Thank you so much! We've started watching Amphibia, and really enjoying it so far. I'll add all these to the backlog. Thanks again!

FWIW

Not sure where to post this, so here it goes.

Life

It must come to an end
For even though we lived a good one
It's time to go away


Remember the good times you had|
and all the fun you had
'cause it's time to go away


But if you have a strong friendship
you might remember them in your next life!
But sadly, it's time to go away