Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
It's a nice retrospective and analysis which I loved to read, I want to add that people that does this usually are insecure so think they are in trouble if any other gets the same knowledge.
A good practice, specially for newbies, when they come to show something they did is to ask why they do that, why they did it that way, and what it solves (use cases into the real world) so they can make an analysis of the "product" they just developed.
Then, if they have questions or difficulties to reach the answer it's important to help them so they can make a previous analysis before developing something and analyzing later.
I expect the young newbies to be better than me at the same age because of the tools, methodologies and so that seniors are developing; it must be always some kinda exponential 😄
Maker of software products and a builder of teams. Director of Engineering
@ Zwift.com⚡ We're hiring! Helping developers rise via The Rising Dev newsletter.
I totally agree with the insecure part, it's a pattern I've seen repeatedly in my own career. I wish folks could be a bit more open. To your point, asking questions of newer devs around why they chose a certain approach, and what they think it solves, is a great way to much more productive conversations - and a new dev will learn so much more through this kind of approach. Thank you for sharing your thoughts, very useful! :)
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.
Take my like my good fellow.
It's a nice retrospective and analysis which I loved to read, I want to add that people that does this usually are insecure so think they are in trouble if any other gets the same knowledge.
A good practice, specially for newbies, when they come to show something they did is to ask why they do that, why they did it that way, and what it solves (use cases into the real world) so they can make an analysis of the "product" they just developed.
Then, if they have questions or difficulties to reach the answer it's important to help them so they can make a previous analysis before developing something and analyzing later.
I expect the young newbies to be better than me at the same age because of the tools, methodologies and so that seniors are developing; it must be always some kinda exponential 😄
I'm happy you enjoyed reading it!
I totally agree with the insecure part, it's a pattern I've seen repeatedly in my own career. I wish folks could be a bit more open. To your point, asking questions of newer devs around why they chose a certain approach, and what they think it solves, is a great way to much more productive conversations - and a new dev will learn so much more through this kind of approach. Thank you for sharing your thoughts, very useful! :)