* Posts by Trixr

561 posts • joined 30 Jun 2009


Beware the fury of a database developer torn from tables and SQL


Yes, totally agree. Just because a translation is older and has "ye" in it, it isn't necessarily any more accurate.

And while an idiosyncratic word order might be more "poetic" in English sometimes, there's no point doing that if the original doesn't have a distinctive tense or style that you're trying to echo.

One of my pet peeves is older translations of non-European languages that are full of "thee" and "thou" when the source language never had a distinction between the formal or informal "you". But translators thought it sounded more "exotic", so that's how they rendered it.

Keeping your head as an entire database goes pear-shaped


Re: Drop and go

If it's anything like where I work, yes, it is being backed up. Into a backup which has never been tested, while the backup account is an AD Domain Admin.

I was actually shocked to find that the DB service didn't use the same cred. No, the "SQLService" account is running ALL the DBs in the entire org, multiple DB farms, scores of servers and applications.

Yes, I have got copies of the emails where I've pointed this out at length to managers and security team, multiple times.


Re: What could go wrong?

Slight modification - its memory.

The brain may function, but like someone with Alzheimer's, if the storage or connectivity to the storage is no good, things fire up but the inputs are all scrambled/meaningless.

Thinnet cables are no match for director's morning workout


Re: Token Ring

See, that's Ethernet's USP - just make broadcast 'storms' into a protocol feature.

I do not have found memories of token ring, nor the place that would have networks going around a couple of floors, then up and down between floors (16 floors, two adjacent buildings), so you'd never know which network the token was "lost" from when something when down. (At least, not as a lowly desktop support peon.)

Then those crappy IBM "gender neutral" connectors that'd fall apart if there was a stiff breeze from rolling your chair forward... There was some plastic device that'd make them more difficult to kick apart, apparently, but we never got those.


Re: Ethernet woes

Sorry, you didn't Cap Up the very important Job Title of "Technical Writer". No wonder it's confusing.

We can bend the laws of physics for your super-yacht, but we can't break them


Re: Overinflated sense of self importance

That's a better deployment of the "rules of the physical universe" talk than the OP's. At least you tried. And at least "speaking to the manager" meant your ear was no longer being bent with the circular argument.


Exactly. Saying, "music sounds better from the player attached to your sound system via a cable than from a radio station, doesn't it? Same with data transmission over phone lines vs satellite" isn't that hard.

I don't doubt that the owner was an absolute arseh*le, but it's always better when the tech helps themselves first (and any other techs saddled with the client subsequently) by at least attempting the reasonable explanation once and not going out of their way to piss said owner off when they're fundamentally asking "why is it different here?"

Of course it's glaringly obvious to anyone who's dealt with this stuff, or even tuned a radio, but when they're a rich prat who's had everything supplied on-tap - especially people who never had to earn their wealth doing real work - there are going to be "knowledge gaps".

There's nothing worse than dealing with "demanding customers" (aka rich prats), though, especially when travel and fatigue are factors - we can all can end up in this kind of situation where the filters go off when confronted with rudeness and the blindingly obvious.

Warning: Windows update breaks authentication for some server admins

Black Helicopters

Cue the black helicopters

They've almost succeeded with getting rid of on-prem Exchange with their diligent work on b0rked CUs in the last several years. Since November last year, they seem to be getting into high gear with stealth-deprecating Active Directory too.

I think every major AD-related update since then has had issues. And that's not counting Server 2022, every month's update for those seems to have something that screws up some AD-related service (me, to boss re deploying 2022 DCs: "NOT YET").

Beijing-backed gang looted IP around the world for years, claims Cybereason


Re: Wait, what ?

If you know what they did with actually-useful WindowsUpdate.log by ditching the text and converting it to some mystery binary format (probably this one) that could not be read by any of their existing tools (like Message Analyser), and requires a stinking powershell command (the command, not powershell) to convert into a readable format, meaning it can't be tailed in real time, this is 100% no surprise whatsoever.

