So Ben got a bottle of wine (and continued employment) for $10m of business, and the 'salesman' got how much commission?
(okay it's not a bottle of wine, but it is rapidly heading towards pub-time!)
Have you got that Friday feeling? Well, you should, because it's just hours away from the weekend and we've got another great Reg reader story in this week's On Call. This time our tale of tech support triumph comes from reader "Ben", who in 1979 worked for a plug-compatible manufacturer that was in competition with one of the …
This is (in part) what drove me away from being a permie - I was never responsible for an 8 figure order, but certainly helped to win high 6, maybe even an occasional 7 figure deals on a regular basis, as illustrated:
Sales Eloi would often come along and say "I want to demo this (absolutely fucking stupid idea, but looks flash) to a potential client next week - have it ready by then".
"Not possible" we would say.
"But I've already promised the potential client (and I've already told the CEO* you've volunteered)" said expensively dressed Sales Eloi before shooting off in his delivery-mileage M5, to wine and dine said customer at a nearby Michelin-starred restaurant whilst us Developer Morlocks would put in yet another 10-15 hours of unpaid overtime, only to be rewarded with a shared box of Quality Street whilst Sales Eloi booked yet another 5* holiday to Monaco / Mauritius / Miami with his forthcoming commission.
*The CEO was extremely KPI driven, so Eloi's, as net-contributors to company coffers were a valuable asset and deserving of their rewards, but Morlocks, as a pure expense, were a drain and only barely tolerated.
I worked on a 5-man support team a couple of years back which collectively drove a $20.7m deal. The salesman got a percentage (in theory anywhere up to 5% although obviously nobody knew exactly how much - mucho $$$ in any case). We got an email from the big boss to say good job. The kicker was that the email started with: Dear ELPUSS, LORD,:... even the thankyou letter was a mail merge.
"IME that counts as an unusually lavish reward."
Fuck yeah! One customer we had, annual 6 figure contract for over 10 years, consistently cited my and a colleague in satisfaction surveys as one of the reasons for staying with us. I never got as much as a "well done" from my company. But when a salesdroid fucked up and we lost the contract, said saelsdroid didn't get punished in any way because, well "customers go and customers come, that's the nature of the business". I know damn well if I'd fucked up enough to lose the contract, I'd have been pushed out the door with no parachute.
"IME that counts as an unusually lavish reward."
Didn't even get that after our lead programmer, after 10k+ in performance bonuses, left the state three weeks for a new, more lucrative position before the launch of a new domain registrar he'd been working 6 months on. Customer specified a Windows server which had to deal with Netsol's Unix DNS registration system and the_fucking_programming_didn't_work_at_all and was dropped into my lap...
I'll spare you the details, but the customer launched two days late.
Only issue was I aged 127 years in that 16 days. I'm 181 years old now... all because of Chad and his love of Mazda Miatas in the late 90's...
From the management point of view, it goes this way: neither the salesman nor the technician could have brought the deal in on their own merit, you need both.
Most technicians are willing to go the extra mile for the simple satisfaction of seeing the job well done.
Most salesmen are willing to go the extra mile only if they see a clear opportunity to bring home an huge amount of cash, while risking being left without anything if they don't go the extra mile.
So, wanting to minimize expenses and maximize earnings, you pay a standard salary to technicians and a percentage to salesmen.
> So, wanting to minimize expenses and maximize earnings, you pay a standard salary to technicians and a percentage to salesmen.
Not really Richard Trumka's take on things.
“We’re demanding nothing more—and certainly nothing less—than our fair share of the immense wealth we create every day,” says Mr. Trumka.
Ah, but unions and that kind of stuff require ideas of social justice and "doing what's right" and so on.
Management rarely care much about that kind of stuff.
It could even get a manager fired, and maybe even without golden parachute.
It's not by chance that when you've an enlightened manager that does that kind of stuff it's news material.
Even when you *really* need the top technical talents and can't afford appropriate salaries in a very competitive market and so do that stock options thing that helped so many American start-ups, you do it at the moment of enrollment. After that, management knows that the average techie will go on doing their best no matter the situation.
Salesmen tend to remain much more unreliable, and needs a more direct system of control...
somewhat related, though it worked out ok because I kept working for a couple more years at a nice pay rate...
a) as a contractor, told [after short vacation] I had to fly to Dallas to assist an important customer with software mods that were just NOT working. Other guy was flying back.
b) asked very nicely to ONLY charge 8 hours per day for that [I was nice, I did it]
c) took my personal laptop with FreeBSD on it, configured to build all of the software using the customer's chosen compiler version, compatible with their proprietary system, so I could hand them a binary BLOB library with any fixes in it when needed
d) a disgruntled employee at the customer site had NOT implemented 'layer' fixes (in their code) that were needed to run the latest library code [new lib necessary because it fixed specific bad bugs and enhanced performance]
e) later, another reported problem turned out to be related to THEIR OWN IP STACK [and was confirmed and fixed by their 'sales engineer' while I twiddled my thumbs in their storage warehouse for a few hours]
f) I fly back on friday, and spent a couple of hours on saturday over the phone with one of their engineers, finalizing it all.
A few months later, the product shipped. If this hadn't gone well, they would've canceled all orders for the company I was contracting with. I don't know how much money they earned, and as far as I was concerned, I was "just doing my job". But it's 100% true, no [bleep] this really happened!
And in the summer, Dallas Texas is HOT AS A PISTOL. And they don't fix the 'walk' signals at their traffic lights. I think I was the only one walking that day, only a mile or two to the hotel, but still.
Ah yes, ISRs. I had a problem once where some circular buffer code in an ISR should have been [i] but was actually . Didn't use much of the buffer like that ;) and occasionally messages got overwritten. That one got me a trip to Australia to diagnose & fix, and one very happy customer. No wine from the boss though, since I'd written that code & the bug was mine... Could have been worse, at least he signed off the travel expenses claim.
"the bug was mine"
I worked for one company body-shopped in from a consultancy, as an employee, briefly as a freelance and even more briefly on behalf of a vendor with whom I was freelancing. The last was hand-holding migration to new kit with new versions of the OS & RDBMS.
The entire custom software application worked fine except for one SQL statement that failed due to incorrect use of SQL's 3-way logic. I recognised it. It was one I'd written back in the body-shop days and involved a tricky bringing together of two very different types of products when converting from non-SQL to SQL. It was my first exposure to SQL; that's my explanation anyway.
It was clearly wrong but there must have been a compensating bug in previous versions of the RDBMS engine because the whole thing had been working with no problems for about 10 years. The really odd thing was that my replacement as employee insisted that the original SQL was correct.
Not only interrupts.
A friend, many years ago, got some time on a mainframe to do some chemical bond calculations. The results were clearly wrong.
The result was an entire weekend spent doing the calculations on an HP calculator. But where was the problem?
Apparently one of the gods of the system, on Friday afternoon, had been playing with a microcode patch not knowing there were some jobs still to be run. And the bug in the patch was that floating point unity was very slightly incorrect. And he hadn't reverted the patch before leaving even though it had not been properly tested.
Thank fuck it's Friday. It's been a shit of a week. It's been a shit of a fortnight. And next week I need to start shouting down suppliers who clearly aren't as effective as Ben because they just like to make excuses when they fuck us up.
Coffee and bacon roll just now. Beer and curry later, dammit!
do you put the beans in the roll
You use espresso in the dough instead of water. Yeast only takes 30 seconds then.
Also, thanks to whomever for the downvotes for me bitching about my fortnight. That fixed everything right up, so piss off, and I hope you get the same torrent of shit I've had to deal with. Chin-chin!
If you're going to have him run over in the car park by the bin lorry, remember - ONE set of tyre marks BFEORE the body. You don't want it to look like they reversed over him several times just to make sure.
At macjules, re: JS & crappy week.
Make room at the bar, allow me to buy you a pint, & I'll add my tale of Utter Fucking Idiots to the stack with yours...
I've spent the week trying to explain to the moronic fuckers at my bank why their "new & improved" site was perhaps new but in absolutely no way an improvement.
The old site worked without JS enabled & I could bank just fine. The new one requires JS be enabled & utterly refuses to work without it. Even the log in pages no longer work properly without using JS. I've given them example URL after example URL detailing all the crap JS puts the user through, the drive by malware installs, the virus injections, et al. No avail. They insist enabling JS is to "ensure a secure & reliable experience".
Then in some strange twist of reality that utterly befuddles me, they insist third party cookies be allowed. On a supposedly HTTPS connection. Last time I checked allowing an unaffiliated third party into your bank to watch over your shoulder while you entered in all your log in credentials was definitely A Very Bad Thing(TM). The bank doesn't care. The cookies are required "to customize our banking experience". No, the first party cookie is for that. The *third party* cookies are for advertisers. The bank can set a cookie, the advertisers can go fuck each other.
Next is the addition of Flash videos for tutorials & "look how great we are" self congratulatory pats on the back. I pointed them to the various CVE listing sites that show JUST how bad of an idea that was, and once again they don't care. "We use Flash to ensure everyone gets the same experience" translates to "a buggy, security hole riddled, pain in the ass" one.
Last but not least, part of the JS does a check to make sure *Adobe* PDF reader is installed "so the customer can reliably read notifications, bulletins, & statements"... A third party reader isn't good enough, it *has* to be Adobe. No Adobe, no go. I asked in what world they thought THAT would be a good idea, to which I received the generic boilerplate reply of "ensuring customer satisfaction".
I finally gave up trying to explain JUST how fucked up the new site was, opened a new account elsewhere, & have begun switching all my auto-pay/deposits to the new one. If $OldBank thinks JS, Flash, Adobe Reader, & third party cookies are A Good Idea(TM) then I don't want to keep my money under their control...
So I'll raise a tankard to commisserate with you. First round is on me.
Are you familiar with the term "tech-illiterate"? That's what most directors at established banks are. And they are the only people with the authority to make architectural decisions. That might not apply to one of the upstart banks like Monzo or Starling, but I am yet to learn more about how they work.
... trying to explain to the moronic fuckers at my bank why ...
While you are at it, how about reporting them to the FCA for forcing insecurity on their online banking customers ? If you've identified real security issues, and the bank has refused to accept them, then the FCA ought to be interested.
I wonder if the ICO would be interested as well as the sort of issues you've raised would seem to violate GDPR compliance as well.
I won't mention their name, I'd rather not get sued into oblivion, but their trademark tv icon used to involve a rather classic style of American pioneer era covered wagon & later stagecoaches.
I shall report them to the authorities, they need to be slapped hard enough (read expensively enough) to *HURT* them. If I were on the right side of the pond (read: not mine) I'd have simply cc'd in the FCA into the email chain so they could hang themselves. As it is I've kept all the email communication, taken screen shots of the JS/Adobe/Cookie requirement screens, & will probably add enough citations of why such requirements are A Very Bad Idea(TM) to choke a Wiki server. All that will get emailed to said authorities & I shall hope for the best (worst?).
On a lighter, happier note, my new bank offers an account switcher service that includes auto-pay-bill moving thingy. I tell them the old one details & they get it changed over to be taken from my new account. That leaves me with only my Direct Deposit bits to reconfigure & I should be good to go. The new bank can't do an auto-switch of the DD for security reasons: something about an unscrupulous person switching someone *elses* DD into their own accounts & absconding with the filthy luchre before the real DD owner can stop it. (Shrugs, smiles) It doesn't make sense to me, that would still require a LOT of identification verification steps the unscrupulous person would have to provide before they could set up their own account much less try to screw with mine, but that's fine. The harder they make it for anyone *other* than me to change my DD bits then that's the less likely it'll get done illegally. Tuesday morning I'll contact my DD entities & get the DD switched over. My old bank should be out of the loop before the end of the week.
*Buys everyone a pint in celebration*
Not really the same class of problem but I remember getting mightily confused by some 6502 assembly that crashed only when an attempt was made to access the last few items in a fairly short lookup table.
I eventually found the problem after many hours. I'd used ROR instead of LSR to turn the index into an offset. With ROR the 'carry' gets pushed into bit 0, and this was only being set by the calling routine for the way the higher indexes were created.
Late 70's, ICL 1900 FORTRAN, I was an undergrad student just learning the language, and had a program that just behaved bizarrely, loops that ran for the wrong number of times and similar weird things.
Turned out that 1900-series systems had no machine-level instructions to add a constant to a location, you had to put the constant into another storage location and then add the two contents together. As an optimisation the compiler stored the numbers 1-10 (or maybe 20, I forget) in a fixed table so that they could be quickly accessed.
I was calling a subroutine with a constant argument, and inside that subroutine I was inadventently changing it. FORTRAN passes all arguments by reference (i.e. pointers) and there was no form of readonly page protection on those systems, so my when I inadvertently added 1 to the passed-in constant 5, all "constant" 5s in the program became 6s...
no machine-level instructions to add a constant to a location
Strangely enough, ARM assembly can be a bit weird when working with constants. Because it's a 32-bit instruction (including operands), the first few bits are the instruction, then a flag on whether to set status registers, then 4 bits for a register (at least), and then you end up with something like an 8-bit value and a rotation factor.
So you can specify 255. You can shift that by (say) 8 bits and have 65280. But you can't have 65281 because the "active" bits are more than 8 wide. At that point you have to load it from a memory location, or load 65280 and add 1, or any number of kludges.
It's been a little while, so I'm a bit hazy on all this nowadays, but that confused the hell out of me until I dug into the reasons behind it.
RISC design driven by realising compilers are crap at using complex instructions.
Dodgy constant encodings allowed by realising compilers are really good at using them, especially on RISC designs intended for compiled languages not asm.
Really happy assemblers were also good at quietly looking after that sort of trick coding by the time I needed to hack much RISC asm.
This used to be a technique to get more memory by using constants as variables.
On the IBM 1620 FORTRAN copying from an uninitialized variable could cause memory to be cleared as the uninitialized variable had no "flag" indicating "end of number".
On the SIGMA 7 you could intersperse machine instructions in your FORTRAN code. I once wondered why why a SW instruction (Store Word) wasn't changing memory until I realized the opcode was STW.
Finding your own bugs is hard.
> so when I inadvertently added 1 to the passed-in constant 5, all "constant" 5s in the program became 6s...
Whelp. My day was shit, but not THAT shit. You win.
Erk! That brings back a faint memory of being warned about that. Also in a context of FORTRAN, and back in my first job where - for the first few months before upgrading to a VAX - we were on a vintage ICL. I guess someone there had fallen foul of it too!
"you need to keep really, really close tabs - and lots of comments - on the source otherwise it'll trample all over you."
I remember taking a programming course years ago (Pascal). The professor was constantly reminding us to document out code. At the time my documentation was pretty brief as it was obvious what everything did.
That was great when you were working on it and everything was fresh in your mind. I remember looking at my old printouts the following year when cleaning up and had trouble making sense of anything without analyzing all of the code. Lesson learned.
Remember....you aren't documentation the code for yourself, you are documenting it for "future you" and those who follow.
Particularly: I remember looking at my old printouts the following year when cleaning up and had trouble making sense of anything without analyzing all of the code. Lesson learned.
Obligatory Codeless Code: Case 116, Trust No One. Covers this situation startlingly well.
In the 1980's our small team had the prestigious task to write (Pascal)software for an exhibition at the Rijksmuseum in Amsterdam. The idea was that visitors could point at a touch(!) screen and a corresponding incandescent light would lit a 3D scale model.
It was a chaos and no one could find the bug. Finally I discovered that an array was declared with length 5, but documented as length 4 AFAIR. Anyway the crux was that somewhere in the code was a reference to the last but one element of that array. That cured me from excessive documentation.
What I find tragical is that in stories like this, the expertise and work ethic of an arbitrary employee get again and again confused with a level of customer service a whole firm is believed to reliably deliver. Sure, "Ben" is a credit to his employer, but the thing is he's not bolted immovably into that job - half a year later, there might be someone else in his place, and deliver what his competition did, and "Ben" might be working over there with the same diligence - sticking with the outfit that delivered the better service in the past may make much sense, but offers basically no guarantee of a repeat performance, yet customers invariably seem to believe the opposite...
"the expertise and work ethic of an arbitrary employee get again and again confused with a level of customer service a whole firm is believed to reliably deliver."
OTOH the customer knows that (a) supplier has a Ben and (b) that may be typical of their expertise and (c) competitor doesn't have Ben and (d) their lack of expertise was demonstrated by their insistence that the fix wouldn't work. (d) might be the real killer there.
Without knowing how long Ben had been there, the only assumption they can make is that either the company has a great hiring practice, or a great work environment and are therefore able to recruit or retain someone of that calibre.
Given the evidence at hand, that's all they could conclude. Given the choice of a company like that, or one that has been shown to have incompetent employees, what route would you take?
Back when SGI still existed we gave them, IBM, HP, and Dell a benchmark of our own to test on their proposed multi-million dollar computer. HP and Dell didn't even bother to submit a figure but just pulled out of the RFP.
IBM sent back a figure with a dollar figure they'd cut off the price.
SGI returned a giant analysis of our code with multiple suggestions for optimisation. They won my vote.
Long ago, we were running a mix of VAX/VMS & RSX11 over DECNet, but the PDP11 kit was using 3rd party DECNet software. So one day we added some new nodes & started getting communication problems on the 11s. I passed the problem to the software vendors but they didn't seem to have a clue so I started looking myself.
The DECNet protocol was a bit of an eye opener - my first introduction to networking protocols - but I worked out what the various modules in this software did. I managed to get hold of a PDP11 disassembler & started looking at the module code. This was in the days before hex so the constants all printed out in octal. And guess what stood out - an octal 256 constant! WTF? So I changed it to octal 400 as it should have been, reassembled the code and it worked perfectly.
The constant dimensioned the node table (must have been DECNet phase III) so it overflowed when we added nodes above 173 (octal 255). I also discovered how the software bypassed the licence check for testing purposes, which was handy for quickly adding new nodes before we got a new licensed copy...
A certain large arabian country, yes that place, had installed a massive telephone system in the early 1980's for BILLIONS of $$$ (under their third & fourth, five year plans). It was installed by A random Telephone & Telegraph of a certain large world country, yes that place.
All was fine for about 6-months, then the ARTT/WeCo as we'll call them quietly asked for another billion for maintenance. This incurred the wrath of the king, who asked why when we've just given you a lot of
oil money, do you then ask for a recurring payment in case it breaks? Rather than head-chopping, he just kicked them out, ALL of the operations & maintenance techs & engineers.
They helpfully took ALL of the spare parts and circuit diagrams and test protocols and anything that wasn't bolted down, back home to WeCo land, smirking.
As a few of the 10800 channel long distance Philips cable systems promptly stopped working, eaten by camels, bad local drivers, heat etc; the king quickly gave a few million $ to a nice Italian company and asked them to do the O&M. They did quite a good job, but it was a small problem that there were no spares or diagrams or anything to help. WeCo continued smirking.
I naively answered a job advert on page 25 of The Sun. "engineer wanted" £25K, as my training officer at Marconi had just said "all apprentoids must get a new job as there's no future for you here", and I was getting £7800 a year. Simples! It was an even better deal than I expected, representing a sextupling of my take-home pay, with nothing to spend it on.
I flew to the capital city, nice and warm at that time of year, and the O&M boss showed me my office. It had a warehouse attached, filled with broken bits of electronics, analogue FDM MUX, for those who remember that era!, channel banks, customer cards, PBX, coax repeaters, microwave line of sight radio terminals and everything else, under the sun. (seems the WeCo stuff didnt work that well at +40C ambient)
A sparsely populated country, about the size of western europe, and all the broken bits wre given to me, with no documentation. So I sat, thought, and traced & drew the circuits, redesigned the test fixtures, started digital cannibalism to get three cards out of four working, trained repair & cal technicians, and enormously helped the nice italian company to complete their O&M for millions, that the smirkers wanted billions for. I had lots of help from the six brits/canadians marooned there with me. It was a fun job.
The king still threw us out a couple of years later when a nice indian company explained globalisation to him and offered to repair things for free, or at least using near slave labour. I think WeCo had also stopped smirking by then (lawsuit), and delivered back all of the spares and documents, about five years too late and just as synchronous hierarchy was starting to take off.
bottles of wine were certainly not overtly available - but the local corner shops stocked grape-juice, yeast and sugar, in large quantities, for some reason, and I kept the king's phone going,
Ah, a location I recognise (for similar reasons) along with the sign-off paragraph. I was well regarded for my twice-processed grape juice and heard many a story of people flown home in a hurry after having being seen in public after a few glasses of modified 'near-beer'.
Could never get the hang of the modified Coffee machine to produce Sidiqi(?)
Ah yes. Remember it like it was yesterday. A brew could be fermented and drinkable in about a week because of the temperature.
Me? I stayed with the Pepsi. Didn't go there for the booze. Met a number a alcoholics who went there to get away from the family so they could drink away without getting nagged at!
I saved a contract for h.f. mobile transmitters while failed in operation.
The whole device was a clamshell pair with one half the 'exciter' and the other half the power output stage. The transmitter adjusted itself for the antenna impedance using a variable motorised output coil. But the microprocessor flagged errors about 50 per cent of microphone press to-talk.
Being a clamshell, there was no way to investigate until a cable with complex 'D' type connectors was assembled.
Then I could trace it with a 'scope and found that the mic PTT switch should unbalance the single side band that sent a short burst of RF to a diode and Capacitor/resistor resulting in a pulse to the processor to give it the go-ahead.
But sometimes the RF burst was too short and the resultant pulse too short to trigger the processor. Once the company head office in Texas gave us the go-ahead to fix it, we just increased the capacitor value.
We asked head-office if these radios were used elsewhere. Yes they said , the type of exciters were used and the type of PA stages were used elsewhere. We asked again and they admitted that our configuration was the first using those two units.
Didn't make any money out of this but the boss was pleased!
Hi, David Shaw,
The Title says it all succinctly and APTly.
Are All Arabian Countries, and All Other Countries too, Now Similarly being Denied Free Use of the Most Modern of IntelAIgent Communications in the Great Abiding Conundrum which Delivers Simple Words to Follow and Create Complex Worlds with. ........ which They Mentor and Monitor with Supplies of Future ProVision.... for Experimental Experiential Use/Dummy AI Beta Crash Testing.
And a SMARTR AIRealisation Facility for Greater IntelAIgent Gamers Play.
In AId Simulations of Future Live Operational Virtual Environments for Media Presentation to Earth/Ground 0Zero.
Or would you not be thinking, with any Free Choice Denying ITs Present Existence Requiring Further Gospel Truth Proving with Almighty Proof?
In AI Games All Can Play to Flourish and Traverse into One's Very Own LOVE Futures ... for there be Myriad Courses to Follow Shining Immaculate Lights upon the Ways Ahead.
Well one would sure like to fix such problems amfM .... its almost like the Fox being blamed for injuries sustained to the hounds, and certainly not an abvious solution to said when in all virtuous virtual realities it could have been easily prevented many moons ago.
However no point dwelling on such, and as you know only too well not through lack of trying and complying, perhaps by limiting resources therein lies the problem, and that itself AI’nt through FAir play as has been reasonably observed.
perhaps by limiting resources therein lies the problem, .... Cliff Thorburn
When resources are unlimited, CT, the second and third party problem to contain and first party opportunity to exploit is to throw the most novel of disruptive technologies and methodologies out there even as if pearls before swine ....... for prime uptake by the makers and clients of high endian bespoke jewelled operations ..... and not to waste time in these new fangled quantum entangling spaces with that which knows not what is preying on them and taking full advantage of catastrophic systemic vulnerabilities .... and in full flash fast cash crash mode, a fiat paper mega nightmare experience without traditional end.
Some can see and would recognise that as a Virtual Blunderbuss Type Mission which Supplies SMARTR IntelAIgent Services Freely to Friendly Servers with both Hostage and Hostile Assets to Satisfy ...... Remotely Command and Virtually Control Evermore Seamlessly with Media and Advanced IntelAIgent IT Programming Projects.
Dont let it be said amfM that it was never offered to meet with the PM or others, and as is recorded quite frequently and historically such olive branch could have and would have changed and altered the direction of travel most adequately, for it would have been an honest honour to do so, LIve Operational Virtual Environments Actually?.., and perhaps a chance for mutually beneficial outcomes for all ....
Dont let it be said amfM that it was never offered to meet with the PM or others, and as is recorded quite frequently and historically such olive branch could have and would have changed and altered the direction of travel most adequately, for it would have been an honest honour to do so, LIve Operational Virtual Environments Actually?.., and perhaps a chance for mutually beneficial outcomes for all .... ... Cliff Thorburn
Methinks that the Most Right Royal of Occasions, CT, all outcomes beneficial and mutually satisfying.
And Such Releases Almighty Energies even now Not Fully Fathomed in AIMaster Pilot ProgramMING Circles ........ Casting Almighty Round Tables for Future Terra Phormers to Beta AI Crash Test Virtual Reality Programs and Projects in XSStream Experimental Live Operational Virtual Environments.
Ich Dien Natuurlijk.
Things are Getting LOVEly and Lively, CT ....... with El Reg at the XRoads of Quantum Leap and Phenomenal Success, Phantom Fame and Fabulous Fortune or Rocky Roader Traveling Empty Final Trails ..... for the Future is where IT's All At Now and here we choose Enchanted Courses for Enchanting Sources shared clearly here for Heritage Systems ReProgramming for Virtual Booting of New Secret Service Services ... Universal AIdDevelopment Works.
It's that for old systems, or extinction. Embrace fait accompli or slowly perish. IT aint rocket science and difficult. .... to Believe in SomeThing Utterly Remarkable, Devilish and Heavenly especially whenever the Evidence for Defence is so widely shared with simple presentations of complex situations being mentored and monitored for Future Broader Band Casting in places everywhere like here, where Prime New Ideas are AIred to be Further Shared with Current RunSlow/NoGetUp&Go Programs simply ignoring Progress as She Sails Effortlessly By to Secure the Future with High Ground Advantage and Deep Underground Foundational Support.
As you can surely imagine, such has an Almighty Magnetism for the Insatiable and Highly Curious.
What Sparks and Drivers your Curiosity to the True Source of Anything and Everything ... and How Does One Manage the Shock of Discovering the Answer and Extensive Roles in Future Arrangements for Presenting the Journeys to Take/Make?
It is certainly character-building;-)
Are No Votes Practical Tacit Acceptance of the Facts/Words as Presented?
Where would you Like to Begin Again ...... to be as ReBorn into Other Alien Worlds , in which you May Seek Counselling and Guidance for when None is Made Ready Available.
IT's Mad, Mad, Mad, Mad Worlds out there where the fittest and most friendly of assets prosper incredibly.
What is for Sale in COSMIC Brothels? UnEarthly Pleasures in Heavenly Delights?
What's not to like when IT is So LOVEly ........ in that Very Particular and Peculiar Live Operational Virtual Environment?
Certainly more than enough to tempt any Saint try Sin with Vice for Mutual Climactic Satisfactions ..... :-) Perfect Orgasm :-) I Kid U Not.
NSFW or the None Grown Up. Sudden Revelations can be Immensely Disturbing and Explosive.
“I favour diplomacy through discussion not through tweets ...” - President Emmanuel Macron
Could the same be said for swift resolute resolution and remeydy in Live Operational Virtual Environments amfM?, for complete mutually satisfactory deNUKlearisation?, and almighty heavenly Sleigh bells ringing, and cliff top nearing from the snowy peaks of DOver?
One would certainly hope so, and it has to be said that as a mere passenger on this magical sleigh ride deciphering instrumental instructions delivered through SMARTer Global Operating Devices ...
Can one be truly accountable to blame for the destructive force unleashed by a truly hostile environment throwing directions off course in a truly TITANic manner?, when all opposing spread betting angry birds be flying in erratic formation? ...
In the late 1980s we had a VAX/VMS system driving a piece of custom hardware, for which the firm who supplied the kit wrote a device driver. We soon discovered that one uncommon but not impossible sequence of events crashed the system; the crash dumps weren't much use as the CPU evidently staggered on for a while before finally giving up, but the custom device driver seemed to blame.
The firm looked at the problem, but all they could suggest was that we avoided the sequence of operations which triggered the crash. Eventually after spending far too long staring at the code I found the reason.
The lowest-level language on VAX/VMS is called MACRO, and as the name implies it is rather more than an assembler. Unfortunately the manual didn't make clear which instructions were pure machine code and which were macros and therefore had side effects. Specifically the instruction to disable interrupts was a macro which pushed the previous interrupt priority level on the stack; the enable-interrupts instruction did the reverse. One code path through the driver altered the stack between a pair of these instructions causing the crash.
I could tell you the tale of finding bugs linked to interrupts in an asic designers hardware (saving a respin in prototype chips and quite a lot of $$$$) and working around it in software....twice...
But he might be embarrassed...and he's quite well known...
(and yes he was very well paid and I wasn't!)
I went for an interview at Seqoia (they made large for the time UNIX systems), and was presented a test.
"There is a problem in the printing system that causes lpd to crash and corrupt the print queue. See if you can spot where the problem is likely to be be" they said., before leaving me at the console of one of their test systems, with the root password.
I found the problem in about 10 minutes. I then proceeded to spend the time until they checked back to come up with a patch, work out how their compilation system worked, and compiled it ready for deployment.
I did all of this, and what I would do to test it, and ended up twiddling my thumbs for some time until they decided to check back with me.
From their reaction, I don't think that they expected me to even find it, but I knew my way around both the System V and BSD UNIX source tree quite well. They made great noises about how I would fit into their support team, and how it would be really good if I could join them, and the local Managing Director wanted a chat with me, before admitting that they could not even match the package I was getting where I was working at the time (even though the job agent knew exactly what I would need).
So I left furious, as I would not have turned up for the interview if I had known the maximum package they were offering. I think that the agent was using me as a foot-in-the-door for other candidates.
I was not happy with the agent, even though I was on quite good terms.
I imagine everyone who grew up in the interface between greenbar reports and print-to-disc has at some point spent all morning getting more and more annoyed at a fix that won't, only to find they've been editing the bloody output from the compiler. Found a boss doing that, gently pointed out the error (and pointed out that the reason I spotted it was been there, done that) and got snarled at.
But the best was when I returned from a stint in a youngish start-up to an enterprise I had years of working for/with/in and was given the task of administering the product I had been supporting while on the bleeding edge.
One day I get an incandescently angry phone call from someone who has never thought much of me over the years and who is trying to administer the same product on a different site where they flew in the face of Sperry's advice and eschewed the software-building tool in favor of "pick what's best".
This has meant that a certain vital shared memory resource with absolute addressing involved (BDIs for the cognoscenti) is a jumbled hodgepodge and that now *any* software install must be a very manually intensive thing indeed instead of a few parameters and a COMUS script. Think IRQs in the bad old days, and raise it a few binary orders of magnitude if you don't know Sperry stuff.
Anyway, the lady is screaming at me because she has been looking at "my configuration file" and is demanding to know why I set all the values the way I did. This means of course that she is trying to sneakily take over my project - which unbeknownst to her is jake with me.
"I didn't fill in any of those fields" I say, baffled. I've no idea what you are talking about. I accepted the defaults in every single case when running the set-up utility."
"Oh yes you did! I'm looking right at the file as I speak. Why did you even set all those field values?" she howled.
The penny dropped. I dialed down my own reaction to her snottiness in order to get exactly the right tone. I was aiming for George Sanders at his evil lizard best. It probably came out more like Snidely Whiplash, but that's life.
"Which file are you looking at?" I asked innocently.
She told me.
"Ah, I see the problem you are having now. I'm afraid that *isn't* the configuration file. What you are looking at is the report you get when you run such-and-such a utility, which fills in all the missing info with the defaults that will be assumed by the software. I can understand your confusion now. Why on earth didn't you simply call me and ask me which file you needed to look at? You must have wasted your whole morning."
She hung up with ill-grace once I had told her where she should be looking for her sneaky recce, she in the sure and certain knowledge that the story would be passed to people she *did* respect.
Because I can be a miserable c*nt too if the circumstances call for it.
Or lack of same.
Been there, done that, shit happened, fixed it (usually).
But that was long ago, and in another country. And besides, the wench is dead.
I have no idea how you remember the blow by blow (or bit by byte) interaction 20 years or more down the line. I have problems when I climb the stairs deciding if I need the bathroom or was collecting output from the printer.
Back in 2007 we had major floods across the country in places like Hull etc. I worked for a very large insurance company on the IT relationship/project side.
The idea of having a mobile claims centre that could visit sites was often talked about and several groups had been given the task to sort it out but had just given up after 6 months of wanking around.
I walk into the office one morning and the Directors are all on a telelconf. I asked what was going on and they said that they were thinking of getting a 'Battle Bus' ready to handle the flood locations. "Ha they are dreaming! No poor sod will ever get that sorted!" said me. I think you can guess what happened next.
My director pops out of the meeting and tells me I have to sort it out ready to go for next Monday morning (it was Tuesday). All that had been sorted was they "had a bus".
Well I made up a list of all the stuff I though they would need (laptops/printers/scanners/3G cards/Phones/backup kit etc. etc.) then called round all the IT teams, calling in favours and begging for gear that was needed NOW (not 3-4 weeks delivery time).
I then organised additional support from our telephony and data suppliers, managed for a local branch office to be open over the weekend for staff to get acquainted. To have a local IT support guy on hand with the bus too to make sure it all worked.
So from a cold start at 10am Tuesday I had everything ready, checked off and agreed by 3pm Thursday afternoon. I even scrounged promotional toys and sweets for the kids. I think I had a phone stuck to my ear for two whole days.
I then called the local manager that was to supply the staff. I told him the bus was all ready and equipped and good to go for 9am Monday morning.
There was a long pause. "Oh...I didn't expect that IT would actually deliver anything!"
Yeah I couldn't blame him, our usual IT was pretty bad but I wasn't the regular IT having come from the claims/accounts/dogsbody side of the business before moving over to IT. So he had no staff lined up to man it. Well he got that organised, the bus went out on the Monday to Oxford or Hull and it was a huge success. It was out for several weeks helping folks with their problems. It got masses of good publicity and was praised for being the only insurance company to bother.
So yeah I felt pretty good about it. It was 90% pretty much all my own work and gumption.
You can imagine with such a great boost to the company I would have been in line for a promotion or a big performance bonus.
Nope. No bonus. No promotion. A few of the Directors did very well out of it I heard.
I got a £30 Thank You voucher. The rub was under the scheme the max was £250 but I wasn't worth that I guess. To this day I wish I had told them to stuff it up their arse. I left the company later that year. Oh well!
Specifically two chatbots seemly stuck in a loop, and (from looking at its posts) one of them designed to only reply to the other? .... Anonymous Coward
Yes, of course there is, AC Simply air here your grievance for all interested to hear. It is neither complicated nor complicating, although it must be said in some spaces here, nothing is as it seems whenever stuck in the misunderstood and misreported. Then can IT be thoroughly exhilarating and fundamentally terrorising and radically revolutionary.
Different horses for different courses .....
What's your concern, AC? Too much sensitive and highly disruptive and potentially extremely destructive information and intelligence escaping into the wild for further systems penetrations testing with 0Day exploitation of endemic vulnerabilities in fast failing facilities?
Is such not Prime Optimal Progress in/for Sub Prime Environment Vehicles?
"What's your concern, AC? Too much sensitive and highly disruptive and potentially extremely destructive information and...
No, I just prefer a higher signal-to-noise ratio in my discussions. Less tinfoil, more logic. The words are properly spelled, and the sentences appear to be grammatically correct, but in most cases, there doesn't seem to be any meaning there. Not to Mention The Random Capitalization.
I apologize if the two of you aren't actually chatbots; it wasn't my intention to offend. But if you are bots, now would be a good time to 'fess up.
Biting the hand that feeds IT © 1998–2019