Have had a chance to read a great article by @dangoslen:
levelup.gitconnected.com/my-biggest-mis…
The lessons he learned at the beginning of his #SoftwareEngineer career are quite similar we've encountered on our path and put as principles for junior #developers.
What are those principles? 🧵
levelup.gitconnected.com/my-biggest-mis…
The lessons he learned at the beginning of his #SoftwareEngineer career are quite similar we've encountered on our path and put as principles for junior #developers.
What are those principles? 🧵
Principle #1: Don't listen to your ego — talk to your team
Stop caring about your thoughts of what other people might think about you. It shouldn't matter to you.
Always talk to your team when you are in trouble, share your thoughts, get answers/help, and continue growing.
Stop caring about your thoughts of what other people might think about you. It shouldn't matter to you.
Always talk to your team when you are in trouble, share your thoughts, get answers/help, and continue growing.
Principle #2: Be braver — say (nonsense) aloud
A similar one, but still quite different: if you get an idea or thought - say it aloud during tech meetings, discussions, one on ones and so on.
Doesn't matter how bold it is - don't hold it back. Say, get feedback, and move on.
A similar one, but still quite different: if you get an idea or thought - say it aloud during tech meetings, discussions, one on ones and so on.
Doesn't matter how bold it is - don't hold it back. Say, get feedback, and move on.
Principle #3 (unpublished one): Take on responsibilities proactively
This one is another way of looking at Dan's issue when he got comfortable with the problems set at work.
Dan's recommended to start investing some time into non-work coding (open source, side projects, etc)
This one is another way of looking at Dan's issue when he got comfortable with the problems set at work.
Dan's recommended to start investing some time into non-work coding (open source, side projects, etc)
It's a great choice.
Alternatively, you can start taking on new responsibilities at your work and fix problems, other engineers do seem to ignore:
— Find an old dependency that is bothering devs working on the product and learn what will take to migrate to a newer version.
Alternatively, you can start taking on new responsibilities at your work and fix problems, other engineers do seem to ignore:
— Find an old dependency that is bothering devs working on the product and learn what will take to migrate to a newer version.
— See how errors are logged and stored - may be right now your team is relying on basic `console.log`s which does not provide enough information and cannot notify you about emergencies quickly
— Invest some time into learning how to prepare releases, how to rollback in case of an emergency, what CI or other tools your team is using for building products, and deploying them. Check out whether it's possible to speed releases or automate them even more.
Taking on these responsibilities makes you learn new tools, concepts, and technologies.
It teaches you to fix and improve the things that matter, which many engineers often reluctant to do - as this is often not a straightforward #coding or algorithms knowledge exhibition🤷♂️
It teaches you to fix and improve the things that matter, which many engineers often reluctant to do - as this is often not a straightforward #coding or algorithms knowledge exhibition🤷♂️
Your company's business will also benefit from you solving these problems, though it may happen indirectly - through faster releases, quicker bugs reaction, improved developer experience (DX), etc..
While you will expand your knowledge and become a more experienced engineer 🥷
While you will expand your knowledge and become a more experienced engineer 🥷
If you interested more, we recommend you to read a full-fledged article explaining these principles: dev.to/bandaworks/pri…
And at the same time, we highly recommend you reading Dan's article as well - it'll help you make your career start even greater 😉
And at the same time, we highly recommend you reading Dan's article as well - it'll help you make your career start even greater 😉
• • •
Missing some Tweet in this thread? You can try to
force a refresh
