patsplat

6 ms·

1.
by patsplat 4mo ago
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.
2.
by patsplat 5mo ago
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.
3.
by patsplat 5mo ago
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/
4.
by patsplat 5mo ago
Physical objects should be rounded, virtual windows should be square. I will die on this hill.
5.
by patsplat 8mo ago
I recommend dialing in a mill before claiming there’s no craft in CNC.
6.
by patsplat 8mo ago
When LLMs transition from predatory pricing to rent seeking, the enthusiasm will evaporate.
7.
by patsplat 8mo ago
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 ar
8.
by patsplat 3y ago
You are correct, I think he was talking about a different device: https://www.fda.gov/news-events/press-announcements/fda-clea...
9.
by patsplat 3y ago
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&#x
10.
by patsplat 6y ago
Note that one big database can decimate productivity as well.
11.
by patsplat 6y ago
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?
12.
by patsplat 7y ago
It works extremely well for ux development ;-)
13.
by patsplat 7y ago
He's been slightly famous for technical writing for a long time https://en.m.wikipedia.org/wiki/Eric_S._Raymond
14.
by patsplat 7y ago
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.
15.
by patsplat 7y ago
Don't debate coding standards beyond the 2 pizza rule. No more than 8 engineers per service.
16.
by patsplat 7y ago
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 lock
17.
by patsplat 7y ago
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
18.
by patsplat 7y ago
The XML bloat is on the processing side.
19.
by patsplat 7y ago
Who needs foreign keys... or relations? Documents do well for a wide variety of applications ;-)
20.
by patsplat 7y ago
YAML predated / was concurrent with JSON. Both were in reaction to the bloat of XML.
21.
by patsplat 7y ago
Also css, early on. Anybody remember LAYER tags?
22.
by patsplat 7y ago
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 th
23.
by patsplat 7y ago
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
24.
by patsplat 7y ago
babel solves the problem of polyfills in a more elegant manner.
25.
by patsplat 7y ago
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
26.
by patsplat 7y ago
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 edi
27.
by patsplat 7y ago
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.
28.
by patsplat 7y ago
This is a disturbing article to read after watching my son struggling to learn to read.
29.
by patsplat 7y ago
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
30.
by patsplat 7y ago
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

More ›