LDSTech 2015 Conference
LDSTech Missionary Opportunities
Design Patterns Print E-mail
Written by Mark Tebbs   
Tuesday, 19 May 2009

Software has been written and rewritten to solve the same problems, in a number of programming languages. In an effort to reprocess solutions to commonly occurring problems, design patterns were created. Design patterns provide a way to reuse experience rather than creating new code. Design patterns are simple ways to use proven experience to create higher quality software, regardless of the programming language.

Design patterns fall into four categories: creational, structural, behavioral, and concurrency. Five examples of design patterns include:

  • Adapter
  • A design pattern that allows one system to adapt to another system that is not compatible without changing the interface of either system


    Client Interface = new Adaptor(Old Interface)Enumeration enumeration = hashtable.elements();
    Iterator itr = new EnumerationAdaptor(enumeration);

    Calls made on the Iterator object will be translated to the Enumeration object.


  Add Comment

The Evolution of the Church's IT Department Print E-mail
Written by Tom Johnson   
Friday, 15 May 2009

Length: 24 min
Download MP3

In a recent poll on podcasts, at least 25% of you reported that you listen to podcasts more than twice a week. Because of this interest, we thought we should expand our content to include podcasts (in addition to article posts).

For those new to podcasting, podcasts are audio shows that you can download to your MP3 player and listen on the go, usually while you’re driving or exercising. Podcasts allow you to listen to content relevant to your niche interests -- at the exact time and location you want to listen.

Add Comment

Automation of the Information Technology Infrastructure Library Using IT Service Management Suites Print E-mail
Written by John Irwin   
Tuesday, 12 May 2009

What Is Information Technology Infrastructure Library (ITIL)?

IT service management (ITSM), a discipline for managing information technology (IT) systems, evolved naturally as IT services required support. At first, IT focused mainly on application development. To incorporate the benefit of these new technologies, the focus then shifted to delivering the created applications as part of a larger offering, supporting the business.

The help desk was developed to help people as they used IT serve services in their business. The U.K. government embarked on a project to discover and document how industries approached service management, thus creating the Information Technology Infrastructure Library (ITIL), containing over 40 books about ITSM. In 2004, Version 2 of ITIL was created, releasing nine books that bridged the gap between technology and business with a strong focus on the processes that effectively serve the business customer (see Figure 1).

Add Comment

Teaching an Old Dog New Technologies Print E-mail
Written by Aimee Smith   
Thursday, 07 May 2009

Fetching the paper was once a useful and impressive skill for a dog to have. To keep pace with technology, though, Fido now needs to be able to get online, create a registration, subscribe to a news feed, and download a podcast. Fido has his work cut out for him—as do we—to keep pace with the increasingly diverse and complex technologies available. We must not only maintain our current service levels, but remain as appealing to our customers as that new puppy in the window. The trick is to identify and manage the gaps between the technologies we have, the technologies we are developing, and technology trends.
Old dogs have been trained until we are comfortable with them and they meet our needs. Working with old dogs is like working with old technologies and platforms. They require an investment in time and resources to ensure that the environments are operationally efficient, that we have skilled staff, and that documented processes are utilized by those who build and maintain the applications running on these environments. We develop a good relationship with old dogs; we know what to expect, and we understand what we can deliver through these environments.

Add Comment

FamilySearch Facebook App Developer Wanted Print E-mail
Written by Cassie McDaniel   
Tuesday, 05 May 2009

FamilySearch is searching for a volunteer developer to help create a Facebook application that will read the FamilySearch API. This individual will work with FamilySearch in discussing, designing, and developing the application. Anyone who has experience creating Facebook applications and is interested in this project is encouraged to contact Gordon Clarke by phone at 801-240-0770 or by e-mail at This e-mail address is being protected from spambots. You need JavaScript enabled to view it .

Add Comment

LDSTech on Twitter Print E-mail
Written by Cassie McDaniel   
Friday, 01 May 2009

You can now receive updates from LDSTech by following us on Twitter.

Twitter is a free service that allows users to send and receive short updates.

We will be using Twitter to inform you about featured articles, opportunities to help with Church projects, hot topics in the LDSTech forum, and job positions.

Read Tom Johnson’s article about Twitter and LDS General Conference for more information about how members of the Church use Twitter to communicate.

Add Comment

Does the Church Really Have Technical Writers? Print E-mail
Written by Tom Johnson   
Wednesday, 29 April 2009

At one of the last technical writing conferences I attended, I ran into a few technical writers who looked at my nametag (which listed the organization I work for) and suddenly perked up with questions: Does the Church have a lot of software? Are there really technical writers in the Church? They looked puzzled.

These questions never cease to amaze me. For an organization of our size, it seems obvious that the Church must have some administrative software and technical writers, but exactly who or how many or where they’re located is a mystery. In this article, I’d like to unfold some of those fuzzy details about technical writing in the Church.

Managing Church Information Technology Print E-mail
Written by Tyler Cooper   
Wednesday, 22 April 2009

The diversity of the temporal activities of the Church requires IT professionals to have flexible service offerings. We try to use industry-based applications and services to minimize our IT resource requirements, avoiding additional human resources costs. We rely on partnerships and contracts with Brigham Young University, numerous Internet service providers, telecommunications providers, software and hardware vendors, and outsourcing companies to move the work forward in a cost-effective manner. Managing IT at the Church is challenging due to diversity, scope, language requirements, and multiple vendor agreements.

We use industry best practices to ensure that we use resources effectively and efficiently. We use diverse software development methodologies, such as waterfall and Agile, to meet the needs of each project.

Add Comment

Meetinghouse Webcast Print E-mail
Written by Cassie McDaniel   
Wednesday, 15 April 2009
Meetinghouse Webcast, as described on LDSTech, makes it possible to broadcast a one-way audio and video feed from one building to multiple buildings.

In a world where travel is expensive and time is precious, Meetinghouse Webcast can help reduce travel time and increase the number of people who can attend meetings. It can be used for any appropriate meeting, such as stake and regional conferences, firesides, and training sessions.


Is Your Database Application Armed? Print E-mail
Written by Lynn Conrad   
Wednesday, 08 April 2009

When debugging an application that is not performing well, finding the real issue can be very hard. Is it The LAN? The WAN? Is it the application server? Load balances? DNS? LDAP? The database server? Maybe it is the SAN or a disk storage device. We can do things to make it easier. You can arm your application and build it so that it is ready to do battle in the complete operation arena that it will be required to run in.

Arming into the DB Layer

Most databases have a procedural language and the ability to trigger audit transactions, and drive functionality. You can also build in debugging triggers that can track what is happening in the app. You can design your procedures and functions to do the same. If you track how long each type of transaction or call takes to complete, and what the parameters were when a function or package is called, then you have a great tool for debugging development, as well as identifying production issues. If you see that the “create new” function doesn’t take any longer to complete than it did before the slowdown, then the database is not the issue; it must be further upstream. If they are taking substantially longer, then it must be downstream (disk, server, DB configuration, DSS queries in an OLTP database, etc.).

Add Comment

<< Start < Prev 31 32 33 34 35 36 37 38 39 40 Next > End >>

Page 37 of 49

LDSTech Conference

Watch session streams from
LDSTech Conferences.

LDSTech Missionaries

Learn how to become a full time or part time LDSTech Missionary.

Meetinghouse Technology

Support for Meetinghouse Technology is available on the MHTech site.

LDS Connected



Email Email
Twitter Twitter