When I was young, My GP was a kind and caring man. I remember him asking my mum how my siblings were, recalling their previous visits.
As a grown up, When I manage to get an appointment they are STILL remarkably effective,-- albeit clearly over-worked and trying to make up time.
More recently it has been impossible for me to make appointments for my parents due to long term under-funding, and covid.
>Well, health (or 'disease control') is a business unfortunately.
This type of thinking in UK social care is exactly what has caused the decline of public health. Politicians and business management have ruined the caring aspect of the NHS through constant budget cuts and medical policies. -- And then they have the gall to claim the NHS isn't fit for purpose.
The whole situation makes me rather distressed. Luckily I am 'well-off' now and look after my parents as best as I can.
I'm not "offended" as such, I just think casual sexism should always be called out (although in fairness, it's an excusable mistake for a non-native speaker, albeit one that still bears pointing out). And yeah, I used sarcasm to do it, because it's more fun; sue me.
I don't think "exculpatory" means what you think it means.
Sad to have just learned from that link that Privacy Guard is gone. That has indeed been a key Cyanogen/LineageOS feature for me for years (my phone is still on 16). I can't say I understand the decision to remove it.
And what about those `reselect` wires?
And that `connect` and `mapStoP / mapDtoP` stuff?
Doesn't that "bother" you? Or you just mentally "pack" it into the verbosity basket and ignore it?
> `reselect` is an option that you don't have to use.
Of course.
It just happens that for my real life needs I've needed state that was derived from redux state: filtering, selections, pagination, normalizing / denormalizing state, relations between entities (classic library data model problem) etc.
So I kinda can't "imagine" any "serious" work with redux without helpers like reselect etc.
> Easy to read/write once you understand the pattern.
Sure, there is nothing "complex" about any of that.
And I am genuinely asking how people deal with that.
It is just way too verbose for me. So I am wondering, how other people approach it.
Close their eyes and plow through? Don't really care?
Why? surely having 47 promises and some on the same line is the authors fault?
Promise.prototype.then()'s callback function does not need to be written inline. At some point the author should have realised it hass become difficult to grok quickly and refactored them out using appropriate function names.
My current project is run in a similar fashion; and it shows... code quality is terrible, technologies are stale and riddled with performance work-arounds, bugs are fixed with the fastest possible implementation and handed off to the testing team then consequently bounced back and forth with trivial disputes.
The worst thing is the manager/ product owner/ tyrannical architect is a actually a nice bloke. but he is absolutely terrible at insulating devs from his stressors, which has a massive knock-on effect on his team. Recently he took leave for around 4 weeks and it was like night and day! we self organised: minimised new features and maximise time spent addressing technical debt built-up over 2 years. I was enjoying work again, and it had a almost skunkwork-like feel to it.
> Do you remember the time when you just copied your file over to the server, and magically everything was deployed? I do. It was a good time. Yes, I am old.
Yep.
That in sense is webpack's job: It allows you to boil down a huge list of interconnected complex dependencies into a neat, portable, highly deployable package.
