Welcome to the Marble
If you were provided a URL then double check and see that you wrote it correctly. If you are still lost. Contact me. You know how.
Everyone Else Read on.
If you were provided a URL then double check and see that you wrote it correctly. If you are still lost. Contact me. You know how.
Everyone Else Read on.
What goes on here at the marble in general are experiments, exploration, consultations, and development.
Issues Tackled:
SEO for small business only (Front Page Ranking Is Very Important)
Database Utilization (taking your inventory spreadsheets and making them useful on the web)
Custom Business Code to fit the unique aspect of your web business (php, sql, html, javascript)
Development Methods that work the way your business works.
Issues Tackled:
SEO for small business only (Front Page Ranking Is Very Important)
Database Utilization (taking your inventory spreadsheets and making them useful on the web)
Custom Business Code to fit the unique aspect of your web business (php, sql, html, javascript)
Development Methods that work the way your business works.
Philosophy: Evolution of your system is the best course of action. From experience and industry research the gamble of swapping out one system for another is way to dangerous. Enterprise Resource Planning has horrible failures and some benefits. This radical concept of coming into your business and replacing what you are doing with an entirely new system is similar to replacing your entire nervous system and spinal cord with a new one and expect it all to work. In 30 years there is no system that could not have been evolved to perform the required function. At the same time the cost of evolving is generally cheaper.
Transition: Suppose your determined to swap out systems. Transition is important you need to ensure the transition is seamless so employees won’t become confused, and make mistakes. Transition is best done with parallel development and testing with the end users in real time simulation. Shock and Awe on the faces of employee when you switch out a system is priceless. The frustration and bad mood of the office can only be recreated with lay-off notices.
Customization: No two businesses are alike. The concept of one all in wonder system that will do what you need is a myth. Many of these systems have a back-end hangover. The developers try to shove as much as they can in there. What you end up with is a lot of system overhead. Thousands of fields you will never use and wasted data streams. 9 times out of 10 you will find the Interface is not what you need. This is why they build these systems with Custom Procedure Calls, Remote Procedure Calls, or some other means for a programmer to intercept the called function and put in a new one. However this is often thwarted by the lack of code access and ability to modify data structures. Of course these systems are encrypted and it cost a fortune to customise. 10,000 dollars a day to pay a foreign company to customize your business can kill you.
nbsp;
Ownership: Who owns your business software, who owns your domain. More than one business has operated a web site without knowing how to access there website. Thats because a third party setup the site and purchased the domain. In the end that person owns the domain and the code. Not the business owner. In fact the programmer owns the code and in general has consented you to use it without license. Such situations can become trouble when the programmer decides to license you. Get your contract right.
Transition: Suppose your determined to swap out systems. Transition is important you need to ensure the transition is seamless so employees won’t become confused, and make mistakes. Transition is best done with parallel development and testing with the end users in real time simulation. Shock and Awe on the faces of employee when you switch out a system is priceless. The frustration and bad mood of the office can only be recreated with lay-off notices.
Customization: No two businesses are alike. The concept of one all in wonder system that will do what you need is a myth. Many of these systems have a back-end hangover. The developers try to shove as much as they can in there. What you end up with is a lot of system overhead. Thousands of fields you will never use and wasted data streams. 9 times out of 10 you will find the Interface is not what you need. This is why they build these systems with Custom Procedure Calls, Remote Procedure Calls, or some other means for a programmer to intercept the called function and put in a new one. However this is often thwarted by the lack of code access and ability to modify data structures. Of course these systems are encrypted and it cost a fortune to customise. 10,000 dollars a day to pay a foreign company to customize your business can kill you.
nbsp;
Ownership: Who owns your business software, who owns your domain. More than one business has operated a web site without knowing how to access there website. Thats because a third party setup the site and purchased the domain. In the end that person owns the domain and the code. Not the business owner. In fact the programmer owns the code and in general has consented you to use it without license. Such situations can become trouble when the programmer decides to license you. Get your contract right.
Hand held Devices: Never ever expect your hand held web presence to be like your desktop presence. Never expect your buttons to be the same. First off fat fingers on little screens are a problem. Design for them. Thats what we do at the Marble.
Thank you
Management
Thank you
Management