I, along with the rest of my group, develop control software for our company's line of commercial ink-jet printing systems[^]. It's essentially a process control application combining embedded programming, systems programming (we use Windows services a lot), and UX/UI (we use a WPF application as a control panel). It's distributed, multi-processor, and multithreaded, even the UI.
I retired a few years ago. Still keep updating my dev machine, renewing tool subscriptions and I read some articles and such. I suppose I’m fooling myself, thinking I’ll build something someday, but not today…
Time is the differentiation of eternity devised by man to measure the passage of human events.
- Manly P. Hall
I'm on 3 different projects, none of which is currently actual development.
P1 - supporting an ancient vendor application that is no longer vendor supported. It's got serious quirks and screws up data storage in odd cases. Most of my support is figuring out what screwed up and fixing the data.
P2 - application that replaces P1. We're at the end of coding, so most of my effort is assisting user acceptance testing and prepping for the data migration from P1.
P3 - PM and TA for COTS project. No coding on our side of the fence; my job has been to ensure the business unit correctly described the requirements, that the vendor understands what is being asked, and keeping the train on the track and moving forward.
Being moved to a non programming project. We need to build something and later on automate it, but atm 90% of my job is phone calls trying to get infos and digesting it to write down documentation or specs...
Damn I miss my previous task
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
I answered "Business applications", but I wonder if a video-surveillance application fits the bill.
Anyhow, I'm more and more involved in Dark DevOps things like TeamCity and Gitea that take just as much time as development in C# nowadays.
I have an in-house diagnostic tool that we've been using and I've been developing for 20 years. It's my go-to project when I need a break from the normal day-to-day. There have been any number of new features I've added just because I could .