barumi

5 ms·

1.
by barumi 6y ago
Just because a company managed to do stuff a certain way that does not mean that way is the right way or adequate or good. Enough with this cargo cult bullshit approach to technical problems.
2.
by barumi 6y ago
>>I think this only solves the problem for the API owner, not the consumer, right? The only problem this solves is their need to sell their product. This so-called "schema-driven development" approach was already tried in th
3.
by barumi 6y ago
> That freedom of Linux comes at a cost that people aren't paid to take care of the level of details other OS have. What do you mean "take care of the level of detail"? I can download Debian right now, install it on hardwa
4.
by barumi 6y ago
> The amount of weird issues is about constant. But linux is free both as in free beer and in free speech, windows required you to pay the Microsoft tax to use, and lastly macOS required you to pay a premium on hardware.
5.
by barumi 6y ago
> While those prices seem pretty good for first world countries, many of the people in my country don't make more than $1000 per month, so it'd still be a substantial investment. That price is just the benchmark for that specif
6.
by barumi 6y ago
> VIM is ideal for people who find it worthwhile to spend the time building their configuration out. I've been using VIM for over a decade and currently my customized config consists of a half a dozen tweaks, such as YAML-specific s
7.
by barumi 6y ago
> But in academia, and I suppose in a criminal gang, everyone has the same skillset. PhDs are notionally being trained with the specific abilities necessary to become a professor. They really aren't. First of all, scientifically spe
8.
by barumi 6y ago
> Because it's a stupid statement when there are companies that are making more money (...) Again, that makes zero sense and is another blatant red herring. If the discussion is about taxing WFH to support vulnerable jobs, it makes
9.
by barumi 6y ago
Sounds to me like taxing WFH fits the description of "ruining everything good with taxation". I mean, there's already a progressive income tax. Why should society create incentives to commute to work?
10.
by barumi 6y ago
From the article: > But when I showed off my build on /r/homelab, reddit’s homelab subcommunity, they mocked me as a filthy casual because I used consumer parts. The cool kids used enterprise gear. It should be noted that you c
11.
by barumi 6y ago
> On the other hand, with marriage, it's generally (hopefully) safe to assume that both parties trust each other fully before entering into the agreement. Whether and how that plays out in practice is another story, but IME, very fe
12.
by barumi 6y ago
> They can't help but penalize change. I don't believe it has anything to do with change. I believe it has everything to do with isolating a vulnerable subset of society to exploit them. Divide and conquer. They want a bigger c
13.
by barumi 6y ago
> Examples of large, modern societies flourishing without the use of taxation? This is a disingenuous red herring. It's one thing to claim that some amount of taxes to finance public spending can be benefitial to society. It's
14.
by barumi 6y ago
> I would gladly contribute a larger share of my income as taxes to ensure my community doesn't suffer (...) I would too, which is why I vote with my wallet and buy local, even at a premium, whenever I can. However, income tax is th
15.
by barumi 6y ago
> Deutsche Bank placed number one in money laundering. How does that ad hominem refute or support the claim that remote workers should be taxed to subsidize vulnerable jobs?
16.
by barumi 6y ago
> Even though they're technically different concepts, I've found in practice they're almost always coupled together. Not really. Event sourcing is typically implemented with CQRS, mainly due to how ES relies on streams of
17.
by barumi 6y ago
>>I'm saying that REST also separates reads from writes in almost identical capacity. Not really. REST just models everything as resources that are targetted by requests. REST states nothing about how rewuests should be segregate
18.
by barumi 6y ago
CQRS+ES is more about event sourcing and not as much about CQRS. The hard part about the scheme is the CAP theorem stuff, not how operations are segregated into commands and queries.
19.
by barumi 6y ago
> The biggest drawback I've seen to CQRS - particularly in an event driven architecture - has been increased complexity, usually in exchange for increased scalability. I fail to see how CQRS is a factor in increased complexity. Afte
20.
by barumi 6y ago
> A dog whistle for what? There's an awful lot of cagey presumption going on in every reiteration of this claim. I'm not a US citizen nor I ever set foot in the US, and even from afar the quasi-fanarical displays of support for
21.
by barumi 6y ago
> There is a difference between being in bad taste and being illegal. It's called "letter of the law" vs "spirit of the law", Purposely violating the principle of the law by abusing loopholes, and proceeding to c
22.
by barumi 6y ago
> "The intention behind the rules" is a thing that lives in your imagination. No, it's pretty straight-forward. There's no healthy democracy that believes that a blatantly partial and biased individual counting the vo
23.
by barumi 6y ago
> The main feature of git flow is having multiple redundant branches for no reason. Namely a separate develop and master. This statement is simply wrong and ignorant. The reason why mainline and develop branches exist is due to the fact
24.
by barumi 6y ago
> The author of "GitFlow Considered Harmful" put out a simpler workflow that achieves all the upsides of GitFlow with none of the downsides: I see no relevant difference between that workflow and GitFlow, besides the rebrandin
25.
by barumi 6y ago
> I don't know what you think git-flow is, but a linear history it is not. Your statement makes no sense at all. Gitflow is a workflow. What do you believe it's supposed to be? It's irrelevant how you see commit histories,
26.
by barumi 6y ago
> It's not git-flow, as all commits are rebased on top of master to make the history of master linear. I fail to see how that is relevant. I mean, the only possible impact that has is if individual commits within a feature branch ar
27.
by barumi 6y ago
> No interviewer has demonstrated anything but perfunctory interest in my open source work, popular or not. In he past when I did candidate screening I used floss work extensively to evaluate a candidate. To me, personal projects are an
28.
by barumi 6y ago
> Seems pretty standard to me. Anything notable here? I agree, it's pretty vanilla git usage. I was curious to see any insightful take of whimsical twist, but it boils down to a basic take of good old git flow, which is git 101 for
29.
by barumi 6y ago
My take is that this is a "correlation does not imply causality" case. It was possible to positively identify a reinfection because the two infections were due to different strains. That was just the means of positively and object
30.
by barumi 6y ago
> This would contradict the one-fits-all immunity argument. I don't think that argument is being made at all. In fact, you only need to consider that the max efficiency that's advertised is 90% to acknowledge that this vaccine

More ›