The Software Craftsman chapter 9 & 10

Chapter 9 talks about recruitment, essentially how recruiters should go about searching for qualified developers. One of the problem with finding developers is how recruiters write their job description. Adding things like years of experience, academic background, certifications is how most companies job description looks like. I have done a lot of job searching in this field and i can agree that most of the description are just specific requirements needed from developers. They fail to focus on the companies culture and values and that is why they are not satisfied we developers they’ve hired.

Chapter 10 continues the previous chapter and talks about what to look for in an interview. Just like a job description should not always list specific requirements, a developers resume shouldn’t be just about knowledge and years of experience. During an interview, recruiters should be looking for passionate developers who are willing to learn or try new things. Those are the developers where if you put them in the right environment, they can really shine. One thing i can agree with from this chapter is that developers should interview other developers. A good developer will know what their company needs and what to look for; they will hire developers that are even better than they are.

From the blog CS@Worcester – Adestin by adestinyblog and used with permission of the author. All other rights reserved by the author.

Sprint 6

We ran into issues with our solution to the problem.

  1. Our fix modifies the npm webpack which is in another github repo
  2. It is a band aid solution since the weeks still shows as the pre set 2,4,6,8,16
  3. We are unable to use Travis CLI since it is not the ng2-amrs repo

In the end, we contacted AMPATH team through Slack and figured out it was through their JSON schema. We contacted the admin who had control over the JSON schema over JIRA. The admin updated the weeks to show 24, and 36 on the dropdown. The issue was then fixed and close.

It just shows how important communication is. When you have a problem, you have to be proactive and ask question on what is going on.

From the blog CS@Worcester – Site Title by nealw5 and used with permission of the author. All other rights reserved by the author.

Sprint 5

I think we figured out the issues for our JIRA ticket.

node_modules/ng2-openmrs-formentry/src/app/components/date-time-picker/date-time-picker.component.html

line 11: <li (click)=”weeksSelected(count)” *ngFor=”let count of weeks”><span> {{count}} Weeks</span></li>

This line is basically our dropdown, when clicked, it will basically iterate over the weeks list and display the count

node_modules/ng2-openmrs-formentry/src/app/components/date-time-picker/date-time-picker.components

line 19
export class DateTimePickerComponent implements OnInit, ControlValueAccessor {
@Input() modelValue: any;
@Input() showDate: boolean = true;
@Input() showTime: boolean = false;
@Input() showWeeks: boolean = false;
@Input() weeks: number[] = [2, 4, 6, 8, 16, 24];

Here is the weeks list, in the list it has 24 but it will only display up to 16 weeks.
There seems to be something funky going on with the weeks variable.

If we add another input for example:
@Input() testing: number[] = [2, 4, 6, 8, 16, 24, 36];

In the html, change weeks into testing

line 11: <li (click)=”weeksSelected(count)” *ngFor=”let count of testing”><span> {{count}} Weeks</span></li>

This will display 2 Weeks to 36 Weeks
——————————————-
1. Test this on your ng2-amrs and see if it’s the same
2. Mess around with the form submission to see if it’s stable
3. Try and figure out why weeks is basically pre set to [2,4,6,16] no matter what is put in there.

From the blog CS@Worcester – Site Title by nealw5 and used with permission of the author. All other rights reserved by the author.

The Clean Coder Chapters 5 & 6

  • Test Driven Development [TDD]
    • Hammock-Driven Development [HDD]
  • Practice
    • Martial Arts of Coding
    • Open source work
    • Programming ethics

Many topics including the above are explored in Chapter five and six. Test Driven Development we all know and maybe don’t love. Or in my situation, having little experience with it. I would like to be able to pair program in the way that is described as randori. Alternating test and solution with a partner would be a frustrating yet fun experience.

I like the mention of HDD – Hammock Driven Development, it is the idea to step back and think about your work. Since we can run our code in seconds or less now, we should consider more than just quickly rushing through the motions. Luckily using a well design test suite makes much of this thought process easier. This is important to note that you would still need to take the time and come up with  all the test cases that accurately represent your specifications.

Practicing is something we know and do every day even if we do not realize. Slowly becoming more adept at our everyday tasks as well as specialized ones we preform. Practicing is something at coding requires in our day in age of frameworks, thousands of similar tools and of course the very basic coding syntax and style.

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

Wednesday, 26 April 2017 Sprint 6

Our semester is finally coming to a close. We have picked up three more issues.

