DEV Community

Divyansh Pratap Singh
Divyansh Pratap Singh

Posted on

Software Engineering Advices (Coding Is Easy People Don't do this?)

Essense of Software Engineering:
1. Create
2. Solution
3. To a Problem

This Problem doesn't have to be a software problem -> any problem
it can be a non-technical problem for which we create a technical solution.

  1. What makes a good software engineer? => Communication Skills

    Programming is least importatnt skill

    Why?
    Most of the SWE can solve the problem given a right set of directions
    Most of the SWE have a certain baseline which they showed in Interview to get the JOB
    No Shortage of Talent, can solve problems (even if they take more time)

    Communication => Convey in a manner that other people can understand
    Don't make them feel dumb

  2. How to get a good job / promotion? => Marketing Skills

    You arn't getting a good job because you lack technical skill,
    You aren't getting a good job becasue you lack showcasing those skills
    Be it resume, portfolio, coding profile etc
    Other people won't see unless you show them -> talk about it online, build in public

  3. If you are Good at technical skills, Communication Skills and Marketing skills => Do a Startup

  4. Never forget : "You are a Creator"

    Never limit yourself
    to one domain/ one language / one techstack

    Get into Habit of:
    Look around, see the problems which you can solve (even non-technical) and create a solution for it.
    Create more Value, because you are a creater, the value you can create is infinite.

    You can jump into any domain and pickup a skill and dominate because you are good at adaptation.

    You are wired to solve the problem

  5. Money you are making is not worth it in most of the job

    Because what value you bring to the company is 10x or even 100x of the amount you are getting paid.

    And no other profession most likely generates this amount of value for their bussiness

    You have a lot moer value than you think you do

  6. Don't think how do I solve this problem rather think why do solve this problem?

Top comments (0)