patsplat

The stolen property in the story in the above comment was recovered. I don’t see how this justifies more surveillance that is likely to be abused.

Are the financials available?

Because based on “asked it to make a profit” I expect financials in the story. Even if it is a bit of a ”Clarkson’s Bot”, for the farm there is discussion of the numbers.

There’s the NYC Mechanical Keyboard Meetup if you would like to see and try different builds. Most people will let you try their builds.

https://nyckeyboardmeetup.com/

Physical objects should be rounded, virtual windows should be square. I will die on this hill.

I recommend dialing in a mill before claiming there’s no craft in CNC.

When LLMs transition from predatory pricing to rent seeking, the enthusiasm will evaporate.

CSS does suck because of the globals. Class names, ids, z index values are all areas where one commonly bumps into other developers in sometimes confusing ways.

But to the point of the article, it’s a technology one has to learn. There are name spacing solutions in css (layers) and around css (css modules, panda, tailwind, etc).

I think another challenge folks may have with CSS is thinking visually. It’s not automatic. In art school one learns both how to see and how to render, and generally learning how to see clearly is a bigger challenge than learning how to render.

Practice your craft.

You are correct, I think he was talking about a different device:

https://www.fda.gov/news-events/press-announcements/fda-clea...

I just heard about a related device from a family member who is an endocrinologist.

https://www.fda.gov/news-events/press-announcements/fda-clea...

First off, he had discomfort with the study methodology. Didn't go into details, but was surprised that the FDA was less conservative than himself in this case.

Secondly, it has been common in his practice for someone to have an unusual event. Someone does something out of the ordinary, they have an unusual circumstances, they don't adjust their treatment, and something goes wrong.

His question was -- does the device have a reset button? Is there a way to restart the management and learning? The answer is no -- the device will learn! But there's no way for the patient or the physician to adjust the treatment. So his answer is -- he would never recommend this device, not the way it's currently setup. It's opaque and there's no means for a person to influence the device's learning.

Note that one big database can decimate productivity as well.

Is it about process space and programming languages? Or is it about source control and CI architecture?

How is a monolith different from a monorepo?

It works extremely well for ux development ;-)

He's been slightly famous for technical writing for a long time

https://en.m.wikipedia.org/wiki/Eric_S._Raymond

This seems a very nostalgic take.

So long as websites pretend they are documents, they will remain bloated poorly performing synchronous applications.

Accept that websites are distributed applications and deliver great experiences.

Don't debate coding standards beyond the 2 pizza rule. No more than 8 engineers per service.

Once I lived in an apartment with a safe that had been locked open. It was a giant, heavy thing too large to move. The owners simply renovated the apartment around it.

Eventually I got bored and started playing with it. Since it was locked open, it was possible to start taking apart the door from the inside. Once the tumblers were exposed, I figured out the combination.

It was tremendous fun!

If anyone here is in a similar situation, I recommend cracking the safe. Building the robot seems like a nice bit of mechanical engineering:

https://learn.sparkfun.com/tutorials/building-a-safe-crackin...

Or rather, was. At the time one could either:

- write a sax event based parser that scaled but was low level

- use a DOM parser with a fairly convoluted API. The combination of attributes and children makes for wordy accessors.

Both YAML and JSON provide formats that more readily deserialize into native map / list / string / number types which at the time was quite convenient.

The XML bloat is on the processing side.

Who needs foreign keys... or relations?

Documents do well for a wide variety of applications ;-)

YAML predated / was concurrent with JSON. Both were in reaction to the bloat of XML.

Also css, early on.

Anybody remember LAYER tags?

Waterfall isn't an engineering methodology, it's an investment methodology. Engineering will mirror the interests of the capital. And sometimes capital wants to build the same thing again for a "safe" return, rather than building something new for a transformative return.

IMHO it's not actually a safe investment strategy, but I understand where it comes from.

There's 6 channels, and I think a high / low setting to get a total of 12.

With indoor positioning, the anchors aren't positioned as precisely as GPS satellites, nor do they have the same quality clocks. Thus time of flight is done with a call and response per device.

It was hard to setup positioning for more than 1x device... remember that 1x device is range finding to 4x anchors.

Am sure these problems can be solved, but in the near term think this is more about precise distance rather than position.

babel solves the problem of polyfills in a more elegant manner.

UWB scales poorly. There's a limited number of channels. Ad hoc range finding requires a call and response.

However.

The range finding is accurate.

So long as one is dealing with a few devices, it is incredibly effective. It's not going to be GPS for the house, but it does make proximity triggers reliable.

First off, keep in mind that even scaling a broadcast publication can be complex. Sure one can bolt on fastly or s3 but cache invalidation is never a simple problem.

Next "power users" as others put it are not a single set of editors. It's more of a social network with multiple levels of trust. The idea of a wiki is that all users have write access, even if those changes are moderated to have different levels of latency.

Of course there are ways to engineer the system, but at that point one is, well, engineering a system. And WMF is doing so on a shoestring compared to other comparable levels of traffic.

Is WMF creating new paradigms of computing? Probably not. But they are doing a good job, IMHO.

The proportion of read/write may skew towards reads, but Wikipedia still is an application where any user can create state visible to all other users. It's not as simple as this comment makes it out to be.

This is a disturbing article to read after watching my son struggling to learn to read.

Managing state is hard. OOP expects state. OOP can make things harder than necessary.

Languages with both first class functions and class semantics are nice, because they allow you to choose the right tool for the job.

Inheritance is way overrated as a tool though. Great for the bouncer ball sprite exercise, otherwise a bother.

It's best to consider YAML in it's appropriate context as a better XML fragment. The ideas in YAML evolved into JSON which is preferable today.

However at the time, a tree data format that deserialized into native types was quite useful. The alternative was writing event based SAX parsers, or incredibly verbose XML object apis.