nige123

The user data (anonymised) and analytics also needs to be shared.

Raku

Too much cognitive load is a flow stopper.

Finding flow while coding is a juggling act to keep things in the Goldilocks zone: not too hard, not too easy.

This is tricky on an individual level and even trickier for a team / project.

Coding is communicating how to solve a problem to yourself, your team, stakeholders and lastly the computer.

The Empathic Programmer?

Perl's maxim - there's more than one way to do it (TMTOWTDI) can make Perl easy to write but harder to read.

Thankfully LLMs can de-obfuscate even the gnarliest Perl with command line utilities like wat (https://raku-advent.blog/2024/12/02/day-2-wat-llm-coding-too...)

There was always content in users’ click paths / search trails.

Google has mined that for profit from the beginning. Cutts and Co turned a blind eye here.

It was ALL OK though - because Google’s mission was DONT BE EVIL!

In 2008 Google was besieged by SEO consultants spamming their index.

Mining the collective intelligence of the hooman’s search trails was their algorithmic escape clause.

Their escape clause in 2025?

Mine for MORE!

Suggestions for putting LLM's to work on the command-line.

OOF

Smell that!? A large part of Google's search business is on fire right now!

There are three types of search: informational, transactional and navigational.

LLM's are competing hard and fast for informational search. Once upon a time we offered 2.5 keywords to the Google Gods only to be ultimately passed to stackoverflow.

That game is up. Google is losing it faster than you can say, "anti-competitive practices in the search engine industry."

Transactional and navigational search remain.

Sigils are just part of the picture. For Raku "twigils" (secondary sigils) are important too:

https://raku-advent.blog/2022/12/02/day-2-less-variable-watt...

I use this everyday. A terminal program to jump to the next thing in your workflow.

do you still use emacs?

GNAP is coming soon: https://oauth.net/gnap/

This is already a hot legal mess.

The World Intellectual Property Organisation (WIPO) should come up with Berne convention 3.0 that provides:

- increased protection for human authorship

- longer copyright terms for hoomans

- shorter copyright terms for bots (5 years)

- moral rights preventing 'globbing' by generative AIs

- royalty system for original authors

- derived computer-generated works pay

I'd like to see a blockchain ledger-esque system where human authors can claim authorship and they receive nano-royalties every time works are derived from it. The generative AI's can 'glob' it but they will need to pay their dues.

Importantly GAI's can't register their stuff in the hooman copyright chain.

"Perl 7" eq "Perl Star"; "Perl 7" =~ m/Perl */;

Ask Jeeves missed out on a massive opportunity in search. Where, what, how, why, when are fantastic contextualisers for search queries.

They should have stuck to their core USP - a question answering service - Google might have had a bit more competition over the last decade.

Google’s going to start losing its grip here. Thankfully there’s all the anti trust, anti competitive legal actions .

But the real threat to Google is the AI powered content farms that are going to spam their index. The arms race is on between AI powered spam creation and spam detection.

Larry Wall also highlighted the importance of: diligence, patience and humility.

https://www.oreilly.com/openbook/opensources/book/larry.html

Love nano. Many of the keybindings work in bash too.

Check out:

https://www.nano-editor.org/dist/latest/cheatsheet.html

Sigils can induce fear in some programmers. The double-edged sword of Perl and Raku's expressivity is something that the community is addressing:

https://raku-advent.blog/2020/12/02/day-1-perl-is-dead-long-...