The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I spent mostly my career in government (Federal research), I'm not sure I would classify it as boring. Sure the deadlines are not as stringent, but some of the capability that I had to come up with are challenging compare to the private sector. Most of my development in private sector are implement known technologies. In research my development involve more theoretical and computational, much more challenging in my view.
With greater challenge comes greater rewards and often the greatest is satisfaction through accomplishment; commercial development has reduced to a level equivalent to cut & paste AGAIN so understand your points and pro-actively agree. R&D is still the venerable black hole it's always been; it draws the dollars and the talent into an inescapable orbit maintained exclusively upon creative thought fueled by the process with no beginning and no end --cyclic, self-serving, inspiration.
I was in pretty much the same industry for my first few decades and then when I started my current job in a completely different industry I ran into a mountain of new terminology that is unique to this one. I have been here two and a half years and I still run across terms that are new to me.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
Wait till they get you to build VAR engines, forecasting using things like the K formula and other arcane financial stuff.
Then they will want you to change tracks and become a data scientist because you have been working with their systems for a while.
Ah the heady world of financial acronyms, make a point of asking for an explanation of every acronym you do not know the meaning of and remember the same acronym can mean different things based on the context. You may never get invited to another meeting
Never underestimate the power of human stupidity -
I'm old. I know stuff - JSOP
I was a CS student between '86 and '88. I remember having 2 required documents for most assignments:
0: handwritten or typed pseudo-code
1: a green-bar printout containing code and results
The green-bar had an ascii-art cover with my name and terminal #. I remember having a special notebook with 80 columns...then I quit school and worked a trade job for 10 years. When I got back into it (programming) in the late '90s things had changed dramatically...I remember the feeling I had when I realized that the computer lab was a thing of the past.
Up until a few months ago, O'Reilly Auto Parts still used them to print customer receipts. They are currently transitioning to newer technology (e.g., thermal).
For those businesses that rely on impact printing (multi-part carbon forms), manufacturers are still making them.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
In a way. Back in the 80's I spent a lot of time working in the computer center at our local Air Force base. The 2nd floor of the building was one huge room, over an acre in size. It was filled with mainframes, super-mini's (VAXen, mostly), the washing-machine style hard drives, and of course line printers. This was back in the day when nobody thought about hearing protection. The noise was incredible.
As a result I have chronic tinnitus (ringing in the ears) . I have a hard time maintaining a conversation if there's any background noise. I don't listen to classical music nearly as much as I used to, as the strings tend to sound weak and muffled (loss of frequency range).
I almost managed to read that. Care to rework that second sentence?
There's hardly any purpose in hanging on to dead hardware, especially something that old.
I was hit by nostalgia a few months back, and had been looking at local ebay equivalents to reacquaint myself with a Commodore 64 (which I grew up with). Fortunately some company managed to put together a minified version (think Nintendo's own NES-mini and SNES-mini from last year) which can use the same disk images as emulators (well, it is, itself, an emulator).
I've tinkered with all the C64 emulators before, but having this in the "right" form factor, with a functional joystick and all, managed to capture my interest over the holidays for far longer than emulators ever have.
First thing to check is the power supply, on tech this vintage the electrolytic filter capacitors are the first things to go: they will either open circuit or short out, neither is good for the electrons in there.
If the power supply passes the test then things get a bit more interesting - more symptoms on "not functioning" will be needed
We have a command line app we run to import data from "foreign" databases. Each foreign database provides its own web service. We import the data in one of four databases, depending on what environment we're in, but we can redirect the imported data into and of the four databases by a command line switch.
We use the database to determine how the app runs via a table of configuration settings. There are also arbitrary command line switches that let you change some (but not all) of the values, however not all of the command line switches are handled through the appconfig object (even though they might override a value retrieved from the database.
I'm almost done with a re-write of that section of code that:
0) Pulls config settings from the database (as before), but only for the specified program type (foreign database source)
1) Allows ANY of those values to be overridden, because I use reflection to get the appconfig object's property names, as well as a generic SetValue method.
2) Produces a program type-specific help screen (if the command line args are something like "/progtype /?"), or an app help screen that describes all possible arguments (again, using reflection for the property names and their default database values
It's pretty impressive, if I do say so myself.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
I write a lot of command-line utilities, some including some stuff similar to that.
However, I _never_ use appconfig. Some do use a custom XML file designed for them.
Your point 2 reminds me of VOS.
I haven't advanced my command line parser to that point though. Even many features of OpenVMS haven't been added yet.
One of the more recent features I added to the parser is the ability to set environment variables to hold commonly-used switches.
For instance, my TFSutil expects a /URL switch (which rarely changes), so
and the command line parser treats it as if it was included on the command line. Slick as snot.
Last Visit: 22-Feb-19 20:24 Last Update: 22-Feb-19 20:24