Your guide to custom software - for the non-tech company

Software has the power to propel a business forward. It also has the power to saddle a company with ongoing maintenance costs. Growing companies struggle to determine when to build custom software for themselves and how to do it. Very large companies in the Fortune 5000 build and maintain large portfolios of custom software in-house. They employ all the trades necessary for this endeavor, and in order to burst capacity, they maintain a network of contract specialists. They also spend a considerable amount of money not only for salaries of specialists but also for the management and tooling infrastructure required to operate a software engineering department.

Growing firms, and especially those in traditionally non-IT industries, cannot invest in this level of infrastructure, and most struggle to determine the right way to buy custom software. For context, building custom software can also be called software development, application development, and computer programming.

Read the full article below

http://blog.clear-measure.com/custom-software-is-the-missing-link-for-non-tech-businesses

Originally published on LinkedIn.

Help! My software developer just quit

If this just happened, and you are the operations executive at your firm, you may be a bit stressed at the moment. The Internet is littered with articles that discuss reasons developers and software engineers quit their jobs at otherwise high-profile tech companies.

The fact is software developers quit all types of companies. If you are a company that is not in the Fortune 5000, and your market happens to be more high-touch than high-tech, then this might have been your only developer, or half of your team of two!

Because the departure of a developer in a small IT department can leave a gaping hole, it’s not a bad idea to look at why the event happened in the first place even as you look to fill the role as quickly as possible.

Read the full article below.

Help! My software developer just quit

Originally published on LinkedIn.