Right now I'm working on custom in-house software to be used on forklifts. The old way of doing things was for an office worker to print out a list of what product needed to be loaded on trucks. The forklift driver had to find pallets in the warehouse to fill the order and put them in the truck. The driver had to remove a sticker from every pallet and put it on the paper list. When it was filled, he took the paper back to the office where the worker had to type in all of the pallet numbers. This was the only way to know exactly which pallets went on which trucks. We bought 10" mounted XP computers and put them on the forklifts. I wrote a program in WPF C# to run on the computers. This is in combination to a new warehouse management system that was installed. Now conveyors and machinery automatically store pallets in racks. The office worker "ships" an order. The system automatically picks the correct pallets and sends them down conveyors to within 15 yards of the truck doors. My software connects to a web service using a proxy. The web service (also in C#) interfaces with several databases to pull the relevant information. It will show the forklift driver which conveyor to pick up pallets and which door to take it to. They then use a barcode scanner to scan each pallet and the door they take it to. They no longer have to use paperwork and the office workers don't have to spend so much time printing out paperwork and typing in pallet numbers. The office workers don't like it because they are now in charge of the warehouse management system, so they have as much work as they did before. I'm currently working on stage two of my project. The warehouse system also stores raw finished goods. After waiting several days (for QA testing) they are called out of the system. A forklift driver then takes them to a line that labels, boxes, and makes pallets of finished product. The driver then takes the pallet back to the system. Right now they need to take the peel off sticker from the raw product pallets and the finished goods pallet. Then someone needs to type those numbers into our ERP system. Only when someone hand enters them (which sometimes takes a couple of days before they get to it, and human error causes some to never be entered) does the ERP system know that the finished goods exist. I'm adding on to the forklift software to have them use the barcode scanner for all of this. Then they aren't worried about stickers, and the ERP gets updated instantly. I work at a factory (obviously) where my title is "IT". We all share hats around here, so I'm also responsible for pallet printers, phones, vendor laptop problems, terminating ends, etc. I am the only person hired as a programmer who is learning networking on the fly. Everyone else are networking people who learned programming on the fly. I'm the only one working on the forklift project. That suits me, because the other IT "programmers" had no idea what I was talking about when I mentioned break points and stepping through code. They write to the event logs to debug their software. What about you, why do you stare at VS every day?