couchand

38 ms·

511.
by couchand 5y ago
I'm not sure what distinction you're drawing. Continuous integration is entirely synonymous with trunk-based development. It's true that as an industry we've overloaded the term Continuous Integration to mean build serv
512.
by couchand 5y ago
CI should be sufficient review for most code changes. Manually review architecture and design, but automatically verify implementation.
513.
by couchand 5y ago
> Good service gets good tips. This makes intuitive sense but empirically is simply not true. Tipping is far more correlated with sex and race discrimination than individual performance.
514.
by couchand 5y ago
> Will the energy remain in the crypto space if the crypto markets fall victim to the very thing they were created to prevent? Yes, because the energy in the cryptocurrency space is based not on rational analysis but religious fervor. T
515.
by couchand 5y ago
> I never quite get the reasoning behind changing box-sizing. The relevant section from Every Layout is a great explainer: https://every-layout.dev/rudiments/boxes/
516.
by couchand 5y ago
This article links directly to the one you linked to and explained why it is no longer relevant. I cannot fathom why the sibling has been killed to death, they are objectively correct.
517.
by couchand 5y ago
The Blichmann BeerGun (v1 -- I'm sure v2 is fine but it's not the same). It does exactly what it is supposed to. It's better than the "pro" tools, despite being marketed to homebrewers. It always reliably fills bott
518.
by couchand 5y ago
This isn't about perfect vs. good, though. The PR as initially written was unsound. The maintainers worked to help point out the deficiencies. The author gave up and wrote a blog post rather than finishing it.
519.
by couchand 5y ago
To bring it back to the article, this really seems like one of those "get it in and run away" cases. Or to be a bit more accurate, run away before getting it in... The author made a number of comments on the PR about how they exp
520.
by couchand 5y ago
I've found Rust programmers to be eminently pragmatic. The economics of bugs have been clear for decades: it is orders of magnitude more expensive to find and fix bugs after they've been shipped.
521.
by couchand 5y ago
If you'll believe it, here in 2021 the state of New York passed a law with "marihuana" (sic) in the name!
522.
by couchand 5y ago
If the code was buggy, fix the bugs. If the code was truly redundant, you could delete it. I suspect you meant more that it was repeated in several places, in which case, of course refactor it to be more DRY. If you can write an abstract
523.
by couchand 5y ago
Found it! https://docs.rs/opentelemetry/0.16.0/opentelemetry/trace/ind...
524.
by couchand 5y ago
Sibling already pointed it out, but it's worth clarifying: IndexedDB is most definitely NOT and in-memory database.
525.
by couchand 5y ago
Well, that hypothetical OLTP database almost certainly has many concurrent clients, right? Your single-threaded JavaScript app is not going to be generating the same usage pattern.
526.
by couchand 5y ago
Something basic that's missing from this tutorial is instrumenting Futures. The tracing crate (which I believe can export to an OpenTelemetry backend) has tracing-futures for this. Is there something similar for the opentelemetry cra
527.
by couchand 5y ago
I've never seen .NET code that has magic properties hiding expensive operations, though my .NET experience is admittedly limited. Is that idiomatic?
528.
by couchand 5y ago
> Another way to look at it is you just removed 300 lines of buggy redundant code into one line that does exactly the same thing but without all the fuss. And now that your code is so small you can understand it better, and test it. Mayb
529.
by couchand 5y ago
I think the term is "isomorphic", as in having a single form.
530.
by couchand 5y ago
> JavaScript allows getter/setter methods that can update the DOM when a value changes; this includes before/after and around-like methods that can integrate AJAX calls in a VARAIBLE name. e.g., you access the variable and an A
531.
by couchand 5y ago
Ha! Then butter your pan! Best of luck to you.
532.
by couchand 5y ago
Far too many promising open source projects have disappeared because the benevolent dictator lost interest and disappeared without leaving an empowered community. Far too many promising open source projects withered and died because the no
533.
by couchand 5y ago
They do suggest that the next mod team spend more time recruiting...
534.
by couchand 5y ago
These "internet activists" you spend so much effort maligning are simply reminding you that there is a human being on the other side of that screen. I'm not inside the Linux developers' world, but from the outside it see
535.
by couchand 5y ago
It is possible for a message to have an intended audience and still be viewable by others...
536.
by couchand 5y ago
Then downvote. Flagging an article you simply disagree with wastes the moderation team's time.
537.
by couchand 5y ago
Ive found that a buttered pan produces dark brown crispy splotches. An unbuttered pan makes a nice, consistently amber and fluffy cake.
538.
by couchand 5y ago
They didn't send you a personal e-mail. They made a PR changing their team status to "alumni" and included the requisite justification in the PR message.
539.
by couchand 5y ago
It's our industry that's getting old. You used to be able to start a big project like a compiler or a browser and have some hope of producing a functional result "organically" (for lack of a better word). But we'v
540.
by couchand 5y ago
Perhaps this message was not written for you?

More ›