Week 4: 7th February – 14th February

This week was more exciting since we began to work with Open MRS AMPath. Building the project was like any other node application. In the terminal, I navagted to the root app folder and used “npm install”, and “npm server”. This started the ng2amrs test local server and was easy to log into. It seems you can not halt the server forcfully or you will not be able to restart it unless you reboot your machine. I have watched hours of Scotch.io tutorials and look forward to rewriting the Authorization Module. It does not seem complex since they import the OpenMRS authorization Module making the hard work already complete.

Let see what this next week brings!!

From the blog CS443 – Triforce Code| Exploring and Learning by CS443 – Triforce Code| Exploring and Learning and used with permission of the author. All other rights reserved by the author.

Week 3: 31 January – 6 February 2017

This week was a slow week out of the semester since we were finishing our tour of heroes.

We have learned a lot about routing, two way binding and the nifty features angular provides. It is sad to note that Angluar does not have a built in sorting algorithm since it added complexity and making a flexible application framework requires light weight and freedom for developers to implement proper efficient algorithms for their use. This is kind of a cop out yet shows that every developer should know how to make efficient sorting algorithms for their programs.

Looking forward to working on Ampath.

From the blog CS443 – Triforce Code| Exploring and Learning by CS443 – Triforce Code| Exploring and Learning and used with permission of the author. All other rights reserved by the author.

The Software Craftsman 15 & 16

Chapter 15: Pragmatic Craftsmanship

Pragmatic – “Dealing with things sensibly and realistically in a way that is based on practical rather than theoretical considerations” This chapter is about encouraging mastery of skills. Stating that Quality is not expensive and doesn’t slow things down.  But Mastering skills is a bottle neck. It is your job to master these skills to provide quality software every time.

Chapter 16: A Career as A Software Craftsman

This chapter details that a software craftsman is dedicated, passionate, and driven. The software craftsman masters their skills and every day is excited to learn new things. Every day they wake up and not only go to work for a paycheck but also try to change the world one block of quality code at a time.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.

The Software Craftsman 13 & 14

Chapter 13: Culture of Learning

Some think that a culture of learning is hard to create or it cost a lot of money and time. But in this chapter, the author details some simple ways to do it. One thing that can help is hiring passionate developers. This step is the most important because passionate developers love learning new things and this can accelerate this process a lot. When you are passionate about something it doesn’t feel like a hassle to learn new things.

Chapter 14: Driving Technical Changes

One thing that is difficult with driving technical change is dealing with people. Everyone has a different stand on what you are trying to change or improve and one of the difficulties is changing the minds of all that you encounter to proceed with your project. One thing that can help change people’s minds is being able to communicate clearly what you are trying to change.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.

The Software Craftsman 11 & 12

Chapter 11: Interview Anti-Patterns

In this section, the author details some things that interviews do and some things that you should not do when looking for a developer. A classic example is the difficult programming problem to get the awesome development job but the author looks down on this. He states that there is no point in haveing a brain teaser or coding on paper without the internet because this does not make any sense. If you think about it this doesn’t help anyone. You should observe the interviewee in their best conditions not make them look like a fool. I completely agree with this.

Chapter 12: The Cost of Low Morale

Low morale is always a problem. In so situations, it can be the cause of the death of a company. Unmotivated people don’t want to do productive things or think out of the box. Companies need innovation to be competitive. Innovation is spawned by passion and drive but low morale can kill this.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.

The Software Craftsman 9 & 10

Chapter 9: Recruitment

In this chapter the author details some interesting facts about recruitment agencies. The author states that they should only be used as a last resort. This is because they are only looking at some skills on paper and don’t really care about the career development of the individual. The author says some interesting things about how to recruit for your own company. His statements are the direct opposite from what I have noticed when looking for a job. He states that you should detail culture and passion and never required experience or academic background. This makes sense when looking for a valued member of the team but has been the complete opposite of my experience so far.

Chapter 10: Interviewing Software Craftsmen

In this chapter, the author elaborates on some interesting skills to learn from your interviewers and what they will learn from you. If in an interview they are very strict then you might be able to pick up how the developers are treated within the company. He also states that developers look for more than just the technologies and the money. They look for a good environment, including a good team, a good atmosphere, and sometimes the technology. In some of my interviews I have picked up on some of these things but this chapter gives me a few more things to think about during an interview.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.

The Software Craftsman 7 & 8

Chapter 7: Technical Practices

This chapter discusses some techniques that can help save time, money, and headaches for all involved if developers can convince management that they help. Some of these techniques are:

  • Test Driven Development- Write tests have them fail, write code to make them pass, repeat
  • Continuous Integration- requires developers to integrate code into a shared repository multiple times a day to detect problems early.
  • Pair Programming- Programming with someone else to bounce ideas back and forth
  • Refactoring- restructuring code to make it more efficient

Chapter 8: The Long Road

This chapter illuminates some potential missteps when choosing a career path. One of these such missteps is allowing your career to be directed by your job and not letting your career choose what job you get. Sometimes the skills that you would like to learn are not used in your job. If this separates too much from your desired path then maybe you should look for a better fitting job.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.

Reflection Sprint 6

Final sprint, final push with the goal of completing our problem and committing our fix. The dreams were crushed. We bit off a bit more than we could chew by trying to recreate the module to make it look better. But if we didn’t attempt that, I highly doubt our simple fix would’ve been accepted.

Unfortunately we never received a response with our questions regarding the problem. We weren’t able to climb over that wall, but overall looking back on this class we gained some knowledge working remotely for a company (especially difficulties in communication). I had fun working with Angular 2, and definitely had fun with the scrum team.

From the blog CS@Worcester – Kyle Polewaczyk by kpolewaczyk and used with permission of the author. All other rights reserved by the author.

The Software Craftsman 5 & 6

Chapter 5: Heroes, Goodwill, and Professionalism

This chapter is very similar to the chapter in clean coder titled when to say no. The author of The Software Craftsman details some situations that require a skilled and professional Software Craftsman to tell the client no. Some of these include situations where the client does not know the full extent of implementing their wants into the product. This could result in a dangerous situation for the client and it is our responsibility to enlighten them on the full context of the situation.

Chapter 6: Working Software

This chapter boils down to how good your software is. As a company and as an individual. As a company, the quality of you software can directly be linked to your flexibility. The ever-changing marketplace requires the need to be flexible to those changes for companies. This means that you need easily changeable and upgradeable software.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.

The Software Craftsman 3 & 4

Chapter 3: Software Craftsmanship

This chapter delves into software craftsmanship. The author states that it is all about professionalism. Like most jobs professionalism is very important. It is always important to provide the best that you can. This is the short summary of the chapter and I believe it to be true when applied to most facets of your life. Who wants sub-par coffee in the morning? or a half toasted bagel, or even a raw donut. I might be hungry but the point still stands no one wants less than perfect. Try to make everything that you do capture and exceed the thing you were trying to accomplish.

Chapter 4: The Software Craftsmanship Attitude

In this chapter, the author details an attitude that is always learning and progressing. This is interesting because I believe that this what I strive for from day to day. Every day I try to tinker with anything and find out how it works whether it’s my mechanical keyboard or the vending machine at my work I love learning how things work. He applies this attitude to a career. In your career, you should always be learning new things. I feel like I am on the path to this applied attitude.

From the blog CS@Worcester – Conundrums In Computing by patrickgrahamblog and used with permission of the author. All other rights reserved by the author.