I wonder if this will stop MSFT inventing all manner of logs that are unreadable by consumers, are also apparently zero use for diagnostics (never once had a support engineer request anything of that nature, admittedly I don't work with desktop systems), and which consume considerable amounts of space at times. I get the need for faster logging at times, but the ETL type should be very limited in size and meaningful output sent to the existing event logs (zillions of those these days too) or a text file.

Including some of their monitoring apps, like the ATP sensor service. One of them DOES log to a text file, and seemingly is a spew of all the .NET activity inside the app with absolutely no way of configuring it to "error only" or something that doesn't churn away constantly.

Microsoft to nudge more users toward Azure Active Directory


If it's as effective as we found the Azure ADDS health monitoring, good luck. Replication failures and LSASS timeout errors in a domain a couple of weeks back, not a peep out of ADDS health.

Saving a loved one from a document disaster


Re: Evil Books!

Exactly. Talk to an archivist any time about how many works have been lost over the centuries due to fire, mould, moths, rot, etc etc etc etc. Which recording company was it that recently had all their pre-70s (?) masters go up in flames when a single warehouse burned down? Film on nitrate stock is literally disintegrating as time goes on, where it's not spontaneously combusting.

A lot of library/archive budgets these days have chunks set aside for digitisation projects, and there are a lot of very good reasons why that's happening.

These days, at least we've got a better grasp of digital formats, we aren't so reliant on physical storage media (at least not in the sense of the one copy being archived on a laser disk or whatever), and people in the biz understand the importance of transferring files to new formats as required.


Re: WordPerfect

Um, why wasn't the printer rendering her document? Why on earth would Word be a better option if the organisation worked with both document types? Especially since WP was apparently on the machine.

As written, I have to say this sounds like more of a support issue than a user one. Perhaps there was a user issue in that the WP document was in letter size and the printer had A4 paper or something, but that would not have been solved by Word. Or your troubleshooting, as described.


Re: Mad dash...

I worked in a place in the late 90s where the secretaries knew perfectly well they had to reboot if a machine locked up (memory issues due to awful Word macros after transferring docs from word perfect), but they would lie about having done so.

So for the more senior ones where it was not worth arguing with them, I had a routine where I would visit, open a dos prompt and run dir /s, let it run though all the file listings, THEN reboot the machine. Some of them subsequently sent notes to my boss praising my "responsive support" and how their machines were "much more reliable" after one of my visits. More than one way to skin a cat. Wish we'd had remote support!


Re: "decades past, when DOS was king and remote access" . .

I'm not anal about many things, but the most minimal vampire power draw and/or standby lights on devices that go unused for more than a day drive me absolutely bonkers, even if it's mere cents per annum to run. So that'd be my solution too (IRL, I refuse to have a printer in the home - they hate me and I hate them).


Re: Imperrfect

And you could search-and-replace the codes, instantly reformatting a document, if you knew what you were doing. It was great, in that sense at least.

Apple has missed the video revolution


Re: I'm no Hollywood editor...

I'm no great fan of Macs myself, but yes, I was eyerolling throughout at the tone of "boo hoo, this one tool doesn't work on this device".

If there's additional context as to why Macs are underperforming when it comes to AV processing in geneal, it's missing from this piece.

You should read Section 8 of the Unix User's Manual


Thank god for Postfix, is all I can say.

Thankfully that was available before I had to try using Sendmail for some pretty complex tasks (yes, it would be capable, not necessarily simple to configure, let alone without opening up some horrible holes).

KDE Community releases Plasma 5.24: It's eccentric, just like many old-timers


Re: Kameleon Desktop Environment.

I agree about the "cloudification by stealth" focus, but I really disagree it's about their enterprise customers. Well, at least not in terms of providing any flexibility to their customers (or actual cost savings much of the time for large enterprises, but you know those sums won't be done properly). They want to take it away from inhouse support, so an end user will basically fire up Windows, connect it to the cloud, and receive as uncustomisable an experience as MSFT can get away with.

