Are there some recommended frameworks or techniques I can learn more about how to estimate software development and maintenance costs / hours? If so, what are they called so I can look them up?
I'm a mechanical engineer and the product needs an app component along with a database to store users' generated data. (I will eventually find a computer science person to be a co-founder.)
What are people's thoughts on renewing software maintenance? Renewing keeps you on the latest version and allows you to call into support if/when you need to.
Company I work is deciding to forego maintenance....I advised that it's not wise to lapse, but they want to save the extra dollar and not renew.
I have just gone through a security audit and have determined that the IT team needs to track 'software maintenance tools', but am having a difficult time defining exactly what this is. Has anyone gone through this? I know something like WireShark would be one, but I'm having trouble drawing the line between what is maintenance what what are the software tools the IT team uses on a day to day basis.
For people in big tech, it's probably common to work on long running stable products which have their fair amount of tech debt. And significant focus is on stability/maintainability of the code rather than feature work. How do people feel about that? Do you find such teams less exciting to work in?
I'm looking for a good program to use in a medical facility. The cheaper the better ( so they will approve) We are currently using logbook but its a big campus and I'm losing time walking to each one then back to the shop. Also hoping to use it for documentation on what I actually do. Picture capabilities would be great and run times too. I constantly get the "we don't know what you actually do but you aren't completing all the tasks. Give it an extra 10%" speech. 20 year old facility with AFC, HFA, SNF licensing. I'm the only maintenance guy. Help a brother out :)
I built my first pc about a year ago and it's been fairly smooth sailing overall. I try to keep it fairly clutter free so I don't have loads of unnecessary files on my drives and I've opened it up once for dusting and to change some wiring. Is there anything more I could do to lengthen the longevity of my parts?
I'm completely new to SCCM and I've been learning from various tutorials on YouTube.
I'm familiar with the purpose of Maintenance Windows and how they are set at the Device Collection level within SCCM; however I'm somewhat confused about the role of the 'Work Information' setting in the Options tab within the Software Center application on SCCM managed devices. Both appear to do the same thing - albeit one is set at the SCCM Server level, while the other can be configured by the end-user on individual SCCM managed devices.
My question is does one setting take precedence over the other? For example, if I define a maintenance window at the Device Collection Level, and the 'business hours' set for an individual device completely overlap the maintenance window defined at the Device Collection level, will deployments be installed during the maintenance window or will they be installed outside of the 'business hours' defined on the device, or will they only be installed after the deployment deadline? I'm aware that Maintenance Windows can be ignored by setting the deployment deadline to ASAP, and that deployments can be 'forced' to be installed once a deadline has been reached also - so with that in mind, my question is probably asked in the context of a deployment with a deadline of say one week from the deployment date, where the Device Collection maintenance window is overlapped by the 'business hours' up until the deployment deadline?
