Coding Computing Coach
@codingcomputing.bsky.social
Making Python simple for you, by exploring the fundamentals.
Posting tips, questions, explanations, solutions, and much more!
Posting tips, questions, explanations, solutions, and much more!
Thinking is your own responsibility. The thought process needs to be your own.
AI can dish out code for you, but don't make the mistake of outsourcing thinking to AI.
AI can dish out code for you, but don't make the mistake of outsourcing thinking to AI.
March 13, 2025 at 8:19 AM
Thinking is your own responsibility. The thought process needs to be your own.
AI can dish out code for you, but don't make the mistake of outsourcing thinking to AI.
AI can dish out code for you, but don't make the mistake of outsourcing thinking to AI.
Interviewers aren't interested in the first 50 prime numbers or whatever.
They are interested in how you approach and solve a problem.
Give your best to explaining that.
What do you think?
They are interested in how you approach and solve a problem.
Give your best to explaining that.
What do you think?
February 23, 2025 at 6:32 AM
Interviewers aren't interested in the first 50 prime numbers or whatever.
They are interested in how you approach and solve a problem.
Give your best to explaining that.
What do you think?
They are interested in how you approach and solve a problem.
Give your best to explaining that.
What do you think?
"Tutorial Hell"
There are 2 things wrong in this term:
"Tutorial", and "Hell".
"Tutorial", because it's not the cause, it's the symptom.
"Hell", because it's not hard to get out of.
Getting out is a matter of attitude change:
From consuming knowledge to applying it.
There are 2 things wrong in this term:
"Tutorial", and "Hell".
"Tutorial", because it's not the cause, it's the symptom.
"Hell", because it's not hard to get out of.
Getting out is a matter of attitude change:
From consuming knowledge to applying it.
February 7, 2025 at 3:54 AM
"Tutorial Hell"
There are 2 things wrong in this term:
"Tutorial", and "Hell".
"Tutorial", because it's not the cause, it's the symptom.
"Hell", because it's not hard to get out of.
Getting out is a matter of attitude change:
From consuming knowledge to applying it.
There are 2 things wrong in this term:
"Tutorial", and "Hell".
"Tutorial", because it's not the cause, it's the symptom.
"Hell", because it's not hard to get out of.
Getting out is a matter of attitude change:
From consuming knowledge to applying it.
I don't know who needs to hear this, but
"I coded for 15 hours straight" isn't a flex.
"I coded for 15 hours straight" isn't a flex.
February 5, 2025 at 2:15 AM
I don't know who needs to hear this, but
"I coded for 15 hours straight" isn't a flex.
"I coded for 15 hours straight" isn't a flex.
Break that big task into small chunks.
Just convince yourself that you'll work on the first chunk for 10-15 minutes.
Usually gives enough momentum to see you through.
Just convince yourself that you'll work on the first chunk for 10-15 minutes.
Usually gives enough momentum to see you through.
February 3, 2025 at 8:53 AM
Break that big task into small chunks.
Just convince yourself that you'll work on the first chunk for 10-15 minutes.
Usually gives enough momentum to see you through.
Just convince yourself that you'll work on the first chunk for 10-15 minutes.
Usually gives enough momentum to see you through.
The ultimate debugging hack:
Know clearly what you're doing.
Explaining the issue aloud is the best way to implement it.
Know clearly what you're doing.
Explaining the issue aloud is the best way to implement it.
February 1, 2025 at 2:23 PM
The ultimate debugging hack:
Know clearly what you're doing.
Explaining the issue aloud is the best way to implement it.
Know clearly what you're doing.
Explaining the issue aloud is the best way to implement it.
Stop trying to satisfy vague requirements.
You can't correctly solve a problem that you don't even understand.
Start asking questions to get the requirements on point.
Then double down on solving and coding.
You can't correctly solve a problem that you don't even understand.
Start asking questions to get the requirements on point.
Then double down on solving and coding.
February 1, 2025 at 4:29 AM
Stop trying to satisfy vague requirements.
You can't correctly solve a problem that you don't even understand.
Start asking questions to get the requirements on point.
Then double down on solving and coding.
You can't correctly solve a problem that you don't even understand.
Start asking questions to get the requirements on point.
Then double down on solving and coding.
Coding is all about applying knowledge.
Unless you apply what you know, you can't build anything.
Unless you apply what you know, you can't build anything.
January 27, 2025 at 2:03 PM
Coding is all about applying knowledge.
Unless you apply what you know, you can't build anything.
Unless you apply what you know, you can't build anything.
There's no way around it, you've got to be a competent coder.
That's the only way you can spot any nonsense that AI sometimes spits out.
Remember, you code is your responsibility. If something breaks, it's you who's got to fix it.
That's the only way you can spot any nonsense that AI sometimes spits out.
Remember, you code is your responsibility. If something breaks, it's you who's got to fix it.
January 27, 2025 at 3:03 AM
There's no way around it, you've got to be a competent coder.
That's the only way you can spot any nonsense that AI sometimes spits out.
Remember, you code is your responsibility. If something breaks, it's you who's got to fix it.
That's the only way you can spot any nonsense that AI sometimes spits out.
Remember, you code is your responsibility. If something breaks, it's you who's got to fix it.
How do you spend time on your favorite programming language/framework?
A) Argue online over it
B) Build stuff using it
Choose wisely.
A) Argue online over it
B) Build stuff using it
Choose wisely.
January 26, 2025 at 6:52 AM
How do you spend time on your favorite programming language/framework?
A) Argue online over it
B) Build stuff using it
Choose wisely.
A) Argue online over it
B) Build stuff using it
Choose wisely.
Change My Mind...
January 25, 2025 at 7:27 AM
Change My Mind...
If you want to rewrite history...
... all you need is `git rebase`.
... all you need is `git rebase`.
January 24, 2025 at 3:15 AM
If you want to rewrite history...
... all you need is `git rebase`.
... all you need is `git rebase`.
Remember the general principle:
✅ Master the language before the libraries
I've seen people jump to scikit without knowing python well.
Sure, the libraries do cooler stuff, but you need solid foundations to use them well.
✅ Master the language before the libraries
I've seen people jump to scikit without knowing python well.
Sure, the libraries do cooler stuff, but you need solid foundations to use them well.
January 22, 2025 at 3:06 AM
Remember the general principle:
✅ Master the language before the libraries
I've seen people jump to scikit without knowing python well.
Sure, the libraries do cooler stuff, but you need solid foundations to use them well.
✅ Master the language before the libraries
I've seen people jump to scikit without knowing python well.
Sure, the libraries do cooler stuff, but you need solid foundations to use them well.
Coding late at night is a surefire way...
... to get nightmares about bugs.
2 hours of fresh alertness >>> 8 hours of drowsy coding
... to get nightmares about bugs.
2 hours of fresh alertness >>> 8 hours of drowsy coding
January 21, 2025 at 6:40 AM
Coding late at night is a surefire way...
... to get nightmares about bugs.
2 hours of fresh alertness >>> 8 hours of drowsy coding
... to get nightmares about bugs.
2 hours of fresh alertness >>> 8 hours of drowsy coding
The "perfect start" is a myth.
Proficiency comes from iteration.
Get started, get feedback, improve.
Proficiency comes from iteration.
Get started, get feedback, improve.
January 20, 2025 at 5:00 AM
The "perfect start" is a myth.
Proficiency comes from iteration.
Get started, get feedback, improve.
Proficiency comes from iteration.
Get started, get feedback, improve.
When code runs without error on the first try:
Newbies: Yayyy!
Experienced coders: Impossible! Surely I forgot to call that function...
Newbies: Yayyy!
Experienced coders: Impossible! Surely I forgot to call that function...
January 19, 2025 at 2:46 AM
When code runs without error on the first try:
Newbies: Yayyy!
Experienced coders: Impossible! Surely I forgot to call that function...
Newbies: Yayyy!
Experienced coders: Impossible! Surely I forgot to call that function...
Writing code is a small part of the process.
Planning your project is the actual beginning.
✅ Understanding requirements
✅ Comparing different solutions
✅ Researching and picking suitable tools
Then coding and debugging becomes simpler.
#coding
Planning your project is the actual beginning.
✅ Understanding requirements
✅ Comparing different solutions
✅ Researching and picking suitable tools
Then coding and debugging becomes simpler.
#coding
January 18, 2025 at 2:43 AM
Writing code is a small part of the process.
Planning your project is the actual beginning.
✅ Understanding requirements
✅ Comparing different solutions
✅ Researching and picking suitable tools
Then coding and debugging becomes simpler.
#coding
Planning your project is the actual beginning.
✅ Understanding requirements
✅ Comparing different solutions
✅ Researching and picking suitable tools
Then coding and debugging becomes simpler.
#coding
Copy-pasting code is all fun and games until you run into dependency issues.
January 17, 2025 at 8:52 AM
Copy-pasting code is all fun and games until you run into dependency issues.
Stop doing random things for debugging.
Debug effectively by:
✅ Knowing what you're doing
✅ Understanding the expected behavior
✅ Knowledge of the steps to get the expected behavior
✅ Diagnosing the cause of discrepancy
✅ Finding a way to fix the issue
Debug effectively by:
✅ Knowing what you're doing
✅ Understanding the expected behavior
✅ Knowledge of the steps to get the expected behavior
✅ Diagnosing the cause of discrepancy
✅ Finding a way to fix the issue
January 15, 2025 at 7:37 AM
Stop doing random things for debugging.
Debug effectively by:
✅ Knowing what you're doing
✅ Understanding the expected behavior
✅ Knowledge of the steps to get the expected behavior
✅ Diagnosing the cause of discrepancy
✅ Finding a way to fix the issue
Debug effectively by:
✅ Knowing what you're doing
✅ Understanding the expected behavior
✅ Knowledge of the steps to get the expected behavior
✅ Diagnosing the cause of discrepancy
✅ Finding a way to fix the issue
Seniors are confident they can find the answer, because they've done that same googling enough times.
January 14, 2025 at 2:40 PM
Seniors are confident they can find the answer, because they've done that same googling enough times.
AI can thrown nonsense at you. And it will look deceptively good to inexperienced eyes.
You've got to make yourself competent. There is no way around it. Yes, even with AI.
You've got to make yourself competent. There is no way around it. Yes, even with AI.
January 13, 2025 at 3:31 PM
AI can thrown nonsense at you. And it will look deceptively good to inexperienced eyes.
You've got to make yourself competent. There is no way around it. Yes, even with AI.
You've got to make yourself competent. There is no way around it. Yes, even with AI.
If you're learning to code, stop obsessing over hi-tech "setup".
A laptop, wifi, and determination. That's all you need.
A laptop, wifi, and determination. That's all you need.
January 12, 2025 at 8:02 AM
If you're learning to code, stop obsessing over hi-tech "setup".
A laptop, wifi, and determination. That's all you need.
A laptop, wifi, and determination. That's all you need.
You've got to commit to learn git
January 9, 2025 at 4:59 AM
You've got to commit to learn git
Stop doing random things for debugging.
Debug effectively by:
✅ Knowing what you're doing
✅ Understanding the expected behavior
✅ Knowledge of the steps to get the expected behavior
✅ Diagnosing the cause of discrepancy
✅ Finding a way to fix the issue
Debug effectively by:
✅ Knowing what you're doing
✅ Understanding the expected behavior
✅ Knowledge of the steps to get the expected behavior
✅ Diagnosing the cause of discrepancy
✅ Finding a way to fix the issue
January 8, 2025 at 3:09 AM
Stop doing random things for debugging.
Debug effectively by:
✅ Knowing what you're doing
✅ Understanding the expected behavior
✅ Knowledge of the steps to get the expected behavior
✅ Diagnosing the cause of discrepancy
✅ Finding a way to fix the issue
Debug effectively by:
✅ Knowing what you're doing
✅ Understanding the expected behavior
✅ Knowledge of the steps to get the expected behavior
✅ Diagnosing the cause of discrepancy
✅ Finding a way to fix the issue
People often have this excuse, that they need some hi-tech "setup" to start learning to code.
Bro, if your potato laptop can run a web browser, then it can run all that's required to practice coding.
Bro, if your potato laptop can run a web browser, then it can run all that's required to practice coding.
January 7, 2025 at 4:17 AM
People often have this excuse, that they need some hi-tech "setup" to start learning to code.
Bro, if your potato laptop can run a web browser, then it can run all that's required to practice coding.
Bro, if your potato laptop can run a web browser, then it can run all that's required to practice coding.