sgtnoodle

It wasn't a laminates company, was it?

I'm embarrassed that I live in HMB and didn't recognize it. I should go to the harbor more.

I asked Gemini to format some URLs into an XML format. It got halfway through and gave up. I asked if it truncated the output, and it said yes and then told _me_ to write a python script to do it.

I have a yoga from 2016 that had its backlight supply rail blow up. Very lame.

You can do some pretty crazy stuff with pipes, if you want to do better than unix sockets.

I've spent several years optimizing a specialized IPC mechanism for a work project. I've spent time reviewing the Linux Kernel's unix socket source code to understand obscure edge cases. There isn't really much to optimize - it's just copying bytes between buffers. Most of the complexity of the code has to do with permissions and implementing the ability to send file descriptors. All my benchmarks have unambiguously showed unix sockets to be more performant than loopback TCP for my particular use case.

There's definitely differences, whether or not it matters for most usages. I've worked on several IPC mechanisms that specifically benefited from one vs. the other.

A former coworker texted me out of the blue yesterday, saying he missed working on a "<my name> codebase". He specifically appreciated that "doing something simple things were kept simple." Made my day!

It's still mass, drag and cost.

It might work in so far as you'll get packets through. The performance would be abysmal, though. Modern Ethernet is built around switching.

The folk that made Crash Bandicoot were pretty clever. They figured out that the PlayStation could render untextured, shaded triangles a lot faster than textured triangles, so they "textured" the main character with pixel-scale geometry. This in turn saved them enough memory to use a higher resolution frame buffer mode.

https://all-things-andy-gavin.com/2011/02/04/making-crash-ba...

I read the XML directly in my browser out of spite.

Crowded? No. Littered? Perhaps, depending on the altitude. The article you linked says the bulk of the existing debris is from a few isolated incidents.

These satellites are generally low enough tha their orbits decay after a couple years if they don't boost themselves, and then they burn up in the atmosphere.

I've gotten CEC to work in Linux on my desktop computer. The funny thing is that most GPU HDMI ports don't implement CEC, but do implement CEC over DisplayPort. You simply need to find a DisplayPort to HDMI adapter that supports CEC.

It's funny that it doesn't have the great lakes. I guess it doesn't have any internal bodies of water.

We're on a good employer plan, and weight loss meds are all out of pocket.

A more obscure use would be for loading multiple instances of a singleton library. This is especially helpful in something like a unit test suite, where you want each test case to start in a cleanly initialized state. If the code under test has a bunch of globally initialized variables, reloading the library at runtime is one of only a few possible ways of doing it.

In my experience, a culture of radical employee-driven compensation transparency can lead to toxicity. A subset of folk have a tendency to become obsessed, and increasingly more resentful about their particular notion of fairness. Then from that, folk start to play the victim, grasping for explanations that don't require introspection or admitting individual responsibility. In that environment, the company is forced to take a defensive position, which makes the culture even more toxic.

What I've seen work well is the company taking pro-active steps to be transparent about compensation in aggregate. For example, HR can put out a periodic report documenting compensation metrics by job title and experience. They can also slice the data along various social factors to quantitatively show whether there's any indicators of unintentional bias. From there, another good idea is for the company to regularly apply adjustments independent from performance, in order to keep the metrics healthy.

Is email not customary? It seems like it would be fine as long as they respond in a timely manner, and provide access instructions. Also, in this situation it seems like that's exactly what happened.

I suppose what might be non-compliant is if their website doesn't explicitly document the process to access the source, i.e. "send an email to this addressm to request the most up-to-date source code."

Given that it's shared memory based, it seems like there has to be some degree of trust that the participants are well behaved. What do you mean by a malformed message, though? If you're talking about the payload of the message, that seems like a matter of the message scheme you're using. If you're talking about correctness of the IPC protocol itself, integrity checking is unfortunately at odds with latency.

I've also developed a strikingly similar low latency real-time IPC message bus for work. It also uses sockets with transparent shared memory optimization. In my case, it's the backbone for an autonomous aircraft's avionics. I made everything agnostic to the message scheme, though, and most of the tooling supports an in-house schema, protobuf, JSON, YAML, etc. There's also clients implemented in C++, Rust, Python and Julia.

What troubles has protobuf caused you?

I liked my Kobo, but it bricked itself after only about a year. I took it apart, and a voltage rail was shorted out. I didn't even finish the first book I put on it!

I'm friends with a small batch gelato maker. He mainly sells individual scoops, but he also sells pints. He started out using fully compostable pint containers, but their permeability leads to ice crystal formation while the product is stored. He's switched to more traditional pint containers, and the improvement is noticable.

This is interesting. They're replacing the pacemaker's leads with optical fiber, with a tiny solar cell at the end. They send a pulse of light down the fiber optic cable, causing the solar cell to convert it to enough charge to "capture" the muscle.

Pacemaker leads don't just deliver charge, though. They're used to measure the heart's natural electrical activity so that the pacemaker can synchronize its pulses. I suppose that's something that can be done remotely through a more traditional ECG electrode placement.

This is pretty neat. Pacemaker leads are an amazing piece of engineering, but being able to place leads non-invasively through a syringe would be a huge advancement. I also suspect the fiber optic could be made to last significantly longer.

As an embedded engineer with about 12 years of battery life, I've thought about this topic a fair amount. It would be neat to somehow integrate a super capacitor capable of powering the device for a day or two, and an inductive charger able to top it off in just a few seconds. This could ideally be done via a standard smart phone inductive charger. Then, reduce the size of the primary cell to cover just a couple years as a backup. For a younger person looking at many decades of pacemaker operation, that could save them from a number of surgeries, as relatively minor as they are.

Thanks! Yeah, the Mark Rober video was pretty great.

There's certainly a smattering of machine learning algorithms involved in some of the software components, but I'm working on Zipline's next generation "platform 2" delivery drone. As an embedded engineer, something has gone horribly wrong if we're trying to solve problems with AI!

I believe that's how satellites are tracked at all? Rather than use visible light, though, tracking stations most certainly use radar, and probably highly directional antennas.

I have several friends that immigrated from Europe, and they've all made comments about their respective countries that suggest that's not really the case in practice.

Pretty much any modern storage medium depends on a healthy amount of error correcting code.