nudgeee

Teensy is based on iMXRT which are NXP, not Nexperia.

Sibling poster did a good job explaining how research relies on labs.

Agree that complex EE work can be expensive for individual and smaller companies, indeed :)

A comment on the application side:

> "[..] for wireless applications you can follow the recommendations of the IC vendor and the remainder of the work is RF-engineering"

Zoom out to the system level, and you cannot just rely on IC vendor recommendations, and this kind of engineering can still require access to $$ labs.

Similar to complex software systems: for example take a large scale distributed system made out of many individual frameworks and services. The system as a whole may now exhibit emergent behaviour, and have failure modes due to the complexity of the system.

Same happens in complex EE designs, your design might pack in multiple cutting edge RF radios such as mmWave, UWB, with bespoke power amplifier, detection and antenna designs. Add in EM from multiple clock domains, high power distribution circuits, digital noise from FPGAs/CPUs, and EM from nearby sources. You can easily have noise couple from sources causing unintended issues in other subsystems. The vendor may say "keep a way from sources of noise", but your application may still be to engineer a solution that fits in the design envelope of a modern smartphone. The system level design needs to be engineered for EMC and coexist/desense, and validated which takes a ton of lab simulation and measurement/characterization work.

By fab you mean lab, then agree.

Fabs are specific to the manufacturing of integrated circuits.

EE encompasses more than just manufacturing of ICs, for example research and applications in radio propagation and EM/wireless, signal integrity, antenna design, coexistence/desense, advanced power electronics, control systems, simulation/solvers, etc.

Hilarious. Reminds me of Pioneer CDJs as well, even on the flagship CDJ-3000 models. If you read the user manual it says:

> About using MP3 files

> This product has been licensed for nonprofit use. This product has not been licensed for commercial purposes (for profit-making use), […]. You need to acquire the corresponding licenses for such uses. For details, see […]

Best use an open audio codec instead.

Agree on this. As a layman in Australia, i had a friend who was coming back from the USA and asked him to buy me an iPhone before its release in AU (late-2007 iirc, iPhone 3G launched in Australia in 2008) and promptly jailbroke it so i could get it on an Australian carrier.

When i whipped it out in public, take a photo at concerts, etc. random people would come up to me and ask me to play with it -- thats when i knew for sure Apple were on to something, a complete game changer that captured the attention of the public.

Why not both? It is possible to achieve comfort with privacy.

Isn’t this how certificate revocation flows work?

Indeed, this is a common vector for leaking PII and sensitive data. For example, what looks like an innocuous logging/print statement in an exception handler ends up leaking all sorts of data.

And it gets more messy when you start to ingest and warehouse data logs for on-call monitoring/analytics/etc, and now you have PII floating around in all sorts of data stores that need to be scrubbed.

In a previous job, we handled credit card numbers. We added PII detectors to logging libraries that would scrub anything that looked like a credit card number. We used client-side encryption where the credit card numbers are encrypted on the client before sending to the backend, so the backend systems never see the plain credit card numbers, except for the system that tokenizes them.

That, and the peace of mind of not being fired at-will when economic times aren’t so good.

My guess is it probably was a content update that tickled some lesser trodden path in the parser/loader code, or created a race condition in the code which lead to the BSOD.

Even if it’s ‘just’ a content update, it probably should follow the rules of a code update (canaries, pre-release channels, staged rollouts, etc).

Ooof missed that, thanks!