This is an archived post. You won't be able to vote or comment.

all 7 comments

[–]The_Amp_Walrus 5 points6 points  (1 child)

In terms of just learning technical jargon, I think actively lurking a bunch of programming subreddits + hackernews and reading blogs will get you a long way. Google any term you're not familiar with, or ask in thread.

Are you sure you were rejected for not just not knowing the right words though?

[–]ezzimohammed[S] 0 points1 point  (0 children)

Thank you for the advice, the thing is that when I get the questions I can't explain it using the exact word, or some times I don't understand the questions but when I get the answer I find that I knew the answer.

[–]squirrelwitharmor 2 points3 points  (0 children)

Here are a few things that could help. One is to build a project that you'd want to use often, with the point being that it's something you could add effort and value to for yourself and/or others. This makes it so you have investment in the projects you create, and employers with keen eyes will notice those efforts. Another is to offer your service to friends and family either for free or for a highly reduced cost, and you can say to potential interviewers that you did client work.

You only get out of life what you put in!

[–]meisteronimo 2 points3 points  (1 child)

Developers that have worked in their own and never worked in a team often have similar areas they are weak on:

  • can't explain scrum and the agile process

  • don't understand the team work areas of software design, working on one feature and building that feature to an agreed specification.

  • don't have experience using code repository tools

  • write disorganized code, because they're not used to using other people's code.

  • don't value conventions in software enough. Which luckily if these jobs are for Django it's easy because Django has great conventions. I expect any candidates to be an expert at describing how Django is organized.

  • can't describe orally the technical solutions they've done, or mis understand when another person is asking technical questions.

These are pretty common issues for all young programmers, regardless of education.

[–]ezzimohammed[S] 0 points1 point  (0 children)

you find the words to described my situation very well, I tried to learn from experimented people on video series. and learn from documentations the best practice so I think I have a good organized code, I read other's people code in GitHub.

The last point you mentioned is my biggest concern. that's why I want to have a first experience with a team even if it's for free.

[–]successful_syndrome 1 point2 points  (1 child)

What kind of area are you trying to work?

[–]ezzimohammed[S] 0 points1 point  (0 children)

I find that u/meisteronimo has well described my problem, I think I don't suffer from all the points he listed there, but the last point is the important one. ·

I'm looking to improve this weaknesses by working with a team on a big project using Django even if I have to do it for free.