chipdart

12 ms·

121.
by chipdart 2y ago
> That would take forever - far too long in our case. It doesn't. It just does not force everyone to rush both clients and services to prod without having a fallback plan. Also dubbed as competent engineering. > We have to be abl
122.
by chipdart 2y ago
> I've witnessed having those packages and versioning only lead down to unmanageable dependency hell. There is no dependency hell. Your consumers allocate work effort to migrate to the latest version. This is work you would still ha
123.
by chipdart 2y ago
> So you might have to update everything that references your changing API to use the new version.... That's how versioning works. - You allow legacy applications to consume the legacy interface, - you provide a new interface to the
124.
by chipdart 2y ago
> Surely the git SHA is "a form of versioning", isn't it? If you're consuming a module from a git as a submodule, yes.
125.
by chipdart 2y ago
> think most people who are poor who voted for Trump expect him to eliminate unnecessary rent-seekers (...) You mean people vote for a slum lord who is lauded by billionaires expecting and who funelled Whitehouse budget to his own hotel
126.
by chipdart 2y ago
> There is a link in this thread that I'll never find that refutes your point. It quotes the bill even. There isn't. Go read the bill. Hell, the bill was co-authored by republicans, and even approved by some republicans after T
127.
by chipdart 2y ago
> Versioning introduces a big maintenance cost, both on the side of the developer of a service and on the consumer side. Not really. From the producer side it only requires that a) you do not break your contract, b) when you need to brea
128.
by chipdart 2y ago
> API contracts are not free Yes, they are. They are as free as adding a new endpoint. > and for things that were not decided to be an API and or a contract an absolute waste of time. You're talking about integrating multiple pro
129.
by chipdart 2y ago
> Preserving contracts has a significant cost. Not really. You just need to break out a new version when you put out a breaking change. This can mean anything between duplicating the code that implements your interface to then apply a ch
130.
by chipdart 2y ago
> Sort of; at medium scale you can blue/green your whole system out of the monorepo (even if its say 20 services) in k8s and flip the ingresses to cut over during release. That's overall a bad idea, and negates the whole point
131.
by chipdart 2y ago
> My only counter argument here, is when those 4 things deploy independently. This brings us to the elephant in the room: monorepo strategies are just naive and futile attempts at fixing the problems created by an absolute lack of suppor
132.
by chipdart 2y ago
> As soon as you split 1 repo into 2 repos you need to start building tooling to support your 2 repos. No, not really. If you're talking about projects for modules and components, all you need is a versioning strategy and release co
133.
by chipdart 2y ago
> I prefer microservices/microrepos _conceptually_, but we had the same experience as your quoted text - making changes to four repos, and backporting those changes to the previous two release branches, means twelve separate PRs to
134.
by chipdart 2y ago
> IMO, this is a huge quality of life improvement and prevents a lot of mistakes from not having the right revision synced down across different repos. This alone is a HUGE improvement where a dev doesn't accidentally end up with on
135.
by chipdart 2y ago
From the article: > Let’s also remember that reviewers aren’t always right—even when the majority opinion disagrees with the code author. After weeks (sometimes longer) spent tackling a problem, the code author is usually the most qualif
136.
by chipdart 2y ago
> We were talking about dev enviroments on desktops, not independently scalable components. Your dev environment is expected to mimick your production environment, not the other way around.
137.
by chipdart 2y ago
> The border deal provided amnesty that is clearly NOT in the interests of uneducated and poor citizens. You should inform yourself about the bipartisan border bill that Trump killed at the last moment. The "amnesty" thing only
138.
by chipdart 2y ago
> In part, maybe. And at the very end of the list of proposal, (...) Not in part. And now you voted on the guy whose only concrete economic policy is to massively drive up inflation by imposing tariffs.
139.
by chipdart 2y ago
> Closing border, halting illegal immigration, mass deportations - these are massively net positive for US citizens who are uneducated and poor. Migrates are competing with them for jobs, housing, social services, all resources. If that
140.
by chipdart 2y ago
> Still refusing to listen to us plebeians. I can't afford groceries. I'm not looking for a scholar-bureaucrat reframe of my problem. I'm looking for a solution. What solution do you expect from Trump?
141.
by chipdart 2y ago
> To give credit where credit is due, Trump successfully switched the Republican party away from the being the party of expansionist war. That's mainly because Trump is a Russian asset and it's in Putin's best interests to
142.
by chipdart 2y ago
> Given the modern hiring practice of "can you pass Leetcode," and "can you memorize and regurgitate how to architect a link shortener," yes, yes I do. You are contradicting yourself. If there's anything that req
143.
by chipdart 2y ago
> This is a bad idea. Not really. It all depends on what are your needs. > It defeats a major feature of the jvm. You're confusing things. Just because Java addressed the deployability problem for Java applications before contain
144.
by chipdart 2y ago
> I think nobody really talks about this, but unless you have a docker-compose.yml that includes everything you need for local development (...) Is this a problem? I mean, in this scenario docker compose serves two main purposes: launch
145.
by chipdart 2y ago
> How do you do that without first running all the services (...) Why do you need to run all services in isolation to be able to troubleshoot and isolate a problem?
146.
by chipdart 2y ago
> Only if you cannot change one service without changing the other simultaneously. Not true at all. You're conflating the need for distributed transactions with the definition of microservices. That's not it. > Multiple serv
147.
by chipdart 2y ago
> If the microservice has dependencies on other services it is not a microservice. You should read up on microservices because that's definitely not what they are not anything resembling one of their traits.
148.
by chipdart 2y ago
> You don’t have to test them all end to end before merging a PR. You have to test the changes you want to push. That's the whole basis of CI/CD. The question is at which stage are you ok with seeing your pipeline build. If you
149.
by chipdart 2y ago
> Your whole argument boils down to "don't write shit software" (...) No. My whole argument is open your eyes, and look at what you're doing. Make it make sense. Does it make sense to launch 50 instances locally to be
150.
by chipdart 2y ago
> This is how you get to "I wrote to the spec, it's your problem that clicking the button doesn't do the thing". No, not really. You only find yourself in that spot if you completely failed to do any semblance of inte

More ›