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.
Current racket is running on top of chez scheme - which is maintained by Cisco - and reportedly extensively used in commercial products (router firmware/os etc).
It was brought into Cisco to do that but the project was eventually shelved, which was a shame because the prototypes delivered some really interesting reliability features. Most Cisco hardware products run firmware written in C. Management systems are often Java and (increasingly) Go. Clojure is used for one of the security product lines, but that was developed as a startup that was later purchased by Cisco. One of the management systems, NSO, is written in Erlang (brought in through the tail-f acquisition). There are certainly a lot of people in Cisco that understand the power of Lisp (I was one), but they are spread out and surrounded by people that just want to push whatever the latest thing is (now Go). C.f. the blub paradox and “worse is better.” They have a lot of legacy code that was written over the last 30 years that powers their devices, and that’s all in C.
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.
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.
HDMI adapters are a dime a dozen. Pick some random crap and save yourself the money, as long as they reasonably work they'll "disappear" faster than a crate of beer...
You don't want to risk damaging an expensive phone/laptop/TV by plugging in the absolute cheapest unbranded cables/adaptors etc if there's a trustworthy brand available.
And with some electrical stuff, such as power strips and chargers, there might be safety issues/fire hazards too.
The German Wikipedia page[1] about the Z1 also contains a quote from Kurt Pannke, who Zuse told about his plans for the computer.
"Oh, Mr Zuse, there is absolutely nothing left to invent in the field of calculating machines. But you are a nice young engineer, I'll give you 1,500
Reichsmarks and when you have come up with something, show it to me."
(Translated by Deepl)
I like the "640K ought to be enough" vibe of that statement :)