It'll be easier to slurp those up in due course by telling businesses they can increase their ROI further by getting rid of those expensive desktop devs (or solutions integrators, ditto). Too bad a lot of places will try drinking the kool-aid before they realise that not everything is in the cloud yet. Nor that it should be.

Since they're giving away the consumer version, they want those peons in "upgrade" lockstep with even fewer customisable features to reduce their own end-user support burden.

Honestly, as soon as I saw garbage like "xbox scheduled tasks" (yes, the gaming XBox!) and consumer data sync services in the *server* OS distributions from Server 2016+ ("contacts", "wallet" etc- you can't get rid of them, just disable, unless you run the Core version with no desktop - can't be done for some products), I just crossed my fingers I'll be able spin out the remainder of my career somehow without winding up in some horrible call centre or working for a "solutions provider" that just slaps their logo in the 16 x 200 px space provided for it in O365. I suppose we've still got Cobol bods out there. We'll see.

To err is human. To really tmux things up requires an engineer


Re: Step outside

Tape jukebox I encountered in the late 90s (maybe HP) had a very bad grey-on-lighter-grey LCD screen with four or five rows of "button" labels in two columns, then the physical buttons to each side of the screen.

Unfortunately, I managed to wipe half the backups one day when I mistakenly selected "Initialise" (top right) instead of "Inventory" (top left). My eyesight is not the best, and in the dim server room with the very dim screen, one label with 8+ characters beginning with "In" looks much like another, and it was only the second time I'd exported the tapes from that device.

But I did know that "Inventory" took a matter of seconds to scan the entire jukebox (only 24 tapes). It unfortunately took me many more seconds to realise that hearing the tapes get loaded one by one and a few seconds of "bzzzzzt" to write the initial sectors was a bit unusual and taking way too long. At least when I yanked the powers supply when the light finally dawned, I timed it sufficiently well so that no tape got jammed in the heads.

Why should I pay for that security option? Hijacking only happens to planes


I personally like the idea of conductive computer keys hooked up to a switch with a variable resistor that begins at say 20V, hooked up to a mains power source. Then in linked to something that tracks the number of jobs they log that turn out to be their own stupidity.

Each new job that gets added to this database results in an increment to the shock that is delivered to their fingers via the keyboard each time they try to open the call-logging form (or email the service desk). Of course results will vary according to locality, but with places that run at ~240 from the mains, repeat offenders will soon be taken care of ...permanently.

No more DRM-free downloads as Amazon's ComiXology app set to disappear inside Kindle



Tor Books does non-DRM publishing, and they use Amazon as one of their distributors. They may not be the hugest publishing house, but they seem to do fine. There are other small "indy" publishers that do similar.

Certainly not disputing it'd be harder to turn a profit, but I don't think it's all doom and gloom either. For example, even though I know Tor don't DRM stuff, I also don't go torrenting their works, both for convenience and the fact I want to pay people for their labour.



While this is accurate in a factual sense, it's ridiculous in a practical sense.

A) the cost of a "licensed" ebook is not significantly cheaper than a paper copy, factoring in printing and shipping and distribution costs. In fact, I'd guess there is likely no actual cost differential applied to the book based on its licensing at all. Not that they provide a breakdown, of course.

B) The concept of "licensing" with no specified period also strikes me as ridiculous. I wonder how it works with author contracts - I presume they're not written with "Amazon gets to license this forever". If not, then the license interval should be no greater than the period that the publisher has licensed it to Amazon, and that should be stated clearly up front.

I'd even be fine if a work was released with DRM, which was then removable after, say, five years. Most profit in a book is generated within a year of its release - people go nuts over new books by favourite authors (I'm guilty myself - I have three authors who I effectively "autobuy" as soon as a new book of theirs comes out). Especially if you look at it in terms of the secondhand book market - no profit there, except for secondhand book dealers. People would still buy non-DRMed books - they do already, from some publishers - because they would not be bothered with the hassle of obtaining them by "other means" if they're already in their favourite app.

