goodlinks

Two totally seperate UIs that can run at the same time, a desktop one and a phone one.. it worked shockingly well imho.

Maybe an additional case where you can use the tablet as an extra screen, but honestly that could probably manifest as an app in the mobile UI.

Imho the long term answer to these problems is trust networks and decentralised moderation. Howbwe get there.. dunno

Patrick boyle video thats got some fun snippets from this interview

E.g. scott manley https://m.youtube.com/watch?v=Ysx4t7ICO58&pp=ygUMc2NvdHQgbWF... @7.40 ish

And use the software not an appliance to manage it.

Its not just the slick ui, its the devices themselves, and how well it all works. I got fed up of wifi at home not being as good as at work. And unifi are cheap compared to some corporate grade stuff

:(

1. Quick and easy: Install pihole and add every reasonable list you can find of tracker urls to block. And just watch the live log.

2. Takes a bit more time: install opnsense or pfsense. Block dns out of your network (but allow pihole) and watch the live log of blocked dns requests. Assuming everythong has been told to use pihole

3 (bonus round). A bit more time again: create vlans or similar put the devices that you have checked every do not call home option on and block their internet access. And watch the live logs of blocked traffic

Its quite a depressing process and not sure its worth maintaing as a live setup, but its certainly an eye opener.

Each one of these steps blocks an order of magnitude less stuff, but is interesting whats in each bucket. Pihole gets hits at an astounding rate

I get that anything can be insecure and its a constant battle as this article suggests, but i thought it was quite secure and stable generally (say on a par with .net or any other tool you may use to make a web app at least?)

try dumber things, sounds stupid but you dont need rules and structure, just data :)

denormalise a more often to break down the problem, the data and problem are your goal not structure (as much as db).

Yes period per tab type of thing is quite common, as at some point you want to close the period and never change it.

Lean into the non-standardisation to handle the real world. E.g for most of your budget its one line per item per month but this one are flexes with headcount so that has its own page, and tax is balnced in month x so ill just over type all the formulae there when the real numbers come in.

Also if the model is complex try naming fields and showing the formula in a cell next to it to remind you how its calculated (if not ready using it check out "format as table" to do this for tabular data)

And yes pivot the crap out of everything.

There is also "add to model" which gives you powerbi type modelling in excel which can also be handy and fast.

Not extensive list, and for lots of things db is better when you know how to use it.. but those are some of the "i get it" scenarios for me

Totally standardised, coordinated, and decentralised. But fragmented (structuraly) or incoherent.

But agree would be a million times worse with a single electronic system

It would take a 1 year project and 5 devs to replace what one finance person created in a day.

Then when it didnt work complain the SME got the requirements wrong.

Im being silly but as a dev i hate the hate for excel, though i know from years of experience that its also a nightmare.

I would expect one ballot paper per vote (based on rare occasion of doing two at once) to ensure the count is simple and accurate.

They make the ballots different colours to ensure you put them in the correct boxes iirc

I.e. an indicator not really following the spirit of the regulation, only the letter?