Solving problems is fun, if you let it.
Have you ever had a third-party application or API change slip by unnoticed until it started impacting your production environment? The process of monitoring change logs for the multitude of dependencies for modern projects is becoming an unmanageable mess. Providing a standardized, developer friendly method of distributing changelog is highly appealing.
Major service failure, seemingly across the world.
Small applications written on limited budgets, tight deadlines, limited specifications and frequent changes often result in code that is difficult to maintain and change over time.
Add to this the dreaded "someone else's code" and you're in for a rough ride.
For year’s I’ve struggled with odd behavior on Windows 10 machines and interestingly this all started with the introduction for Microsoft Account sign-in.
Some software packages fail to install because the user path cannot be found, mostly because they don’t support unicode characters in paths. Others create the “missing” directory with interesting interpretations of the original character, see the screenshot above.
A quick overview of how to search for solutions for your crashing application issues.
Over the last few days, I've seen numerous reports of Photoshop CC 2015 crashing on launch with a 0xc0000005 (Access Violation) error code and no faulting module other than Photoshop.exe
I started experiencing the same issue yesterday, and so I decided to take a look into the problem to try and resolve it.
