I’ve had that kind of reaction - on rebases also - and most times it was in fact a code smell pointing to a case of spaghetti code.
If you get to the point that you fear upstream merges/rebases into your WIP, stop for a second and ask yourself if maybe that might be an issue with too much interpendencies inside the code itself. Code should be as close to an directed acrylic graph as possible. (doesn’t count, I was not speaking of git! :b )
Given this trend, GPT 5 or 6 will be trained on a majority of content from its previous versions, modeling them instead of the expect full range of language. Researchers have already tested the outcome of a model-in-loop with pictures, it was not pretty.
You mean Microsoft will recoup the cost of unbundling by charging more per product compared to the previous bundle, given that it’s now different products?
'cause at work the powers that be has gone all-in on MS and this decision won’t change a bit their “strategy”.
Forewarning : ops here, I’m one of the few the bosses come to when the “quick code” in production goes sideways and the associated service goes down.
soapbox mode on
Pardon my french but that’s a connerie.
Poorly written code, however fast it has been delivered, will translate ultimately into a range of problems going from customer insatisfaction to complete service outage, a spectrum of issues far more damageable than a late arrival on the market. I’d add that “quick and dirty code” is never “quick and dirty code with relevant, automated, test coverage”, increasing the likelihood off aforementioned failures, the breadth of their impact and the difficulty to fix them.
Coincidentally , any news about yet another code-pissing LLM bothers me a tad, given that code-monkeys using such atrocities wouldn’t know poorly written code from a shopping list to begin with, thus will never be able to maintain the produced gibberish.
That’s a lot of words for “I’m too lazy to master the most essential tool of my professional life and keep it updated to my requirements”.
If you don’t want to do it, feel free to pay an Ubuntu support subscription, open a ticket, and get back to work. As you said: you should be working on your problem instead of whining. Or maybe you earn more whining?
There’s a saying that goes like that: “To a bad workman, there’s always bad tools.”
Modular’s Mojo might interest you - it just popped up in my news feed, it’s entirely a coincidence.
Others has answered the specific cases where TTM is paramount.
When time is less of an issue, in my experience it’s in no particular order a mix of:
All in all, instead of short term profit, it’s a lack of not-so-long term vision and engagement from everyone involved. They just don’t care.
Yeah, I’m the one in charge of fixing the mess, why you ask?
Your question is a bit vague but it looks to me that what you want is some sort of expert system of inference engine.
There might be some open source solutions, and there’s always the GNU Prolog language that might suit your needs.
I suspect that you won’t get a graphviz structure out of it though.
EOL of version 7 is next year in June, you got a nice pile of work here!
And *nix shells a perfect example of the KISS principle.
On behalf of garbage, I loudly protest on this attempt to assimilate it to Powershell.
A merge from upstream once a day, at the beginning of the day.
I’m working on a DevOps setting, and even though we’re a small team, we have about two to three changes going through the pipeline a day.
If you keep your fork too long without syncing, it just get more complicated to merge, and more importantly if you need help from the upstream change author they’ll have moved on to another subject and the change won’t be as fresh in their mind as if you had merged the day after they pushed it.