Chapter 4 Reading

Chapter four is about writing comments. This chapter surprised me by saying comments are not typically a good thing. They make up for poor code that does not explain itself. This contradicts what I have learned throughout my few years coding here. I usually lose points on assignments if I do not add a great deal of comments explaining my code. This leads me to believe that my teachers do not expected us to write professionally when making our code. The chapter talks about using TODO comments. That is a practice that I have done when I know I will be taking a break from writing that part of the code with the intent of coming back to finish it. If you can avoid using comments by writing self explanatory code, then you should do so. However, when this isn’t possible, you should write short comments that explain what is happening in the code.

From the blog chanson2016 by chanson2016 and used with permission of the author. All other rights reserved by the author.

Chapter 2 + 3 Reading

Chapter two was a very repetitive chapter. The main point of the chapter was to make sure you pick names for variables, methods, classes, and objects that make sense. The names should be understood by everyone and be easily distinguished from any other names used. The complexity of the names should also reflect the complexity of the variable or method.

Chapter three is about functions and how they should be simple yet effective. They should only do  one thing and have descriptive names that describe what that one thing is. You want your functions to be well organized so that they are easy to follow. You have to be willing to change your functions to keep them organized. You should make sure to have tests that pass no matter how you change them around.

These chapters are about keeping your code organized and easy to follow while still being functional.

From the blog chanson2016 by chanson2016 and used with permission of the author. All other rights reserved by the author.

When to say yes, when to say no..

I believe for any software developer first beginning their career they want to be “Yes Men”. We are so eager that we have what it takes to be a professional we don’t know what the word “no” means. “Can you stay late and complete this? Can you make this all by yourself? Can you do that… etc” We want to belong, we want people to believe in us, we want a paycheck every week. This saying yes all the time must be a stage because once we actually know we belong, we learn our limits. We learn from experience that we need a team to complete something, we need time away from the office to be productive, we need a life outside of work to keep our heads in the game while we’re working.

 

Chapters 2 and 3 of “The Clean Coder” emphasized these points concisely and effectively. By only saying yes, you agree to add features that cannot be implemented and this in turn shifts focus away from the primary goal. Learn to say no when appropriate and work hard and deliver when you say yes and respect will be earned. I believe Martin said it best when he stated, “Professionals know their limits… Professionals are not required to say yes to everything that is asked of them. However, they should work hard to find creative ways to make ‘yes’ possible.”.

From the blog CS@worcester – My Progression as a Developer by xg2016 and used with permission of the author. All other rights reserved by the author.

When to say no… and when to say yes

Chapter 2 of clean code deals with learning how to say no in a professional environment. The chapter is very helpful in the sense of giving example of exactly why you should never commit yourself to something that you will not be able to carry out completely. If you overbook yourself and commit to jobs that you are not able to complete you will create a chain of problems that will come back to you later in the future. The moment that you tell your boss that you can “possibly” get something done, the expectations have been set at the point and there will now be disappointment and possibly consequences depending the the importance of the project that you are working on. It is also a let down to your team when you begin to commit to things that cannot be done because you will often drag others down with you.

However, this does not mean that you should not take on tasks that will challenge you because life should be comfortable and easy. By all means if you know for a fact that the task being asked of you is something that can be tackled, than DO IT! Showing that your team can perform on demand and have fantastic outputs is a great thing, but it is very important to ensure you do not allow yourself to be taken advantage of. It really all comes down to a very simple phrase by a very wise man..

“Do; or do not. There is no trying.” – Yoda

The Clean Coder Chapter 1

Chapter 1 of the clean coder written by Robert C . Martin covered a number of topic that apply to workers as they enter their professional work environment. The transition between being a student and a being a professional in the work field is a tremendous difference. Responsibility is probably the most significant factor regarding working in a professional environment. Anything that you say, do, or create is directly attached to you, and you should take pride in the things that you do. With this being said it is very important that you stay up to date with things and be sure that your work is something worth sending out for other people to see. In order to stay up to date with the changing times and technology, it requires you to take a good portion of your own time and do further reading and studying in your field. Spending time outside work to further your career is a very good investment of time because it will allow you to increase your skills, while at the same time making yourself a much more marketable employee for future employers who could potentially hire you. Your work should not be faulty to Quality Assurance. What this means is that you should not be known as the person who always has issues when the code is send off to be tested. You want to be known as the person that has the code that is impossible to find problems with.

All in all this was a very good chapter and I really enjoyed the reminder of learning outside of work and being sure to exercise pride and caution in everything that you do.

The Clean Coder Chapter 2 and 3

After reading chapter 2 and 3 of Clean Coder I understood that saying no is part of being a professional. Sometimes managers have unrealistic expectations in the limited time. So, whenever you think that you won’t be able to do task on time you should say no instead of saying “I’ll try”, because that will give a false impression to everyone that the task is doable. Professionals are also expected to explain their positions, and come up with viable alternatives. Professionals negotiate with their superiors until both parties are satisfied with the chosen direction. On the other hand, saying yes is as important as saying no. When you are sure that you are able to do the task on time you should say yes. But you should be careful about saying yes, when you say yes you make a promise and you should work hard to make yes possible.

