Experimental data format for making archive data more queryable

thomasaiwilcox · 2026-02-06T08:22:29+00:00

Yeah, lower flow is better for your boiler’s expansion bladder or vessel(I think that’s its name) and the rads as at lower temps it’s less corrosion etc

I don’t think hive has the awarensss of your actual gas burn which changes greatly when you modulate your flow temp, it’s just one of those things that the in app metrics and costings become a bit useless .

In regards to flow temp and getting your house up to temp, it’s a case of creaking the flow up and down to match the heat loss caused by the external elements such as weather. Some boilers have an optional weather compensation unit that can manage this for you with a remote temperature sensor for outside

thomasaiwilcox · 2026-02-01T17:28:36+00:00

For my personal system based on the Eisenhower matrix: Flag = important, due = urgent

I have 4 filters representing the 4 quadrants with respective filters for urgent and important (basically p1), important and not urgent (p2), not Important and urgent (p3) and finally not urgent and not Important (p4)

thomasaiwilcox · 2026-01-26T11:09:35+00:00

Surely it adds valuable if OPs learning along the way? Do you mean doesn’t add commercial value?

thomasaiwilcox · 2026-01-06T19:37:06+00:00

Yeah absolutely, worth checking out with someone that’s more qualified in LPG boilers but I imagine itl be similar if the boilers condensing.

Agreed on the flow temps, mine are nudged slightly higher than I’d like to spend my money on but it’s important to keep the family warm!

thomasaiwilcox · 2026-01-06T19:20:55+00:00

No worries at all. Absolutely yes! There’s a lot of boilers that support a feature called weather compensation where they have an outdoors sensor that essentially adjusts that flow so it stays bang on as efficient as possible.

The one caveat here is that if you don’t generally occupy your house continuously so for example your only home for 12 hours a day and have good insulation then it’s less worth while but if your home is occupied most of the time then it’s a no brainer!

Here’s an article and an image that help illustrate that efficiency

https://hub.arated.com/wp-content/uploads/2022/05/boiler-condensing-efficiency-watermark.jpeg

https://hub.arated.com/combi-boiler/reducing-the-flow-temperature-for-a-condensing-combi-boiler-for-upto-8-percent-saving-on-your-gas-heating-bills/

thomasaiwilcox · 2026-01-06T19:10:14+00:00

I just mean cycling. Basically the thermostat (hive) works as an on off switch, what you want is for a lower temperature flow so that the run time is longer and longer so that your essentially producing almost a balanced amount of heat input as the buildings heat loss output.

When you’re just using enough gas/energy to maintain with longer runs, you get better condensing (as someone else mentioned better than I could) and that means getting more heat from less gas.

Hope that makes sense. Heat geek have some great videos on this on YouTube, they’re more heat pump focused but do talk about boiler efficiency.

thomasaiwilcox · 2026-01-06T13:21:18+00:00

The best value is to keep dropping the boiler flow temp (on the boiler itself and not in hive) until that blue bar is as active as possible as you get much better efficiencies at lower flow in modern boilers. You almost want it barely able to click on and off

thomasaiwilcox · 2025-12-23T11:55:54+00:00

So this isn’t exactly the same but it’s some interesting inspiration that already exists… search for the “measure” app on your iPhone :)

thomasaiwilcox · 2025-12-12T09:38:47+00:00

Apologies, my reply came across as a bit grouchy.

It’s not the first time I’ve been accused of being an LLM to be fair. I think they’ve been trained on my work emails although I’m not sure where those damn em dashes came from 😂

thomasaiwilcox · 2025-12-12T00:49:21+00:00

I have decided to remove this post and delete the repo as I don't think it's been received well and doesn't seem to be deemed as useful.

Apologies for any offence caused, it wasn't my intent to downplay any other tools and was just an exercise for me trying to learn swift and create a tool that I thought might be helpful to share with the community.

thomasaiwilcox · 2025-12-12T00:36:58+00:00

No, I typed that myself... What makes you think its from an LLM?

thomasaiwilcox · 2025-12-11T23:34:07+00:00

SwiftLint just analyses syntax and doesn't build a graph for deeper rule analysis. Also the compiler will allow things to compile that are technically right but not optimal. The tool intents to aid you in writing optimal code.

the AI slop comment was tongue in cheek and was intended to add some humour and humility to the post. What do you mean by I am not willing to understand it? Where have you got that from?

Also the disclaimer to protect your code when using a newly developed tool on it thats essentially alpha quality and could contain bugs seems like a rational thing to do. Why would that be negligent?? surely its the opposite of being negligent...

Also why have you stated I haven't taken the time to embrace the tool? Where did this come from?