In any case, I pay about the same for DRM vs non-DRM ebooks (e.g. Tor books) distributed by Amazon, so I have zero qualms about stripping the DRM and transferring it to my own ereader. I personally get incredibly frustrated by book piracy, since I would actually like my fave authors (and the editors etc) to be paid for their work, but I feel like publishers get around that anyway in the same way that supermarkets mark up goods to cover "shrinkage". Ideally, of course, people would pay a fair sum for the books they own, and if more people did that, the less they'd cost for everyone.


Re: I always keep local copies.

But will that work with the comics? Since it's a different file format, it may well not work so well.

I do the same backup/copy-to-ereader (I prefer Kobo) process with my regular ebooks, although Amazon are making it increasingly difficult.

JavaScript dev deliberately screws up own popular npm packages to make a point of some sort


Re: Why is this malicious?

What laws are being broken here? In any jurisdiction? What "reasonable" developer is sucking code off a source they don't control directly into their own products? What enforceable guarantees are there that the code is fit for purpose and does what it says on the tin?

There's convention, as you say. There's even malice in their actions, especially if they know that people that pull the code are that stupid they don't do basic checks before modifying their own products. As to some kind of ~actionable intent, well, if it's not breaking cybersecurity laws - seems unlikely - that's something else.


This is really nothing to do with JavaScript, other than highlighting incredibly poor practices with how people maintain their code.

This could happen with literally anything where people are directly pulling the source into their code with no intermediary steps.


Re: Proof that the industry is mad

It happens in *some* shops (too many, obviously) that don't bother trying to do the absolute minimum with maintaining a known set of dependencies that are not directly pulled from the source.

How can you maintain a product if everything is constantly being modified beneath the hood? Leaving aside the amazingly glaring security hole, of course.

Ooh, an update. Let's install it. What could possibly go wro-


Re: Windows NT 4 SP2

Oh no, the idea of rolling in any NT patch before three months had elapsed (yay the 90s) just fills me with horror. And it wasn't just the even-numbered ones. ISTR SP5 had a niggle or two. Great practice for Exchange CUs, which they STILL screw up. Not to mention Kerberos just before xmas.

At least working with NT made you very aware of using a test environment, piloting with specific user groups and so on... if you survived that without major outages, you were pretty well set up.


Re: Never trust fixes from random people on the internet

Yep, I would have had the backup prepped first, only after having argued up to the job-endangering level of "I do not want to install a non-vendor-supported change for critical infrastructure" before agreeing do to the work with sign-off by at least two managers - security and main IT boss. And after having reviewed code in said change first to the best of my abilities and explicitly highlighting potential risks, in writing.

Or, yes, ideally, a standby system with the new config, swapped in and readily swapped out - with all the aforementioned risk sign-off.

Some things are really not worth the hassle. Especially for only 25 quid p.h. and all that stress - unless my hourly rate was eight, maybe.


Re: Netware? Less than 20 years ago? Where was he working - Jurassic Park?

Ahem, I got to set up a greenfields AD to transition from Novell in the year of our Lord twenty-nineteen. The only reason they did it is they wanted free Office, so of course MSFT was dangling good-old O365 AND you can buy this edu license plan with Windows licenses bundled and yadda yadda. (Too bad you have to pay $$$ on top for the AV/security licensing to match up with the requirements for govt orgs).

To be honest, it was very, very fortunate we had it all up and running before La Covid came to town - being able to work in O365 and leverage remote access for staff (the student learning system was already remote-accessible, as they mostly are these days) was a life-saver. I can't imagine what would have happened if it'd been pure Novell still.