From the blog cs@Worcester – siminshamsblog by sshamsfallah and used with permission of the author. All other rights reserved by the author.

Clean Coder Chapters 2&3

The readings from chapters 2&3 were mainly about knowing when and how to say yes and to know that it’s okay to so no. One must present themselves professional after stepping out and should be realistic regarding their commitments with the given tasks. Working on a particular task with so many responsibilities, we should know ahead what we are capable of before committing by saying yes, and it is completely fine to let the manager know that you won’t be able to finish the given task on time. Saying no is definitely very difficult for us, but by doing so, can prove to be beneficial by managing expectations regarding what is possible and what is not possible. These two chapters were very helpful and taught us how to deal and handle with various commitments and responsibilities in the workplace and be a professional programmer which are very helpful for us to build a successful career ahead.

From the blog CS@worcester – pavanimothe by pavanimothe and used with permission of the author. All other rights reserved by the author.

Setting up OpenMRS Evironment

Setting up the environment necessary to run OpenMRS on my system turned out to be quite the process. I think that the major reason that it gave me so much trouble was all of the previous years of “stuff” that had gathered on my laptop. I have a Macbook Pro running OS X El Captain.

The installation procedure was relatively straight forward. You begin the process by downloading the OpenMRS repository from git hub and storing it in your desired location. After downloading is complete you build OpenMRS using Maven, and begin to set up the server. Once at this point, you navigate into the directory with the server and start it up. If this runs for you without complaining about anything, that wala! Your almost done! Mine however had many issues that were preventing it from installing. Many of my issues had to do with things that needed to be updated and properly assigned (i.e. Java). Once the server is going you need to install a GUI that you can use to interact with the OpenMRS system. For the purposes of this class we installed the Legacy UI.

For me the one issue that was continuously surfacing was the Java on my machine not lining up with the Java that the compiler was searching for. After many struggles and much consulting I finally got the Java pointing to the right directory. Once this was corrected everything ran perfectly, and there were no further errors.

Clean Coder Chapters 2-3

In the reading for Chapters 2-3 I read about knowing when and how to say yes and that it is okay to say no. The biggest thing that I took from this reading that I hope to use in my professional career is to not make promises or say yes to something I know will not get done or not be finished on time. It is better to be honest and tell the manager or boss that you won’t be able to do a task. I hope to be more upfront with people as stated in the yes chapter where he mentions what commitment sounds like. There is no uncertainty and there is no hesitation. I believe that after the readings there is a clearer understanding for myself what saying yes and no really means and when to chose to say either of them. It is the simple words yes and no we use everyday but as a professional in your field you need to know it means more than just a work to make someone happy, you gave them a commitment that you are expecting much like you are expecting your co workers to do their part in the project.

From the blog CS@worcester – Greg Tzikas by Greg Tzikas and used with permission of the author. All other rights reserved by the author.

Setting up Environments suck, a lot.

Really, it does. It usually goes one of two ways. Scenario One: You are starting a new project  and all the perfect little tools and programs you’ve been using get tossed out the window for a new dev kit or a new compiler. Everything that you’ve had set up for months is just tossed out because the new project you are doing doesn’t use a single thing from you’re last project. Scenario Two: (The one I just had to go through.) You join a project that has been going on for a while, they tell you how they set up their environments, but its never quiet the same. Stuff gets updated, freeware they used gets removed, maybe a component or two now conflict as they have different versions, and one of them, the one that is vital to the project hasn’t been updated in months and all current downloads are busted.

Sounds like a blast, right? So you improvise, trying to get substitutes working, but the thing is most of the team has everything set up just right, and having them try to help you troubleshoot just a slightly different program than the one they had never goes anywhere. But you mange to get to the right setup eventually, or one that’ll do. So here is what I did: Cloned a project from OpenMRS, a very large opensource program my CS class is working on. Easy enough, github is a rather well polished program that is easy and simple to use. Once I got the massive collection of files onto my computer I started to get a JDK setup for it. The initial suggestion was IntelliJ. That sure as hell didnt work. After a couple of days fiddling with it, most of the class gave up on it and moved back to the tried and true eclipse program. Its solid enough and everyone is very comfortable with it, so it was a good choice. Next on list of programs I need for this project was Maven. Cool, Ive used it before, had it setup perfectly a few years back. Since then Ive had a few wipes on my laptop, so I had to get it working again. Of course, the second time wasnt as easy, in the end I figured out I had misspelled one of my environment paths for it, such a silly mistake cost me hours of confusion and annoyance. Then end was in sight! All i needed to do was get the command mvn jetty:run to work and the battle was over. And mvn failed to launch. guess who also didnt have MySQL installed. Also did have that at one point, but hey my computer likes to fail every so often once I mess with settings and things that shouldn’t be messed with. At least SQL was painless to install. Tried that magic command again, and this time it was a success! The battle with setting up my environment was over, I have conquered the mighty beast and got everything running correctly. At least until my next project in 6 or 7 months…

From the blog CS@Worcester – dkayak by Code Complications and used with permission of the author. All other rights reserved by the author.