I must say, as a Self taught Dev, I have to disagree with this article.
This reads more like a college assignment you were doing and published, than shared experience.
You should have talked about finding ways to bring programming into your day to day life, and iterating on issues you run into, as you solve a problem.
For me it was controlling my lights to not wake up my newborn baby.
I had a cause with a time constraint, and a test environment, to see my code in action right from the start.
Becoming a strong Software Dev isn't about doing Vocab and learning all the syntax, possible data types, and libraries that you might need to know one day.
It's about having a problem, and knowing how to go find the answer.
You aren't a self taught Dev so all you've done here is describe being a college student with more steps.
Yes learning theory is important, but it isn't first.
The first thing you need to do is fail.
Write sloppy code that works, and then learn the reasons why it's sloppy by tracing issues and having the drive to improve your code.
If you worry about doing it right the first time, you're going to end up writing an article like this.
I suggest picking up an app called Tasker, or another framework like Node-Red or Eventghost.
And wait you actually hand write code because you think it will retain better?
Bruh the correct answer is to Mqtt pub your notes to your Ec2
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I must say, as a Self taught Dev, I have to disagree with this article.
This reads more like a college assignment you were doing and published, than shared experience.
You should have talked about finding ways to bring programming into your day to day life, and iterating on issues you run into, as you solve a problem.
For me it was controlling my lights to not wake up my newborn baby.
I had a cause with a time constraint, and a test environment, to see my code in action right from the start.
Becoming a strong Software Dev isn't about doing Vocab and learning all the syntax, possible data types, and libraries that you might need to know one day.
It's about having a problem, and knowing how to go find the answer.
You aren't a self taught Dev so all you've done here is describe being a college student with more steps.
Yes learning theory is important, but it isn't first.
The first thing you need to do is fail.
Write sloppy code that works, and then learn the reasons why it's sloppy by tracing issues and having the drive to improve your code.
If you worry about doing it right the first time, you're going to end up writing an article like this.
I suggest picking up an app called Tasker, or another framework like Node-Red or Eventghost.
And wait you actually hand write code because you think it will retain better?
Bruh the correct answer is to Mqtt pub your notes to your Ec2