$30 off During Our Annual Pro Sale. View Details »

You call yourself a Senior Developer?

You call yourself a Senior Developer?

Once upon a time, Senior developer was the real role-model, a person that everyone looked up to, a developer that you seek for advice and wisdom. Nowadays, seniority is a synonym for large salaries and big egos.

Let’s have a trip down the memory lane and drift away from the money-driven mindset. Instead of that, let’s inspire you to be better developers who are fulfilled by knowledge, success, and accomplishments.

Antonio Peric-Mazar

August 27, 2021
Tweet

More Decks by Antonio Peric-Mazar

Other Decks in Technology

Transcript

  1. You call yourself a Senior Developer?
    Antonio Perić-Mažar, Locasti
    c

    27.08.2021. - #phpsrb, Belgrade

    View Slide

  2. Antonio


    Perić-Mažar
    CEO @ Locasti
    c

    Co-founder @ Litt
    o

    Co-founder @ Tinel Meetu
    p

    t: @antonioperi
    c

    m: [email protected]

    View Slide

  3. https://www.iqvis.com/wp-content/uploads/2019/08/Developers.jpg

    View Slide

  4. How do you become a
    Senior developer?

    View Slide

  5. How do you become a
    Senior developer
    ?


    In year and a half?


    View Slide

  6. How do you become a
    Senior developer
    ?


    In year and a half
    ?

    Full-stack?


    View Slide

  7. Salary!

    View Slide

  8. View Slide

  9. • 33% of projects are never complete
    d

    • 50% of projects fail to meet their goal
    s

    • 75% of execs expect their project to fail
    The aftermath

    View Slide

  10. View Slide

  11. https://thevaluable.dev/software-developer-titles-junior-senior/

    View Slide

  12. https://thenextweb.com/news/why-these-developer-job-titles-are-ridiculous-and-shouldnt-exist-syndication

    View Slide

  13. A title with no of
    fi
    cial/
    standardized de
    fi
    nition is
    useless.

    View Slide

  14. Titles are only useful
    when changing jobs.

    View Slide

  15. View Slide

  16. Junior developer

    View Slide

  17. View Slide

  18. • Focus should be trying your best to lear
    n

    • Needs directio
    n

    • Needs supervisio
    n

    • Needs mentorin
    g

    • You can still be a junior even after a decade in the industry
    Junior developer

    View Slide

  19. A junior developer is
    code focused, not
    development focused,
    and doesn’t understand
    the distinction.

    View Slide

  20. Junior developers are
    not responsible for the
    projects!

    View Slide

  21. Intermediate developer

    View Slide

  22. On the mission of finding
    the Right way of building
    the software

    View Slide

  23. View Slide

  24. • They understand project, goals and teamwor
    k

    • They can estimate thing
    s

    • They can participate in improving things and process around the projec
    t

    • Systems built by intermediate will work far longer, but will lead to some sort of
    disaster


    • The sad fact is that vast majority thinks they are senior developers
    Intermediate developer

    View Slide

  25. They can be trusted to
    raise issues of code
    design, and play a
    valuable role in design
    discussions. They are
    also the “workhorses” of
    the dev team.


    View Slide

  26. Senior developer

    View Slide

  27. • They wrote under and over designed systems. And both failed
    .

    • They are solving issues -
    fi
    re
    fi
    ghter
    s

    • Hates complexity and it is obsessed with simplicity
    They know how failure
    looks like

    View Slide

  28. A high-level
    understanding of how
    systems work

    (closed systems, design
    patterns, why, how, not
    hype-driven)

    View Slide

  29. They fully understand
    that their job is not just
    writing code but solving
    problems
    .

    View Slide

  30. Knowledge about the
    business' problem is
    essential!

    View Slide

  31. They fully understand
    context when applying
    theory!

    View Slide

  32. There is no “right way”
    to build software.

    View Slide

  33. The only way to build
    good software is by
    adapting theory to
    fi
    t the
    needs of the client,
    budget, codebase, team,
    tools, and organization
    .

    View Slide

  34. https://www.datocms-assets.com/7756/1579270413-soft-skills.png

    View Slide

  35. Core skills not soft skills!

    View Slide

  36. Your team members are
    humans too…

    View Slide

  37. View Slide

  38. Your team members are
    humans too


    Teamwork. Be nice. Care.

    View Slide

  39. Making other humans in
    the team better!

    View Slide

  40. Be the senior you needed
    when you were a junior.

    View Slide

  41. Being able to
    communicate clearly in
    business language - not
    tech jargon - with
    business people / non-
    technical co-workers
    .

    View Slide

  42. View Slide

  43. They understand it is not
    about them, but about
    customers.

    View Slide

  44. Old people in the
    Industry?

    View Slide

  45. View Slide

  46. "The most important skill in the future will
    be the ability to "connect the dots" in your
    own way!" - Fabio Moioli

    View Slide

  47. “You can know all the cool functional
    programming techniques in the world, but if
    you are unable to communicate well with your
    team, or you are not able to focus on
    delivering actual value to a customer, you are
    not a senior developer.”

    View Slide

  48. Thank you!

    View Slide

  49. Questions?
    Antonio Perić-Maža
    r

    t: @antonioperi
    c

    m: [email protected]

    View Slide