You hit multiple great points in a single article. I don't know which one is the best. But I will start with this.
> a series of ‘habits’ and ‘feelings’ instead of clear mental and conceptual models for design or programming.
Well said, this is me after years of so called self-learning. Lot of maybe's and I think so's. Yes, I got the job and been in a better place but definitely not the most confident of the bunch. Having a bout of imposter syndrome every time I start a new job and tired to having to deal with a perpetual good to be here syndrome, which just drains me.
> This leads to a workplace where people hide from each other. They use the shield that ‘smart people’ are unique and need focus.
This is a really interesting thought, It never occurred to me. The more people we have who are insecure about their skill, the more closed and complicated the team communication will become.
I am on one of the first batch of the coursera Rice university python course (which of course change my life) where the instructor used to quote, "by the end of this course you know enough to be dangerous". I used to think of that in a good way. Yes, why not, I am going to learn enough to be dangerous and break things.
This will be good for short term, its easy to learn fast and break things. In a longer timeline, which you should always optimise for, learning enough to be dangerous is bad. What you want is strong basics and great mental models which will help you build things. Wish I had know this when I am staring out.
Thank you for taking part in the conversation! I was thinking about 'prototyping' yesterday - and I DO think that we should make prototypes early and often / and that's kinda like "move fast and learn about things" haha. I certainly don't think that everyone who is 'self taught' is dangerous - but I've really worked hard on the curriculum at perpetual.education - to create a way to really deeply learn the foundations - and to create a standard. Maybe it's more like "Learn enough to be competent and confident to know how to learn and what to learn next." haha. That's too long of a tagline. What are you going to use those new Python skills for?
yeah, practical application trumps theoretical knowledge any day! Coursera story is roughly 10 years old and I have been working as a developer since then. perpetual's cirriculum does sound interesting and in depth.
They are certainly one type of gatekeeper! We need them in all roles! I'm glad you are working to be one of them, Marco. We need your unique and positive perspective.
You hit multiple great points in a single article. I don't know which one is the best. But I will start with this.
> a series of ‘habits’ and ‘feelings’ instead of clear mental and conceptual models for design or programming.
Well said, this is me after years of so called self-learning. Lot of maybe's and I think so's. Yes, I got the job and been in a better place but definitely not the most confident of the bunch. Having a bout of imposter syndrome every time I start a new job and tired to having to deal with a perpetual good to be here syndrome, which just drains me.
> This leads to a workplace where people hide from each other. They use the shield that ‘smart people’ are unique and need focus.
This is a really interesting thought, It never occurred to me. The more people we have who are insecure about their skill, the more closed and complicated the team communication will become.
I am on one of the first batch of the coursera Rice university python course (which of course change my life) where the instructor used to quote, "by the end of this course you know enough to be dangerous". I used to think of that in a good way. Yes, why not, I am going to learn enough to be dangerous and break things.
This will be good for short term, its easy to learn fast and break things. In a longer timeline, which you should always optimise for, learning enough to be dangerous is bad. What you want is strong basics and great mental models which will help you build things. Wish I had know this when I am staring out.
Thank you for taking part in the conversation! I was thinking about 'prototyping' yesterday - and I DO think that we should make prototypes early and often / and that's kinda like "move fast and learn about things" haha. I certainly don't think that everyone who is 'self taught' is dangerous - but I've really worked hard on the curriculum at perpetual.education - to create a way to really deeply learn the foundations - and to create a standard. Maybe it's more like "Learn enough to be competent and confident to know how to learn and what to learn next." haha. That's too long of a tagline. What are you going to use those new Python skills for?
yeah, practical application trumps theoretical knowledge any day! Coursera story is roughly 10 years old and I have been working as a developer since then. perpetual's cirriculum does sound interesting and in depth.
Web designers are the gatekeepers ;)
They are certainly one type of gatekeeper! We need them in all roles! I'm glad you are working to be one of them, Marco. We need your unique and positive perspective.