adregan

I'm grateful for your framing of the issue from Brooks's perspective. I've been noodling on Conway's law in this changing world.

> organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations.

With all business functions consulting the central hub of AI to carry out their work designing systems where the users consult that same hub, what system is left except for the central hub?

In that case, what happens to all of Brooks's wonderful insights on how we might work together when we are no longer working together?

I think that’s why it stuck with me.

At some point, after watching this video[0], I was never able to watch a movie with Tim Curry and not think about Haskell.

0: https://youtu.be/LnX3B9oaKzw?t=3m6s

I think you'll find your workflow is still required. `git history split` is really only focused on turning a commit into 2 commits, so if you wanted multiple, you would need to run the command multiple times.

Add to that, it's patch functionality isn't as robust as `git add --patch`. For example, you cannot edit a hunk, so if you intended to tease out atomic changes, you won't be able to.

I'd love to, but I keep/cut my grass on the longer side and my dog was eating so much of the clippings (and then throwing it up) when I mulched that I chose to compost far away from where she could get it.

I have a small yard and I'm not optimizing for the fewest moves, I'm optimizing for both the longest continuous lines (because I think they look nicest) and the shortest distance to carry the clippings at the end.

I have a different definition of optimal to this game.

I can’t tell if this is sarcasm.

If not, I doubt some typesetter in the 19th century (or earlier) was so drunk with power when setting out the lead type to make the 3-em dash.

EDIT: Additionally, unicode primarily exists to encode the typographic symbols that exist—that is to say, it's a catalog of what already is. Take Ogham[1] for example.

1: https://en.wikipedia.org/wiki/Ogham_(Unicode_block)

It’s a famous “Yogi-ism”[0]

> On why he no longer went to Ruggeri's, a St. Louis restaurant: "Nobody goes there anymore. It's too crowded.”

0: https://en.wikipedia.org/wiki/Yogi_Berra

My issue with DDG AI result is that sometimes I would accidentally hit the "more" button to expand the result and it would begin a painfully slow crawl of text that pushed the results I was actually interested in further and further down the page. It was usually preferable to refresh rather than wait. So this is a welcome change.

A decade ago I was working with an intern who wasn’t allowed access to push to any branch. As I wanted him to get experience with the development cycle, I set up a bare repo in a shared Dropbox folder and had him push code there.

Aside from that unique use case, I might consider this for storing code on a network attached drive (archival).

I apologize for taking the conversation off course as it wasn’t my intention, and I also thank you for providing examples of Dijkstra‘a writing. In asking for a recommendation, I was admitting a great blind spot, so you needn’t be breathless from the ignorance.

The only thing that I feel bears repeating is that I also compared Dijkstra to Ken Iverson—a mathematician who worked in the same time period and also taught in North America—who didn’t (as far as I have seen) muddy the waters of his writings/teachings with superfluous insults.

Note that Roger Hui here foregrounds the fact that

> Ken Iverson invented his notation as a means of communications among people

(Emphasis mine) and I think that it is important that this fact of APL is conflated against one’s desire to prove a program. A fact which Hui says has little to do with the correctness of the result.

One aspect of the original which I believe you are eliding over, but which I focused on and tacitly referenced (wouldn’t be an APL discussion without a little tacit programming reference), is that in conveying one’s ideas or proofs, one can distract from their point by introducing unrelated jabs or insults. I believe this fact is present in Roger Hui’s writing.

I suppose the thing that stuck in my craw is what I perceived as a personal slight:

> Your writings made me wonder in which discipline you got your doctor’s degree.

It’s ambiguous, so I can give the benefit of the doubt. However, if intended as an insult, I believe that goes beyond speaking frankly about one’s feelings about a programming language in a manner consistent with one’s culture.

APL is the only language I've ever dreamt about writing (as in: I could see the characters); I'd dreamt about programming in the past, but those dreams were usually what I would categorized as a nightmare—desperately trying to fix a bug that I couldn't figure out.

Due to my affinity for the language, and my wish to have worked in its heyday (would love to have an APL gig someday), I have been exposed to various writings and recordings of Ken Iverson. I've also been exposed to a few of Dijkstra's thoughts on APL.

I have to say that Iverson generally comes across as a very generous and curious individual while Dijkstra seems to have been a miserable ass. Maybe, given the lens, I've not given Dijkstra a proper chance to demonstrate a more positive attitude, so I'm open to any suggestions of writings where he doesn't seem like such a grump.

