spion

50 ms·

421.
by spion 4y ago
How did you go about achieving that identity goal?
422.
by spion 4y ago
Why would code running on a computer be unable to become sentient?
423.
by spion 4y ago
Sums are tagged unions, whereas unions are more general. Given the types T1 and T2, the union type `U = T1 | T2` includes all values of type T1 and values of type T2. A tagged union on the other hand is a new type which does not accept valu
424.
by spion 4y ago
If you're looking to get into the k8s space Go would be the way to... go. Purely as a language, Go is worse than TypeScript by a lot (yes, even with generics), yet has a really well made standard library that more than makes up for it
425.
by spion 4y ago
It depends. If you do server-side rendering with something like nextjs, then its quite a lot of code. With trpc you can share types without going through an intermediary schema language ( https://trpc.io/ ) although I think i
426.
by spion 4y ago
I was keeping a list at a previous company: - default text size is too small, text block widths are often not constrained enough getting the "slashdot unreadability effect" - 0.5s+ lag when clicking any textbox - 1s+ lag when cl
427.
by spion 4y ago
How is that different in a monorepo? Would you be tasked in implementing the changes for those teams yourself? If so, why not just do that as PRs in their repos?
428.
by spion 4y ago
> Splitting your code over many repositories massively increases the cost of refactoring, making it that less likely that your system will be "well factored" The project should stay a full monolith until the factoring is more c
429.
by spion 4y ago
Why would a complex dependency update be faster in a monorepo? In my experience the biggest savings are for simple updates that happen acorss multiple repos - when the update itself is complex, the extra time to make multiple PRs is dwarfed
430.
by spion 4y ago
We already have tools that handle this for us for OSS libraries, such as dependabot etc. Good factoring can probably be quantified too: dependency chains should be shallow and graph connectivity should be low. The more dependants a module h
431.
by spion 4y ago
Its important to avoid deep dependency chains when doing this, yes. I usually recommend a "framework" multi-package repo and then multiple "application" / "service" repos. I like having examples, even cont
432.
by spion 4y ago
For that particular article, I would respond with the following: 1. I don't see how this is a problem specific to polyrepos. Have an "open PRs" link in the onboarding handbook that gives you a view of pull requests from all r
433.
by spion 4y ago
I've worked with both models, and the monorepo model has been far more demanding in terms of time and resources to maintain as you push past the limits of the available tools one by one. Standard build tools go out of the window almost
434.
by spion 4y ago
If you have an issue handling tech debt due to PMs, you'll have that problem with other tech debt too; typically solved by having a better process to handle it
435.
by spion 4y ago
I think this article clearly shows that the effort of handling a monorepo is way higher. If you have a good process for external dependencies you can apply that to internal. If you don't have a good process for external dependencies a
436.
by spion 4y ago
Changes will be handled just like external library updates.
437.
by spion 4y ago
We know how to do that. Versioning, deprecations etc. We do that with all external dependencies.
438.
by spion 4y ago
That can be handled with alerts and deprecations just like any other library dependencies
439.
by spion 4y ago
A well factored system should not have cross-project changes. Individual projects should be able to upgrade dependencies separately.
440.
by spion 4y ago
Yes they actually document which bit is what > Get the source element type of the given GEP operator Notice the relentness repetition that provides precision and clarity? I now know the argument GEP is a GEP operator. Might seem redundan
441.
by spion 4y ago
Don't worry, I really enjoy being called dumb and ignorant. Its truly the best way to make me stop and listen to the other side so I can find out what my mistake was.
442.
by spion 4y ago
Why should I be ashamed by pointing out poor library documentation practices? > Those type variables CAN’T be named anything better because they could be absolutely anything at all, that’s the point of generic types. I was talking about
443.
by spion 4y ago
Having petabytes of stats doesn't mean the interpretation of those stats is any good. The retention for your web app might suck, for example, because you're constantly showing popups to the users telling them to switch to the mobi
444.
by spion 4y ago
I'm not sure this will help solve any of our problems. Theoretically, there would be no more need for compilation tools after this change is implemented. In practice, lambdas need to be bundled, frontends still need to be bundled and r
445.
by spion 4y ago
> Right... Like the doc of the regex match function in Rust is useless because it doesn't explain regexes. https://docs.rs/regex/latest/regex/struct.Match.html At least they name their type variables:
446.
by spion 4y ago
> I don't feel like you are approaching this from a fair point of view so I will stop replying. Can't convince people who don't want to be convinced. You asked what's wrong, I assumed you'd like to know what I th
447.
by spion 4y ago
Oh the overview page is even worse for readability _1 :: Lens' (a,b) a is used immediately after set :: Lens' a b -> b -> a -> a which completely messes with anyone who's mind works in a way that makes
448.
by spion 4y ago
Documentation for people that already know what the thing is is called "useless documentation". Its not within any reach whatsoever. The overview isn't linked anywhere in Setter. Rule of writing documentation: if you're
449.
by spion 4y ago
Here is the documentation I would write for a function like this, in a normal language: {-| Given `Conversion` options and a Dhall type `ExprX`, try to convert the JSON value `Value` to a Dhall expression of the specified type.
450.
by spion 4y ago
Oh the documentation of Setter is fun: https://hackage.haskell.org/package/lens-5.1.1/docs/Control-... Absolutely nothing explained whatsoever. Yup, sounds like like the typical, familiar Haskell experience o

More ›