Thank you so much!! I've been working on porting the code to react native expo for an iOS and Android app for the last couple months. It's so much work.
This is mitigated by wrapping the main scrollable content in a container that has height: 100dvh and overflow: auto. It means that phone controls are always showing but it made a bottom anchored menu reliably static.
This blog post shows how not to use AI. The author would have been unlikely to write such a uselessly redundant conclusion if they had to type it themselves.
Edit: I like the post, but it didn't need to be padded with fluff.
We shouldn't be too quick to jump to "AI did it." People write redundant paragraphs and sentences in articles all the time because they're led to believe that every article needs a conclusion that sums up what's already been said. Ironically, including one in this article showed a lack of good judgment, which isn't confined to AIs.
It does show an interesting second order downside of publicly using an LLM for anything: it raises everyone else’s suspicion that the rest of your work is LLM generated.
A certain amount of redundancy can be helpful. If you explain the same thing two different ways, one way might make more sense than the other to a particular reader. The judgement comes in because you should not just be doing this by rote or because you were "lead to believe" it was necessary, but in consideration of who you are writing for.
In common lisp, you don't need a build system at all; you can `(load "file.lisp")` everything and it should generally just work. But of course, build systems are useful tools, so nonetheless ASDF exists and it's nice enough to the degree that nobody has built a better and more widespread common lisp build system.
Some good trivial examples are in the lisp cookbook:
No idea why you're being downvoted for asking a simple question about an acronym. From Wikipedia [1]:
> ASDF (Another System Definition Facility) is a package format and a build tool for Common Lisp libraries. It is analogous to tools such as Make and Ant.
Contemporary developers using more mainstream languages are likely more familiar with asdf [2], the "Multiple Runtime Version Manager".
I'll look into a better way to collect emails. We have a quite a few people sign-up for the daily email as it's a good reminder to play each day, but we could place the sign-up elsewhere :)
This is impressive and mirrors a lot of thoughts I have had about the future of backend frameworks. I love the focus on local development for things like pub/sub.
FYI, the redirect to /login breaks the back button on Firefox for Android and probably other browsers. Had to hold back and go to a history entry to escape.
When something absolutely doesn’t make sense to me I often go back to a point in time and do a checkout of when I was 100% sure “it worked” and if it doesn’t then I assume something external changed, hardware, backend service, the earth’s wobble. If it does work then I will bisect the timeline until I Iocate it. This works for me 99% of the time on tough bugs that just defy any logic. It’s kind of known quantity as opposed to going through endless logs, blames, file diffs, etc. I know in some cases it isn’t really possible but in code that you can have a fairly quick turn around on build/install/test, it works really well.
Yeah, good times. I just recently had one that was a really strong misdirection, ended up being 2 simultaneous other, non related things that conspired to make it look convincingly like my code was not doing what it was supposed to. I even wrote tests to see if I had found a corner-case compiler bug or some broken library code. I was half way through opening an issue on the library when the real culprit became apparent. It was actually a subtle bug in the testing setup combined with me errantly defining a hardware interface on an ancient protocol as an HREG instead of an IREG, which just so happened to work fine until it created a callback loop inside the library through some kind of stack smashing or wayward pointer. I was really starting to doubt my sanity on this one.
Ah, yes. But a roll- your own device with C++ on bare metal, so lots more fun.
(we’ll need a few thousand of these, and the off the shelf solution is around 1k vs $1.50 for RYO )
By the way, the RISC V espressif esp32-C3 is a really amazing device for < $1. It’s actually cheaper to go modbus-tcp over WiFi then to actually put RS485 on the board like with a MAX485 and the associated components. Also does ZIGBEE and BT, and the espressif libraries for the radio stack are pretty good.
I wonder if there is a law of coincidental succeeses too. (if you're an old timer, you might call this some sort of Mr. Magoo law, or maybe "it seems to work for me")
This is the root of 'pigeon religions'. Someone sees a string of events and infers a causal link between them and an outcome. Confirmation bias kicks in and they notice when this string of events occurs again, which is made more likely by the fact that the events in the string are largely the person's own actions which they believe the events will produce the desired outcome. They tell their friends and soon a whole group of people believe that doing those things is necessary to produce that outcome.
That's how you get things like equipment operators insisting that you have to adjust the seat before the boot will open.
