This article was originally published on Hashnode for the 4 Articles in 4 Weeks - Hashnode Writeathon.
In this article I will share 7 most useful articles that have made a big impact on my engineering journey. And I believe this will help anyone make a big impact on their own journey.
1. Teach Yourself Programming in 10 Years
When learning a new language it is easy to think you can just watch a 1-hour video on Youtube and Boom! You are now a master coder.
Truth is, that's not enough time. To be a a good programmer, you must be **passionate about programming; you must program; talk to other engineers; read their code and collaborate; Learn multiple languages with different styles, not just OOP languages. And this will take some time.
It's a timeless article. And it is worth bookmarking.
2. Don't Call Yourself A Programmer
How do you write your Twitter bio? how do you tell others what you do in a few words? Written by Patrick Mckenzie, Patrick suggest rather than calling yourself a programmer, you sumarize your most important experience and wins e.g I'm the software engineer who wrote the HTTP Request class on Laravel.
3. Always Be Shipping, Always Be Writing
You may not start your own blog, but sharing knowledge can bring lots of opportunities your way.
Jeff Atwood confounder of Stackoverflow who is the author of this article advice you pick a schedule and stick to it. If you have a good message, you will find success - over time.
4. The Pragmatic Programmer
HugoMatilla / The-Pragmatic-Programmer
Summary of the book The Pragmatic Programmer by Andrew Hunt and David Thomas
This is my summary of the The Pragmatic Programmer, by Andrew Hunt and David Thomas. I use it while learning and as quick reference. It is not intended to be an standalone substitution of the book so if you really want to learn the concepts here presented, buy and read the book and use this repository as a reference and guide.
If you are the publisher and think this repository should not be public, just write me an email at hugomatilla [at] gmail [dot] com and I will make it private.
Contributions: Issues, comments and pull requests are super welcome 😃 There is a Quick Reference at the end.
Table of Contents
A great book to read. A pragmatic programmer is proactive; fix problems before they get bigger; open to new knowledge; and also more importantly a catalyst. Can't read the book? Hugo Matilla did a summary on Github which is the link above.
5 / To get rich, make something people want
This is a popular one from Paul Graham of Ycombinator. You may not want to get rich and just reading won't increase your bank account - it may reduce it. But it encourages you to create things people want - even for programmers.
6 / Have a Maker's Schedule without ignoring the necessary
As a programmer you can't avoid meetings, it is part of your career. But you can organize your schedule in such a way that you won't have to think of attending a meeting. This article was also written by Paul Graham.
7 / Learn to explain your simple projects to any employer
How I got my first job as a developer by making simple projects seem big
Julia 👩🏻💻 ・ Aug 25 '22
To win or get hired, you must clearly explain yourself. In her article @yuridevat shared how she landed a job by explaining her simple projects.
Thanks for reading - I appreciate it.
Top comments (6)
wonderful list, thanks!
Glad to know you like it.
You can add my article in this also.
How to become a good developer?
MD Sarfaraj for This is Learning ・ May 13 ・ 3 min read
oh, good suggestion. However I simply listed articles that has made impact on my experience. Most of them are as old as the 21st century but still relevant than some recent self help articles.
Wonderful list!👍
While reading, I felt as if every article was exactly what I was looking for.
Good to know. Thank you for taking the time to read.