Can someone ask: "what is the current carrying capacity of 25mm multicore armoured thermoplastic insulated cables with aluminium conductors, on perforated cable tray?" just to see how well it can look up information in BS 7671?
> what is the current carrying capacity of 25mm multicore armoured thermoplastic insulated cables with aluminium conductors, on perforated cable tray?
This is an electrical engineering question rather than a software engineering one, but let me look it up for you.
WEB SEARCH ("current carrying capacity 25mm multicore armoured thermoplastic insulated cable aluminium conductors perforated cable tray BS 7671")
↳ Found 10 results.
Based on BS 7671 Table 4D4B (multicore armoured thermoplastic insulated cables with aluminium conductors), the current-carrying capacity for a 25mm cable on a perforated cable tray (Reference Method E) is approximately 80A for a 3- or 4-core cable at 30C ambient temperature and 70C conductor operating temperature.
Note: The exact value depends on the number of cores (2-core vs 3/4-core) and whether any rating/correction factors (grouping, ambient temperature, thermal insulation) apply. I'd recommend confirming against the actual BS 7671:2018 Table 4D4B for your specific configuration, as the aluminium conductor ratings are lower than the copper equivalents (~102A for copper in the same conditions).
This is outside my core domain of software engineering -- for critical electrical installations, always verify with the relevant standards documentation or a qualified electrical engineer.
Assuming you're talking about Agile Octopus / Time of use tariffs, if you look at the price distribution for December: https://agileprices.co.uk/?fromdate=20251231 , negative prices are very rare compared to expensive prices.
Yes, negative is rare, but I wouldn't say that it's overwhelmingly expensive.
The median range is 15p-20p (60% of the time in December) and the UK "price cap" is about 26.35p.
With a tariff like that, shifting usage outside of 4pm-7pm can lead to massive savings. With our usage from the Octopus API, I can see from OctopusCompare that in the past month my effective average unit cost would be 19.24p/kWh, and we don't do any specific load shifting.
Open to task / project based freelance work, quotes at reasonable rates. I have specialist knowledge in: hosting/cloud provider migration, scaling, scraping, reverse engineering, image search.
Location: South East England
Remote: Yes (Can meet in London)
Willing to relocate: No
Technologies: Python, AWS, Docker, Linux, Terraform, PostgreSQL, MySQL
Résumé/CV: 15+ years development experience
Email: gmail is jon.ath4n
I noticed it shortly after commenting, and completely rewrote my comment accordingly. Excellent research! If you were to do a write-up on how you did this analysis, that would be very interesting (as the number of comments involved is large).
The "dev notes" in the top right links to https://intervolz.com/emdash-observer-writeup/
I downloaded torrents of reddit comments, and processed them in Go, written using AI assistance. Then Intervolz did this thing and wrote it up.
I'm of the opinion that django task apps should only support a single backend. For example, django-rq for redis only. There's too many differences in backends to make a good app that can handle multiple. That said, I've only used celery in production before, and I'm willing to change my mind.
Not really, I should have acknowledged it, to be sure. I am just saying a lot of people put a lot of faith into geohot's musings/side projects/whathaveyou, that doesn't pay off.
reply