vlfig

8 ms·

1.
by vlfig 8d ago
Love the enthusiasm but I don't buy the two macro tailwinds he's counting on: ever larger monorepos & more centralisation. What you version together you build and release together, and there are architectural tensions pushing
2.
by vlfig 2mo ago
But you still let the user put in the effort before revealing they'll have to sign up. Just be upfront.
3.
by vlfig 3mo ago
You're absolutely right, and I share the frustration. I'm thinking a possible solution to this signal-to-noise problem is to embrace the longitudinal view: instead of comparing each scan with the normal across the population compa
4.
by vlfig 5mo ago
You are not alone. https://en.wikipedia.org/wiki/Wu_wei
5.
by vlfig 6mo ago
Don't "let it" generate tests. Be intentional. Define them in a way that's slightly oblique to how the production code approaches the problem, so the seams don't match. Heck, that's why it's good to write
6.
by vlfig 8mo ago
Eminently doable, yes. Two notes: - I'm not convinced the graph is necessarily cyclic. Often two codependents are actually dependent on some common bits and otherwise independent. - this is essentially deterministic propagation of conf
7.
by vlfig 8mo ago
Next step: embeddings and similarity.
8.
by vlfig 11mo ago
I sanction this comment.
9.
by vlfig 1y ago
Although it isn't yet clear how much the brakes did actually brake, it is known they would never be enough. So the cable was a critical component and initial findings suggest it wasn't being verified as rigourously, thoroughly and
10.
by vlfig 2y ago
We shouldn't dismiss the theory of how to do things right just because it is common to do things poorly.
11.
by vlfig 3y ago
a Dhall configuration file will never: - throw an exception - crash or segfault - accept malformed input - produce malformed output - hang or time out in https://docs.dhall-lang.org/discussions/Safety-guarantees.ht...
12.
by vlfig 3y ago
Different requirements, different guarantees. Principle of least power. Have a look at https://docs.dhall-lang.org/discussions/Safety-guarantees.ht... .
13.
by vlfig 4y ago
Ban on cash: impose negative interest rates. CBDCs: all manner of restrictions to fungibility.
14.
ACM's "Research for Practice" Reboot(queue.acm.org)
1 points by vlfig 4y ago|0 comments
15.
by vlfig 5y ago
Sigh. Generally what happens is that: - Everyone is able to prove a transaction's correctness; - There's no way for a third party to track the contents of a transaction adversarialy; - there are ways for first and second parties t
16.
by vlfig 5y ago
Mostly yes. My advice on this topic is to read up on Liberating Structures, which I think are a level up. https://liberatingstructures.com/
17.
Solutions Story Tracker(storytracker.solutionsjournalism.org)
1 points by vlfig 5y ago|0 comments
18.
by vlfig 5y ago
A request for a synchronous form of communication is a request for your time. People should earn it first.
19.
A Primer for Decentralized Identifiers(w3c-ccg.github.io)
80 points by vlfig 5y ago|15 comments
20.
by vlfig 5y ago
Obsidian + GitJournal + NeuraCache. No-cloud (except for git, could be self hosted), local-first, plain data formats solution for note taking, knowledge organisation, text production and spaced repetition.
21.
by vlfig 5y ago
For a less romanticised, more practical resource on the topic, I recommend The Hitchhiker’s Guide to Online Anonymity https://anonymousplanet.org/guide.html (also, Monero > bitcoin)
22.
by vlfig 5y ago
Aside from the click-baity article, the actual report puts emphasis on the quality of the existing data about food waste. A bit of an "let's measure this first" attitude, which is a bit of a let down to me. "Food waste m
23.
by vlfig 6y ago
The version of the API and the version of the artifact that implements it are distinct, not the least because the artifact can implement several (major) versions of the API. Using tests across versions is a definitely a trick to consider bu
24.
by vlfig 6y ago
Base64 padding, probably.
25.
by vlfig 6y ago
Exactly this. One thing is to have (today) the same behaviour, another is to (forever) be the same thing.
26.
by vlfig 6y ago
Hah! Not seriously, no. > REST is a solid, simple, and powerful transport method and let's maybe do without CORBA moving forward. Chill. :-) The world agrees with you.
27.
by vlfig 6y ago
Author here. Thanks for reading. > * What build toolchains are suited to these arbitrary DAG arrangements? In general any CI/CD tool that allows for easy composition of jobs/pipelines, where versioned artifacts are a first-clas
28.
Microservices – architecture nihilism in minimalism's clothes(vlfig.me)
2 points by vlfig 6y ago|0 comments
29.
by vlfig 6y ago
I love the candor in your post but you're being too hard on yourself. Learn functional programming, gradually. You'll get there. I like to think I reverted a decade of brain damage inflicted by enterprise java development in three
30.
by vlfig 9y ago
If the main purpose is to document decisions on a project, not your journey as an engineer, consider using Architecture Decision Records — ADRs. Simple, to the point, live-with-the-code. https://github.com/npryce/adr-to

More ›