Starting a career in programming can be intimidating. Whether you're switching careers, joining a bootcamp, starting a C.S. degree, or learning on your own, Your First Year in Code can help, with practical advice on topics like code reviews, resume writing, fitting in, ethics, and finding your dream job.
I was crying internally by the time I was reading the appendix. This would really help people starting out in tech. I definitely wish I had read it sooner, I would have known what all those buzzwords meant instead of trying to google them later on.
Especially liked the chapters on burnout, DevOps and ethics.
I am not a developer, I'm more into design, but I am looking to improve my skills in Html/CSS. I stumbled upon this book and I loved it! It is simple, packed with tips but easily understandable for those like me who know next to nothing about programming.
There are sections about history, about code conventions, about what to study and what not to, about looking for a job in development etc. It is not a very long book but it's better like this, too long would have been too many information while it is more focused this way. There are different authors and the style can vary a bit from chapter to chapter. Overall I feel like I learned a lot from it and am more prepared to learn more about programming.
What a terrific resource for folks either thinking about getting into tech or who are newly working in the field. If you are an engineer or work with engineers, this book gives you an understanding of what you need to be successful and happy in your chosen field.
We all write codes. because we are programmers/coders/developers/software engineers. we have a dream to change the world through our special codes or applications. we all wanted to be better / seniors / whatever you wanted. but we fall into imposter syndrome in our first year of code life. we feel the anxiety for some reason and can not produce good code and the final result is our product can not see the face of the sun. we have to overcome those situations but we do not know how can we overcome or how to get out of this situation? good luck for you some of the experienced developers comes to help you grown up. they wrote a book called "Your First Year in Code". This is a very important book for newcomers or junior developers who are looking for some tips and wanted to be a senior or better developers/engineers whatever title they wanted. so do not waste your time grab the book from the below link and start reading. I found this book very use full and thats why I am sharing it with you.
"Programs must be written for people to read and only incidentally for machines to execute."
Very welcoming guide into coding with several perspectives from different authors that helps you understand and get a first view of the whole field without being too specific. Chapters are independent and let you focus on what you wan't or need to know without having to follow any fixed path.
I wish I had this book when I first started coding. Full of stories, some history, and some career advice. I wish I had this book when I first became a leader - to help remind me what my peers and team members were thinking when they started.
I wish I had this book back when I first started learning to code. The book title says it all. For new programmers having their first year in code, I strongly recommend this book.
Taking into consideration the fact that I usually read & review fiction books, it is kind of funny that the first book I actually *finished* this year is a book about coding. This one contains lots of practical advice and different perspectives. I wouldn't lie if I said I knew 85% of the stuff already, but the other 15% were absolutely worth reading it. Plus, the delivery is brilliant (I died laughing during the "How to code" chapter) and I found some other chapters like "Women in code" extremely relatable.
If I had read this book in 2017, it would have been so much easier to get familiar with the world of programming. Unfortunately for me, this book only came out in 2019, but I can only be happy for people that will get to read this book in the beginning of their career journey.
Read it after 2 years already in tech. Some chapters were relatable to the heart. Some chapters were trailer to what's going to happen in the future. My personal favorite chapters are:
You are an interpreter. Burnout. Software development beyond the keyboard.
Terrific book filled with tips and real life experiences shared by multiple writers. A must read for anyone interested in programming, starting with it or in their junior years.
This is a helpful read, both for understanding what to expect in the first year and how to optimize it. Code is just a tool for implementing algorithms that solve user problems. Consequently, code is best used in the social context of communicating with those we work for. We should work together as a team to understand various demands and desires and translate them into a coherent idea and 'application' everyone understands, including the computer.