Monthly Archives: February 2014

Jan 27 Class Work and Reading

Well, the classwork from last time was certainly more than the usual busy-work that most first-classes tend to be. Granted, given how rarely this class is planned to meet, such a thing is pretty much understandable. All in all, it’s a shame that we couldn’t finish everything during the class time, as I’m still not completely sure how the Git and IRC things are going to work. I’m pretty sure I either missed something or got lost in the Git activity, as while I could make it work on the online (GUI?) interface, I never got it downloaded to the program on my laptop. Was planning on going through everything again on my own time, to find what I missed, but I never saw the activity document posted… The fact we never got to the IRC part didn’t help my understanding of that, either.

The readings were interesting, if almost predictable, in content. I myself am fully aware that I can tend to overlook things, and it’s a great help to have more people pointing out problems and solutions to you (Cathedral and Bazaar). Heck, even outside of programming, this is a proven concept. I can’t count the number of times the attendant in charge of the shift before mine at my part-time job could not for the life of them find what was making their drawer off, only to have myself (or the next person coming in after me, should I get the first shift) take a look and point out something either misread/misused, or even unaccounted entirely. It was certainly nice to see how such things began evolving and was taken to the extreme with some computer programming. It’s long been known that, where the Internet is concerned, there is little to no privacy and information gets hacked all the time, but to see it used to create such a large project, then turn around and say ‘hey, rather than going to look for information to rip out and use, why don’t we all just open it up and work on it together?’, and turn things around to the point that innovation happens so quickly and so often….. It really is a whole new age that this sort of idea has brought about.

On the second reading, on Free vs Open……. Well, to be honest, it’s really not the type of argument that I generally get in to. From my own understanding, the main difference between the two terms stems from a difference in understanding the intended meanings of the terms. There have been numerous times in my life where I, personally, have had instances where I say or possibly do something and have my meaning be misunderstood. To me, misunderstandings are something that happens pretty much all the time, and are the reason why things should be taken with a ‘grain of salt’, as it were. From my own understanding of the reading, the biggest differences between the two terms are the ‘ideas’ and ‘philosophies’ behind them. Sure, there are some issues about ‘open software’ being restricting in the sense that ‘you can’t freely modify, use, and redistribute it’, but that seems to be a more minor justification to the argument that was presented. The real ‘argument’ is about the ‘freedom’ aspect of both, where people say that ‘open’ software isn’t truly ‘free’ software; and maybe in some cases, they’re actually right, but from what I understood of what I read, they’re also complaining about ‘free’ software that is labeled as ‘open’ and claiming it shouldn’t be called as such, even though the software in question still falls under the qualifications of ‘open’ software. I’m the type who cares more of the results rather than the ‘spirit’, as it were, so the whole thing starts coming off as pointless squabbling when there are other, better things to be doing with one’s time and energy.

As for our final reading work, the OpenMRS Developers Guide, well, it kinda reads like a brochure, but it’s nice to know just what we’re going to be working on. Having some background and information on just what you are helping to accomplish can be a rather great motivator. Now let’s see if we can’t start making differences in the world at large while getting some real life, practical experience in there as well.

From the blog Kyle's Works » CS@Worcester by kyleprimmer and used with permission of the author. All other rights reserved by the author.

Week One

I hope that this class gives me a better idea about how working on a large scale project is, especially working with others who are all remote. I agreed with the beginning of the cathedral and the bazaar, with how it would make sense that large scale programs should be more closely controlled so that they work better together. Linux operating systems seem to be the exception to that rule though. 

From the blog ckelley6 » CS401 by ckelley6 and used with permission of the author. All other rights reserved by the author.

Expectations

I am looking forward to working on this open source project! I am very excited to see how we can develop the project as a team and maybe make a real world impact. I am a big fan of open source projects, I use them at work daily and at home as-well. I have never worked on an open source project and I cannot wait to get started on this one!

From the blog tbruceblog » cs401 by tbruce731 and used with permission of the author. All other rights reserved by the author.

What I’m Expecting..?

Well, this is probably shaping up to be the first computer science class the most involved with things to do outside the classroom. Never really had a blog or anything else to that nature before starting this class, so that’s probably going to cause me some headaches.

What am I expecting out of the course itself..? Well, I generally try to go into things with an open outlook, so I can’t really say I’m “expecting” anything. We’ll just have to see how things go. There seems to be a good amount of expected reading to start with, at least.

