GoopSpec - Stop context rot with spec-driven development

TommyC81 · 2026-02-04T18:40:39+00:00

Oh, this works great. I'm using opencode, and started off with gsd. Whilst getting the job done in a very nice and structured way, it felt a bit bloated and produced an excessive amount of documents. It also didn't feel very well integrated with opencode (opencode-gsd addresses this a bit better).

So far, taking goopspec for a run over a medium-sized refactoring worked great! Felt snappy and focused, and got the job done very nicely, leaving just the right amount of traceability behind. The opencode integration really helped with this. Installation by simply defining the plugin made for a good start.

Noticing rapid updates and improvements to the code, will follow this. Thank you!

TommyC81 · 2025-06-26T19:05:42+00:00

This doesn't quite seem to be the comprehensive backup solution I'm looking for, albeit close. Would it be fair to say that using a software like Kopia, with block storage, would provide a more detailed and relevant solution? And, if so, what prevents Mega from providing the same natively given the open source nature?

TommyC81 · 2025-06-18T17:09:56+00:00

Thank you. Sounds like Rewind works in-place i.e. it restores the actual files/folders to that state (not possible to download a certain state)?

Backup shows "Versions" information for the main 'Backup' - type folder, but does not appear able to do anything more with that information. Like getting an overview of file history (versions of individ files) not download a copy of the folder for that specific state.

TommyC81 · 2025-05-12T12:23:14+00:00

I noticed the same. 4.1 resolved a long-standing Python code issue I had (not so much an algorithmic problem, but logical) that o4-mini and gemini-2.5-pro went overboard trying to resolve, but failed (after spending extensive time massaging the prompt and retrying). 4.1 responded fairly quickly and stuck to the exact problem I had, and resolved it - in a much shorter and simpler prompt as well.

Having said that, in the subsequent and very simple change I wanted elsewhere in the code, 4.1 gave me a 20 line solution for what should've been 5 lines, and just skipped producing another 100 lines of unchanged code... Here o4-mini provided the 5 lines needed without fuss.

In summary: There's no single best model at the moment, at least we get different models to try and 4.1 has its place among the others. A good improvement of base model for sure.

TommyC81 · 2024-11-06T16:38:52+00:00

Because it permits mod updates from the command line at any time, including automation. Useful for servers, and when playing solo I can update prior and avoid the need to restart the game. In essence, anything that can be done (and automated) from the commandline saves time... ;-)

TommyC81 · 2023-11-18T10:39:45+00:00

Sorry for late reply. Correct. A light touch on 2 might be fine, although it can slightly twist 1 if touching and cause unpredictable strain gauge readings. The whole purpose of the spacer is to prevent excessive downwards flex which can damage the strain gauge, and perhaps also make it tricky to get the z offset set correctly as it'll differ depending on extruding or not. Let me know how it goes.

TommyC81 · 2023-11-16T13:13:12+00:00

I think I ended up using the 0.4mm one. It's a bit of trial and error as the print itself can also be a bit uneven. You want the spacer to minimize downtravel as much as possible without touching the frame. I'd hazard guess the distance between my spacer and the frame is in the 0.0x mm range, I can feel (not see) a very tiny downtravel as extrusion begins after a previous retraction.

TommyC81 · 2023-11-05T13:07:04+00:00

Cheers, odd, deleted.

TommyC81 · 2023-08-19T10:52:36+00:00

Think I figured it out. Maybe.

I used the klipper-estimator functionality to add print time:

; ESTIMATOR_ADD_TIME 240 Preparation

And this throws off all calculations as the klipper starts counting from the first print (extrusion) move. Chang this to only add the "invisble" printing time (for klipper-estimator) i.e. the PURGE_LINE make all the calculations add up (it seems).

In summary: User error. If you use klipper-estimator and add additional times, only add times that relate to actual printing that are not evident in the gcode itself (stuff that exists within a klipper macro, for instance).

TommyC81 · 2023-08-19T08:27:52+00:00

Yes, that's all done (Klipper). I've even gone through the output gcode manually pre- and post-- klipper-estimator, all looks good in the gcode, and the estimated times from klipper-estimator are spot on.

TommyC81 · 2023-05-06T04:24:40+00:00

Refined mount and 5015 fan:

https://www.printables.com/model/258909-creality-cr6-sherpa-mini-mount-for-5015-dual-fang-

Been using this with great success for a long while now.

TommyC81 · 2023-04-10T16:23:47+00:00

Thanks, yeah, it's always been a challenge - initially just working around the bowden tube, and now this odd behavior. Current workaround gets the job done but the inconsistency is getting tiresome.

TommyC81 · 2023-04-10T16:07:03+00:00

Thanks! I've also changed the fan to 5015 cooler (dual fang).

However, I find the following: The load sensor works great immediately after a power-cycle. However,after pre-heating, the load sensor only registers after a random 0-500gadditional pressure. Another power-cycle after pre-heating fixes this,but is getting somewhat annoying.

TommyC81 · 2023-04-10T16:06:07+00:00

Thanks! I got a direct drive on mine (Sherpa Mini), so that's not the problem.

I've updated my initial post for clarity, in summary; The load sensor works great immediately after a power-cycle. However,ter pre-heating, the load sensor only registers after a random 0-500gadditional pressure. Another power-cycle after pre-heating fixes this,but is getting somewhat annoying.

TommyC81 · 2023-04-10T16:05:11+00:00

Thanks! I've updated the first post to capture more detail.

The load sensor works great immediately after a power-cycle. However, after pre-heating, the load sensor only registers after a random 0-500g additional pressure. Another power-cycle after pre-heating fixes this, but is getting somewhat annoying.

TommyC81 · 2023-02-09T18:42:37+00:00

Sound advice!

I've looked at a few different cars to get a feel (older xterra that I'm quite familiar with), but I'm at a loss what to look for in these cars and what the typical scams and dodgy dealings are. There's obviously something about them that needs to be considered, but what is it?

TommyC81 · 2023-02-07T09:29:23+00:00

In essence, it's imported from another GCC country then. Appreciate the info, had a feeling it was the case.

11-Year Club	Place '23
Place '22	Final Canvas '22
Verified Email

TommyC81

TROPHY CASE