"My instructions are to amuse visitors with information about themselves. [...] The need to be observed and understood was once satisfied by God. Now we can implement the same functionality with datamining algorithms."
Cool! I might add links to these in my tool so folks can find alternatives. For me at least, I've been loving the ability to try many different tools and compare how my visualisation differs between them. So I hope others would like that too.
We thought it would only keep us entertained for a few hours and ended up staying all day. Most of the enjoyment was the surrealism (I can't even remember details of any rides) but that was a LOT of joy.
This was incredible writing. The voice reminded me a bit of David Foster Wallace. I think I’ll be making my way through these archives :)
And I’ll be sure to head to Huis ten Bosch next time I’m in the area. I think soaking in the echo of everything it is, was meant to be, and did not become, will be a real treat.
One of my biggest jaw dropping sighting was to see a "le petit prince" Park in the middle of nowhere in Hakone, as a French, from south France, I was damn surprised to see that such museum existed, I think I had seen an ads on the billboard when going to Hakone and was double surprised.
I reached the same conclusion for my own static blog. One step beyond just having an email link is to run an AWS lambda that takes a web form post and sends you an email with the contents. That way you can add a captcha (hCaptcha seems like a good alternative to Google), and your email address doesn't float around on the public internet.
It's fairly low maintenance and easy to replace if you ever did want to step away from AWS.
The blog is on a domain, that comes with tons of email adresses. Doesn't it? So just ínvent a dedicated one that well may float. Change once appropriate.
Catching a form-post on the server doesn't take AWS (unless you only ask the Amazon evangelists). 50 lines of bash cgi do it for me.
> The Fediverse really could help if just somebody would implement such a comment engine. But that engine has to be deployed decentral. On each blog.
I’m really not sure what you mean with that. The old blogs generation had a pingbacks system, but it’s really not suitable for commenting: that is usually not moderated by the target, it requires having set up your own blog, it’s really inconvenient for discussions when you have to keep jumping through (unless you use a federation tool but then it’s back to centralisation), and it can be awkward to reply through a blog post as the reply might not rise to that level of interest to your own subscribers, plus the subject at hand might not be one you aim to cover in your normal posting.
the fediverse promises to connect across instances.
Imagine your blog is one, too and can receive likes and replies just like any other fediverse instance. Each comment is both on the commenters fediverse profile as well as under the blog article that it refers to.
These kinds of static sites are generally served from a shared host like GitHub Pages, Netlify, etc. The baseline is configuring Jeykyll or whatever the first time.
imo lambda/serverless can get overdone and too complicated but it works well for one-off services like this.
I've been playing around with the Lego and Raspberry pi combination on and off through the years [1], with the goal of building a standalone tracked vehicle (pi on board) that can move around my apartment. There were various ways to do this already, mainly by using off the shelf motor controller boards and later the third party Bluetooth motor bricks. This was all for the old "power functions" system though, Lego has since revamped their lineup with a lot of new parts that all use a different connector. I'm really looking forward to getting one of these.
Lego has the bad habit of not extending their 'systems' thinking to their electrical and electronic components. New connectors are introduced rather willy-nilly and supply voltages and communications protocols change with potentially every model year.
This allows them to quickly follow trends but it is totally contrary to the mechanical interface which is backwards compatible for over 60 years.
The same goes for the train sets, the track width is more or less the same for ever but the track interconnects and the way the trains are powered have changed often.
Fortunately for the trains there is a solution (subset of track, only use the old 12V system for the track it will also support battery powered trains giving a reasonably broad coverage), but for the electronics and the various motors the situation is quite a bit more complex. Note how the article essentially limits compatibility to a single one of the 10 or so systems that Lego has over the years used to connect electrical components.
Anybody remember the very old style electrical interconnect plates?
Someone ought to cook up a compatibility kit that allows you to connect older and newer stuff at will.
I love cycling. Did my first solo touring cycling trip over ten years ago when I was in my twenties. I've done a cycling trip every couple of years since then, until I got a mortgage. Then I started focusing on my career and kept delaying the next trip, thinking "next year will be the year that I'll make time for it". Now I'm approaching my 40s, I have a medical condition that limits the enjoyment I get out of cycling, and due to covid travel restrictions I can't travel to the country I want to cycle in.
It used to make me sad that by the time my kids were old enough to cycle up big mountains, I might be too old/unfit to join them... but the massive growth in the last few years of electric bikes (mountain and road) makes me really excited that I actually might be able to keep up. I don't know if e-bikes would help given your condition, but if you haven't tried one, it might be worth a shot - they're amazing
Oh gosh :/ I’ve been delaying my trip to Asia for 3 years. I can’t eat spicy food like I used to now (or even drink and party). I want to believe I’ll be doing it next year but…
Cboe Europe | Web Software Engineer | Full stack: Python (Django), JS (React) | London | Full-time | Partially Remote
Cboe Europe (https://cboe.com) is one of the largest truly pan-European equities exchanges by value-traded and market share. Through our exchanges in the UK and the Netherlands, Cboe UK and Cboe NL, we offer trading in more than 6,000 securities across 18 markets.
Our web applications play a critical role in the command, control and monitoring of the Cboe Markets in Europe, in addition to presenting high-quality market data to our members and the investing public.
You'll work across the entire web stack, using agile software development techniques to build high-performance, scalable, testable data-driven web applications with Python, Javascript, HTML, CSS and SQL.
This is the kind of thing that I love to see as a blogpost, and I admire the ingenuity of the author, but I would hate to ever see this in a production codebase.
Unfortunately, most enterprise applications will have something like this, because they'll need to be customisable for individual companies. I've worked with a CA product years ago that had written their own SQL engine for doing exactly that. I would have much preferred the Django solution.
Totally in sync with you. I used to work for Zenefits, and if there's one technical reason I could point to for the company's failure to calculate accurate insurance rates (and eventually get a lot of support cases leading to lesser margins leading to an eventual failure in the insurance space), it was the blatant abuse of Django models.
Yeah anyone who did this in a codebase I manage would be on their way to looking for a new job. Trying to save a couple lines of code by relying on undocumented private API functions is seriously not acceptable, especially when there are multiple other ways of doing this.
This is not about "trying to save a couple lines of code" at all. Sometimes you want to gives the customer the ability to customize the app however they want and sometimes this is needed in order to do that. E.g. custom profile fields, building custom forms themselves (like Google Forms), etc.
> Sometimes you want to gives the customer the ability to customize the app however they want and sometimes this is needed in order to do that.
What's wrong with using a JSONField with a different Cerberus validator for each client, and then using a Django form (and possibly some custom admin template code) to make it possible for the client to perform CRUD operations in the admin?
I personally would still just build a React front end and do the CRUD operations via REST endpoints, but if you really want to use the Django Admin then that's a much better way to do it than monkey patching the migrations system.
- https://www.youtube.com/watch?v=pKN9trFSACI