julik

11 ms·

121.
by julik 2y ago
I am well aware of those challenges, but I believe for the purposes I need it for it will work just fine.
122.
by julik 2y ago
There is another that is fairly intuitive for a Mac person: tap-and-hold to get a contextual menu. Shame they have hidden it under some kind of "haptic feedback" thingamagig.
123.
by julik 2y ago
Well, hooking into system undo is tricky as there still seems to be no native web platform thing for that. I see all kinds of things like https://github.com/samthor/undoer but the article was about the foundation, rath
124.
by julik 2y ago
This is absolutely spot-on. Just last week, I have experienced at least 3 major issues because of "experimental" features getting pushed haphasardly. A much more complex issue is that A/B testing frequently causes feature int
125.
Writing a tiny undo/redo stack in JavaScript(blog.julik.nl)
170 points by julik 2y ago|69 comments
126.
by julik 2y ago
At this point in time this is absolutely a "people and process" problem. But also the process that is there has been excercised and is known to folks you may hire. Trying to come up with less of it (or with a different version of
127.
by julik 2y ago
It is incredibly pertinent. Even with the 20+ years of web dev I sometimes get swayed with clickbait like "If you are not using <frontend tech x> you are behind the curve, you are missing out, nobody works this way anymore, you a
128.
by julik 2y ago
I wrote https://blog.julik.nl/2024/03/those-people-who-say-no in response to that Mastodon thread back when it was posted. I fully agree with the article. The problem, I believe, is that "getting off the trea
129.
by julik 2y ago
I think the issue here is mostly the background the CI setups came from. They were frequently coming from the "ops" part of the ecosystem, and some ops folks held some ideas very strongly back then (I heard this first hand): &quot
130.
by julik 2y ago
Seconded. Moreover... > as long as it is proper, maintainable code ...in an imperative language you know well and which has a sufficient amount of type/null checking you can tolerate.
131.
by julik 2y ago
The interesting part here is that if AWS docs state "We expect header X with request Y" the "compatible storage" implementors tend to add validations for presence of header X. In that sense it is tricky for them, but I w
132.
by julik 2y ago
I did, mea culpa!
133.
by julik 2y ago
Maybe I need to read more on this regression, you might be right.
134.
by julik 2y ago
The other option is not being overly strict with the data you receive from a client, especially when dealing with a protocol which is not a standard.
135.
by julik 2y ago
Even more so: treating a proprietary API as a standard but _also_ adding your own checks on top which crash the interaction "because it seemed more correct to you". No, you are not guaranteed a CRC and you are not guaranteed a Con
136.
by julik 2y ago
Seconded - it's also unnecessarily creative overvalidation on the part of the devs at those joints.
137.
by julik 2y ago
Requiring a header "just because you sniffed it to usually be there" is not Amazon being cynical, it's creatively-developing-overly-strict-checks. And it happens on the side of the S3-compatible service. If your service no lo
138.
by julik 2y ago
Sometimes people forget that the S3 API is not an industry standard, but a proprietary inspectable interface the original author is at liberty to modify to their liking. And it does, indeed, have thorny edges like "which headers are ex
139.
by julik 2y ago
Did I just officially see an 18v battery drill that is not much special and is more expensive than the most expensive Festool 18v drill? I am impressed. What is this brand, if I may inquire?
140.
Musings on Module Registration (and Why It Could Be Better in Rails)(blog.julik.nl)
7 points by julik 2y ago|0 comments
141.
The Surcharge of Big Tech(blog.julik.nl)
2 points by julik 2y ago|0 comments
142.
by julik 2y ago
Or, what happens sometimes, a "team lead or someone" was replaced with a pack of freshly appointed team leads, with nobody being positioned to "break ties" with them and with an explicit ban on any sane engineering guida
143.
by julik 2y ago
We haven't forgotten anything - rather we were forced to remain silent. https://blog.julik.nl/2024/03/those-people-who-say-no I may do a writeup on how the mentioned things are very indicative of a certain or
144.
by julik 2y ago
With any decent host runtime, as it were.
145.
by julik 2y ago
It is much cheaper, because you won't have roundtrips or requirements for the availability of extensions on the database server end. It's really a very very sweet capability that SQLite is able to provide exactly because it is hos
146.
by julik 2y ago
We actually use a couple Ruby UDFs with BigQuery, deployed as Google Cloud Functions. Works pretty well.
147.
by julik 2y ago
The user-supplied busy handler has been available for a long while, it's just that the Rails connection adapters did not quite use it right. Indeed, there is elevated interest in SQLite these days.
148.
by julik 2y ago
This. We did discover, however, that Postgres will, in fact, swallow a UUIDv7 just fine. After having written that library :-)
149.
by julik 2y ago
> Why not use UUIDv7 if you want time-ordered UUIDs? It is our flavour of NIH, that said - Tou has a finer-resolution timestamp. We also didn't do our homework right and assumed the v7 UUIDs won't be accepted by Postgres becaus
150.
by julik 2y ago
OP here. Yes, it is, except that the only builtin flag it offers is `deterministic` - if you want to also use "directonly" you probably will need the same OR trick.

More ›