Λ V
38
debug window X

X
ZebSoftware Settings
ZebSoftwareAboutContact
Welcome to ZebSoftware
Slideshow Image 1 the Zebulon sunflower
Slideshow Image 2 the 'phi' expression
Slideshow Image 3 the 'golden ratio' manifest
Slideshow Image 4 and Pikes Peak

The name ZebSoftware comes from the Zebulon Sunflower, which has an amazing geometric pattern that exposes the power of phi, or the golden ratio. In conjunction, I live by Pikes Peak, which was named after the explorer Zebulon Pike. The golden ratio is applied to designing and building, and Pikes Peak keeps me fit by exploring this majestic purple mountain.

About

Company Goals

  1. Security1st. Help keep the internet, software, and/or your privacy safe.
  2. Deliver reliable, uniform, and maintainable software.
  3. And, always do your best!

I'm a software developer looking for work. I started writing software in 1990 after receiving a BA in Mathematics with Computer Science Minor from Fort Lewis College, Durango, CO. In the year 2000, I received a C++ Object-Oriented Programming Certificate from Colorado Technical University, Colorado Springs, CO.

If you're in need of software or website design, development, and/or support then please read more... ▼

I started writing C and x86 assembly code for Softronics that developed a communication and terminal emulation application (Softerm) bundled with IBM's OS/2 and also ran under Windows 3.0. Highlights: I developed a script based OS/2 and Windows dialog formatter that followed the IBM CUA (Common User Access) standards and supported multiple languages. I received a huge bonus in my effort to get our product converted and released into 14 different languages. I stayed with this job for 6 years, but had to move on after the pc, UNIX, & Windows Servers overtook the mainframes/terminals.

I then moved on to testing tape drives for the Quantum Corporation. I stayed with this company for 12 years until the magnetic tape gets replaced with cheaper hard drives and solid-state disks.

Serving as lead software engineer (10+ years) for Quantum's “Ongoing and Reliability Test” software, I tested SCSI tape drives & libraries, solid state disks, and multi-disk backup systems. This tester software under my development started running in 1 reliability lab here in Colorado Springs and then grew to become a critical required tester for design, engineering, process, production, and customer verification testing. This software was purchased by at least 2 other companies and ran worldwide. It had to be bullet-proof to provide critical data for timely executive decision-making and had to run for months on end without stopping. It was written in C++ and used Windows SCSI pass-through (SPTI) over SCSI, Fiber Channel, SATA, SAS and USB hardware connections. The ‘real-time’ output test data was communicated to a Windows server application, using Winsock 2 packets, which then stored it to a SQL Server database.

Commentary: this software was written to be reliable like its objective on testing our products. My favorite company offered-class was the SCSI Nuts and Bolts class. I enjoyed the 1's and 0's, the big-endian, and the SCSI spec.

Designed and developed .Net component libraries to provide a SCSI protocol for all internal Quantum applications from product design to production testing. This software was written in C# and script driven from sending a complex SCSI mode sense command to writing random data to an entire disk/tape with a bit by bit read verify test. The second component communicated to the CRL class library was a Win32 dynamic linked library (DLL) written in C++, which communicated the SCSI commands using Windows SCSI pass-through (SPTI).

Team lead developer of a multi-threaded C++ Windows application to automate, control, and monitor up to 48 DLT tape drives ‘simultaneously’ running a 96 hour confidence test using the COMM (RS-232) interface on 1 pc. A script engine was included for controlling the tests with encrypted scripts written by the process engineers. Components to this application included test status updates to a central reporting application through a socket connection, which in turn talked to hand held devices used to instruct the operators of tests requiring their attention; COM based interfaces to VB and VC++ executable's for the GUI; data collection.

From March, 2016 to end of 2017, I volunteered to support the local Women's Resource Agency's website and thoroughly enjoyed learning the process, software, and the code development. During this time I decided to return to software development.

In April, 2017, I then volunteered to setup a calendar for the Pikes Peak Women to “capture in one place” our local community work responding to our recently changing political environment: Pikes Peak Social Activism Calendar. To respond quickly, I used the Joomla content management system, complemented with a free version of the dpCalendar extension.

So, I now have a company and have created this website in “plain-vanilla” HTML, CSS, JavaScript, PHP, a MySQL database, and GoDaddy. This includes the greenhorn toolbox page linked below. No other external dependencies or references in this website. Keep it simple (more security, less dependencies), make it attractive (eye pleasing, minimize flashing), and then release it with improvements and updates along the way (security, technological advances, and higher search engine ranking/website visits).

What I've learned:

  • Develop with quality. Which means the software needs to be reliable, consistent, maintainable, and secure. To achieve this means to develop tidy ‘bullet-proof’ code in a ‘as is required’ secure environment and then test, test, and keep testing. Testing not only enhances your skills for coding but always improves the interface. When editing other people's code try to stick with their style, which in turn improves your style.
  • Design with the top-down method. Shoot for the stars…and then discuss the feasibility, time and money. Research many possible methods to reach the goals. Then draw a blue-print.
  • Develop from the bottom-up. Get the nuts and bolt's working then continue up from there. This allows the development process to test the important components as your building and testing on top of it.
  • Design your interface using phi (Golden Ratio). From nature to buildings the Golden Ratio is pleasing to the human eye. Add comments while coding and logging/tracing capability throughout the source code.
  • Recognize not to let time and/or money overtake security. As displayed recently, the risk of security is unmeasurable. As technology advances and hackers evolve the security should continue with support and updates.
  • Keep it as simple as possible. When possible, always use the core/native/default/built-in components.

What I'm looking for:

Close

Or, visit my ever-evolving web skills toolbox:

Greenhorn Toolbox
ZebSoftware LLC
Software Developer: Doug Marts LinkedIn Icon
Colorado Springs, Colorado
ZebSoftware Logo

Contact ZebSoftware