nieceandtows

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

Designing a simple photo frame. I wanted to make it so that it prints without supports. While printing, however, the back support part wobbles/vibrates with movement, and is printing terribly.

Ender 3v3 CoreXZ, PolyTerra matte black filament, using the CR-PLA Matte profile in Creality Print 7. Tried printing at slow speeds, the issue still persists.

I've tried making the back support with only 45 degree angles (previously it was an x diagonal), made it thicker (from 0.75mm to 1.5mm). Nothing is working. Please find the stl and 3mf here (https://www.thingiverse.com/thing:7281179).

Is this a printer issue, a model issue, or a slicer issue? Please advise.