#scottprogramming — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #scottprogramming, aggregated by home.social.
-
ERROR 180-322: Statement is not valid or it is used out of proper order.
-
ERROR 180-322: Statement is not valid or it is used out of proper order.
-
ERROR 180-322: Statement is not valid or it is used out of proper order.
-
ERROR 180-322: Statement is not valid or it is used out of proper order.
-
ERROR 180-322: Statement is not valid or it is used out of proper order.
-
In 15 years, when half of the worlds critical software is LLM-infested, indecipherable vibe-coded spaghetti, and there aren’t enough traditionally-trained software engineers to hire because the entry-level pipeline was strangled in 2025, and people my generation have all retired, well…
Well just remember I said this would happen.
#VibeCoding #ChatGPT #ScottProgramming #ScottThoughts #ScottEconomics #Year2025
-
In 15 years, when half of the worlds critical software is LLM-infested, indecipherable vibe-coded spaghetti, and there aren’t enough traditionally-trained software engineers to hire because the entry-level pipeline was strangled in 2025, and people my generation have all retired, well…
Well just remember I said this would happen.
#VibeCoding #ChatGPT #ScottProgramming #ScottThoughts #ScottEconomics #Year2025
-
In 15 years, when half of the worlds critical software is LLM-infested, indecipherable vibe-coded spaghetti, and there aren’t enough traditionally-trained software engineers to hire because the entry-level pipeline was strangled in 2025, and people my generation have all retired, well…
Well just remember I said this would happen.
#VibeCoding #ChatGPT #ScottProgramming #ScottThoughts #ScottEconomics #Year2025
-
In 15 years, when half of the worlds critical software is LLM-infested, indecipherable vibe-coded spaghetti, and there aren’t enough traditionally-trained software engineers to hire because the entry-level pipeline was strangled in 2025, and people my generation have all retired, well…
Well just remember I said this would happen.
#VibeCoding #ChatGPT #ScottProgramming #ScottThoughts #ScottEconomics #Year2025
-
In 15 years, when half of the worlds critical software is LLM-infested, indecipherable vibe-coded spaghetti, and there aren’t enough traditionally-trained software engineers to hire because the entry-level pipeline was strangled in 2025, and people my generation have all retired, well…
Well just remember I said this would happen.
#VibeCoding #ChatGPT #ScottProgramming #ScottThoughts #ScottEconomics #Year2025
-
A lot of the analytical work I do really adapts well to #Jupyter Notebooks. It's very helpful to organize the code into logical chunks, one chunk per cell.
However, now I want to re-run the entire workbook, changing only one parameter.
Is there an easy way to do that without merging all the cells together?
ETA: My notebook has a parameter section at the top, but now I want to re-run for a range of values that would be a pain to do manually.
-
A lot of the analytical work I do really adapts well to #Jupyter Notebooks. It's very helpful to organize the code into logical chunks, one chunk per cell.
However, now I want to re-run the entire workbook, changing only one parameter.
Is there an easy way to do that without merging all the cells together?
ETA: My notebook has a parameter section at the top, but now I want to re-run for a range of values that would be a pain to do manually.
-
A lot of the analytical work I do really adapts well to #Jupyter Notebooks. It's very helpful to organize the code into logical chunks, one chunk per cell.
However, now I want to re-run the entire workbook, changing only one parameter.
Is there an easy way to do that without merging all the cells together?
ETA: My notebook has a parameter section at the top, but now I want to re-run for a range of values that would be a pain to do manually.
-
A lot of the analytical work I do really adapts well to #Jupyter Notebooks. It's very helpful to organize the code into logical chunks, one chunk per cell.
However, now I want to re-run the entire workbook, changing only one parameter.
Is there an easy way to do that without merging all the cells together?
ETA: My notebook has a parameter section at the top, but now I want to re-run for a range of values that would be a pain to do manually.
-
A lot of the analytical work I do really adapts well to #Jupyter Notebooks. It's very helpful to organize the code into logical chunks, one chunk per cell.
However, now I want to re-run the entire workbook, changing only one parameter.
Is there an easy way to do that without merging all the cells together?
ETA: My notebook has a parameter section at the top, but now I want to re-run for a range of values that would be a pain to do manually.
-
@vathpela @joshbressers In the spirit of being constructive:
I've looked at Rust a bit. I've coded professionally in both C and C++, and I can see a bit of why C and C++ people might not like Rust.
If someone can add memory safety to C in a way that otherwise is extremely minimal in how the new code looks, great. I'm not an expert in developing programming languages, but I can see how that might be challenging given a few C things like the language is not type strict.
-
@vathpela @joshbressers In the spirit of being constructive:
I've looked at Rust a bit. I've coded professionally in both C and C++, and I can see a bit of why C and C++ people might not like Rust.
If someone can add memory safety to C in a way that otherwise is extremely minimal in how the new code looks, great. I'm not an expert in developing programming languages, but I can see how that might be challenging given a few C things like the language is not type strict.
-
@vathpela @joshbressers In the spirit of being constructive:
I've looked at Rust a bit. I've coded professionally in both C and C++, and I can see a bit of why C and C++ people might not like Rust.
If someone can add memory safety to C in a way that otherwise is extremely minimal in how the new code looks, great. I'm not an expert in developing programming languages, but I can see how that might be challenging given a few C things like the language is not type strict.
-
@vathpela @joshbressers In the spirit of being constructive:
I've looked at Rust a bit. I've coded professionally in both C and C++, and I can see a bit of why C and C++ people might not like Rust.
If someone can add memory safety to C in a way that otherwise is extremely minimal in how the new code looks, great. I'm not an expert in developing programming languages, but I can see how that might be challenging given a few C things like the language is not type strict.
-
@vathpela @joshbressers In the spirit of being constructive:
I've looked at Rust a bit. I've coded professionally in both C and C++, and I can see a bit of why C and C++ people might not like Rust.
If someone can add memory safety to C in a way that otherwise is extremely minimal in how the new code looks, great. I'm not an expert in developing programming languages, but I can see how that might be challenging given a few C things like the language is not type strict.
-
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
-
In #Python, you could write sensible and transparent code, like this:
if (curNode):
curNode = curNode.nextBut if you prefer something that is functionally identical, but harder to read, try this:
curNode and (curNode := curNode.next)
Follow me for more great tips on how to make life hell for the next person working with your code (which could be you).
-
In #Python, you could write sensible and transparent code, like this:
if (curNode):
curNode = curNode.nextBut if you prefer something that is functionally identical, but harder to read, try this:
curNode and (curNode := curNode.next)
Follow me for more great tips on how to make life hell for the next person working with your code (which could be you).
-
In #Python, you could write sensible and transparent code, like this:
if (curNode):
curNode = curNode.nextBut if you prefer something that is functionally identical, but harder to read, try this:
curNode and (curNode := curNode.next)
Follow me for more great tips on how to make life hell for the next person working with your code (which could be you).
-
In #Python, you could write sensible and transparent code, like this:
if (curNode):
curNode = curNode.nextBut if you prefer something that is functionally identical, but harder to read, try this:
curNode and (curNode := curNode.next)
Follow me for more great tips on how to make life hell for the next person working with your code (which could be you).
-
In #Python, you could write sensible and transparent code, like this:
if (curNode):
curNode = curNode.nextBut if you prefer something that is functionally identical, but harder to read, try this:
curNode and (curNode := curNode.next)
Follow me for more great tips on how to make life hell for the next person working with your code (which could be you).
-
I heard from a colleague that a system was just identified with a y2k bug.
Wait, how is that possible?!
A system was using 2 digits to store and transmit the year. To resolve the initial y2k problem, the system employed the date window technique, where that window ended with 2025.
https://en.wikipedia.org/wiki/Date_windowing
1/2
-
I heard from a colleague that a system was just identified with a y2k bug.
Wait, how is that possible?!
A system was using 2 digits to store and transmit the year. To resolve the initial y2k problem, the system employed the date window technique, where that window ended with 2025.
https://en.wikipedia.org/wiki/Date_windowing
1/2
-
I heard from a colleague that a system was just identified with a y2k bug.
Wait, how is that possible?!
A system was using 2 digits to store and transmit the year. To resolve the initial y2k problem, the system employed the date window technique, where that window ended with 2025.
https://en.wikipedia.org/wiki/Date_windowing
1/2
-
I heard from a colleague that a system was just identified with a y2k bug.
Wait, how is that possible?!
A system was using 2 digits to store and transmit the year. To resolve the initial y2k problem, the system employed the date window technique, where that window ended with 2025.
https://en.wikipedia.org/wiki/Date_windowing
1/2
-
I heard from a colleague that a system was just identified with a y2k bug.
Wait, how is that possible?!
A system was using 2 digits to store and transmit the year. To resolve the initial y2k problem, the system employed the date window technique, where that window ended with 2025.
https://en.wikipedia.org/wiki/Date_windowing
1/2
-
With a job change, I've spent the last 2 years learning Hadoop and Python. For reasons™, they are replacing the Hadoop component with something else. Ugh. At my career stage, I'm a little annoyed to have spent time and energy learning something that likely won't have any long-term benefit to me. I'll roll with it, though, because I have no other choice.
-
With a job change, I've spent the last 2 years learning Hadoop and Python. For reasons™, they are replacing the Hadoop component with something else. Ugh. At my career stage, I'm a little annoyed to have spent time and energy learning something that likely won't have any long-term benefit to me. I'll roll with it, though, because I have no other choice.
-
With a job change, I've spent the last 2 years learning Hadoop and Python. For reasons™, they are replacing the Hadoop component with something else. Ugh. At my career stage, I'm a little annoyed to have spent time and energy learning something that likely won't have any long-term benefit to me. I'll roll with it, though, because I have no other choice.
-
With a job change, I've spent the last 2 years learning Hadoop and Python. For reasons™, they are replacing the Hadoop component with something else. Ugh. At my career stage, I'm a little annoyed to have spent time and energy learning something that likely won't have any long-term benefit to me. I'll roll with it, though, because I have no other choice.
-
With a job change, I've spent the last 2 years learning Hadoop and Python. For reasons™, they are replacing the Hadoop component with something else. Ugh. At my career stage, I'm a little annoyed to have spent time and energy learning something that likely won't have any long-term benefit to me. I'll roll with it, though, because I have no other choice.
-
Microsoft in 1995: we’ve added support for spaces in file and directory names.
Me in 2024: I’d better use underscores instead of spaces just in case some application doesn’t handle spaces in file paths correctly.
-
Microsoft in 1995: we’ve added support for spaces in file and directory names.
Me in 2024: I’d better use underscores instead of spaces just in case some application doesn’t handle spaces in file paths correctly.
-
Microsoft in 1995: we’ve added support for spaces in file and directory names.
Me in 2024: I’d better use underscores instead of spaces just in case some application doesn’t handle spaces in file paths correctly.
-
Microsoft in 1995: we’ve added support for spaces in file and directory names.
Me in 2024: I’d better use underscores instead of spaces just in case some application doesn’t handle spaces in file paths correctly.
-
Microsoft in 1995: we’ve added support for spaces in file and directory names.
Me in 2024: I’d better use underscores instead of spaces just in case some application doesn’t handle spaces in file paths correctly.
-
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.