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).

https://github.com/RSS-Bridge/rss-bridge is what I've been using for the same purpose.

It's a shame https://en.m.wikipedia.org/wiki/United_States_v._Paramount_P.... was never applied to streaming services.

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.

The use of "how the turntables" was likely intentional. See https://digitalcultures.net/slang/pop-culture/how-the-turnta... for reference.

Is it any wonder then that the Liberals dragged their heels on the 2015 campaign promise of electoral reform?

As part of the process, the parliamentary committee released a survey asking questions like

  * Independent candidates should be able to be elected to Parliament
  * The current electoral system adequately reflects voters' intentions
  * Seats should be allocated in proportion to the percentage of votes received by each political party
  * Voters should elect local candidates to represent them in Parliament
  * The current electoral system should be changed

When the committee concluded with https://www.ourcommons.ca/Content/Committee/421/ERRE/Reports..., recommending that Canada adopt proportional representation, the Liberal Party responds with their own survey, asking questions like

  * There should be parties in Parliament that represent the views of all Canadians, even if some are radical or extreme.
  * Governments should have to negotiate their policy decisions with other parties in Parliament, even if it is less clear who is accountable for the resulting policy.
  * It is better for several parties to have to govern together than for one party to make all the decisions in government, even if it takes longer for government to get things done.

Yeah...

"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.

Since 2001, it seems: https://github.com/python/cpython/blob/3.11/Lib/doctest.py#L...

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.

> if only just to have some sort of open-system for rating charities

While the following examples aren't exactly _open_ systems, some organizations address the niche you highlight. Examples: https://www.givewell.org/, https://animalcharityevaluators.org/

https://www.superrune.com/tutorials/loom_ega.php might be of interest.

Didn't we just have a conversation about how not to average things? https://news.ycombinator.com/item?id=29200103

The same principle could be applied to upvotes/downvotes too, yeah?

https://en.m.wikipedia.org/wiki/United_States_v._Paramount_P.... applied to streaming services would have provided that, no? It's unfortunate it's been terminated.

There are a number of approaches to this with increasing complexity:

- Sum of votes divided by total votes

- More advanced statistical algorithms that take into account confidence (as this article suggests)

- Recommendation engines that provides a rating based on your taste profile

But I'm pretty sure you could take this further depending on what data you're looking to feed in and what the end-users' expectations of the system are.

A key benefit you might not be getting that OpenTelemetry (and Fluentd for logs in the interim) provides is routing. The ability to trial multiple downstream storage solutions is useful!

https://docs.python.org/3/whatsnew/index.html, each subpage of which has summary highlights.

> I was tracking it on a separate issue

Do you mind linking to that issue? Thanks!

I suspect people know what they're getting out of that $4 cup of coffee. With a $1 app, it might end up being a waste of money.

Does the Apple Store have refunds? If a user could refund an app within 48 hours of purchase (no questions asked), might that increase sales? (An abrupt change in policy might negatively impact premium "one time use" apps though...)

Gibson also wrote on how our abilities to predict the future are superbly limited in his 2003 essay In The Visegrips Of Dr Satan: http://williamgibsonblog.blogspot.com/2003/01/?m=1#90248174

A quick image search for "farmed animal lifespans" (https://www.google.com/search?q=farmed+animal+lifespans&tbm=...) certainly points in that direction.

I got hooked on building tools to assist in collective decision making. A decade back I built pyvotecore and https://modernballots.com to help folks run elections with fancier systems (e.g. SchulzeSTV). Years later, I built https://boardgamemenu.com to help reduce choice paralysis with boardgame selection (consensus). A few after that was https://sortmatch.ca to assist in Glicko tournaments.

Most recently, I built https://deckofnames.com to help new parents decide on a name they'd both like. I built it for myself, but figured others might find it useful. So it's a bit rough around the edges, but does the job pretty well, I think.

Part of the fun of implementing it was hunting down name statistics from various regional governments to compile a list of "which names are popular in which regions in which years". I really wish that kind of thing were standardized around the world, but that's life.

> OSM simply has to exist, and the longer it exists, the better the data will become.

Probably, but not necessarily. The world changes with time and if OSM contributions languish, it falls out of date with the world and tangibly becomes a worse product. Certainly not inevitable, but a possibility worth noting.

Tofutti's cream cheese does it for me. Likewise can't quite recall the difference, but I enjoy it nonetheless.

> Any thoughts about [GPS accuracy]?

Unless I'm missing something, couldn't you just fetch the GPS location and truncate the precision to 1/2/3 decimal points? There are subtler ways of doing this that mitigate

A: Oscillation of a user on the border between X,Y and X,Y+1

B: Distortion of precision area near the poles

but I'm sure you get the gist.

Not to drift too far off topic, but you may be surprised to learn about biomass transfer efficiency. It takes a lot more plant mass to feed to animals than eating those plants directly. This "plants might feel pain too" gotcha doesn't really play out.

What's the pricing structure? Seeing no reference to it on your website makes me caught of adopting it.