Being a hardware guy myself, it can be difficult. But after years and years of experience I've found it best to take a step back and look at the hardware in use and how the end user is using it. From there its easier to decipher problems. Debugging comes easier as the years grow longer.
Software...software is hard. At least to me. I've found that, like you seem to of found out, its a different logic used in its operations and functions.
I guess I'm also referring to the business aspect of it. With software, if you screw up, it can be costly, but seemingly not as costly as a hardware screw up. Do you find this to be the case?
Where I work at, we do not follow any CD or CI structure due to federal requirements. The only main time we might have major problems on hardware would be during the initial facilitation/installation. As with anything, there are always hiccups.
Afterwards its just standard up keep and maintenance.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Being a hardware guy myself, it can be difficult. But after years and years of experience I've found it best to take a step back and look at the hardware in use and how the end user is using it. From there its easier to decipher problems. Debugging comes easier as the years grow longer.
Software...software is hard. At least to me. I've found that, like you seem to of found out, its a different logic used in its operations and functions.
Good article.
I guess I'm also referring to the business aspect of it. With software, if you screw up, it can be costly, but seemingly not as costly as a hardware screw up. Do you find this to be the case?
Where I work at, we do not follow any CD or CI structure due to federal requirements. The only main time we might have major problems on hardware would be during the initial facilitation/installation. As with anything, there are always hiccups.
Afterwards its just standard up keep and maintenance.