It still persists with some file and print, although the reason it hasn't shifted is because no-one wants to take it on with "these uncertain times". And because certain managers have completely drunk the MSFT Kool-ade of "ALL files go to Sharepoint Online". Yeah, sure Adobe suite products and similar work great if they're having to pull huge project files down from the interwebs. Standing up an AD-joined NAS and print servers would have enabled us to have Novell completely out by now.

Microsoft patches Y2K-like bug that borked on-prem Exchange Server


Smells like stealth deprecation of on-prem Exchange

Honestly, it's hard not to hear the black helicopters overhead from this latest screw-up with MSFT's avowed intention of forcing everyone into the cloud. Although, since a hybrid Azure deployment still requires Exchange servers on prem even if all mailboxes are in EXO, it's hard to know if it's Exchange or simply on-prem AD they're really after. (I joke. Kind of.)

That said, it's classic business as usual with Exchange CUs. While the window between OS patch releases and production deployment has increasingly narrowed in my little world, there's very little that'd induce me to apply an Exchange CU less than 2 months after release. In fact, in recent years, there have been perhaps two I've applied within a month. (Applied other workarounds for a few others in the interim. )

For even the "super urgent" ones, I've waited at least 10 days after release and carefully reviewed the changes... and waited for the screaming to die down and the fixes to be released.

Wi-Fi not working? It's time to consult the lovely people on those fine Linux forums


I did an exam at the end of an RHCT course lo these many years ago, which comprised them breaking a few simple things and you needing to fix them, plus set up a web server or some such.

The course had lead us through doing the network config via the GUI (this was just for lowly "technicians" of course), and when the test machine showed a "broken" network, it was a matter of opening the same control per the earlier demonstration and toggling one setting. Alas, I can't exactly remember what it was - I think perhaps enabling DHCP on the wifi adapter.

That was the first step. Without the network, none of the other components in the exam would work. Some poor bugger adjacent to me did not get even that far - they were struggling and sweating bullets throughout and didn't finish.

They had seemingly bypassed the GUI for the first step and dived straight into the various conf files - at least I assume, since whenever I glanced their way, they were staring at text on the screen, whether confs or man pages. I always found wpa_supplicant and the various confs for the network stack as a whole a bit of a maze on Linux. A little config like DHCP being enabled on a specific interface isn't necessarily that obvious when you're staring at a conf file ... assuming you've got the right one. Assuming you figured out "no DHCP" was the problem you had.

So yes, sometimes you jump to "things can be tricky in Linux" without considering first principles.

(Although I could have done without the annoyance for many years of having to write a shell script to enable my Dell laptop trackpad every goddamned time I rebooted.... never got to the bottom of it)

When civilisation ends, a Xenix box will be running a long-forgotten job somewhere


Re: Prototyping for production

My sympathies re the Sendmail. Having to use a set of custom commands to reliably modify the configuration file just demonstrated its "quality".


Re: ICL :)

And not to "play the gender card", try also being a girl in the days when we were explicitly forbidden to do subjects like technical drawing over home ec, etc. Being actively discouraged from doing sciences, especially physics, "because you're so good at French and German". Actually, I was equally good at the sciences and languages before being forced down the "arts" stream. At least the typing eventually came in handy. Never saw a computer at school.

We weren't middle class - no techie people in my family or family's acquaintanceship. No engineers or scientists or any such type. Our most sophisticated bit of kit in the home was a VCR. In fact, I was the first person to go to university in my family, studying linguistics. Thankfully, I fluked into a philosophy module that taught propositional (aka Boolean) logic - I didn't know its relevance to computing circa 1987.

Dropped out of uni due to utter boredom and didn't lay my hands in anger on a computer till the mid-90s. My girlfriend at the time was doing a masters degree - she had a computer for writing her thesis and emailing and exciting stuff like that. Something when "bing!" for me then. Went to uni and did a couple of modules in computer science - ahah boolean logic - and coincidentally got a job in a publishing company that was doing very interesting things with SGML. (No, not an oxymoron.)

