When I was a student in the late 1950’s, I was working as a waiter. I remember being so busy doing basic jobwork and talking about it that I couldn’t help but wonder why I didn’t do the basic job all the time. I made a list of the things that were most important to me so I could make sure I had the time to do it. I worked on my first job at the end of the year and took advantage of the opportunity.
I remember working in the kitchen at my family’s restaurant and being very excited for a chance to get paid for it. I was also excited because I wanted to make a good impression on my boss and wanted to impress other servers my age, so I wanted to impress them by being the best at what I was doing. However, my excitement was short lived. I was so busy doing basic jobwork that I forgot what my goal was and ended up getting fired.
It’s not that I was fired for trying to impress my boss. The job was also not as fun as I thought it would be. I remember working in our restaurant in New Orleans for 2 1/2 months and being so excited for the opportunity to get paid for it, but I was so busy working that I didn’t really notice the real reason why I was fired, which is that I wanted to be the best server at my age.
It’s the same reason some people quit their jobs, I guess. After a certain point, you stop caring about what you’re doing. I guess that’s different with programming and it seems to be the case with CAD software as well, but I think that’s true for most jobs, too. I guess a lot of us programmers are just too busy with our own stuff.
The biggest thing to keep in mind is that your job as a server is to give people the information they need to get to you, to ask questions, and to take the pain of asking for that info and then to keep it going. You can’t do that with every client you have.
The same goes for CAD software, where you’re the guy who tells a client what to do because you care about what youre doing. The same goes here too. It seems like a lot of us care about what we’re doing. I guess thats different with programming and it seems to be the case with CAD software as well, but I think thats true for most jobs, too.
I feel like the same goes for programming, too. It could just be because I have a lot of experience with it, but I know that I do. It’s just that I tend to do a lot of things that seem to be a little bit… messy. It seems like our profession needs to be a little more transparent when it comes to the actual work that we are doing.
I’m not saying that programs have to be perfect, but it does seem like some of the more “complex” ones are a little more prone to errors. I’m not saying its the best way to write code, but I do think it’s important to keep in mind that an error can be a good thing.
Some of my more complex programs seem to have problems with errors much like we do with bugs. This is one such program. The problem is that the program’s error handling often doesn’t work properly. For example, in a program to print a list of cities to an HTML file it prints the list of cities in the wrong order. In this case the problem was that the program was calling a function that it shouldn’t have been.
The main problem with this is that we must be clear about what makes up the errors, especially the ones that are caused by code. In this case we’re talking about the code being broken, not that it’s the problem. If this is the first time you notice that your program is causing errors, you should know that it’s an error. If you’re going to fix this issue, then that means you need to figure out how to fix it.
