Do you write code 100% of your job time?
I’m guessing the answer is no. Ignoring the whole management part, meetings, coffee, youtube, cats, etc, even if you’re sitting at your keyboard you’re not typing all the time. So what else are you doing?
The short answer: you’re probably figuring out what to write and where to add new features (and what to fix)… so you’re mostly reading and trying to understand the code.
With around 230 positive reviews (85% of five stars) (4.7 on the average), John Sonmez made a huge splash when he published his first book “Soft Skills”. 2.5 years later we get another book. Can the new book continue his success?
Can it move you further along with your?
How does your typical coding session in Visual Studio look like?
What’s the first thing you do when you’re about to start coding?
Yes… let’s check Gmail, Youtube, Reddit, etc… :)
OK, please be more professional!
So, let’s assume my Visual Studio (2013, 2015 or 2017) is already started. What to do next?
As you might already know, I work remotely. That’s why I try to follow and read guidelines/articles that relate to that style of working. Recently, I got very curious when I saw a new book called “*Async Remote*” from the Arkency team. Let’s see what it offers.
Warning: the book is not only about remote!
Some time ago an intriguing article appeared on reddit: “Do Experienced Programmers Use Google Frequently?”. The author discussed if expert programmers use google more often than novice coders. He mentioned than using google is actually a good thing. It helps to find best solutions, validate ideas, speed the development. Google nowadays seems to be a crucial part of any developer toolbox.
Visual Studio is my main development environment. I’ve been using this tool probably since version 2003…2005. I am really happy that VS is getting more and more powerful these days and you can also use it on multiple-platforms (through VS Code, for web or cloud apps). What’s even better - it’s free for personal use or if you’re a small company (Community Version)!
Programmers are not machines that just write code. We have feeling and emotions as well! ;)
We all need to learn a lot of new things, sharpen the saw, focus, make good choices about our career path, and simply, have fun.
While most books describe the technical side of coding, not many address the psychological/business/economic side of our profession.
How to be a better programmer? What technologies should be learned? How to have fun when coding? Read more to see where are the answers for those questions.
Intro Programmers have this wonderful opportunity to often pursue a dream career path. Lots of us would not like to only pay the bills but actually change the world as well.