Where are these jobs that onboard non-APLers? Asking for a friend ;)

Excited for the new release!

Though looks like `git history split` won't yet replace my typical workflow:

    $ git rebase -i // with e on commit in question
    $ git reset HEAD~
    $ git add -p

As I can't edit the hunk.

`git history reword` will be handy once I wire up a script to pipe the log of recent commits through fzf for interactive selection (not sure if it's just me, but I prefer interactive selection over any other form of reference to a git hash).

And I bet I'll get some use out of `git rebase --trailer`.

I’m not really understanding the notion that these people are so sincere. Perhaps we have different definitions of sincerity.

To my eye, the entire fascination of unsafely injecting peptides in a desire to change your being is largely the opposite of sincerity.

I typically prefix my commit messages with the ticket number to make it easier to spot the commits to drop.

You head to the farthest branch in the chain, fetch the latest main, and run `git rebase --update-refs main` (I prefer interactive mode myself) and then force push all of the branches from start to the end.

1: https://git-scm.com/docs/git-rebase#Documentation/git-rebase...

Is that by convention or is there a good reason that it’s so CPU bound? I don’t have experience with CAD, so I’m not sure if it’s due to entrenched solutions or something else.

Have you asked them to compile it to BEAM bytecode directly?

In the section on security:

> One large enterprise employee commented that they were deliberately slow with AI tech, keeping about a quarter behind the leading edge. “We’re not in the business of avoiding all risks, but we do need to manage them”.

I’m unclear how this pattern helps with security vis-à-vis LLMs. It makes sense when talking about software versions, in hoping that any critical bugs are patched, but prompt injection springs eternal.

Last 2 positions I’ve had haven’t had 401k matching and the health insurance costs are eye watering. I might consider an improvement in both to be worth a fair bit.

How are folks navigating the sheer rate of inflation in the last 5 years?

In job listings, I’ve seen salaries for Senior or Staff remain about the same as they were (thought usually edging a little lower), but adjusted for inflation, they are way lower.

If I were to insist on my 2021 salary with inflation adjustment, I’m often blowing past the listed range by anything from 15k to 30k.

With the market the way it is, how are y’all handling that?

For pines, not great. Timber farming was so heavily encourage for so many years that there is a glut and prices have stayed about the same in real dollars for decades.

Solar panel leases are so long (50 years on top of the decade to interconnect), so they come with additional negatives as you are often signing up the next generation for a relationship that they had no say in.

> This question may be naive, but why is the agricultural industry so subsidized?

I believe this is the same tune we hear in other industries: it’s the effect of the consolidation of companies which provide the inputs (seed and chemicals) leading to a lack of competition and the increase in prices on a captive consumer base.

When farmers feel the crunch due to macro forces in the market (and tariffs), the government effectively acts as a backstop for the conglomerates providing the inputs. Think of the farmer’s hand as an open palm, the subsidy flows through it directly to the company to which they are indebted (“the money is in the ground” as I used to hear during a brief time in crop insurance).

While these subsidies may have initially began with the quaint notion of protecting against scarcity (as many sibling replies seem to believe), the reality is that farmers are being squeezed just as the rest of us. Profits are way up while competition is way down.

When I was a young urbanite, I might not have believed you if you told me that one day I would gain great pleasure in discovering large blooms of Dog vomit slime mold in the garden, but here we are.

Slime molds are really amazing; large patches spring up overnight and they are so vibrant in color.

I suppose I’m pointing it out to highlight the trade offs with any of these solutions.

What is unsaid is that we need to sequester CO2 for hundreds of years—often far beyond the lifespan of the trees. Trees are short term storage, and sometimes the storage is a lot shorter than popular imagination purports.

One little appreciated fact is that trees also respirate CO2 when they are cracking their stored sugars produced via photosynthesis. So they don’t sequester all of the CO2 that they consume.

The main commercial use is enhanced oil recovery—shooting it into old wells to extract more oil (super ironic if captured from the air).

One application I think is neat is that it’s a pretty robust refrigerant in a heat pump application.

The gp's comment wasn't made regarding the look of the operator in its ascii representation `|>` but about the vertical misalignment.

Typically you align a pipeline like so:

     df
     |> rbind(other_df)
     |> select(...)

But these topics are largely left to code formatters these days.