By 1998, I was in the UK, working in IT - thank god for Y2K shenanigans and the lack of bodies to do the grunt work - and here I still am running key tech in a pretty large state govt environment. As they say, access to all kinds of things - such as occupations that suit your mindset and abilities - often depend on "intersectional" forces. So for me, class and gender definitely had a synergistic effect. I'm white, so I can't imagine if you threw in having a skin tone darker than a brown paper bag on top.

Well, actually, I can imagine - there were plenty of bright people I went to school with (a poor, majority non-white school). Some have become teachers, but aside from one notable exception, the only other non-white person in my class now in a STEM career is of East Asian descent. At least now, with tech pervading all levels of schooling, it should be easier for kids of any background to get into IT. Somewhat, at least. And hopefully not through a set of entirely random flukes.


Re: ¯\_(ツ)_/¯

Doing stuff for the greater good is fine, but there's also taking the p---.

And if someone starts off requesting a favour by denigrating my explicitly TEMPORARY solution years later, they can f--- right off.


Re: .MRE Lifespan

It's still going strong in the antipodes, Nestle-branded and all. No idea if the flavour is different to the US version.


There's only one cure for passive-aggressive Space Invader bosses, and that's more passive aggression


Given your evident charming personality and lack of evidence for having done "much worse", I really wonder how it is that people don't listen to you.

Engineers' Laurel and Hardy moment caused British Airways 787 to take an accidental knee


Re: Hang on a moment...

Yup, UI design is not just about computer interfaces.

Without prior knowledge, I would have done exactly the same thing, because t'wrong 'ole has that circle around it making it look even more like a target.

I think it's because it looks like a pivoting part, so it's a surface phlange for the internal pivot, but that very plain hole adjacent does not look functional at all.

So the surface "decoration" should indeed look different and preferably, the holes have different dimensions and/or shapes to prevent accidents happening.

So many engineering accidents have happened due to ambiguous controls, and planes downed multiple times. You think that designers would have a better handle on this kind of thing by now.


Re: When did we stop saying "kneel"?

...and the latter is exactly what the headline is alluding to, in its cutesy phrasing

Ubuntu on a phone, anyone? UBports reaches 18th stable update, but it's still based on 16.04


Yes, wow, just invent any BS to create as many google accounts as you need. I have four... I think.

It's not rocket science.


Re: Funny thing...

... which is after the debacle of the Nokia phone, so that didn't apply in this instance.

Windows 11: What we like and don't like about Microsoft's operating system so far


Re: Can't they just drop the GUI and boot to powershell

Give me 50000x Powershell over VB scripting. Never got to grips with that, Powershell actually makes sense.

Yes, the command syntax is clunky, but it's reasonably consistent. It's a scripting, not programming language - if you want do your programming, fine, do one of the languages that sits on top of .Net.

For me, having had Perl scripting experience back in the day, I found it pretty simple transferring most of that to PS. Now you may commence hosing me about Perl.


I have got ADHD. Don't blame this bs on us.

I personally want a reasonable amount of consistency so I don't spend time hunting around for something for hours, give up, start reading El Reg....

Try placing a pot plant directly above your CRT monitor – it really ties the desk together


I totally agree, I would have cursed at myself as well!

First IT job, first job in the UK, first job in a law firm, first time handling such a large, expensive piece of kit - I was the absolute definition of a PFY.

In my slight defence, if the desktop build guys had been around, I would have scarpered downstairs and asked for assistance. At the very worst, it's possible we could have scavenged a VGA connector off another monitor and replaced it.Thinking back now, I should have tipped them the nod on Monday morning, but things you do when you're young, foolish and guilty...


Ah yes. Not nearly as interesting, but my first encounter with a 20" CRT was in 1998, when some lawyer in the firm I worked at *required* one to be installed and working by the next day (a Saturday).

