|
Richard Deeming wrote: (Try explaining the difference between "@" and "@" to your elderly relatives.) to the elderly? I know a bunch of people of my age that already is problematic for that
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
They need to do this regardless of folder. Too many malicious emails slip through the filtering and end up in inboxes.
|
|
|
|
|
We are launching our newest flagship model and making more capabilities available for free in ChatGPT. This one goes to 'o'
It was either that, or a quote from Office Space (that I'm sure you can guess, but that isn't kid sister safe enough IMO)
|
|
|
|
|
"O" might be non-KSS too.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Microsoft has improved the C# Dev Kit for Visual Studio Code (VS Code) with support, Aspire integration and easy SDK acquisition – but developers are complaining of “terrible quality”. But what do they know of C#
|
|
|
|
|
The question is... are those "improvements" in the way they are described in the dictionary or in the way they are described in the windows marketing handbook?
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Adding features is faster and easier in good code than bad code. "Faster, Pussycat! Kill! Kill!"
Beat that strawman!
|
|
|
|
|
Article wrote: Adding features is faster and easier in good code than bad code. No fvck Sherlock...
On the other hand... how fast will the good code be transformed into bad code by the additions?
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Old aphorism: quality, speed, content--choose two. But I'd say that's in the short term. In the long term, taking time to refactor extends a product's lifetime. Not doing so slows development to the point where it may even become unprofitable.
|
|
|
|
|
Now, Microsoft Word will use the ‘merge formatting’ option by default. They do listen to feedback (it just takes decades some times)
|
|
|
|
|
Kent Sharkey wrote: They do listen to feedback (it just takes decades some times) I bet the usual way is something that have annoyed a lot some manager lately...
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Unbundling Teams from Office has apparently failed to impress EU regulators. There's a lot they should face for Teams, but I'm not convinced antitrust is one of them
|
|
|
|
|
Yep. It's titan vs. titan in the EU. The complaint was brought by Slack, which is owned by Salesforce.
|
|
|
|
|
I can't say I'm crazy about this new, "compete via government" strategy companies have been using more often lately.
TTFN - Kent
|
|
|
|
|
Hey... at least they are making governments useful for something
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Time honored strategy of crony capitalists. It was "compete via government" that got AT&T the monopoly on telephone service in the United States.
|
|
|
|
|
Yeah, yay!? I guess?
Why don't they see about shutting down the fruit company that's cheated and robbed everyone blind for 30 years and set man's computing capability back 100? That'd be sweet.
|
|
|
|
|
Since ChatGPT dropped in the fall of 2022, everyone and their donkey has tried their hand at prompt engineering—finding a clever way to phrase their query to a large language model (LLM) or AI art or video generator to get the best results (or sidestep protections). Just let the computer do it
|
|
|
|
|
Quote: AI prompt engineering is dead What a speed... it looks like a google product.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Your statement reflects a philosophy that emphasizes the futility of worrying. Let's break it down:
"If something has a solution... Why do we have to worry about?": This suggests that if there's a solution to a problem, worrying about it serves no purpose. Instead of worrying, one should focus on finding and implementing the solution.
"If it has no solution... For what reason do we have to worry about?": Similarly, if a problem has no solution, worrying about it won't change the outcome. In this case, worrying is also considered futile because it doesn't contribute to resolving the issue.
In essence, your statement advocates for a mindset of addressing problems directly when solutions exist and accepting circumstances when solutions are beyond reach. Worrying, in either case, is seen as unproductive. It encourages a focus on action and acceptance rather than dwelling on uncertainties or difficulties.
|
|
|
|
|
And you needed an "AI" to find it out?
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Developers are still spending too much time on troubleshooting application performance issues, rendering them incapable of spending enough time on innovation and other productive work, new research has claimed. Nothing up this sleeve, nothing up that sleeve...
|
|
|
|
|
Quote: too much time on troubleshooting application performance issues The faster the hardware, the biggest and most numerous the crap in the apps that make that hardware go to the limit anyways.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
For the bigger dogs, Dynatrace seems to be something of a must.
I note that it is "performance" issues. Lots of times that may not have much to do with code. When it is to do with code it is probably going to be architectural where fundamental design flaws can be corrected and change the metrics considerably.
Some of this is people treating literally everything as preoptimization and relying on Dynatrace to optimize where specifically needed.
I might argue that you aren't gonna innovate terribly much, and maybe it'd be counterproductive if you did when you're banging stuff out that chokes under load but don't know why till a Dynatrace tells you.
...But I am a good bit salty today.
|
|
|
|
|
The co-author of SQL, the standardized query language for relational databases, has come out in support of the NoSQL database movement that seeks to escape the tabular confines of the RDBMS. SELECT * FROM table not enough?
You mean, sometimes all data isn't tabular? :boggle:
|
|
|
|