mkreis

Scheme is mostly used for teaching, but there are many production applications out there written in Lisp (Emacs for example). Also I'd like to mention Clojure, which is "lispy" and used by big cooperations.

Depends whether you see it as a production method or an art/recreational activity. There can be both, and don't worry, hand-made products will always have a special value. Even if everybody can order custom made knitted sweater from a machine.

Shh... we don't talk about those dark ages any more. Times were different.

So true. My first job was in QA. Involuntarily, because I applied for a dev role, but they only had an opening for QA. I took the job because of the shiny company name on my resume. Totally changed my perspective of quality and finding issues. Even though I liked the job, it has some negative vibes because you are always the guy bringing bad news / critizing others peoples work (more or less). Also some developers couldn't react professionally to me finding bugs in their code. One dev team lead called me "person non grata" when coming over to their desk. I took it with pride. Eventually I transitioned to develoment because I did not see any career path or me in QA (team lead positions were filled with people doing the job for 20+ years).

Bootstrapped solo dev here. I enjoyed using Claude to get little things done which I happed on my TODO list below the important stuff, like updating a landing page, or in your case perhaps adding automated testing for the frontend stuff (so you don't have to click yourself). It's just nice having someone coming up with a proposal on how to implement something, even it's not the perfect way, it's good as a starter. Also I have one Claude instance running to implement the main feature, in a tight feedback loop so that I know exactly what it's doing. Yes, sometimes it takes a bit longer, but I use the time checking what the other Claudes are doing...

Finally. I remember buing "genuine" Samsung HDMI adapter and receiving counterfeit products all the time (technically inferior with bad shielding and failing quickly) Might have been a good idea on paper, but reality proved otherwise. Actually I'm surprised it took them so long.

I'm curious to learn from your mistakes, can you please elaborate what went wrong?

Looks nice, but... what is this and how is it supposed to work?! There is no explanation, no tutorial, ...

It is in regards to the GDPR. If you're a European vendor and process PII, you must ensure some level of data protection. If you want to be on the safe side, you'll pick European providers instead of US hyperscalers (who have EU data centers, but are still US owned).

I can still remember when the first inkjet printers came onto the market as the successor to dot matrix printers. I wanted one because, as a child, I thought it would allow me to imitate my handwriting with a fountain pen and I would never have to write my homework by hand again...

I'd emphasize that it's a problem with your particular code base. If you set it up correctly, all dates are properly parsed at the boundaries and you would only deal with one type of date inside your app. I'm working on a large Clojure app with a lot of date handling and never had any issues. For me, a date is always juxt/tick date.

Thanks for the link. Unfortunately it seems it is currently removed due to unclear bugs.

This is really nice, and I am impressed how much effort went into the documentation, to make the demo nice and interactive.

At first I thought this is something new, because it's cool and I haven't heard of it, even though I'm coding in Clojure for about 3 years now. But this project is already 10 years old and hasn't received much attention for the last few years, which is a pity. I wish it was coming with Calva, my favorite Clojure tooling in VS Code.