ac50hz

s/oven/cms/g

Looks like it’s time for me to revisit my 1st edition of a New Kind of Science, for a refresher.

I enjoy these carefully worded posts from Anders Murphy, illustrative and informative, not opinionated and preachy. Very useful, it’s great to see the process, and ofc bookmarkeable material for sharing with others.

Sadly, Richard died in January this year. This book is available to download from one of his academic pages:

https://www.eis.mdx.ac.uk/staffpages/r_bornat/#compilerbook

https://www.eis.mdx.ac.uk/staffpages/r_bornat/books/compilin...

https://en.wikipedia.org/wiki/Richard_Bornat

Share an attribute, not an identifier, https://yivi.app/en/for_developers/

I’m looking forward to it.

Exactly. Yivi isn’t new having been renamed from IRMA (https://privacybydesign.foundation/en/). Nevertheless, adoption outside the Netherlands remains almost non-existent.

Except for the additional download requirement for a user, the friction is pretty low once it’s setup and you have created some attributes.

The project would benefit from a rebranding review, standardization, an enterprise-capable infrastructure to promote and support alternative service providers, and a review of clients. The current Yivi mobile app hasn’t changed much over the years and when I last used it I still needed a PIN instead Face ID.

https://github.com/PeterBengtson/Ooloi-docs

Anders’ blog is a joy to read.

The absurdity of the use of beauty in the descriptions of designs, code and equations is as absurd as telling me, who is certainly not a beauty, that there are clear personal defects and deficits because of that property, or lack of that property.

This can join the absurdity of the websites that proclaim _Made with love_.

Marketing nonsense that has nothing to do with functionality, utility, usability may certainly be useful for marketing, promotion, and leveraging nostalgic pangs, but let’s remember that these are usually vacant, sometimes deceptive and often inaccurate.

The deception of beauty and its insidious insertion into many different fields does little to advance those fields and detracts from accuracy, improvement and inevitability reality.

And then there are the similarities, both video and song, between Can’t Get You Out Of My Head and Doll on a Music Box/Truly Scrumptious from the UK musical/movie Chitty Chitty Bang Bang… There was a mashup floating around somewhere, years ago. Probably lost.

Great analogy.

Of course, it’s possible that the intent or otherwise wasn’t the objective. They’ve succeeded in bringing together several associations which allude to a sophisticated and peaceful future for all of us, in spite of the possibility of any minor legal hiccups. Whether the man with something of the dark about him was responsible, involved or unaware, the company continues to lay out its strategy, concerns and targets in plain sight. I’ll try to remain outside of this chaotic arena.

This could be a useful alternative:

https://github.com/quentinlesceller/macmediakeyforwarder

It charged startups between a few thousand dollars and $18,000 to $20,000 for its training programs

This was one of several red flags for me…

I simplify my prioritization strategies to use only 2 priorities: High (do it now) and Low (do it later). There should only be 1 high-priority item at any time, and when it's completed, the (next) low-priority item becomes the single high-priority item.

Maintaining multi-level priorities requires more decisions to evaluate relative priorities of different tasks and possible priority re-evaluation when new tasks arrive. Throw some colleagues, friends or others into the mix and agreements on the decisions become more distant.

Within the low-priority list these are sorted on the date and time required. If you then choose to ignore the priorities or sorting, the deviation will take you down the priority re-evaluation rabbit hole again. It's then your choice to follow the process, or not. Avoiding adding complexity to task scheduling and processes ensures I have focus.

Of course, this will not be for everyone. Good luck with that LLM!

Whilst i agree with all of this, I like paper, and to set time aside (with coffee) to review batches of notes.

I’ve been heading in this direction, and Quarto continues to be the end point, on the road from pandoc.

Record keeping, for better or worse, is essential.

Memories fade. Ink fades but rarely corrupts.

100% yes.

And a new page per day (paper is cheap), with the date always on top outer corner of the page. Never share a page across dates.

Thoughts, however bizarre, around the topics are very useful. Elaborate where possible. Names, keywords and classifications will be useful later, so do consider the future as you write.

My Yubikeys are great and have been since I started using them (2011), adopting newer products if necessary as they are released.

Passkeys are a confusing mess for most users, and the limited storage on Yubikeys doesn't help. However, 1Password's passkey support manages to reasonably successfully hide the confusions that always exist when explaining passkeys to anyone.

For now, I'm happy with my Yubikeys+1Password for all the platforms I use.

;-) Yeah, I do get that, but when there's no promotion of personal responsibility, chaos reigns. When everyone does wat they want to do, or what they think is necessary, nothing is completed. This is from experience with different companies, organizations, teams, projects, people. Of course, nothing is perfect, but without some structure, there is only communication mayhem ;-(

Promote a culture of responsibility, and attach responsibility to every person, every decision and every action.

That’s my experience too.

The title would better represent this approach by appending “…at any cost.”

This isn’t a judgement, but clarity of intent can help everyone make decisions relevant to the effect that such an approach would have on them. Elaborating on risk is usually conveniently omitted, because it gets in the way of reality.

The large, distracting menus are quite exciting.

+1

This is a pleasant take. I may borrow the sentiment expressed here to help me describe some similar distinctions.

Let's not forget the OS that the Atari Transputer Workstation used, HeliOS...

https://en.wikipedia.org/wiki/Atari_Transputer_Workstation https://en.wikipedia.org/wiki/HeliOS https://github.com/axelmuhr/Helios-NG

In my experience, if the management, processes and teams aren’t trusted then it can turn into unwelcome micromanagement.

Engaging with people, who have different motivations and reasons for being in a job, and stripping away often unhelpful implied titles of rockstar programmer to QA robot, can help everyone to see the big picture and in turn to see how their contributions, their cogs, fit into that picture.

Production-line programming can be left to new automated systems, whilst we can embrace and capitalize on people exercising their intellect for productive, feedback-oriented work.

+10

That’s common sense, otherwise we’re just not taking real-world problems into consideration.