#scottcomputing — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #scottcomputing, aggregated by home.social.
-
I got into an argument with #Microsoft #Copilot today.
I asked for PowerShell code to trim the first N digits from every filename in a directory. Testing showed it actually removed 2·N characters. When I reported the bug, Copilot insisted that was impossible and said I must have run it twice.
I knew the cause and the fix, but I treated it as a learning exercise to see what it would take to get Copilot to correct itself.
1/4
-
I got into an argument with #Microsoft #Copilot today.
I asked for PowerShell code to trim the first N digits from every filename in a directory. Testing showed it actually removed 2·N characters. When I reported the bug, Copilot insisted that was impossible and said I must have run it twice.
I knew the cause and the fix, but I treated it as a learning exercise to see what it would take to get Copilot to correct itself.
1/4
-
I got into an argument with #Microsoft #Copilot today.
I asked for PowerShell code to trim the first N digits from every filename in a directory. Testing showed it actually removed 2·N characters. When I reported the bug, Copilot insisted that was impossible and said I must have run it twice.
I knew the cause and the fix, but I treated it as a learning exercise to see what it would take to get Copilot to correct itself.
1/4
-
I got into an argument with #Microsoft #Copilot today.
I asked for PowerShell code to trim the first N digits from every filename in a directory. Testing showed it actually removed 2·N characters. When I reported the bug, Copilot insisted that was impossible and said I must have run it twice.
I knew the cause and the fix, but I treated it as a learning exercise to see what it would take to get Copilot to correct itself.
1/4
-
I got into an argument with #Microsoft #Copilot today.
I asked for PowerShell code to trim the first N digits from every filename in a directory. Testing showed it actually removed 2·N characters. When I reported the bug, Copilot insisted that was impossible and said I must have run it twice.
I knew the cause and the fix, but I treated it as a learning exercise to see what it would take to get Copilot to correct itself.
1/4
-
Can the ai components (NPU) of new processors be used for non-ai work?
What I'm thinking is along the lines that the vector-processing components of GPUs have also been used to speed up non-graphic mathematics on large arrays.
-
A co-worker using Python is having issues trying to load a dataset. The error is it can't allocate 40+ Gigabytes RAM.
In #SAS programming, this is mostly not an issue because SAS is generally oriented to data sets on disk. It loads a chunk at a time, performs operations, and progressively writing results to disk. Thus, SAS has no hesitation working with data sets much larger than available RAM. A strategy that worked in the 1970s and the 2020s.
-
A co-worker using Python is having issues trying to load a dataset. The error is it can't allocate 40+ Gigabytes RAM.
In #SAS programming, this is mostly not an issue because SAS is generally oriented to data sets on disk. It loads a chunk at a time, performs operations, and progressively writing results to disk. Thus, SAS has no hesitation working with data sets much larger than available RAM. A strategy that worked in the 1970s and the 2020s.
-
A co-worker using Python is having issues trying to load a dataset. The error is it can't allocate 40+ Gigabytes RAM.
In #SAS programming, this is mostly not an issue because SAS is generally oriented to data sets on disk. It loads a chunk at a time, performs operations, and progressively writing results to disk. Thus, SAS has no hesitation working with data sets much larger than available RAM. A strategy that worked in the 1970s and the 2020s.
-
A co-worker using Python is having issues trying to load a dataset. The error is it can't allocate 40+ Gigabytes RAM.
In #SAS programming, this is mostly not an issue because SAS is generally oriented to data sets on disk. It loads a chunk at a time, performs operations, and progressively writing results to disk. Thus, SAS has no hesitation working with data sets much larger than available RAM. A strategy that worked in the 1970s and the 2020s.
-
A co-worker using Python is having issues trying to load a dataset. The error is it can't allocate 40+ Gigabytes RAM.
In #SAS programming, this is mostly not an issue because SAS is generally oriented to data sets on disk. It loads a chunk at a time, performs operations, and progressively writing results to disk. Thus, SAS has no hesitation working with data sets much larger than available RAM. A strategy that worked in the 1970s and the 2020s.