Daily-Notes

Authentication proves who you are (usually by means of some password or token). Authorization proves what you can do. An http 401 error is for the former and an http 403 is for the latter. Note the confusion of terms. http 401s are named Unauthorized while they really mean not authenticated.

The understanding, like the eye, whilst it makes us see and perceive all other things, takes no notice of itself; and it requires art and pains to set it at a distance, and make it its own object.

Locke

The great benefit of computer sequencers is that they remove the issue of skill, and replace it with the issue of judgement. With Cubase or Photoshop, anybody can actually do anything, and you can make stuff that sounds very much like stuff you’d hear on the radio, or looks very much like anything you see in magazines. So the question becomes not whether you can do it or not, because any drudge can do it if they’re prepared to sit in front of the computer for a few days, the question then is, ‘Of all the things you can now do, which do you choose to do?‘

I have been doing Math Academy lessons for a couple weeks now. I tested into Foundations I at about 80% complete so will be done with that course in a couple more weeks. I suppose a whole course could take me about 6 months. So I probably have a few years of work ahead if I go the route of Foundations II and III, then Methods of Proof, then Discrete Mathetmatics. (Or another path to ML or Probability and Statistics… img. The gamification, repetition on the student’s weak areas, and “dependency tree” for the order of learning are impressive. I’ll re-evalautae a few months later, but I could see this being a better way to learn than the classroom setting simply because it’s so targeted at the individual’s weaknesses (and still exercises the strengths as well). On the flip side, nothing can replace learning through dialogue - dialogue which is allowed to meander to and from related ideas. If I had to design a Math class today I’d think MA could be the basis of homework/exercises which some kind of face-to-face Q&A or seminar or traditional lessons at a certain frequency. Still, for me, it’s a perfect way to get some schooling in the gaps of my day.

TIL about csvkit which has a number of CLI tools for working with CSVs. The cool thing I’m after is csvjoin which merges two CSVs on a common column (like a sql join).

I am active in as true and high a sense in my unconscious operations, as in what are properly called my volitions. If this were not so, moral character could attach only to those acts which are performed after deliberation, which is not true. The real moral character of the man is determined, almost solely, by his spontaneous operations, the unconscious motions of his soul.

Brownson

Today I:

  • Fixed my led light on my microphone mute button (which caused me all kinds of confusion during meetings)
  • Added wluma to serve mainly as a reminder that my privacy shutter is open [edit] I removed wluma several days later because it wasn’t very good. Brightness levels jumped all over the place and app window switching slowed because it spiked in CPU usage for window switching.

Today I am trying out the Cookie Store API which is a relatively new addition to browsers. It’s quite easy to use and has some slick features like the ability to subscribe to changes on the cookie. Am presently having trouble with storing a cookie that has semi-colons so either have to encode or find a new delimiter for the thing I’m storing.

Today I’m thinking about a “coding standards” document and what should be included in it. Linters cover most rules except for casing… scratch that, eslint has a calcase rule. I like to case database tables and fields one way (snake_case), code a different way (often camelCase but depends on the language), and th there’s also things like url parameters other things that should follow a consistent pattern. Other topics (brainstorming here) to include are DRY (more and less), file size, logging patterns, commenting (or lack thereof), error handling, uri testing, code coverage standards. I’ll be thinking of more later. Some of these things can be enforced with Draconian linter policies, but I tend to like to put just the big things in linter rules (e.g. no unused variables) and leave at least a little creative freedom to the devs. It’s fun to be able to look at code and know who wrote it without looking at git history/blame to find out - since the mark/style of a human remains.

Recently I’ve wired up nvim-obsidian ‘daily notes’ to get posted here automatically. So, perhaps there’ll be more note-takings and musings here under the Notes (anything) and Techne (nerd stuf) sections.

Using niri as a standalone wayland wm on nixOS presents a few challenges (and benefits) since there is no full fledged desktop environment that it’s beholden to (you can more easily choose any tool rather than the one for your desktop env) or can take advantage of (there’s no obvious tool to choose). IOW it can be good because one is not ’tied into’ anything, but can be bad (esp. for the overly analytical types like myself) because it can take some time to choose everything from the ground up. e.g. much of what I’m using is terminal based rather than point and click. I’m using bluetuith for bluetooth, nmtui for wifi connecting, fuzzel + bash scripts for app launching, various tools for pipewire audio. Mostly everything works great, and for those with the DIY linux spirit, it’s worth the time.