What was your mistakes in your career path?

Mistakes help us grow, What was your one mistake that you want others not to do that?

Comments

[Keith Lee]

Being reluctant to change jobs

When I realized that I was coding myself into a corner where I knew that:

• No-one would maintain my code after I left and the project would slowly self-deprecate
• I was going to be stuck on the same project for the duration of my tenure regardless of my skills, and have limited upward mobility

I should have developed my exit strategy immediately.

Be realistic about your prospects and your self-worth. Don't trap yourself because you still really like your job.

Keeping my creativity to myself

I often find myself coming up with great ideas from which my company could really benefit or I will have an epiphany about how to drastically improve one of my projects. Sometimes I've kept these to myself in case I can turn them into something on my own time, or I'll do little more than mention them in passing to my supervisor.

A better approach would be to write something up. Flesh out the details, do a cost/benefit analysis, approximate number of person-hours required, and so on. If you don't champion your ideas to the right people, they'll never see the light of day.

[Ali Navidi]

thanks a lot for sharing!

[Chris Gustin]

Thinking that a handful of free tutorials and short courses would be enough to learn web dev. When I finally started investing time and money into in-depth courses with experienced teachers and planned curriculums, I learned way more, way faster, and retained it a lot better.

In that same vein, I wish I had picked up some certifications earlier on than I did. Once I did that and added them to my LinkedIn profile, I started getting good quality inquiries from agencies/recruiters/employers.

[Yannis Folias]

have you got some examples of more in-depth courses?

[Chris Gustin]

Your mileage may vary, but some paid books/courses/platforms I found helpful in my career path, in the order I did them:

• A Better Way to Learn... (series of books, I went through the HTML/CSS/JS/jQuery ones and highly recommend)
• Javascript: Novice to Ninja (book, highly recommend although may be a tiny bit dated)
• Various Wordpress books and a PHP/MySQL book that I can't remember the name of now. If you're going into Wordpress dev I highly recommend going through an intensive PHP-specific course of some kind, as opposed to just grinding out Wordpress courses and fumbling through the PHP. Makes things way easier
• Frontend Masters (online platform, very helpful for learning intermediate to advanced JS)
• Academind Vue.js courses on Udemy (I think I did the Complete Intro and their Nuxt.js course too. very easy way to learn Vue, highly recommend any course Academind makes)
• Packt (online platform with access to technical books. very hit or miss but I did find a few gems in there)
• CS50 (free course through EdX, I opted to pay for the verified cert. highly recommend if you're serious about a career in IT. it's like learning music theory after being a self-taught musician: you can get by fine without, but knowing it will open even more doors)
• CS50W (this is the web programming specific follow-up to CS50, i'm about halfway through and took a pause to focus on some career changes that came up, to beef up my JS chops, and to learn React. it's very Python/Django-heavy, but the overall concepts are valuable if you're a web dev and want to be full-stack)
• Scrimba.com (i'm going through their Frontend Dev Roadmap course and can't recommend it enough. one of the pricier platforms i've used, but also one of the easiest, best designed, thorough, and up to date. have skilled up quickly on Flexbox/Grid, modern JS, and currently working through their React modules. i feel like i've leveled up the most going through their material, although i'll probably look for something else once i finish the React modules)

Hope that helps!

[Yannis Folias]

many thanks for your reply. my path does indeed vary but in any case these are extremely valuable resources

[Ali Navidi]

thanks a lot for sharing!

[Ali Navidi]

Starting with me: I trusted my employer on my first job and gave him my code without a contract so he didn't gave me any money so, DO NOT GIVE YOUR CODE TO ANYONE WITHOUT A CONTRACT

[Chris Gustin]

Adding to this, I found out late in my freelance career that a contract can be as simple as an email laying out “I’m going to do {scope of work} for {payment details} within {timeline}” and having the other person reply that they agree.

Obligatory: I’m not a lawyer, check your local laws, this worked for me but it may not apply to every situation.

Just putting it out there in case anyone feels daunted about trying to draft up contracts (make sure you have something in writing before you start working on stuff).

[Ali Navidi]

Thank you very much🙏🏻

[Tawhid]

I also fall into a similar trap and it was something I learnt the hard way

[Ali Navidi]

me too :(

[🚩 Atul Prajapati 🇮🇳]

I first mistake is very common which most of developers always do which is

"blindly get attrackted to shiny objects like new code editor, new programming language, new course, etc"

[Muhammad Mutahhar]

New Courses ✋

[Ali Navidi]

thanks a lot for sharing

[Jesus Guerrero]

• Take people words without contract.
• Let vacations for later because my project "needed" me.
• Believe in "talk is cheap show me the code" managers seems to value more people who talk more and don't code.
• Practice algorithms and take interviews even when you're not looking for a Job maybe we don't agree that we need to take live coding challenges and algorithms to prove our value but those are the rules of the game and we have to be prepared.

[Ali Navidi]

Thank you very much 🙏🏻

[Ben Halpern]

Probably anything that involved trying to go it alone in different contexts if there was help that was available.

[Ali Navidi]

thanks a lot for sharing!

[Randall]

I would say the biggest mistake I've made was when I started getting into freelancing, I started out by just going to the biggest freelancing platforms and placing bids there. Got very little good work from those places, and wasted quite a lot of time there. Eventually I joined a more exclusive contracting agency and got good work relatively easily through that.

Besides that, there are some things I wonder about sometimes, but it's unclear if they were mistakes.

After I graduated from university, I had an offer from Amazon. I turned it down because I had heard a lot of bad things about working there, and I took a lower paying offer from a lesser known company with a great work culture instead. Now I tend to think I would be better off if I had gone to Amazon, stayed for a year or something, got Amazon on my resume, and got my career off to a faster start that way. But I don't know, maybe I made the right choice after all.

Another thing was when I quit my programming job and moved to Japan to teach English. That didn't work out so well and I didn't stay there for very long. But that began a two year journey of digital nomadding and freelancing. It probably slowed me down career-wise, but it was also a great experience over all. Mistake? Perhaps, but I tend to think not.

[Ali Navidi]

Don't regret the past, thanks for sharing and good luck🙏🏻

[Brad]

1. Not caring enough in high school
2. Not caring enough in college until I got a big fat F for a class (then I kicked it into gear)
3. Maybe sticking around longer than I should have at specific companies that were not going to go anywhere.

I'd also like to point out, none of these mistakes are regrets. Each was a learning experience.

[Ali Navidi]

thank you very much for sharing!

[Nathan Stevenson]

Not collaborating with others on projects, opting to fly solo most times.

I only have the one internship under my belt, about 9 months. I do not work in development presently, but I work on various personal projects on my free time. So take this for what it's worth.

I've come to realize that having just one other person to collaborate with is a game changer. Talking through problems, developing a path forward, bouncing ideas of each other as we work towards a solution, and a greater drive to put in effort as to not disappoint our peers. We also bring something different to the table, which help fill in knowledge gaps.

Collaborating with others can also help with networking and employment later on. All it takes is for one of the people you've worked on a project with to suggest you as a candidate for an open position and you now have your foot in the door.

[Ali Navidi]

Thanks for sharing!!!

[Nathan Stevenson]

No problem! If I can help someone learn from my mistake, it wasn't a mistake.

[leob]

Not going freelance sooner ... my last "boring office job" was really a low, and a waste of time - it totally didn't live up to the expectations that I'd had, it was a dud on so many levels ... but, it really convinced me to change course and go freelance, and do things completely different :)

[Ali Navidi]

thanks a lot for sharing!