Moinerus | Dev, AI, Crypto (@moinerus) header
Moinerus | Dev, AI, Crypto (@moinerus) profile picture

Dev by day, fully AI pilled. Side projects at night, build in the open, here for banter and feedback, hit or miss. Family, nature and a camera off the screen.

Joined June 2011
BTC cycle bottom: $40,600 to $50,700, 26 Sep to 31 Oct 2026. Low so far $58,525 and plenty reckon that was it. In which case I've missed the lot. My quant tool says lower. Quant's generous. Posting before the fact so it can be marked after. Egg on my face or a grin ;p
2
1
5
199
Bitcoin wicked to $55,106 on Saturday, below June's $58,525 low. Then closed at $60,086. On daily closes June still holds. Could be a double bottom, but only possible until it breaks the high in between. For what it's worth, I'm back to 100% BTC. Not advice ;p
1
13
Moinerus | Dev, AI, Crypto retweeted
Prompt of the day (a long one): Take a look at every code comment in <my codebase | this section of the code>. Categorise each comment as: - Tautology: simply repeats what is already visible from the code - Excuse: many comments allow the agent to get away with a hacky implementation, which then gets propagated through the code - Stale: references code or implementation information that is no longer relevant - Decision Record: documents an important, non-obvious decision about the code For each comment, take this action: - Tautology/Stale: delete the comment - Excuse: delete the comment and file an issue to fix the hacky implementation - Decision Record: move it into an ADR Once this is done: - Create a lint rule banning comments for <my codebase | this section of the code> - Take a ratchet approach, assuming not all comments will be deleted this PR - Create a /delete-comment skill in this repository so we can repeat this process later - Estimate for me how many lines of code we'll shed by deleting all comments --- I'm sold - comments considered harmful
185
214
47
4,779
453,258
Are we as men, the simplest of creatures?
46
126
15
2,500
338,801
Really like this. Especially the last paragraph. If an agent writes the tests too, I look for the junk first. Zero assertions. Tests that can't fail. Coverage that looks fine and proves nothing. Power tools are fine. I'm still the one responsible if it goes wrong ;p
Disengaging from syntax is not disengaging from engineering. I’m working on a significant project at the moment. It’s in a pre-production state so far. More than a prototype, less than ready for real users. I’ve been making multiple passes over the structure for each of the following concerns: Architecture, coverage, race & concurrency, security, API, etc. Each of these requires significant interrogation and review of verification procedures; but not review of the code. At base are the /ub-mode (GitHub.com/unclebob) rules that keep the agents disciplined as far as coding structure and tests are concerned. But above that it’s me making sure that all the bases are covered well enough to keep my client safe from stupid sloppy mistakes. I am the engineer. I am responsible. The agents are just my tools. They are power tools, to be sure. But power tools in the hands of novices result in missing fingers. So I am very careful.
1
1
19
Bitcoin's Stablecoin Supply Ratio fell eightfold between its two measured bear bottoms: 20.14 to 2.52. Two readings cannot set a reliable threshold. The dashboard tracks it outside the score.
1
13
Moinerus | Dev, AI, Crypto retweeted
“Your job has fundamentally changed. It is no longer to write code, and LLMs are not here to help you write better code faster. Your job is to help the LLM write better code faster.” Bingo.
Replying to @josephfcox
Here is Proton CTO's AI manifesto, that I obtained multiple copies of 404media.co/manifestos-fear-…
27
18
4
239
12,509
Scoring my call, as promised. The lowest daily close in the window was $77,110. Not even close. June's $58,525 still holds. Quant was generous. My rules weren't ;p
2
Scoring my call, as promised. The lowest daily close in the window was $77,110. Not even close. June's $58,525 still holds. Quant was generous. My rules weren't ;p
BTC cycle bottom: $40,600 to $50,700, 26 Sep to 31 Oct 2026. Low so far $58,525 and plenty reckon that was it. In which case I've missed the lot. My quant tool says lower. Quant's generous. Posting before the fact so it can be marked after. Egg on my face or a grin ;p
1
1
1
16
The signals were mostly there in June. One rule held the model back. I'm adjusting it to hopefully catch the next top, and future bottoms. More on that soon.
12
Bitcoin may already have bottomed, and I may have got the call wrong. Basically, I don't know. Quant is apparently still hard, even with all these AI advances ;p So I've built a cycle comparison tool to look at a few ways this could play out.
2
1
31
I can line up the same paths from June's low or October 2025's high, keeping percentage moves and calendar days. Some cases overlap. Old cycle gains can produce daft prices when rescaled. I haven't shown that any of this can predict the next bottom.
1
10
The comparisons are now live: peakandtrough.com/#compariso… My original call is here: xitter.gq/moinerus/status/209872… What would make you rule out June as the bottom?
BTC cycle bottom: $40,600 to $50,700, 26 Sep to 31 Oct 2026. Low so far $58,525 and plenty reckon that was it. In which case I've missed the lot. My quant tool says lower. Quant's generous. Posting before the fact so it can be marked after. Egg on my face or a grin ;p
6
I had a hunch a pipeline was flaky for years. It wasn't taken seriously until I pulled the run data and plotted it. The DevOps Handbook's Second Way is about feedback. Get the data, test the theory, then decide what to fix.
1
18
Exchange net flow was negative at all three measured Bitcoin bear bottoms: -0.232%, -0.056% and -0.262%. The 2018 low sat close to zero. A much deeper cut-off would have missed it.
1
1
19
Done isn't merged. Before users arrive, we need dashboards, alerts, a runbook and a rollback path. Developers should follow the change past the deploy and into the on-call rota.
1
19
Hash Ribbons was negative at all four measured Bitcoin bear bottoms. The readings ranged from -14.70 to -0.86. A zero flash line catches each of them.
1
2
35
An andon cord nobody answers is decoration. When main goes red, we need to stop merging and fix the build. The DevOps Handbook's Second Way is about fast feedback. Who calls the stop, and who picks up the fault?
1
24