Philosophy: Create opportunities through the evolution of technology and innovation.

Technology

Technology

We are privileged to create technology products and services that make a meaningful difference and impact in our client's businesses and the world around them.

Why use a Framework

By: Ben Liptak
“A developer should not worry about the mundane, but do the extraordinary.”

The best frameworks sit in the background without being noticed. They provide services that are lightweight, robust, and best of all, take away mundane tasks from the user. It's less of a question of why we should use a framework and more an understanding of how best to implement one.

What makes a framework?

There are 3 core elements to any common framework:

  • Control Inversion: control flow shifts from the caller to the framework itself, freeing the caller up to do its job.
  • Default Behaviour: The framework will take initiative and intelligently perform tasks needed without input from the caller.
  • Static Framework Code: Non-modifiable code to drive the framework (and source of most arguments against using a framework…)

For a framework to last, it needs some key elements: It should be easy to extend and override, easy to implement and understand and lastly, should not limit the developer. The developer's role should be more than just connecting to a database, constructing and manage a service or communicating data to a View. Pure and simply put, a developer's deeper job is to understand and meet the client's requirements as accurately, efficiently and sustainably as possible. Let the framework do the legwork and concentrate on completing the job at hand, which is to help the client succeed.

Arguments Against Frameworks

The most common argument against a framework is that it comes with heavy overhead. While bloated frameworks exist and should be avoided, many more have little overhead at all. The flaw usually is in the implementation of the framework. A solid framework will allow you to disable or better yet, not even implement functionality you don't need. What's important is to do your homework and chose the right framework for the client's needs.

The other common argument is that frameworks come with an expensive and time consuming learning curve. Again, many frameworks are bloated and hard to work with. Successful frameworks simply build off of what a developer knows already. A harvested framework is the preferred option, since it will simply help implement what a developer would have implemented anyway. As a result, the framework becomes more an extension of the developer instead of a new development language in itself.

As more team members learn the framework, our ability to ramp up resources and maintain the client's codebase increases in turn. The benefits compound - Future projects also gain from the team accrued knowledge of the framework and codebase, reducing development time with every iteration.

Lixar is part of the larger development community that promotes using standard frameworks. If we take away the mundane tasks, we are freed up to accomplish some extraordinary things! And it's the extraordinary that sets us apart.

issue
01
  • Contact Us
    Headquarters:
    47A Young Street
    Ottawa, Ontario
    K1S 3H6

    t: 613.722.0688
    f: 613.722.5297
    sales@lixar.com

    Map >
    East Coast Office:
    300-800 Windmill Road
    Dartmouth, Nova Scotia
    B3B 1L1

    t: 902.405.4443
    f: 902.405.4435
    eastcoast@lixar.com

    Map >
  • Support
    For all emergency inquiries for applications that Lixar supports for existing clients through service level agreements (SLA's), please contact us 24/7 either via

    - General Support Inquiries: 1-866-788-4239
    - Support for Existing Customers: 1-866-722-0688
    - Email: support@lixar.com

    More >
  • Lixar is a web technology services company with core competencies in design-development-support of web applications, business process automation, and system/database integration.