In a previous article, we looked at the various stages that I feel are helpful to use as a general template or framework when thinking about how a ...
For further actions, you may consider blocking this person and/or reporting abuse
Perhaps an unpopular opinion, and I understand why people do this, but once you get your first developer job, drop the "junior." You're a developer, be confident! It might help some of the impostor syndrome!
I think it's important to understand that you have a lot to learn - years worth of learning!
But yes, as a tactical move, speaking and presenting yourself as a "developer" vs. "junior developer" can help in marketing yourself and even positioning yourself confidently 😊
I don't think anyone new to having a career in development goes in thinking they are expert, but keeping the "junior" mindset does seem like it could be a little self-defeating in wanting to grow and learn.
Really like the achievement list idea, I wish that had ocurred to me before. Right now I'm rewriting my resume to transition more into a development job and that would have certainly be useful. Great Article!
Thanks Robert!
Thank you for you paper , It was so useful , but how we know we are junior or not
for example in my CV ? I think I shouldn't call myself junior and let the company to assign whats my level , Do you think is it true?
That seems like a decent move - just call yourself a "software developer".
Thanks for the great post! I think it's important that we discuss these issues in a constructive, action oriented way, as you do here.
I particularly like your point that the codebases are different than the ones we used in school, whatever that education may be for you. I'm a strong believer in the importance of soft skills as key to success and happiness in development careers, something that is often not talked about in a formal education setting.
The article 7 hard truths about starting your career as a developer addresses some similar concerns and pieces of advice that you offer here.
i really like this article and the idea of an achievements journal. i think this is something that all developers and aspiring developers should read.
Not sure there's a "right" way. You might want to start with tutorials so you can get some basic understanding of what is possible.
You might learn better by watching videos?
The best, I think, is to just solve some real problem. Learn as you go!
I think this is generally great advice for any newbie -- I wish I was able to read something like this back in 2013 when I interned at a startup as a graphic designer. Great read! I really like the paper and a list idea, and keeping a private list of achievements too.
Thanks for the great post! As a self taught developer looking for my first job this was right on time.
Sweet! Good luck 😊
Love the achievements library idea. Every developer I've spoken with talks about how the learning feels soooo sloooow until you look back and see all the distance you've already covered.
Those achievements might help in your CV
Yes, it will def. give you a whole list of ammunition to work from 😊