Hi, I'm Vince
Hi, I'm Vince, a worldwide educator turned web developer.
That's me in the middle there in the above picture, when I w...
For further actions, you may consider blocking this person and/or reporting abuse
This is a good one! I especially like your story about how you turned your career around. Would love to read more about it one day, all the ups and downs. I'm sure it would be valuable to many who are on the same path as you.
I was gonna say this. It'll help a lot of people who are trying to get into the field including myself.
good idea! I'll definitely consider this.
I think this is especially important. You will start to work on a project with a tech stack of your choosing, and a week later, you will hear about how that tech is bad and that you should switch to a new one. A week later, you will hear about how that one is bad, and you should switch to a third one, and so on...
Remember that the tech is not as important as your skill. Much of the obtained knowledge can and will be transferable to other projects regardless of the tech.
yeah I totally agree. And if you're enjoying what you're working on, you're more likely to go deeper and gain a larger set of transferable skills
Number 10 is definitely up there, if I would put these in some kind of prioritized order!
So many are a) too hasty b) too lazy c) poorly educated on their communication skills, especially difference between formal communication by email compared to informal one-to-one messaging.
Also being respectful towards customers, even though their requests might sound weird/stupid. Customers are often NOT technical people, but it's easy to get caught in your own bubble of tech-driven people.
oh man, so true!
Last one is the best one, a lot of developers forget programming is just one part of the job, being respectful to others and humble will help you be a person other people want to work with, which pretty much will help you grow in this career.
yep. for example, being someone others would like to work with > being skilled and arrogant.
#1 is something I feel strongly about. You don't have to be super smart to become a good programmer but you do have to be interested. Sometimes I see people who hate programming struggling with it anyway because they think they will make a lot of money, but as long as they hate it they will never succeed, and just drag down the people around them.
If someone hates programming then their first step has to be finding out how to like it. Not sure how frequently anyone succeeds at that. I'm sure it's possible at least for some people.
hey brother , i know i love coding but sometimes it frustrates me and i avoid it :( does it mean i dont have love for it
No, getting frustrated is totally normal! Happens to me all the time. If you keep feeling drawn back to it, and keep wanting to go deeper, despite the frustration and difficulty, then I think that's a sign you do really love it, and will do well.
"10 π£ Programming is definitely not the only skill youβll need. Being respectful, communicative, conscientious, ambitious, and humble will put you in a different league and make you a valuable asset in any tech team."
Absolutely agree! While technical skills are crucial in programming, possessing qualities like respect, communication, conscientiousness, ambition, and humility enhances collaboration and teamwork. These interpersonal skills contribute to a positive work environment, foster innovation, and ultimately make you a well-rounded and valuable member of any tech team. It's the combination of technical expertise and these personal attributes that sets individuals apart in the dynamic field of programming.
Good summary. A point-per-point commentary from a greybeard:
Have a nice journey!
Absolubtelly agree. As admin DB nothing teach you as hard as a delete without a where clause. If you want to be a Linux Ninja should love terminal, open projects and hours over hours of bootstrap it. Every Developer should begin from 0 to hero first reading, then planning and finish with code
Very nice list ! However I am not sure about 3. I remember loosing a lot of times trying to learn with free resources without any progress. What really helped me was reading book and frontendmasters.com/
cool. yeah what worked for me might not work for everyone. thanks for sharing the resource!
I wrote about my journey a while back, and mine was drawing on my experiences working as a software engineer, in a company building software. I love that yours is more generalised and applies to anyone in tech.
Well said and very relatable!
Thanks!
I have found this article quite interesting, because due to fact that I can agree on majority of the points. However, I would like to highlight one more thing, there is a difference between someone that has a Computer Science degree and someone who has not followed traditional path.
Someone with Computer Science degree will be thinking in a different way than someone else, it is just the thing that studying computer science develop in an individual.
totally true. learning computer science fundamentals is always a good idea
πππ...This guy worked in my country. I just love this piece...am still laughing, and the voices in my heads. Thank you @vincanger
A great place it is!
Yes indeed! You should visit again.
These are all great points, and accurate ones. After attending an intense bootcamp they seem like common sense, but helpful to go down the list to make sure my head is still on tight. The job hunt is brutal for Jr. Devs right now, so you figure out pretty quick its gotta be about more than the money.
nice. glad it was helpful!
Totally agree and love your story! However I think sometimes we need to read books and take some courses to dig deeper into what weβre doing.
This is a valid point
If you want to go fast, go alone, if you want to go far, go together! ππΌββοΈ
wise words, brother.
I am really intrigued by the motive you have suggested. Your explanation has given me a clear path to follow, and I am confident that I can practice accordingly. Thank you for providing me with the guidance and roadmap that I needed.!!!
glad it could be of use to you!
That's interesting, I enjoyed reading about your career switch and what you've learned.
π
completely agreed
Love it. Awesome advice.
something that I really needed today, thanks!
you're welcome!
Good Advice π
thank you
100% agree with you
π
Well said
thanks!
Thanks for the good article.
you're welcome. glad you enjoyed it.
This is called truths. Thank you for share your valuable content.
This is cool!
Good One! Thanks for the article. FMPOV, this can be for Senior ones too.
well putπ
thanks!
Thanks for sharing.
Great list! Slightly disagree on 4 - trends to some degree do dictate job markets, hard agree on 10, soft skills / people skills I've found sometimes gets you far more than the technical ones.
yeah definitely, but i think if you're proficient in one tool you can easily learn the other
This is very true. Thanks for the post
π
Thank you for this wonderful piece.
glad it could help π
Great article, Vince! Iβve bookmarked this for later and I will definitely be checking out Open SaaS for my side projects.
Nice one! we're here to help if you've got any Qs about Open SaaS
This article is truly what any developer needs to read, regardless of how much experience he/she has. Thanks for these pieces of advice :)
thanks for the kids words :)
I agree with this list, especially #6, as an outsider looking in , and here purely as a hobbyist.
This was a fantastic read. Just what I wanted.
Thanks :)
π
I think it is also important to mention that you don't just need to learn how to program in one language -> you should also have a grasp of CS basics, know how to use git, find your way in the terminal, ... . Having an entry-level of these skills gives you advantage over others.
oh this is a good one I definitely should have included. Especially git!
Thank you, Vince, for sharing your insights through the "10 Hard Truths" for junior developers. Your post opens up a necessary dialogue about the realities of starting a career in tech. However, I find myself in disagreement with several points based on my observations and experiences in the industry. I believe it's important to shed light on these differing perspectives for a well-rounded view.
On the Necessity of Deep Technical Knowledge (Point 5):
The current job market's competitiveness arguably demands more from junior developers than a broad understanding of technology. The sheer volume of candidates per job opening means that having a specialized, in-depth knowledge of certain technologies can significantly enhance one's employability. This contradicts the notion that a surface-level understanding is sufficient, especially in a landscape where differentiation is key.
On Salary Expectations (Point 8):
The expectation of high salaries in tech, while common, doesn't always align with reality, especially in diverse geographic regions. For instance, the reality that senior full-stack developers in countries like Germany might earn as low as 40k a year challenges the narrative of universally high compensation in tech. This point emphasizes the need for a more nuanced understanding of tech salaries, beyond the often glorified figures.
On the Importance of Challenging Oneself (Point 9):
While the advice to find a balance in challenges is well-intentioned, the current job market dynamics suggest that merely stepping out of one's comfort zone may not be enough. The level of effort and perseverance required to stand out from thousands of other candidates often means pushing oneself significantly, sometimes beyond conventional comfort levels.
On the Primacy of Programming Skills (Point 10):
It's crucial to acknowledge that, particularly at the job entry phase, technical skills are paramount. The emphasis on soft skills, while undeniably important for long-term career development, might not reflect the immediate reality of job interviews where technical proficiency is the primary criterion. This perspective is not to undermine the value of soft skills but to highlight the critical importance of technical excellence in the initial stages of one's career.
In conclusion, while the "10 Hard Truths" offer valuable guidance, it's imperative to consider these alternative viewpoints for a more comprehensive understanding of the tech industry's complexities. The journey of a junior developer is multifaceted, and embracing a variety of perspectives can better prepare individuals for the challenges ahead.
i love this post ,
i have been coding for like 2-3 years now in and out tho
and i feel like i have learnt nothing,
bro , i sit down on a project and wonder if i know anything
okay , i figure things out but whenever i break things , i get stuck but one thing is true, i want to leave this hole
Good article. These shouldn't be "hard truths" but just common sense. And some even apply to multiple fields, not just software development.
unfortunately wisdom doesn't always prevail. but, yes, you're definitely right!