HN user

milanove

35 karma
Posts0
Comments19
View on HN
No posts found.

The Raspberry Pi and Arduino platforms weren't meant to power commercial-grade products, nor be cost effective at scale compared to raw/custom ARM and AVR devices. However, they've become ubiquitous in education, which I imagine has impacted industry. Similar to how software companies give out free student licenses so that upcoming engineers become familiar with their software for when they start working, an entire generation of embedded systems engineers were taught on official (or compatible) Arduino and Raspberry Pi devices. While these platforms aren't meant for commercial products, I imagine engineers in industry might use these platforms to prototype or work with subcomponents, before they integrate it with a raw/custom AVR or ARM platform. After all, when prototyping, it's easier and faster to get up and running when you have a massive collection of libraries and tutorials online to use, which RPi and Arduino offer, versus doing it all yourself with raw AVR and ARM.

I'm not an ML expert or practitioner, so someone might need to correct me.

However, I believe the parcel's components together as a whole would capture the state of the audio+visual+time. However, I don't think the state of one particular mode (e.g. audio or visual or time) is encoded with a specific subset of the percel's components. Rather, each component of the percel itself would represent a mixture (or a portion of a mixture) of the audio+video+time. So, you couldn't isolate out just the audio or visual or time state specifically by looking at some specific subset of the percel's components, because each component is itself a mixture of the audio+visual+time state.

I think the classic analogy is that if river 1 and river 2 combine to form river 3, you cannot take a cup of water from river 3 and separate out the portions from river 1 and river 2; they're irreversibly mixed.

Unless I'm doing something simple like writing out some basic shell script or python program, it's often easier to just do something myself than take the time to explain what I want to an LLM. There's something to be said about taking the time to formulate your plan in clear steps ahead of time, but for many problems it just doesn't feel like it's worth the time to write it all out.

Q-Transformer 3 years ago

I’m glad to see people in the open source community taking the initiative to implement these tools for the general public. It’s one thing to understand the high-level concepts in a paper, but another entirely to implement them efficiently. Some people just really have a knack for reading academic papers and implementing those ideas in software.

I wonder if many of these lowball salary job postings could just be companies applying for an employee's greencard through the PERM system. IIUC, for PERM, the applicant's employer is required to put out a job posting for at least 10 days to show nobody else can do the job their employee/greencard applicant does. The salary they list in the posting must be at least the minimum wage dictated by the Department of Labor for the role.

However, I suspect that the company making the ad will just list the lowest possible salary in the posting to deter real applicants from applying, hence making the greencard applications smoother.

However, don't quote me on this, since this is just my very vague knowledge on how greencard applications work. Somebody else here who knows more about this topic, please chime in to let me know if this is true.

Getting something working in the beginning feels very different from a coding puzzle. During the next phase of optimizing something is where it gets interesting. Understanding the hardware and figuring out the right way to make full use of it via memory tricks or specialized processor instructions always felt more like a puzzle. Unfortunately, I feel engineers are seldom given the opportunity to go deep down the optimization route once something is working reliably, since it's already getting the job done.

Waf is another interesting build system I've seen used in production. It's config is done with Python scripts, which is cool.

One thing I've noticed when using many open-source softwares with a GUI is that they just don't look and feel like a professional piece of software. The programming and project architecture may be stellar, but without a clean, professional looking user interface, most folks won't give it a chance. Take Gimp for instance. The software is an excellent alternative to Photoshop, but most people who aren't really into OSS or programming tend to overlook it or immediately disregard it, due to its UI.

Like the article's author talked about contributing answers to forum questions, I think other areas open-source software projects need some changes. I think the OSS community needs to try and recruit more design folks into their teams, rather than just programmers.

The article said the patient showed signs of recovery and then later on started showing signs of the virus again. I don't know if that means they conducted an exit test to confirm that she was negative for coronavirus after her first bout with it. Maybe it died down in her system, but wasn't completely gone when she was deemed healthy again and later on it flared up again for some reason.

Yeah the article didn't really present anything very useful. What I took away from it was that the U.S. government claims of potential malicious backdoors in Huawei's devices are unproven, but plausible. I think we all were already thinking this though.

Maybe I was expecting a technical overview or reverse engineering of how their backdoors work, but really the article was non-technical. If I understand correctly, it can be summarized as: The WSJ made a claim that Huawei was using a backdoor into a backdoor, so that Chinese intelligence would have access to their devices globally. However, the claims were unsubstantiated and attributed to anonymous U.S. officials. Then, Huawei made a video clarifying what backdoors are, stating that a "backdoor" which is used by law enforcement is really a "frontdoor".

Covering every detail of the technology wasn't really the point of the article. It's a New York Times article. It's meant to give a brief explanation, for non-engineers, as to how this technology works. The target audience don't need to know all the different companies' achievements nor the specifics of the technology used.