Your First Year in Code

Author: Isaac Lyman Created time: March 12, 2021 8:36 PM Page No.: 184 Progress: ✔️

Bad Tools can waste your time sometimes.
Don’t be religious about your tools it is just a tool not a human even a living thing.

You can use whatever coding language or framework you want it is just a line of code that can change by anybody. It is doesn’t matter that much.
It’s all about the product. The user cares about what you’ve built and how it solves their problem, not so much about how you got there.

Understanding the people using our software is the highest priority of development.
If you create something using company time or computers, it may legally belong to your employer, so check your contract to make sure you’re aware of that possibility.
Use a side project to remind myself why I love to code.
Well-organized folders and files. Most programming languages and frameworks have conventions for how things are organized.
Consistent code style. It doesn’t matter what styles you choose.
start with something simple: a tic-tac-toe game, an “About Me” web page, a metric unit converter.
Burned out

I didn’t want to go to work when I woke up in the morning.
You can potentially identify it through a decrease in work performance or long-term changes in mood, it can be as simple as asking if they are okay
Engaging in non-work related hobbies and activities.
Keep your personal life separate from your work life.

Coder had the lowest Glassdoor salary of any position I looked at, even lower than Junior Software Developer.
The programmer is a term that’s gone the way of the dinosaur.
The developer is, as previously noted, an unnecessarily ambiguous title. If your job involves building condominiums, you’re reading the wrong book.
Front End Developer is a very volatile title. Not only does it have almost the highest salary variability of all the job titles researched, but anecdotally I’ve heard it defined in contradictory ways.
JavaScript Developer, a Vue Developer, or a .NET Engineer, and this is a good name.

The DevOps discipline was created to bridge the gap between developers and operations people.
The container, for the sake of simplicity, can be thought of like a tiny operating system that runs on top of your existing one and is completely portable.
If you don’t understand something, Google it. If you can’t figure it out easily, ask. No one expects you to know everything and you never have to.
If someone has told you otherwise, you’re in the wrong company. Automate as much as you can. Anything that has to be done manually is error-prone and far more time-consuming.
Never stop learning. DevOps is a great field and is evolving rapidly. You need to keep your knowledge up to avoid becoming outdated or obsolete.

If you know how to write clear and organized documentation, you can reduce these expenses dramatically.
Good planning helps to avoid wasted time and effort if the requirements change or a solution already exists.
Valuing simplicity and trusting their developers.
Any standard that a group of experts has decided is the “best way” to do something.
The three virtues.

Laziness: The quality that makes you go to great effort to reduce overall energy expenditure. It makes you write labor-saving programs that other people will find useful and document what you wrote so you don’t have to answer so many questions about it.
Impatience: The anger you feel when the computer is being lazy. This makes you write programs that don’t just react to yo needs, but actually anticipate them. Or at least pretend to.
Hubris: The quality that makes you write (and maintain) programs that other people won’t want to say bad things about.

Q&A