does sound daft at first
but if actually used, an e-bike could help someone get over the hump of being in too bad a condition to start exercising
38 posts • joined 30 Jun 2015
Another example of CSV-to-XLS(x) problems. Was asked to help migrate old data by exporting from their database into a format the new application could read. But the data included a Comment field, and that fields data entry allowed Carriage Returns. Meaning a single record could span multiple lines in the CSV file! They sent a nice letter to my boss about the extra effort developing a "bespoke migration tool" (really just a little PowerShell to stitch the lines back together by changing the extra CR to a flag character).
Back to the main thread, yeah - default should assume incoming CSV columns are text. Then I will assign formatting as needed for display or calculations.
A quick search for "power cord extension and splitter" will help with bricks blocking the ports. Very short cords just to let the brick lay on the floor next to the strip. I am in the USA so mine are 120V NEMA 5-15, even have a couple C14 converters for getting notebook juice from the 240V rack PDU in the computer room.
Though this does mean more stuff to carry, unless you forgo the circuit breaker and replace, instead of augment, the regular power strip.
A couple of random product photos;
#C14 - NEMA
# multi-tail NEMA
I lost the original URL for these, but enjoy!
10. Specifications are for the weak and timid!
9. You question the worthiness of my code? I should kill you where you stand!
8. Indentation?! - I will show you how to indent when I indent your skull!
7. What is this talk of 'release'? Klingons do not make software 'releases'. Our
software 'escapes' leaving a bloody trail of designers and quality assurance
people in its wake.
6. Klingon function calls do not have 'parameters' - they have 'arguments' - and
they ALWAYS WIN THEM.
5. Debugging? Klingons do not debug. Our software does not coddle the weak.
4. A TRUE Klingon Warrior does not comment on his code!
3. Klingon software does NOT have BUGS. It has FEATURES, and those features are
too sophisticated for a Romulan pig like you to understand.
2. You cannot truly appreciate Dilbert unless you've read it in the original
1. Our users will know fear and cower before our software! Ship it! Ship it and
let them flee like the dogs they are!
Coding "minimum viable product" for "critical flight and weapons software" is asking for catastrophic failures! And to "release capabilities via smaller, more frequent service pack updates", in other words not giving you everything needed to do the job, is digging the hole even deeper.
This level of adherence to Agile religions can work for non-critical accounting applications, or games. But for stuff that can kill you? For stuff that is actually DESIGNED to kill you?
Yes, Waterfall has its own problems. But swinging the pendulum all the way over just exposes other issues.
While EDI is a "standard" (the shop using it had even bought the dictionaries) it was also open enough that you could do whatever you wanted, and still be "within standard'. The half dozen partners we had were all doing the same business, but none of those streams were formatted the same.
NO media / platform is a permanent backup / archive - everything will fail eventually. You have to keep copying (with checksums) to newer platforms every few years.
The point about at least two instances of the data set, on different platforms, is also very much a good idea. When Platform-A gets bricked [hack, firmware, license, key server, bad batch of disks across multiple machines (yes, this was a personal nightmare - remember Bigfoot?), ...], you can still copy from Platform-B to a new Platform-C. Not so easy if all your copies are just multiple instances of Platform-A.
Today's joke is by Ben Mackay
Officer: Hello, Mr. Kornada. I'm calling to follow up on your recent ethics test.
Officer: You were asked the classic trolley car problem. You said that you would redirect the trolley to hit one person rather than hitting five. It was your reason for doing so that disturbed us.
Officer: "It would do less damage to the trolley car."
Officer: Yes, you are correct, but I really think you're missing the point here.
I was systems/assembly programmer on an IBM 360-40 in the late 1970's. We had an expansion box that brought the total RAM to 512KB (yes - Kilo). Similarly limited disk space, but DOS/VSE was running several partitions (print spooler, online terminals, multiple batch). I was so appalled when we brought in COBOL, and one of those daft folk used the literals "YES" and "NO " (note the trailing space) for a flag. I could fit 8 binary tests in a byte, and they were using 24 bits for a single condition!!! Not to mention a TestMask against my bit was sooo much faster then their string compare. And TestMask could check for multiple bits in that byte during the same clock cycle, instead of a page of chained If Then Else string compares (which had to invoke micro-code routines on top of the the "real" CPU instructions). <huff><huff></rant>
Sorry, but the Socialism threadlets free-associated into an old joke, parts of which:
You have 2 cows.
The State takes one and gives it to your neighbour who doesn’t have a field to put it in.
You have two giraffes.
The government requires you to take harmonica lessons.
one version of the list from;
Even with best intentions, training, equipment, conscientious staff, ..., your "local" police cannot "protect" you unless they are actually "local" - say within 20 feet. If they are not able to stop the miscreant _at_the_time_ of the attack, they are only a nebulous background presence threatening some possible future punishment. Any call for help with a response time greater then single digit seconds means I am responsible for the defense of me and mine.
This showed up in my Flipboard feed last week
911 OPERATOR: 911—what’s your emergency?
ROBERT: Hi, I . . . uh . . . I work from home.
OPERATOR: O.K., is anyone else there with you, sir?
ROBERT: No, I’m alone.
OPERATOR: And when’s the last time you saw someone else? Was that today?
ROBERT: Uh, my wife . . . this morning, I guess.
`yep, I am a grumpy old bastard, but yet another vote for being able to read the actual content. If there is not enough content for a article, why should I waste my time with audio/visual fluff?
Text does not interrupt those around me. When interrupted I can just let the window fall to the background until ready for it again.
No, I am not a headphone-kind-of-guy. I want some awareness of my surroundings, and need to respond to walk-up questions.
My first impulse at some chunks of work is "What Were They Thinking?". Sometimes realize I was the one who wrote that, and ask "What Was I Thinking?". Often the answer is it was a workable solution, given the constraints at the time it was done. Sometimes things that worked then, do not work now after changes in scope or use; then I owe folk a beer. Even if it still works, I will shake my head and vow to never do crap like that again!
Guess how much bandwidth you have available / choose to buy is based on how much importance you assign to this aspect of your security. It is just one of the onion layers to manage.
If you have X bandwidth, assess your criteria to assign Y% of it to "secured" traffic, then keep that Y% portion filled.
Along the lines of "everyone should encrypt everything", another old component of Operational Security is amount of traffic. Each site within a group should always be sending the same about of traffic to each other site. Random cruft when nothing is happening, then real data if something is going on. But those watching will not see a spike of traffic to realize what triggers when. You should never panic and send of burst of out-of-band / unusual traffic to flag your intentions.
Oh yeah,that is right, it can make phone calls! Maybe once a month.
My NoteII is note book, historical activity logs, documentation, password vault, email, calendar, books, imdb, map, wiki, even the odd card game. even sms messages happen more often than a telephone.
Biting the hand that feeds IT © 1998–2020