👋🏽 Hi! This is Jeremy's Craft by Zen

A curiosity sparked because my co-worker pointed out the Spring Framework is currently owned by Broadcom. That’s because VMware is now part of Broadcom, and Spring Framework was part of VMWare prior. I had an inkling there was a scandal Broadcom had awhile ago. Low and behold: SEC Charges Four Current and Former Broadcom Officers for Backdating Options (Press Release No. 2008-87, May 14, 2008). In 2010, the charges were dropped - Chipmaker Broadcom stock options backdating case ends. That’s not all though. Their first CEO, Henry Nicholas had criminal charges. The SEC dropped those charges in 2010, but that was enough to disgrace the people involved. Their former SEO left Broadcom before the SEC investigation back in 2003 to “work on his marriage”. He was sleeping with prostitutes.

Read: Henry T. Nicholas III: A human tragedy. And the follow-up a decade later with Orange County tech billionaire Henry T. Nicholas III charged with drug trafficking following Las Vegas arrest.

The court filings in the past case painted Nicholas as a ruthless entrepreneur who slipped drugs to competitors without their knowledge, who threatened the lives of employees he believed had turned against him, who had the means and motive to flee beyond the reach of justice in his private jet.

His start was in researching ICs, and later that’s what Broadcom sold. He was given awards for his research. He’s like a walking contradiction, trying to save his name with his philanthropy while making wildly bad decisions. File under downfalls.

It’s always fun when the MDN documentation doesn’t tell us what the options are within the methods page, I you have to dig deeper into the constructor. The TypeScript bindings don’t always make sense.

MDN - toLocaleString

Anyways, I needed a datetime string with the date, time in hours and minutes, and the timezone. I’ve made the timezone explicit and came up with this snippet.

date.toLocaleString("en-us", {
  year: "numeric",
  month: "short",
  day: "numeric",
  hour: "numeric",
  minute: "numeric",
  timeZone: "America/Los_Angeles",
  timeZoneName: "short",
});

This would return something like “2024-07-03, 12:00 PM, PDT”.

The shorthand option is must be used in object destructuring to remove redundant prop: value to be prop.

What I wanted was this shorthand:

const { asFragment } = render(container);

But what codemod generated was the following:

const { asFragment: asFragment } = render(container);

While both are true, I would rather have the shorthand, as that’s what we have strictly for eslint rules. This Github Issue helped describe the solution on how to implement in your transform file.

const code = j.objectProperty(j.identifier("h"), j.identifier("h"));
code.shorthand = true;

j.variableDeclaration("const", [
  j.variableDeclarator(
    j.objectPattern([code]),
    j.callExpression(j.identifier("require"), [j.identifier('"packagename"')])
  ),
]);

How to embed TikTok videos in Obsidian’s editing/live preview and reading mode.

<iframe
  src="https://www.tiktok.com/player/v1/7382225350710824222?autoplay=0"
  allow="fullscreen"
  style="width:100%;height:50vh;"
/>

where 7382225350710824222 is the video id you get from TikTok from this example link: https://www.tiktok.com/@_jen_hamilton_/video/7382225350710824222.

The TikTok v1 player has a bunch of controls that you can use to modify from this documentation.

There’s still some wonky height issues, and I suspect this is the default height Obsidian has on the container around the editor. I gave it a good enough viewable height of 50vh, which should be enough.

Example Video

Reference links

• How do I embed TikTok Videos? - Help - Obsidian Forum
• Emedding TikTok Videos - Help - Obsidian Forum
• html - How to stop auto play in an embedded video? - Stack Overflow
• TikTok for Developers

d3 v7 is packaged as ESM only. That made it difficult to use in the Node.js REPL. From this StackOverflow thread, I found a solution.

let d3;
import("d3").then((module) => {
  d3 = module;
});
// Then you can use d3 anywhere once the promise is resolved.

Extremely esoteric bug. I’ve had an open issue for the past three months related to this other issue. I couldn’t figure out why npm’s registry would pull an older version of d3-scale-chromatic when I upgraded the @observable/plot library. As a future note for myself, if I run into this issue again, I’ll have to go into the package-lock.json file and update d3-scale-chromatic to v3.1.0.