I’ve noticed a lot of changes on the site recently, which I believe is powered by Ghost which makes messing around with feed links a more advanced (for lack of a better word) tweak than many platforms as you download/upload a routes file. I’m a 10+ year developer and have found myself chasing route changes in Ghost with trial and error.
I thought the two sounded similar, then I saw at the bottom they both have come from the same two founders. Nice to have a straightforward alternative to NextDNS to recommend to relatives.
Agreed. We bought my wife an NC last year when the criteria was “cheap, petrol, naturally aspirated and Japanese”. The criteria was in response to my Land Rover (Discovery / LR4) which is none of those things and becoming a bore.
After stealing the MX-5 whenever I get the chance I now wish we could run two. That would make family trips troublesome though…
I have a small flask - about the volume of a cup of coffee - made by Kinto. It can deliver those surprise burns hours after filling. It’s almost too good, and has been relegated to long road trips or post-surf coffee where I know it’ll be >3 hours before I want to drink it.
A large vacuum bottle with ice cubes on a hot summers day is hard to beat too.
That was my sense too. Used it for a few similar programs today (like converting HTML to Markdown but parsing certain <figure> elements to shortcodes) and scaffolding a Rust web app.
It's done a reasonable job — but rips through credit, often changing its mind. Even strong-arming it into choosing an approach, it wanted to flip-flop between using regex and lol_html to parse the HTML whenever it came across a difficulty.
If you're a US developer on whatever multiple of $ to the £ that I earn it might make sense, but burning through $100p/h for a pair programmer is a bit rich for my blood.
I did this recently when a blog post described the exact, very niche issue I was having with a production server. This post described the symptoms of the issue clearly and included a flow-chart of required fixes. There was no preamble, just clear guidance. It was more an incident management manual than a blog post, and it saved me a lot of Googling under considerable stress.
I sent the author a quick thank you, explaining how it helped me in my hour of need. Exactly as others have said here, it goes a long way to making the effort of blogging worthwhile!
Hello, sorry for not making the demo accessible without an account. Currently there's an open issue which I'm working on to do so. This project under heavy development, sorry for the troubles.
