bradbeattie

I spend a lot of time side by side with other devs watching them code and providing guidance. A trend I'm starting to sense is that developer velocity is just as much hindered by unfamiliarity with their tools as much as it is wrestling with the core problem they really want to solve.

When to use your mouse, when to use your keyboard, how to locate a file you want to look at in your terminal or IDE, how to find commands you executed last week, etc. It's all lacking. When devs struggle with these fundamentals, I suspect the desire to bypass all this with a singular "just ask the LLM" interface increases.

So when orgs focus on a "devs should use LLMs more to accelerate", I really wish the focus was more "find ways to accelerate", which could more reliably mean "get more proficient with your tools".

I think there's a lot of good that can be gained from formalizing conventions with templating engines (another tool worth learning), rather than relying on stochastic template generation.

The softer approach to this I've implemented in the past is to ingest and link up org data (user accounts, groups, projects, etc) into one central DB and then provide an audit notifications or dashboards to authorized users. Examples:

    - Slack user detected with full access that isn't associated with a staff-grouped LDAP account
    - Group A in System X doesn't match the members of Group A in System Y)
    - Service Z provisioned, but their associated customer account is deactivated

These kinds of violations _can_ be automatically synchronized in a variety of ways, but I've seen that result in politically embarrassing outcomes (e.g. Sensitive user X is fired, their Slack account is automatically deactivated, people notice before some kind of staff meeting can be held to talk about what's going on).

I run into this with melee attacks in a lot of first person games (Cyberpunk, Deep Rock Galactic). Often the camera is pinned to the character's head, the head which is animated during a melee attack. Both games above actually have screen shake accessibility sliders which critically do nothing to prevent this source of motion sickness.

I suspect it has to do with "camera movement I didn't control". I recall some research done by Valve during the VR development days that resulted in the "teleport" movement fix.

To make it more clear, perhaps replace "$9/month" with "$9/month/user"? Seems like an easy fix.

"Interface evolves toward transparency. The one you have to devote the least conscious effort to, survives, prospers. This is true for interface hardware as well, so that the cranial jacks and brain inserts and bolts in the neck, all the transitional sci-fi hardware of the sci-fi cyborg, already looks slightly quaint. The real cyborg, the global organism, is so splendidly invasive that these things already seem medieval." -Gibson

Sorting by random is coming in Jellyfin 10.9, if that's of any help.

Any plans on dealing with topsoil vs bedrock? Seeing water only on the surface above what looks like an impermeable layer looks odd to me, unless I'm misreading the video.