The thing wasn't delivered till late Friday afternoon, when everyone else had departed for the pub. I managed to lug the thing up to the 14th floor in the lift and then to the lawyer's desk - no trolleys for us desktop support peons. It was no mean feat since my fingertips barely reached the back of the monitor (I'm 5'6" with t-rex arms). Thankfully the lift had hand rails where I could prop the thing while it ascended.

It being a long day and me being desperate for my escape, it took me a few unfortunate minutes to realise that the connector wasn't seating correctly because I had it upside down. I tutted to myself, turned it right way up, reseated it, turned on the power, and was greeted with a vibrant display in lovely shades of green.

So I switched off the power, gingerly pulled off the connector, and to my horror, found I'd mashed one pin completely and two of the others were not looking too great. At that time, a 20" CRT was a good chunk of my annual wage - I think in the order of at least 50%, maybe more - so I felt a bit faint at the sight. I scurried over to our workarea for tools, only to find there was zero in the way of screwdrivers to be found or any other suitably pointy tool. The desktop build guys had all departed after I collected the monitor and I did not have after-hours access to their "workshop".

Necessity being the mother of invention, I located a small knife in the tearoom and with that and a large paper clip, was able to straighten the less-bent pins. The mashed pin took a lot longer to jiggle up, and to my horror, the end of the pin separated completely. Without a pair of needle-nosed pliers, there was no hope that I could get the thing back in.

Once again, another desperate lightbulb moment, and I stuck the pin into the female VGA port on the PC. With some very careful jiggling due to the delicacy of the other previously-bent pins, I eased the connector on. Thankfully I'd managed to get the loose pin into the correct socket on the first go - it was not going to come out again. Even more thankfully, when I switched on the power, the monitor came on in beautiful RGB.

I screwed down the connector with extreme prejudice, left the monitor on with the flying toasters flapping across the screen (this lawyer was bleeding edge with his PC toys on Win 3.11), then beat a hasty retreat to the comforts of the nearest Sam Smith (pub). Blessedly, there were no rumptions when I returned to the office on Monday morning - relief, I was then in the plausible deniability zone. Never heard a peep about any issues with the behemoth for the remainder of the time I worked there.

Hubble, Hubble, toil and trouble: NASA pores over moth-eaten manuals ahead of switch to backup hardware


Re: Sounds Like...

Honestly, chapeau. That's the best ever El Reg riposte and I have seen a few...


Re: Ka-ching! thank you :-)

And I'm sorry, but I do not believe that he NEVER made a mistake on any production IT gear.

Yes, as time goes on, you certainly learn not to make stupid mistakes, and in highly-regulated, relatively static environments, it's much less likely you'll make a mistake, especially one that has a noticeable effect.

I'll even accept no mistakes that cause an outage - certainly possible in said highly-regulated and highly-redundant environments. I personally never had any downtime in Exchange while running it over 15 years, as one complex system I dealt with.

But never, ever any mistakes, from the beginning of his career? I'll have to take that with a big grain of salt, I'm afraid.

IBM insiders say CEO Arvind Krishna downplayed impact of email troubles, asked for a week to sort things out


I literally cannot believe that IBM was running off Notes on someone else's kit. It's bad enough they were using Notes (although understandable since it's their crappy product), but why on earth was it cloudified at all?

One good deed leads to a storm in an Exchange Server


Re: Happened in the Exchange team

Unless it was 20 years ago, no excuse now for setting up an Exchange list with more than a few people in it and not locking down who can send to it. Especially if it's a dynamic distribution list.


Re: Use of private email aside

Well, no, it was making a change in production without telling anyone.

And how was this guy going to test this effectively? The error only got triggered because the destination bounced it too. What if a series of messages he tested with didn't meet the spam criteria at the other end until the 100th message?

Updating in production, like a boss


Re: re: My-Handle

That is literaly how I got into IT.

I was a *copy editor*, then correcting SGML markup, then within a year, I'm running NT domains in a different country and getting to grips with token ring and IBM connectors.



Biting the hand that feeds IT © 1998–2022