"list" っていう変数を宣言した上、その要素にmapで変更を加えて、また同じ "list" に上書き代入しているコードに出くわしました。
こういうのって書いている人はどうやって把握してるでしょうね…
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
I recently came across code that declared a variable with the name "list" and then mapped over it making modifications and then re-assigned it to "list"!
I have no clue how the author can keep track of these things...
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
const to mutable ratio is your real coding skill measure
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
Immutable is good, saying by John Carmack of all game devs
World is really changed, hot damn
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
rah retweeted
John Carmack on mutable variables
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
Suwako — e/acc retweeted
Immutable by default is the way!
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
KwonHan retweeted
TIL that Carmack does some Python
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
reminds me how much the old Carmack talk on FP encouraged me down the rabbit hole ~10 years ago.
I hope this next generation understands that there’s plenty of applicable wisdom there, but you probably shouldn’t go “full Haskell”
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
Eu faço isso no python, e é uma *MARAVILHA* pra debuggar.
Cara esse maluco é um exemplo de programador a ser seguido. Escutem esse fdp, leiam seus rants.
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
可変変数に関するジョン・カーマック
John Carmack on mutable variables
x.com/id_aa_carmack/status/1…
2025-11-01 05:00:10 +0900
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
From 1 to 10 how much Rust this desire has?
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
"I wish it was the default, and mutable was a keyword"
pq isso me soa familiar?
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
TRUTH BOMB
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
John Carmack on mutable variables x.com/id_aa_carmack/status/1… (news.ycombinator.com/item?id…)
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
mutable data is the bug's nest
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.
learning clojure fixed this for me
When I started working in python, I got lazy with “single assignment”, and I need to nudge myself about it.
You should strive to never reassign or update a variable outside of true iterative calculations in loops. Having all the intermediate calculations still available is helpful in the debugger, and it avoids problems where you move a block of code and it silently uses a version of the variable that wasn’t what it originally had.
In C/C++, making almost every variable const at initialization is good practice. I wish it was the default, and mutable was a keyword.