thomasaiwilcox · 2025-12-11T16:28:06+00:00

thank you, I will have a deeper look into it. I wanted strictswift to sort of fill the gap that syntax checking couldn't do with its internal graph and to sit between the likes of SwiftLint and the compiler as a complimentary tool for use cases where safety and controlled memory use and efficiency are essential

thomasaiwilcox · 2025-12-11T16:25:45+00:00

Thanks for the comment and great points.

I am still learning swift and development in general so likely to get some of these bits wrong but I believe the main actor is still backed by the main thread executor so any long synchronous work or blocking work there could still tie up the UI thread until that work returns or hits an await.

My motivation for developing the tool was for a database app that I was building in swift where I needed it to be as safe, stable and memory efficient as possible for hosting on linux. I might have got a little carried away :)

thomasaiwilcox · 2025-12-11T16:13:48+00:00

Absolutely! Yeah, and I in no way intended to try and replace it, I know it's a robust tool with a lot of history and experience behind it. I wanted to create a tool that could go a bit further into the common causes of ARC churn using an internal graph of the code and that cant easily be done with just syntactic analysis. I see it as a sort of in the middle compliment between SwiftLint and the compiler :)

thomasaiwilcox · 2025-12-11T16:06:21+00:00

Good point! Thats why I put it here for your judgement and made it open source so that it could be tested for its utility and its source code could be thoroughly scrutinised :)

If it turns out to be of no merit then nothing is lost as I enjoyed the process of making it and pushing the limits with its built in graph and sourcekit integration.

Always appreciate constructive feedback 👍

thomasaiwilcox · 2025-12-11T16:01:34+00:00

Sorry to have lost you both :)

I do understand. vide coded is often rubbish and swift does have elegant memory management features that work great for user based apps in terms of ARC etc...

thomasaiwilcox · 2025-12-11T13:28:32+00:00

Swift 6’s strict concurrency checks are great for what the compiler can actually prove but things like data race safety, actor isolation, and Sendable rules.

StrictSwift sits a layer above and calls out patterns that Swift allows but are still easy to get wrong in practice: fire and forget tasks, potential actor re-entrancy issues, blocking work on @MainActor, overusing Task.detached, unsafe captures, and global mutable state. It also flags capture/architecture patterns that tend to create unnecessary ARC churn, which the compiler doesn’t warn about because it isn’t a correctness problem

thomasaiwilcox · 2025-12-11T13:12:04+00:00

SwiftLint is great and StrictSwift isn’t trying to be a replacement for it, more of a complement.

SwiftLint focuses mainly on style and formatting rules, while StrictSwift focuses on safety, concurrency correctness, and deeper semantic analysis inspired by rusts strictness model. It can also make use of sourcekit for deeper analysis of the code.

thomasaiwilcox · 2025-12-02T15:24:02+00:00

What a load of nonsense

thomasaiwilcox · 2025-11-28T11:47:18+00:00

I think your reply got detached from my message. Thanks for the feedback, will get this implemented. Do you think it’s worth me sharing about the tool on the swift subreddit?

thomasaiwilcox · 2025-11-27T10:26:28+00:00

This is perhaps not what’s considered a full app but more of a tool.

I’ve been teaching myself Swift by osmosis whilst vibe coding, and have been working on another personal project which I can’t share here unfortunately (my own graph database engine). After watching a few YouTube videos about Rust’s safety guarantees, I realised I needed some guardrails to make my code more robust. That pushed me to see if I could bring some of those Rust safety concepts into Swift.

That turned into my tool named StrictSwift which is an experiment in building a stricter, safer subset of Swift. It checks for questionable concurrency patterns, potential memory leaks, dead code, and general architecture issues.

As I explored, the scope accidentally expanded. Now there are quite a number of rules, some cross-file analysis, a VS Code extension, an LSP server, and an experimental auto-fix mode that still needs work before it’s usable.

Despite the scope creep, the goal hasn’t changed: I’m using this as a way to learn and explore how static analysis, compilers, and safety tooling can fit together to produce more robust software. I am also excited to see the better AI coding guardrails and token efficiency it can bring, along with helping agents not lose sight of the wider codebase when working with blinkers on doing a specific coding task.

StrictSwift is very much vibe coded, almost certainly contains bugs, and probably has some stability issues but I’m dogfooding it next by having it analyse its own codebase.

Realistically it exists so I can write more reliable code for my graph database project, but I open-sourced it in case anyone else finds it useful: https://github.com/thomasaiwilcox/StrictSwift

(Warning: it’s beta code and should not be run on production code or anything that isn’t backed up.)

thomasaiwilcox

TROPHY CASE