2,196 karma · joined February 9, 2013
It doesn't reliably give you 10 slices, even if you ask it to number them. None of the frontier models seem to be able to get this right
Each letter is a json that defines the bezier curves according to a schema.
They were created by starting by drawing the letters freehand, yielding essentially a dot to dot, and then (2) using an approximation/smoothing algorithm to convert that into beziers. Finally,I went through touching up/fixing each letter by hand, using a purpose built editor.
So I would say overall it's more time consuming than challenging.
That stills leaves the problem of joining letters together. For that I heavily lent on AI to propose an algorithm, although it required a lot of back and forth to get something even semi decent. At the moment it's probably 'good enough' but there's still lots of room for improvement.
On the countries quiz, you should be able to move and zoom on the bloge using click and drag (or pinch and drag on mobile). Letter constellations uses shaders. Both of those are only tested on Chrome, so that might be the issue.
Example letter: https://github.com/RobinL/letterpaths/blob/main/packages/let...
JSONSchema
https://github.com/RobinL/letterpaths/blob/main/packages/let...
Editor
And examples of games is can power:
https://rupertlinacre.com/maths_vs_monsters/
The idea is that it provides all the geometry to enables games like these to be built: (These are just rough demos)
https://www.robinlinacre.com/letterpaths/writing_app/snake/
https://www.robinlinacre.com/letter_constellations/
And here is like the admin/demo: https://www.robinlinacre.com/letterpaths/
And, separately, I made an educational country quiz, again FOSS:
I think the primary reason I enjoy working with them is that coding, for me, has always been a means to and end. I like the product of it more than the process. This quote sums it up quite well for me:
> People are really worried about their jobs. And I just want to remind them that the purpose of your job and the tasks and tools that you use to do your job are related, not the same. I've been doing my job for 33 years. I'm the longest running tech CEO in the world, 34 years. And the tools that I've used to do my job has changed continuously in the last 34 years, and sometimes quite dramatically, you know, over the course of a couple, two, three years.
A lot of wind and solar are on Contracts for Difference. That means when market prices go above the agreed level, the generator pays the difference back through the scheme, which reduces supplier costs rather than the generator simply keeping the whole windfall.
This is particularly relevant when e.g. the price of gas goes way up due to the Iran war, it doesn't mean that the consumer ends up paying more for the energy from wind
As with any other skill, if you can't do something, it can be frustrating to peers. I don't want collegeues wasting time doing things that are automatable.
I'm not suggesting anyone should be cranking out 10k LOC in a week with these tools, but if you haven't yet done things like sent one in an agentic loop to produce a minimal reprex of a bug, or pin down a performance regression by testing code on different branches, then you could potentially be hampering the productivity of the team. These are examples of things where I now have a higher expectation of precision because it's so much easier to do more thorough analysis automatically.
There's always caveats, but I think the point stands that people generally like working with other people who are working as productively as possible.
When you look at people's energy usage, quite a lot of it ends up being the embodied energy in the stuff they buy. For quite a lot of people, it's probably the largest category of energy consumption. I once had a very rough go at calculating this here: https://www.robinlinacre.com/energy_usage/
It was for school, and I recently found the write up and was surprised how well the system worked.
Ever since I've marvelled at how easy it was to build something highly functional that could incorporate complex business logic, and wished there was a more modern equivalent.
It was developed by a single guy in the IT department and she liked it.
About 5 years ago the company was acquired, and they had to move to their COTS 'enterprise' system (Maconomy).
All staff from the old company had to do a week long (!) training course in how to use this and she hates it.
In future I think there will be more things like 'Time' (though presumably not MS Access based!)
At the very least, it can quickly build throwaway productivity enhancing tools.
Some examples from building a small education game: - I needed to record sound clips for a game. I vibe coded a webapp in <15 mins that had a record button, keyboard shortcuts to progress though the list of clips i needed, and outputted all the audio for over 100 separate files in the folder structure and with the file names i needed, and wrote the ffmpeg script to post process the files
- I needed json files for the path of each letter. gemini 3 converted images to json and then codex built me an interactive editor to tidy up the bits gemini go wrong by hand
The quality of the code didn't matter because all i needed was the outputs.
The final games can be found: https://www.robinlinacre.com/letter_constellations https://www.robinlinacre.com/bee_letters/ code: https://github.com/robinL/
That said, polars is good, and if the team agree to standardise on it then that's a totally reasonable choice.
I guess one of my reservations is I've been (historically) burned by decisions within data eng teams to use pandas, causing all sorts of problems with data typing and memory and eventually having to rewrite it all. But I accept polars doesn't suffer from the same problems (and actually some of them are even mitigated in more recent versions of pandas)
There's actually something very valuable about a user specifying what they want using a working solution, even if the code is not mergeable.