  • AA-680- Can’t add child to parent relationship
    • This issue required a database entry to be added.
    • The current entry is a Parent to Child relation ship. We need a record entered to represent a Child to Parent Relationship
  •  APTS-254 – Viral load reminder to pop up after 6 month after switching to new ART Line
    • This issue requires us to modify a ETL server configuration for reminder calulations
    • We did not have responses in time to be able to contribute to this issue
    • Large amount of questions were left for the implementation
    • Vague requirements but gave a decent start once directed to the ETL git page
  •  APTS-159- Lab Tests data should be sorted by most recent
    • We invesigated this issue and found that the sorting alorithm was in place.
      • Angular does not offer a sorting method so a simple algoritm was made by the Ampath team.

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

Wednesday, 12 April 2017 Sprint 5

It turns out we all were wrong in both what the issue was and the solution.Dan the man has completed this issue with a simple observable to wait for the requests responce to log the user out. The main issue that we noticed after this was fixed is that if you logout and get rerouted before the credentials clear you will look like you are still in the application. Refreshing reveals that you are actually logged out but it was a small gap in time that allowed it to seem like we did not log out. The issue was simply to log the user out once the prompt had been clicked to leave the drafted form. What was needed was the response from the pop up that asks if the user is sure. The logout button would just log you out and ask anyway so the prompt was useless but in the application prior to our work on this issue.

Great to have an issue done, I hope we get to work on more and have a better understanding right out the gate.

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

Wednesday, 29 March 2017 Sprint 4

Since Spring break was last week I did not focus much time into experimenting with the NGModel. I hope to continue more tutorials to try and apply the NGModel to our issue. Tyler and Dan have reason to believe that we are looking at this issue all wrong. We have many theories yet no real solutions. We noticed that the request respose is what we need to investigate to get an idea of what the code may look like as well.

This has proven to be slow moving but learning a whole lot about angular and other JS tools.

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 7: Wednesday, 8 March 2017 Sprint 3

We have finally reviewed and selected our Issue. NGPOC-185, this issue essentially is that we want the user to be able to log out but if they are editing a form then they must be prompted to exit without saving the form data or to stay at the page and continue their work.

We are not sure yet how this should work but we know we must use the Materialize CSS library since the interface for Ampath is made with this CSS package. This issue could also involve detecting if a user has ‘touched’ the form. This is a feature of the NGModel: This allows angular to detect if the form is ‘dirty’  been changed, ‘touched’ if it was edited but not altered. and ‘untouched’ if the user did not touch the form yet. Looking forward to seeing how to implement this models capabilities.

We have decided to regroup and collaborate our ideas that we may have found towards this idea. We do not fully understand the project structure so this may take some time.

 

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 6: 23rd February – 30th February

This week we have finally connected with our Project admin Johnathan Dick. We are now added to the Ampath Jira software, it is great to be exposed to these issue tracking and continuous integration tools such as Travis CI. We need to connect to the test server they have set up so we can have some data to play around with in the Ampath application.

Looking forward to starting work on some issues

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 5: 15th February – 22nd February

This week has been slower than last week. I have rewritten the authorization module, yet I feel as though I am copying and pasting their code. It is a simple module that really has the imported Open MRS Auth. Module to do the heavy lifting and take care of the passing of credentials. This leaves the routing and the request observer for login. None of this code is really changeable so I am hoping to dive deeper into the core of this application. Class has been slow moving at this point, but we are reviewing angluar 2 issues, tutorials and development in general.

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.