Great article, great points. I really liked the honesty but also applicable tips.
// edit: Based on your journey, do you have any advice regarding code quality? Especially when you transformed from a part-timer/freelancer to full-time professional? How did the transitsion impact the quality of your work?
Thank you! That’s an interesting question re: code quality. In the early part of my journey, I was happy with code that worked! When I was solo, I tried writing code as efficiently as possible with not writing too many lines of code and trying to gain as much of a performance edge as possible.
Since I’ve started working with teams, I try to make my code as readable as possible. Even if it isn’t perfectly efficient or not perfectly performant. Writing readable code allows my teammates and future employees to understand it, maintain it, and build on it.
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.
Great article, great points. I really liked the honesty but also applicable tips.
// edit: Based on your journey, do you have any advice regarding code quality? Especially when you transformed from a part-timer/freelancer to full-time professional? How did the transitsion impact the quality of your work?
Thank you! That’s an interesting question re: code quality. In the early part of my journey, I was happy with code that worked! When I was solo, I tried writing code as efficiently as possible with not writing too many lines of code and trying to gain as much of a performance edge as possible.
Since I’ve started working with teams, I try to make my code as readable as possible. Even if it isn’t perfectly efficient or not perfectly performant. Writing readable code allows my teammates and future employees to understand it, maintain it, and build on it.