A.I. companies repeat the claim that “this is the worst A.I. will ever be” and
that’s simply not true. As Carl notes in the video, with the release of
ChatGPT-5, it’s clear that it’s not an across the board improvement over
ChatGPT-4.5.
Hardware tends to improve over time: gets faster, does more in parallel.
But LLMs are software, and software doesn’t have that track record.
I’m trying to work outside my home office more, but all my email is hosted on
my home server. While disconnecting is nice, not having access when I need it
has sucked.
After installing on my laptop (MacOS) and my desktop (Ubuntu) I updated
.ssh/config with my desktop’s IPv6 address and was able to SSH via IPv6 over
my local network. Perfect!
Step two: install on a server with a public IP. One more service running on
my Digital Ocean instance.
I’m not interested, at the moment, with joining the full yggdrasil network, so
I configured my public instance to only allow peering from my laptop and
desktop’s public keys:
On the public server, I listen via TLS rather than plain TCP. It’s slightly
slower, but also slightly more secure. Since I’m not moving a lot of traffic
over the connection, the extra security is worth it to me:
Listen: [
tls://PUBLIC-IP-ADDRESS:56603
]
I couldn’t find a recommended port to listen on, so I picked a random number. 🤣
(The only “gotcha” was remembering to open the firewall for
yggdrasil.)
Ramces Red’s article about
yggdrasil has more
information about installing and configuring a basic VPN.
I’m far from the first person to decry how “business speak” destroys our
ability to communicate. However, yesterday I read
a blog post
where “business speak” rendered–genuinely insightful–information less
readable:
Even if a project fails before any go-to-market attempt, you can still get
learnings out of the experience: You might have picked up some new
technology or at least understood somewhat better the inner workings of the
organization you work for.
What will be important is to make some effort to capture these learnings
lest this value is lost.
(Emphasis added.)
Learnings?
Do people talk like this in real life?
Learnings might be old, but its
above usage is decidedly modern and “buzzwordy”.
Why repurpose a word that conveys less information when we have existing
strong nouns and verbs?
How about:
Even if a project fails before any go-to-market attempt, you can still
learn from the experience: You might have picked up some new technology or
at least understood somewhat better the inner workings of the organization
you work for.
What will be important is to make some effort to capture this knowledge
lest this value is lost.
I won’t nitpick the rest of the sentences: those two changes already improve
clarity.
Fred Waitzkin was smitten with chess during the historic Fischer-Spassky
championship in 1972. When Fisher disappeared from public view, Waitzkin’s
interest waned—until his own son Josh emerged as a chess prodigy.
In the past month, I decided to get back into chess, so
when I stumbled across “Searching for Bobby
Fischer” browsing my library’s collection, I had to check it out.
I had heard the title as a kid, but that was the extent of my knowledge.
The story’s core is Josh and his chess training and competitions.
I saw reflections of my childhood: my passion was computers. I spent
hours pouring over obscure manuals and typing programs in from magazines.
This was at a time long before computers or programmers were “cool”.
Controlling the blinking cursor on our TV captivated my imagination.
Computers also fascinated my father. It was our shared interest
(like chess for Fred and Josh.) And like Josh, I soon outpaced my dad.
But that’s where the similarity ends. There were no computing competitions.
There were no computing clubs.
No public computer centres
to practice at.
Mine was a private passion that I pursued for my own pleasure.
I think that difference meant Dad and I could continue our interest for
decades without outside forces interfering. I’m glad that Josh and Fred
appear to have a healthy relationship. Josh did and saw amazing
things, but as a parent, I’m not sure the years of stress and
tension were worth the lost childhood possibilities.
Throwing around the word “prodigy” is a curse. It sets kids up for failure.
Let them find their passion, encourage it as best you can, but don’t place
your expectations upon them.
Check out this book for the cold war chess politics, the
father-son dynamics, and the world of competitive children’s chess.
For years, I used Plug to manage my
vim plugins, but after seeing TJ DeVries
experiment with lazy.nvim, I decided to
go all in!
By far, the biggest challenge was learning Lua 5.1. All the scripting
languages I’ve used in the past (Ruby,
Perl, Python) emphasize a
“batteries included” approach. Lua, in contrast, felt like I had to assemble
everything from tiny parts.
Once I got past the Lua hurdle, the rest of the conversion was
straightforward. Most of the time I could swap out Vimscript with
neovim Lua API methods via a regexp.
I’m pleased with the results. Startup time is faster, there are fewer weird
bugs, and I understand all the configurations.
What should we do, or leave undone, in a day or a lifetime? How much
messiness should we accept? What balance of the new and familiar is the most
fulfilling? These may seem like uniquely human quandaries, but they are not.
Computers, like us, confront limited space and time, so computer scientists
have been grappling with similar problems for decades. And the solutions
they’ve found have much to teach us.
Fascinating book on how the problems of computer science apply to “real life.”
I know about time/space trade-off with computers, but never considered how
this can also apply to life. Or how some problems are
wicked problems.
Whether you’re a computer science expert or not, the ideas presented will
change how you view potential decisions.
With a new year, it’s time for a new look! Over time, I found the old design
too busy. I didn’t have a good idea for a new theme until I happened across
Thomas A Caswell’s site.
Drawn in by the clean design (inspired by
Blue Penguin), I created a
new Hugo theme!
I had to make some changes to preserve existing links from the old theme and
to maintain the banner images on a smattering of posts.
No Javascript and a lot less markup and CSS.
And if I ever want to switch back, it’s a config.yaml away!
I’ve listened to Mike and Grey talk about
their yearly themes since 2017, but this
year I’ve finally felt motivated enough to commit to a theme.
If you don’t have the time to listen to dozens of hours of podcast episodes,
Grey has a great video explaining “yearly themes”:
2020 was a rough year for more than just the
pandemic. My parents
were diagnosed with cancer. I felt like my life stopped as my attention
focused on their care. Mom recovered: dad didn’t.
With my father gone, I picked up the pieces for my mom and helped with
all her issues. I deprioritized myself and began to languish. Days spent
working as nights devolved into mindless
Youtube videos, endless refreshing of my RSS
feeds, and bite-sized articles saved to Instapaper.
I created nothing.
After almost three years of this same grind, I can’t keep going on the same
path. I started replacing Youtube with books and
read almost 20 books since May.
While reading is better than watching, it’s not the same as making.
Therefore, 2023 is the year of creation!
Using Scriptable, I created a yellow sticky note in my phone’s today
view
to remind me of the year’s theme.
My years’ first act of creation: writing today’s post!
I was looking at my old development projects recently when I noticed that all of them predate
2005. In 2005, I started work at ePublishing
as a Perl developer. In the past 17 years I’ve been:
In all that time, I’ve written hundreds of thousands of lines of code (maybe more
than a million), but it’s locked away.
It’s a bit depressing that almost two-decades of creativity is
forever hidden from view. It’s the curse of corporate development: we can
write blogs, give talks, and prepare papers, but we can’t show the code
itself. All anyone sees are shadows on the wall.
More companies should release their source code. Most
of what we write is not the company’s crown
jewels.
Let people see how you solved that weird 3rd-party integration! Or how you
monitor some obscure open-source service.
Every company is standing on a mountain of
open-source code. Give
back and let
your developers have the opportunity to show off!