I think the 600$ price point was inflated with the Pi and the Arduino being used. Simply changing some parts for cheaper ones would have allowed to reduce the BOM cost and thus reduce the price. The author mentions this in his post.
Also seemingly not a lot of people paid 600$ for the sign, with a lot going for a lot cheaper than that.
I think you're missing the forest for the trees. It's one thing to store the lyrics in the file, but the entire UX around the use of those lyrics is pratically non-existent.
Storing the text is the easy part. Procuring files with lyrics baked in or adding lyrics to your pre-existing library is another. And so far, almost no music player supports them, their UI isn't necessarily optimized for displaying lyrics, and there is no widespread standard for their format.
> Note that since our technical discussion is a conversation. I don’t expect a perfect answer from anyone. If I hear some right keywords, I know that the candidate knows the concept, and I try to push them in the right direction.
You seemed to have missed the most important point in this interview. I agree with you that rote memorization is useless, but the goal here is to have a technical discussion on topics like mobile design, accessibility and SEO. And if you're not willing to have this kind of discussion you're doing the interviewer a favor by walking away.
You also don't need to know how to code those by heart, but you need to view at a glance what their use is if you ever need to diagnose an issue, even if it's generated by a framework, because a framework may not generate the proper code for you.
You missed the entire point of the article. The point is now to know whether you know those 10 lines by heart, it's whether you can have a discussion starting from just this.
Do you know why the document starts with a doctype declaration? What accessibility tags are and why they are important? What is OpenGraph and why SEO is important? What are CSS resets and why do we use them?
If you can take a guess you're already halfway there. If you can explain what you know about them you've aced it. It's not about knowing all of the meta tags or the OpenGraph attributes, it's whether you can have a discussion about mobile design, accessibility and SEO.
The touchscreen is still there on my 2020 model. but I always use the roulette to navigate. It's a bit akward at times but it's much better than taking my eyes off the road to try and line up my finger on the touchpad. It's disabled in Android Auto mode, and probably in CarPlay but I never used it.
I too had problems with Android Auto when using my old phone, it constantly crashed. When I switched to a Pixel 4a in 2020 I no longer had any issues. It works like a charm.
So I suspect it could be your phone, or something related (the cable, the type of USB plug, etc.).
There are plenty of websites that detect that I'm using an adblocker. It's mildly annoying, but then I get to decide if what I was about to read was worth it.
Most of the time it's journaldemontreal.com (and other Quebecor-related websites) that prevents me from reading their articles with my adblocker. Which is a blessing in a way, because it's basically a glorified tabloid with a lot of articles of dubious quality.
I'm on Firefox with both AdBlockPlus and uBlock Origin.
This kind of function overload is present everywhere in the Java collection framework (and probably other libraries). It is a performance optimization (variadic arguments in Java require creating an array), and variadiac overloads also exist (Map.of needs a list of Map.Entry for type safety) for creating collections of any size.
Can you elaborate on your reasons why it would be a bad thing?
I think the argument for this is mainly that this would be funded by taxes, so it would not need to rely on advertisements and exhibit the predatory behaviours that Facebook and other social media do.
I've seen this multiple times, and there seems to be a pattern emerging.
At first, people name the machines after the software they install on it. Then, when you get to about 4-5 machines, you start finding a "cute" naming convention (Constellations, Star Trek ships, mythological figures). As long as there is only a handful of machines, it's easier to remember which machine does what.
Then, as you start to scale up, between a few tens to a hundred, finding names gets harder, so you switch to a more standard naming conventions. Something that communicates the physical/logical location and the organizational unit, as well as an index for duplicates / replicas / redundant machines.
So I think it's fine to be clever as long as it's manageable. The moment it's going to start getting out of hand you can switch to a more scalable approach.
msquic would be a good start, which is the protocol implementation from Microsoft. I used it for a project of mine which used Quic for something not HTTP/3 related.
I think it's a great first effort, but there are a number of possible improvements to do. The most obvious one would be to support passing the file as an argument instead of using cat or the redirection operator every time. It's great that it works with stdin to allow piping into it, but it's cumbersome if you just want to take a file and print it, which will no doubt be a common use case.
Historical records seem to contradict themselves on this matter. What I recall reading was that they were created for two different things: JavaScript was created to add basic interactivity on the page, and Java was intended to be used for more CPU-intensive work.
I think the same thing about SHA-1. It is possible to generate a collision with it, but it is costly, inefficient and practical.
If you design software, then yes you should put mechanisms in place to replace older and less secure ciphers with new ones, and prefer and limit the ones you chose for some who are considered safe at the moment. But I don't think we should put red flags all over a cipher or a hashing functions because someone with unlimited resources and money managed to fool it once.
Most of the time it isn't my version on OpenSSH client that limits me but the remote software I'm connecting to. If I can generate an Ed25519 ssh key I will, but most of the time it isn't supported.
I'll usually go with the same order of the preference in the article, Ed25519 then ECDSA then RSA. I haven't yet seen a server not support RSA. But fairly recently I had to register an RSA 4096 on a Bitbucket Server because it did not support both elliptical curve algorithms.
So yeah, it's definitely lacking a lot of software support, but I'll use it if possible.