HN user

nige123

39 karma

https://nigelhamilton.com

Posts30
Comments33
View on HN
raku-advent.blog 7mo ago

Raku Advent Calendar 2025

nige123
3pts0
raku-advent.blog 7mo ago

Day 1 – Dancer, Dasher and Dosh (LLM-powered shell commands)

nige123
2pts0
raku-advent.blog 11mo ago

Perl Is Dead. Long Live Perl and Raku (2020)

nige123
7pts2
raku-advent.blog 1y ago

Wat LLM coding tool do you want for Christmas?

nige123
2pts1
raku-advent.blog 1y ago

Day 2 – WAT LLM coding tool do you want for Christmas?

nige123
2pts0
raku-advent.blog 3y ago

Variable sigils don't cut it. Twigils for the WIN

nige123
3pts0
raku-advent.blog 3y ago

Less Variable Wattage = More Flow

nige123
1pts0
github.com 3y ago

Jmp

nige123
1pts1
nigelhamilton.com 3y ago

Raku's brand values? Let's ask the machines

nige123
3pts0
nigelhamilton.com 3y ago

Perl's New Mascot? The Machines Know

nige123
1pts1
raku-advent.blog 3y ago

Day 2: Less Variable Wattage = More Flow

nige123
2pts0
6guts.wordpress.com 4y ago

Raku's New Dispatch Mechanism Has Landed

nige123
2pts0
raku-advent.blog 5y ago

Perl is dead. Long live Perl and Raku

nige123
2pts0
www.youtube.com 5y ago

A Perl and Raku Programmer Went to the Bar

nige123
4pts0
www.youtube.com 5y ago

FOSDEM: Perl and Raku Branding

nige123
2pts0
raku-advent.blog 5y ago

Day 1: Why Raku is the ideal language for Advent of Code

nige123
2pts0
www.epicgames.com 5y ago

Monopoly Busting? Apple's 1984 vs. Fortnite

nige123
2pts0
web.jinfo.com 6y ago

Blazing User Search Trails

nige123
1pts0
rakuadventcalendar.wordpress.com 6y ago

Jmp into Raku (Perl 6) powered code diving

nige123
3pts0
rakuadventcalendar.wordpress.com 6y ago

Raku (aka Perl 6) powered jmp-ing to the coding coalface

nige123
3pts0
wordpress.com 7y ago

Day 1-: jmp-starting your workflow

nige123
1pts1
perl6advent.wordpress.com 7y ago

Day 10: jmp faster to the next thing in your work flow

nige123
2pts0
perl6advent.wordpress.com 7y ago

Day 10 – jmp starting your work flow

nige123
2pts0
perl6advent.wordpress.com 7y ago

Day 10 – jmp-starting your workflow

nige123
2pts0
perl6advent.wordpress.com 7y ago

Perl 6 – jmp 2 it

nige123
2pts0
nigelhamilton.com 8y ago

Perl Branding Proposal – free all the butterflies

nige123
1pts1
perl6advent.wordpress.com 8y ago

Perl 6 Powered Work Flow

nige123
2pts0
perl6advent.wordpress.com 8y ago

A changelog with a future for finding flow

nige123
1pts0
perl6advent.wordpress.com 8y ago

Day 18: A poor man’s Memex to help throttle cognitive load and facilitate flow

nige123
1pts0
perl6advent.wordpress.com 8y ago

Day 18: Helping your work flow: do, doing, done

nige123
2pts0

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?

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!

ChatGPT Search 2 years ago

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.

Jmp 3 years ago

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

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.

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.

Expressiveness + Extensibility + Stability

Sounds like excellent values for a programming language.

I'm interested to hear what the top three values for Perl 7 are?

Exciting times for Perl!

I had fun writing my Master's thesis on 'Flaming' back in 1995. There was a 6 month long flame war between the denizens of alt.tasteless and those quiet, kind, kitty lovers in rec.pets.cats.

And what about Kibology - where is Kibo now??! ;-)

In 2019 we've only scratched the surface of how tools can potentially augment our cognitive capabilities.

Simple word completion in the shell or in your $EDITOR saves some cognitive buffer. Completion in Gmail feels a bit too creepy at the moment. Outsourcing personal responses to a bot seems wrong. What comes next?

Imagine if you and your recipient(s) could toggle a setting "always accept Gmail completion" - in theory the Gmail "agents" could then proceed to have a conversation between themselves.

A way to avoid this problem is to use a combined copyright + trademark licence.

"smartcar" feels like a weak trademark and is likely not registrable. "Otonomo" is inherently more distinctive - making it a stronger mark.

To avoid this problem - "smartcar" needed a stronger trade mark in the first place. Secondly the API copyright licence needs to work in combination with the improved "smartcar" trademark.

The Artistic Licence 2.0 for Perl 6 is an example of a copyright licence that works in combination with a trade mark.

Copyright licences are incredibly flexible - it's possible to restrict server-side implementations for example. Depending on the business objectives it should be possible to strike the right balance - binding the API to your trademark via the copyright licence - could be a good move if your API is a market-maker.

Linux was named after Linus.

Linus admits that he named "git" after himself too. At least he had some self-awareness of his own "git"-ishness.

Trump, for example, is too far along the narcissistic spectrum to even feign humility.

The software industry is sadly plagued by empathy-free, narcissistic gits.

It's sad - Why?

Empathy is actually essential for creating good software (and good leadership too) - we write software for humans not computers.

Trump is sadly too far gone to show real empathy. Linus may be too ... but at least he's seeking help.

Peace Linus - I hope you find your true empathic self.

More empathy in the development of Linux would be truly great (and not in the Trump sense).

Google is not a search engine.

It's an association engine.

We know what Google is trying to do - associate the best solutions to search questions.

To game Google you need to help them achieve their objective - associate their search queries with your solutions.

Broadly there are three types of search desire:

1. navigational - the user wants to find a resource or place?

2. informational - the user wants to learn something?

3. transactional - the user wants to perform an action (pay a bill, book a flight, hotel, restaurant etc)

If a page satisfies a user's search desire - they won't search for it again.

This missing search trail is a valuable signal to Google. It provides some evidence that page A satisfies query B. The more these signals fire the stronger the association.

SEO 2018?

Ideally make pages that solve your users' search problems without them needing to go back to Google to search again.