Pangram: fully AI generated, confidence high.
2. This one works. It's peer-reviewed.
This isn't even particularly good slop. If you can't identify this, we're entering a not so good space.
Anyhow, I'd recommend you roll away from this hill because it's really not worth dying on. Common sense and peer reviewed slop detection aren't working for you. I provided my opinion and backed it with evidence. That's why I posted what I did.
AI generators do a better job of conversational output than traditional language translators (although there is a risk that if you can't read the target language as a non-native speaker, it can distort or destroy the message).
I actually find it an insulting imposition on my time. I don't think this is unreasonable or even unusual.
So much that. No one likes "drive-by advice" - if you want something to be fixed, there should be a person responsible for that. Maybe it's you doing all the work, or you convincing management, or management who is asking for an advice... But if you are just saying "we should fix FOO by doing this and that" with no plans as to whom those "we" are, it's only annoying.
(Although, it's worth noting that in this era of more remote work, perhaps a little more read-in and context is useful to avoid burning time on back-and-forths that used to take minutes in front of someone's desk but can now take hours over Slack).
If I'm not going to change something, I'd rather not talk or give opinions.
Related: https://strangestloop.io/essays/things-that-arent-doing-the-...
Talking at the right place at the right time on the right topic is.
Until the desired outcome is defined and documented, holding off on solutions and effort would benefit both parties.
if they do, there's an equal chance that you either didn't understand the situation to begin with, or you work in a team with poor leadership and strategy. learn from the former, leave the latter.
giancarlostoro•30m ago
There's always way more work to do and those key enhancements or research stories that could improve everything get deprioritized.
leetrout•21m ago
> Tech Debt Thursdays
Yes, "Fix it Fridays" is another alliteration.
Have you ever heard the phrase "man your battle stations"? Turns out in the US Navy there is also "cleaning stations" and there is a call for all hands to cleaning stations on the regular. I have proposed something similar on a few teams I've been on. Daily won't work and quarterly is too long. The problem is the sprawl that comes from cleaning up things that have unintended side effects. But yes, paying the interest on the tech debt needs to be normalized across our industry.
https://www.navy.mil/Press-Office/News-Stories/display-news/...
https://www.youtube.com/watch?v=fyJH8VbFE6g
shadowgovt•14m ago
Fiscal debt is a one-dimensional number that becomes higher or lower from some offset, but it can't change direction. There's no "complex numbers debt."
But software engineering is only one-dimensional if your problem domain is so constrained that the only roadblock to execution is time-at-keyboard, and that's rarely the case in most software (especially startups and hacking). I've too often seen that debt just "evaporates" when the company pivots or the entire system is replaced by another system or rendered completely irrelevant to continue accepting the notion that debt works as a metaphor. Even in the small, too often I've seen things flagged as, for example: "debt - we should consolidate these two pipelines on top of a smaller set of helpers" only to see the use of the pipelines diverge over time such that it turned out to be a great first step to keep them separate and duplicated.
Sometimes things to be improved / cleaned up are obvious, but cleanup assumes taking disorder and making order out of it, and that requires us to know what order even looks like.