What I expect to take away from the course..? Probably something along the lines of ‘a better understanding of the greater world of computer science and how programmers and developers get in touch and interact with one another in an open environment’. Well, something like that. I never claim to be the best at putting thoughts into words.

All in all, it’s shaping up to be an interesting experience, all things concerned. Let’s see what we can learn…

From the blog Kyle's Works » CS@Worcester by kyleprimmer and used with permission of the author. All other rights reserved by the author.

Course Expectations, Reading Assignments, Git Activity and IRC Activity

My expectations of this course is to gain a solid foundation on the complete developmental lifecycle of a piece of software along with the legalities surrounding the licensing or freedoms that go along with it. I have previous experience in Agile/Scrum so I would like to build upon those previous experiences of being part of a development team and I also intend to become an active member of the OpenMRS community.

I enjoyed reading the three articles. In the article the Cathedral and the Bazaar, I felt that Mr. Raymond focused more on the bazaar methodology and his transformation of popclient to fetchmail. Although Mr. Raymond makes valid points about the Bazaar methodology and its ability to produce software that is robust and cutting edge by releasing early and often and having many sets of eyes analyzing a particular problem which in turn lead to less buggy software. I believe it is also necessary to have proprietary software. I think having closed software creates a healthy competition between companies to expand and advance their software while at the same time supplying hundreds of thousands with jobs. In one of Mr. Raymond’s quotes he stated “Too often software developers spend their days grinding away for pay at programs they neither need nor love.” Well, too often carpenters spend their days grinding away for pay building houses they neither need nor love, but they do it because it’s their source of income. Unfortunately millions of Americans are unable to work on projects of passion during business hours. In the Free vs. Open readings, I was impressed with the clarity of the Free Software Definitions. With that set of freedoms you can see why a piece of free software has the ability to develop at an exceptional rate and quality. One thing I don’t understand about free software is the ability to receive a copy of software, modify that software to fit your needs and then sell your modified software for a monetary value. I understand the saying you should think of “free” as in “free speech,” not as in “free beer”., but if some people pay while others don’t pay for the same software it seems to be a little confusing and misleading. The first four chapters of the OpenMRS development guide was a great introduction on what OpenMSR is and what OpenMRS’s goal is. Open source projects like this one that have a humanitarian goal must be very fulfilling to those who contribute. It seems to be a win/win for all parties. For the patients themselves they now have the ability to have their medical information in a central place where it can be accessed, monitored and updated. It also benefits the patient by less medical mistakes where hand- written physician records are misinterpreted and incorrect medication is provided to a patient. For the software users in the hospitals and clinics it gives them the opportunity to become more accurate and efficient when entering or retrieving patient data. For the developer they get to contribute to a piece of software that can truly make an impact on millions of lives.

I have heard of IRC but have yet to actually make use of it, so I am looking forward to using it. While I was working at MasterCam CNC Software Inc., if a team meeting were taking place over the internet we would generally use Skype or some form of Go to Meeting. Skype was great because you could easily embed code snippets right into the textbox for your group to see. It was also great for quickly sending files and links to team members.

The Git activity was interesting. Using the Git Bash felt a little foreign to me. I’ve used version software before called TortoiseSVN. TortoiseSVN came with a pretty polished GUI that made finding and handling conflicts on large files a breeze. Push, pull and commit were also simple. I liked the way it displayed and highlighted conflicting areas of the files side by side, which could make a real stressful commit a little less stressful. I’ve also noticed that Git comes with a GUI so I think I will use that feature while working on OpenMRS.

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

First Week, CS-401

Well then, the OpenMRS is certainly a very large and interesting project to say the least.  But with such a large and ongoing effort to provide an Open Source EMR database one is immediately struck with the question.  “What could (what I consider) a novice programmer possibly contribute to such a large ongoing effort?”  The upcoming few months will certainly answer that question without doubt.  As for the time being, I am very excited to be working (soon) be working and contributing to the OpenMRS community.

My expectations of this course are already set quite high, with the hopes of simply becoming a much more savvy programmer.  My only regeret is not being introduced to such sources as GitHub and exposure to other open source projects sooner, but that cannot be helped at this point in time. On that topic, over the Eric S. Raymond’s article The Cathedral and the Bazaar have also opened me up to the raw potential  — and how powerful open source communities can be.  Maybe my current inexperience will still be of good use to the OpenMRS project after all.

From the blog aboulais » CS WSU by aboulais and used with permission of the author. All other rights reserved by the author.