i got my first job as junior python developer.
i'm gonna start tomorrow.
i'm scared to death.
any advice?

  • 8
    Don't worry too much about it, there will be senior developer who are going to guide you.
  • 14
    yeah, don't be embarrassed to googleing the most basic stuff daily.
  • 20
    Don't die.
  • 7
    @rutee07 but what if that's the best option?
  • 15
  • 6
    Don't overdress, just take a nice shirt or something. They are most likely doing the casual dress code, you just need to scope it out.
  • 2
    You are starting on a Sunday?
  • 4
    Be aware of imposter syndrome, it can be hard with new jobs
  • 2
    Master venv & docker
    -> docker is great to test your projects in fully sandboxes envs + if you don't want to install cuda on you local system for exemple
    -> learn to optimize your dockerfiles for pip
    Add a linter if the company doesn't already use one (flake8 with 100 chars line limit is ­čĺ»)
  • 2
    @rutee07 Hey you can't steal my advice... I'm supposed to be the serious one and you the fun one! Remember?
  • 0
    @MagicSowap Any thoughts on tox ?
  • 1
    @alexbrooklyn Personally I never needed it as my Makefiles did everything tox does and some more, without additional configuration files.
  • 2
    Don't be afraid of taking help from senior developers. They helped me a lot, in my case.
  • 2
    Just remember that mr google is always there
  • 2
    - Fuckups Happen , it's how you respond that counts. Many junior devs are literally setup to fail within the first week to test them, and to test the companies own failure procedures.
    - You can't know everything. I ask my peers even the most basic questions, because my area of expertise is elsewhere
    - Challenge assumptions, ask why, listen first.

    You're going to rock this job. Let us know how it goes.
  • 1
    Ive been a professional dev for 6 years. I still regularly have to look up stuff that someone else probably knows off the top of their head. Different people have different skills. So dont sweat if theres something you don’t know.
  • 3
    @LLAMS I am clocking in my 21 year as full time dev and 40th with computer and I also often ask questions.

    My rule is that you are never done learning in this profession and even junior devs, straight from school might have learned something I missed or an area I previously had not worked with.

    Also, by proving that I also can as questions I show them that it is ok to do so, so they should not be afraid to ask :)

    Especially ad a new one. The company makes no money bu forcing new people to do unnecessary work.

    Or that they do something in the wrong direction if a quick question could have gotten them on track.

    And also, ever developers makes mistakes even senior, any one that says otherwise is hiding something ;)
  • 3
    Don't worry too much man. I've been linuxing for 10 years now and I still learn new stuff regularly.

    Hell, I recently taught a senior Linux admin (someone who started with this when the kernel was developed) a command he didn't know existed and his face was priceless but he has been a Linux admin for idk, 20+ years?!

    I'm a junior cyber security engineer right now and while I have loads to learn, it's funny to see how having extensive tech knowledge + a certain way of thinking can already get you so far!
  • 1
    Here is what I will tell you as a Python (Django) devloper.

    2 years ago, I was in your shoes. I'm still noob in python and django not because I don't know how it works but there are too many things I still have to learn. It will take time.

    Bottom line is, after getting access to the codebase you will not understand a single damn things for first few days or might be few weeks depending upon the size of codebase. That's totally fine. Give it a time. And senior will help you out.

    One advice I want to give is, if you're working on Django, try not to skip the part of understanding how things works under the hood. This is what you will do after getting some what comfortable with codebase.
    Django is highly abstracted framework which is both good and bad.
  • 0
  • 1
    get a expensive moleskine note book. Make your notes and reminders worthwhile.
  • 0
    23 days later

    So how are you doing? Everything working out for you?
  • 1
    @Hazarth @devphobe
    not really.
    i had to leave there because they wanted me to learn docker and graphql in one week.
    but i found an internship in a bigger company.
    good for me.
Add Comment