matijsvzuijlen

6 ms·

1.
by matijsvzuijlen 2mo ago
This is a nice idea but a lot of the OSM tiles show as blocked due to lack of a Referer.
2.
by matijsvzuijlen 4mo ago
Thanks, that makes sense. I actually just parsed aes as related to encryption without even considering how weird that was given the contect.
3.
by matijsvzuijlen 4mo ago
Yes, I will do that!
4.
by matijsvzuijlen 4mo ago
Why are all the parameters full words except 'labs'? I find it jarring because to me 'lab' is short for laboratory, not label.
5.
by matijsvzuijlen 9mo ago
I wrote one for my own use (on Linux): https://github.com/mvz/mdv
6.
by matijsvzuijlen 9mo ago
What made you decide to squash when merging instead of leaving the commits in the history so you can always bisect?
7.
by matijsvzuijlen 10mo ago
I worked on a project that used haml, and merge conflicts in the haml files were very hard to resolve due to the lack of any nesting info besides indentation. I think it's worse than, e.g., typical yaml files because the nesting is dee
8.
by matijsvzuijlen 10mo ago
If you already know k8s, this is probably true. If you don't it's hard to know what bits you need, and need to learn about, to get something simple set up.
9.
by matijsvzuijlen 1y ago
I can understand requiring 100% test coverage, but it seems to me that requiring a test file for every file is preventing your team from doing useful refactoring. What made your team decide on that rule? Could your team decide to drop it si
10.
by matijsvzuijlen 1y ago
What makes you think TDD assumes that? It sounds like the complete opposite of what TDD is about.
11.
by matijsvzuijlen 1y ago
For people who, like me, prefer to read the abstract first: https://www.arxiv.org/abs/2508.06471
12.
by matijsvzuijlen 1y ago
In such cases, I generally checkout main, do the side quest, and rebase my original branch on top of it. Then, I can just continue without waiting for the side quest to be merged. Depending on the situation, I may make a separate PR for the
13.
by matijsvzuijlen 3y ago
The idea is that --amend would be used before pushing the commit that it amends, and so before a reviewer ever sees the original commit.
14.
by matijsvzuijlen 3y ago
Linking to the abstract instead would have been nice.
15.
by matijsvzuijlen 3y ago
If you follow SemVer strictly, the version bump is not necessary unless the number of rerenders is part of the documented API.
16.
by matijsvzuijlen 3y ago
What could the frameworks do to make it more natural for inexperienced developers to do the right thing?
17.
by matijsvzuijlen 3y ago
This means having to keep these branches around cluttering up everything, and makes git bisect a lot more complicated.
18.
by matijsvzuijlen 4y ago
The format itself has several warts, like the ancestor list continuation syntax, or whether or not to add a backslash if you want a literal asterisk. The implementation lacks checking, so for example if you have some text between square bra
19.
by matijsvzuijlen 4y ago
Asciidoc starts out great but has a lot of surprising gotchas and complexities.
20.
by matijsvzuijlen 4y ago
Wasn't that Perforce?
21.
by matijsvzuijlen 4y ago
The result looks beautiful but there are too many surprising magical actions for my taste. E.g., I wonder how "Last year MIT handed out 104 degrees to wombats." would be rendered.
22.
by matijsvzuijlen 5y ago
Git has a built-in GUI for that. Just run 'git gui'. It's not pretty but it works.
23.
by matijsvzuijlen 7y ago
Item (f) in that same Article 6 can be applied to collect data without explicit consent: (f) processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests a