I'm a new developer. Here is the top advice I've received:

0. Think like a programmer, outside of work too.

1. Programming is tough. It takes a certain kind of mindset to sit in front of a monitor and think it through a problem till the end. Develop that mindset.

2. Handwork pays.

3. Do it for fun. Be exceptional. Money will follow.

4. Care about the craft you build. Write such a beautiful code that your fellow devs would think about your code and have a nerdgasm.

5. Simple is beautiful. Anybody can make things complex. It takes a stroke of genius to make things simple.

6. Write modular code. It makes your code reusable and easy to maintain. Future developers who will work on your piece of code will appreciate it.

7. Share your knowledge. Unlike materialistic things, knowledge grows when you share it.

8. Add comments. You think you'll remember why you wrote that piece of code that way or a clever hack you created but trust me, you won't.

9. Be humble. You'll never know everything. Don't hesitate to ask for help.

10. Writing code is exciting! Of course there will be some frustrating moments. But don't give up! You'll miss a lot of fun.

I want to say I would not have been the programmer I am now, if it hadn't been for all of my mentors in my past and current job who took a chance on me.

I am socially awkward, am nervous and stutter around new people, cannot sustain conversation, and as a consequence come out rather poorly in most kinds of interviews.

But there has been 3 mentors/leads in my life so far who saw through the nervous wreck I was in the few hours of the interview and took, what felt like to me, a gamble by hiring me. My current mentor even taught me everything I know on my job and has vastly shaped the programmer I am.

A humble thank you to all the amazing mentors out there, who inspire and enable the now green engineers, who will later be the mentors of the future generation!

Programmer OAth. Just read on a github repo

0. I will only undertake honest and moral work. I will stand firm against any requirement that exploits or harms people.

1. I will respect the learnings of those programmers who came before me, and share my learnings with those to come.

2. I will remember that programming is art as well as science, and that warmth, empathy and understanding may outweigh a clever algorithm or technical argument.

3. I will not be ashamed to say "I don't know", and I will ask for help when I am stuck.

4. I will respect the privacy of my users, for their information is not disclosed to me that the world may know.

5. I will tread most carefully in matters of life or death. I will be humble and recognize that I will make mistakes.

6. I will remember that I do not write code for computers, but for people.

7. I will consider the possible consequences of my code and actions. I will respect the difficulties of both social and technical problems.

8. I will be diligent and take pride in my work.

9. I will recognize that I can and will be wrong. I will keep an open mind, and listen to others carefully and with respect.

I am a good person. I can even say I am a good programmer. I have worked hard to get where I am and that shows perseverance. Although, where I am right now is not what I expected, I am somewhere. I can do something. I have good intentions.

Someday, I will build software which will be used by millions of people around the interwebs. And they will love me, for I will have made their lives better....in some way. Some will even consider paying me for it. Not because the well placed and non intrusive donate button I put there, but out of pure adoration and bare necessity to preserve someone as brilliant and precious as me. I shall be the definition of success. But I long for neither adoration nor wealth, for I am humble or at least that is how I will be perceived.

Like flies to the honey my success will attract big evil corporations to acquire my business. And I shall spit on their wretched face....at first. I would like to be wooed. Such display of integrity shall inspire generations of programmers. Let ye be inspired. There will be those who envy my achievements and they will be mocked and shunned by my true believers. But being the kind soul that I am, I will bring back my minions, for it could a PR nightmare.

All these events will take place in a not too distant future. Sure, I am going through a dark time now, it will pass. 'tis nothing but me transitioning from a lame ass PHP coder moth to this totally badass software engineer who is also a cool bro. This eclipse of my brain shall pass. My neurons will fire in all directions like photons from the sun during late winter, for it may overheat and we definitely don't want that.

I pray to the gods of engineering to grant my wishes. Trust me guys, you will be thanking yourselves when donate my money to charities that will help me set up. But that's another scheme. Amen.

Here comes lots of random pieces of advice...

Ain't no shortcuts.

Be prepared, becoming a good programmer (there are lots of shitty programmers, not so many good ones) takes lots of pain, frustration, and failure. It's going to suck for awhile. There will be false starts. At some point you will question whether you are cut out for it or not. Embrace the struggle -- if you aren't failing, you aren't learning.

Remember that in 2021 being a programmer is just as much (maybe even moreso) about picking up new things on the fly as it is about your crystalized knowledge. I don't want someone who has all the core features of some language memorized, I want someone who can learn new things quickly. Everything is open book all the time. I have to look up pretty basic stuff all the time, it's just that it takes me like twelve seconds to look it up and digest it.

Build, build, build, build, build. At least while you are learning, you should always be working on a project. Don't worry about how big the project is, small is fine.

Remember that programming is a tool, not the end goal in and of itself. Nobody gives a shit how good a carpenter is at using some specialized saw, they care about what the carpenter can build with that specialized saw.

Plan your build. This is a VERY important part of the process that newer devs/programmers like to skip. You are always free to change the plan, but you should have a plan going on. Don't store your plan in your head. If you plan exists only in your head you are doing it wrong. Write that shit down! If you create a solid development process, the cognitive overhead for any project goes way down.

Don't fall into the trap of comparing yourself to others, especially to the experts you are learning from. They are good because they have done the thing that you are struggling with at least a thousand times.

Don't fall into the trap of comparing yourself today to yourself yesterday. This will make it seem like you haven't learned anything and aren't on the move. Compare yourself to yourself last week, last month, last year.

Have experienced programmers review your code. Don't be afraid to ask, most of us really really enjoy this (if it makes you feel any better about the "inconvenience", it will take a mid-level waaaaay less time to review your code that it took for you to write it, and a senior dev even less time than that). You will hate it, it will suck having someone seem like they are just ripping your code apart, but it will make you so much better so much faster than just relying on your own internal knowledge.

When you start to be able to put the pieces together, stay humble. I've seen countless devs with a year of experience start to get a big head and talk like they know shit. Don't keep your mouth closed, but as a newer dev if you are talking noise instead of asking questions there is no way I will think you are ready to have the Jr./Associate/Whatever removed from your title.

Don't ever. Ever. Ever. Criticize someone else's preferred tools. Tooling is so far down the list of what makes a good programmer. This is another thing newer devs have a tendency to do, thinking that their tool chain is the only way to do it. Definitely recommend to people alternatives to check out. A senior dev using Notepad++, a terminal window, and a compiler from 1977 is probably better than you are with the newest shiniest IDE.

Don't be a dick about terminology/vocabulary. Different words mean different things to different people in different organizations. If what you call GNU/Linux somebody else just calls Linux, let it go man! You understand what they mean, and if you don't it's your job to figure out what they mean, not tell them the right way to say it.

One analogy I like to make is that becoming a programmer is a lot like becoming a chef. You don't become a chef by following recipes (i.e. just following tutorials and walk-throughs). You become a chef by learning about different ingredients, learning about different cooking techniques, learning about different styles of cuisine, and (this is the important part), learning how to put together ingredients, techniques, and cuisines in ways that no one has ever showed you about before.

0) I can be as socially withdrawn as possible without getting eyes and comments on being socially withdrawn. Going to a tea house with a laptop to code in a corner sipping Earl Grey is great without getting questioned.

1) I can make whatever the hell I want. I can do whatever the hell I want. I can automate whatever the hell I want. And then I can Humble Brag™ to everyone.

2) Because it's fun. I get to meet more folks I haven't met before through hubs like this and programmer Discord servers. And we can be nerdy together.

Edit: Also because I have a fecking pillow fort on my bed made for tucking in while coding. It feels gud in pillow fort. All of us needs a coding pillow fort.

!rant
Just looking at Cap'n Proto. Too impressed by the code, Kenton Varda... Feeling so dim, just a little light.