When I started out, business casual was the norm, just as it is today. A big difference was that many of us had "pocket protectors" where we carried our pens, pencils and slide rule. You may have seen those in some movies as a distinguishing feature for nerds.
There is no doubt what I do is programming. It's similar in some ways to SQL, but the tool I use enables me to implement much more complexity than possible in plain SQL. It actually enables a lot of the functionality available in a procedural language like C, but within a structure built around database manipulations and joins. In this way it breaks the bounds of memory constraints and becomes a big data programming language. Admittedly, I don't have to type out individual commands, but that's a good thing. The logic is the same, but the development time is much less. It enables you to concentrate more on the algorithm design while the command syntax and other minutiae are handled in a much more efficient (and maintainable) manner.
I haven't been able to find the colored bar, maybe because of refreshes, but let me suggest you use something that is searchable. That way you could use CTRL-F and then jump from one to the next. Right now, I'm searching for " min" (note the space) to find the most recent posts, and "1 hour", "2 hour" etc. to find older ones.
I wouldn't mind sharing, but I don't want to take the chance that someone in my company could be reading this. I started in 1963 at $1.55 an hour, which was actually pretty good back then. It's mostly been increasing, except for several years when I was self-employed. Now it's more based on my domain knowledge in healthcare fraud detection than on my seniority and skills as a programmer.
I should also mention that I recently bought a Flexispot stand up desk converter. So now I can stand up and work when I want to. It only accommodates two of my monitors, but that's all I really need anyway.
That's a lot of questions, but let me take a couple. I got my Master's degrees in the early 1970's, when we used something called a "slide rule". In 1990 I went back to school to update my skills and expand my knowledge into artificial intelligence, which I had become enamored with. Unfortunately, I didn't finish my PhD (big mistake!) because in 1995 I jumped on an opportunity to join a company that had this amazing software that enabled very advanced analytics on big data (except it wasn't called "big data" back then). The software was called HOPS (for Heuristic Optimized Processing System) and I still use it today to develop custom machine learning applications among other things. I went back to school again in 2016 to fill in some gaps so would qualify as a real "data scientist" - the latest craze. I will say that HOPS was and is the biggest idea in software that hasn't worked out - at least not commercially. It's a system that is great for data scientists working on big data and enables them to do their own programming with minimal effort. I'm still hoping HOPS will take it's deserved place in the world of software development. It will be a great loss if it doesn't! It's one reason I'm holding on - to prove the exceptional things that it enables and prevent it from being tossed into the trash bin of history.
The one thing that comes to mind is to avoid the "hammer looking for a nail" syndrome. I see this all the time, especially in academia. Rather than worry about learning all the latest stuff, concentrate on solving the problem at hand in the simplest and most effective manner. If that requires you to learn new things, then that's a great time to expand your repertoire - working on a specific problem. Of course you have to strike a balance, but mainly concentrate on solving problems rather than being up-to-date on all the latest stuff and trying to find the proverbial nail for your new hammer.
I think someday we will be able to duplicate the basic brain of an infant in a computer. Don't forget all the information is in our DNA and there's not that much innate knowledge - most of the infant's brain relates to the amazing capacity to learn. Someone will then take one home and train it like a human baby. It will become so close to a human that it will spark debates about whether it has self-awareness and whether it should have human rights. I regret I won't be around to see it, but who knows - maybe I'll be back :-)
About 1 hour in the gym 4 times a week with a mixture of anaerobic and aerobic always setting goals and constraints on my heart rate (using a Polar monitor). At least that is what I was doing until about 2 years ago, when my personal life changed for a number of reasons. Now, I mainly concentrate on walking 3 or 4 miles a day.
One reason I posted this is because I may attempt to gain recognition in the Guinness World Records. I know my career is longer than the person they now have listed as the "Longest career as a computer software developer" - Kaneyuki Yamaguchi in Japan
For most of the past 25 years I have been working from home - which is a problem because you never leave your work. The main thing that has changed over recent years is that I now take a 1-hour nap around 2 or 3 PM every day, except when I have conference calls that prevent it. After the nap, I feel rejuvenated and productive. I'm sure this is partly related to old age, but I'm also dyslexic and I think my brain needs a rest from struggling with written communications.
Just briefly, then I have to hit the sack - I'm on the east coast. I developed a set of programs to allow them to map out the design of a steel building, and my programs would calculate all the pieces they need to load on the truck to build it. Mitchell was very progressive in this area - this type of computerization enabled them to have the building up in record time. A Civil Engineer worked with me and used the computer to design the main support beams. Between the two of us the entire process was automated.
So far I really haven't sensed any mental decrease, but I know there must be some. I do type some source code in Python and R, but primarily I use a rapid applications development tool that allows me to build custom machine learning algorithms and ad hoc analytics to work on big data.
I sit in an office chair (tilted back slightly) with 3 large HD monitors about 3 feet from my eyes - I have special glasses for that range. The monitors can be switched among 3 computers, and the wireless keyboard/mouse has a switch to move from one computer to another. Most importantly, I have a dog that needs walking several times a day, and that forces me to get up and walk a couple miles every day.
I definitely experienced age discrimination in one company that will go nameless. The small company I'm working for now has been great - I love the culture. However, they were just bought by Thomson Reuters and this Monday I will officially be a TR employee. I understand their culture is similar, and I'm hoping it's true!
I hope to make 80 - not sure my health will hold up. I did see the article on Grace Hopper on Wikipedia. She began her computing career in 1944 and she died in 1992, so that's a maximum of only 48 years. On that measure, I have her beat by 9 years already.
I know what you mean. Many of my contemporaries never got past the mainframes. I'll have to admit that it took me a little while to accept the PC to be more than any intelligent terminal. I was lucky in that I worked for Digital Equipment Corporation from 1976 to 1982 - they pioneered distributed computing.
I actually was only 16, but turned 17 right after I started. I had finished all the math and science courses in my high school in Mississippi and I had a lot of extra time in my senior year. As a junior, I scored the highest in the U.S. on an engineering aptitude test and got a write-up in the local paper. Mitchell Engineering was trying to get into computers but didn't know how to find people who could program. When they heard about me, they approached me with the idea of becoming a programmer. At the time, I had no idea what a programmer was, but they hired me and trained me on the job.
I guess not smoking, no drugs and regular exercise. I really enjoy what I do - the challenge of achieving an analytical objective with limited resources has always given me great satisfaction.