"Perhaps you mean horde."
I think hoards was better. After all, hoards are often buried or at least hidden out of the way.
40432 publicly visible posts • joined 16 Jun 2014
"All these analyses and methodologies seem to start with the assumption that "software" consists of FaceBook and Enterprise CRM systems."
I'm not sure an Enterprise CRM system would be a good place to start either. First you need a good RDBMS. The good news is that at least you don't have to be Agile about developing that; you can buy it in. Then you need a database schema to sit on it. And once you have that in production you'd better have it right because once it starts to accumulate data it'll be a pig to do a reorg. If you're clever and take the time beforehand you can make your schema general enough and the application configurable enough to set it up for all sorts of different enterprises but ISTM that that's the opposite of Agile.
"For me, a 2009 talk by Andrew Clay Shafer codified this thinking right around the time it was codified into DevOps. To a room full of agile lords and ladies, he proposed something wild and crazy: what if you were responsible for how your code ran in production?"
We were doing this over 20 years earlier. I've previously supposed that we were doing DevOps ahead of time. But...
"Systems will go down catastrophically, but you can't simply give up, and punishing people just takes you back to the overly cautious state where software is released infrequently. So, as described by the Google SRE book, you instead celebrate failure"
Thanks for explaining to me that we weren't doing DevOps after all. They didn't go down catastrophically so we didn't have failures to celebrate, only successes to lament.
As a database guy to some extent I've always been puzzled about this salami slicing thing. Do you set up the database by introducing a table at a time or do you set up all the tables empty for the first release and then add the columns one at a time for each subsequent release? And how many release cycles do you expect to have before the developers get anything to develop against. At least as the data volume grows with use each reorg following each sprint's schema change will get longer and longer so eventually there'll be really good failures to celebrate.
Cynical? Moi?
I'm not sure I see the use case for this machine readable data extract. If I might well want to stop using a service. I might also want to use another. The two are not necessarily connected. If they're not then I need to input sufficient data into the new service. I'd also want the old service to delete all such data as the GDPR says it must if I ask. But if I were to ask for the data from the old service to save me from inputting data into the new I'd likely find that the formats and maybe content differ. I'd end up either doing the input manually as I'd have to do in other circumstances or I'd have to convert it if possible but although most of us here could do that the bulk of people wouldn't and in any case we'd probably find the job more trouble than it's worth.
And that "if possible" phrase covers a multitude of possible problems. Just take addresses. Different businesses have different ideas as to how many lines go into an address and how long they are, what the fields are* etc. I have memories of trying to cram reasonable addresses from the order processing system into the unreasonably short fields of the accounts system; the accounts staff had the same problem wrapping individual address lines over multiple lines in the accounts.
* Why do so many address formats assume I live in a city? Apart from just visiting I haven't lived in a city since the early '70s.
"Being able to make up new jargon whenever you like is one of the finest unique features of the English language."
My distant memory of a year of Science German in the 6th form says that not only can German do this but it can do it with twice as many letters and probably more with a bit of effort.
"That is to say the current design looks reasonably pretty"
Pretty dreadful would be my description. it was obviously designed by someone who'd just bought a load of whitespace going cheap and wanted a punter to unload it to. A browser really ought not have to go full screen to display a small handful of fields.
I'm not in the least surprised if they ask people to tweet bank details. This is the same crowd that sends out spam looking exactly like phishing spam - says Coop bank in From and Reply to but originates elswhere, asks customers to click on in-spam links which claim to go to their own domain but which resolve to an IP address belonging to the same non-bank domain as the spammer. IOW they're training their customers to be phished. Anyone with the mentality to do this clearly has such a deep ignorance of IT security that they're likely to get phished themselves.
TL;DR if this was down to some stupid pratt in the bank getting pwned I wouldn't be in the least surprised.
"Since it's easier to repeat the previous success than try something new, you end up with everything looking like clones."
You've just described the process which ensures that if there's no product today that meets a particular demand there won't be one tomorrow because it will be dubbed "niche", not because anyone knows it's niche but because, without an existing product, it's niche by definition.
The polite summary of this is that it's a self reinforcing feedback loop. The alternative is that marketing spends all its time looking up its own arse and finding the obvious.
That's why the "no demand" joke rings true with so many people.
"I'm also confused when people need to buy a laptop for work, and complain about the cost. If it's an essential tool, then it's a cost you factor into your fees, and assuming your accountant isn't an idiot, it should be a tax write off in some form or another. At the very least you should get the VAT (or local equivalent) back."
I agree in principle although, in fact, for someone who isn't VAT registered, VAT is the one thing they won't get back.
But what the OP wanted was a netbook. That was a genuine product but it threatened MS because it was sold without Windows*. MS then made a cheap licence for Windows available with the stipulation that it wasn't powerful enough to challenge the regular laptops running full price Windows. This effectively stopped the products from being as effective as they might although, as I said, with Linux they were powerful enough.
There may also be an element of snobbery; "it's a chicklet keyboard". Of course it is at that size and price. So what? You can type on it.
*It's also possible that the market couldn't then, comprehend a computer that didn't have Windows. That's no longer the case.
"14-inch laptops have screens that are too small for more than one working window"
The netbook size is usually about 11". I have one running Linux. I use it for work in libraries or archives where I want something small for data gathering. I normally run text-based applications in a 80x25 window which leaves room to spare but then I did used to use an Osborne luggable as a terminal back in the day. If I wanted to use multiple full screen applications I'd simply use multiple workspaces. That comes naturally to a long-term Linux user and I understand Windows has caught up with that so it's not really a problem. As the OP said Unix he might not even be intending to use GUI - another trick that Unix/Linux users are used to is having several command line sessions running and flipping between them with Alt/F1, Alt/F2 etc. You're not going to use them for compute-intensive stuff but if you adapt to flipping between several single application workspaces or terminal sessions they're quite functional. Mine is running an Informix RDBMS to power the data gathering applications.
"your desire is extremely niche, and the laptop market is very much mass marketed. ... The laptop and consumer desktop market is designed around price points, not features."
Designed by whom? By marketing of course. Tell me again how marketing, with their deep understanding of customers' desires, have created these soar-away sales figures.
"I predict much wailing and gnashing of teeth in recruitment, as soon as a recruiter sends out a job spec to half the internet and lots of legally switched on types notice that they didn't give consent under GDPR and fire up the lawyers."
And well deserved. One could spend time customising a screed for one particular gig only to have the pimp send it out for something quite different. I'm sure this must occasionally cost perople gigs they might otherwise have got so real money's involved.
"we had to call in the Leitz engineer to lock the lenses in place"
Back then even the sales guys were techies. We had one new microscope, actually the new top-of-the-range job, as a loaner to try to sell it to us. The objectives weren't par-focal. One was one of the 0.95 NA Plan Apo dry lenses so that couldn't be touched, but when the salesman rolled up and we told him he took the 10x out, adjusted the internal components to fix it and locked them in place with a smidge of SWMBO's nail varnish.
"to stop the students nicking them. And these were medical students - supposedly the creme de la creme."
I was in Halls with medical students - it brought an air of reality to any subsequent dealings with the profession. The Leitz salesman left a sample of a new Fluroite 0.90NA with us on approval one time which I've still got somewhere. It wasn't a patch on the Plan Apos. They didn't want it back, I think it never went into production.
A fair chunk of my working life was spent looking down Leitz microscopes. Beautiful pieces of kit.
It sounds like a very inexperienced microscopist. The image in the eyepiece is upside down already.
I used to help out as a demonstrator for a pollen analysis course (not my job but there weren't enough of the regular staff with the knowledge). This was the first time in about 2 1/2 years into a degree course that students had had to set up a microscope for maximum resolution; at least it felt like that. So they were shown how to set up the Kohler illumination etc. You could guarantee that the first thing to do when called over to help with an identification was to set the microscope up properly, even if you'd done that only a few minutes earlier.
" When you have a preferred orientation in mind and the imaged object seems to have a different idea in mind, rotating the camera so that all images are oriented the same way is often the best solution."
A microscope normally inverts the image compared. This means that when you move the specimen on the stage the image moves in the opposite direction. It's not difficult to get used to this, especially when using a mechanical stage. (I'm surprised the microscopist in the story had a problem with this.)
Cue using a microfiche reader. The lens is rotatable and has the same effect as rotating the camera in the story. If you put the fiche in the wrong way round so the text appears upside down you can just rotate the lens but then you have to move the fiche in the opposite direction to the way you want to move the image. Again, it's not difficult to adapt, at least I never found it so. But if the fiche was photographed to the writing is sideways on you have to rotate the lens a quarter turn; that fixes the image orientation but then sliding the fiche on one axis moves the image in the same direction whilst sliding it on the other axis moves it in the opposite direction.
"the rest of the world has nothing to do with American case law"
It wouldn't necessarily be binding on other jurisdictions but it could still be put before a judge as a model of how to handle such a case. If the judge accepted it that might then set a precedent elsewhere.
"Not that it will be of course. Sane results like this directly undermine their attempts to wage economic espionage on a cowed and fearful populace."
The way case law works suggests that this will be cited in the future, at least in the US. The great pity is that it's less likely to be useful in the UK.
" Every once in awhile one of sleeping non-entities in the courts wakes up enough to veto the latest grab but goes back to sleep soon after."
Have you spent much or, indeed, any time actually watching real judges at work in courts?
Disclaimer - my experience of this excludes US courts.
"I think people are missing some of the details in my original post here."
And you are missing the point: company rules provide for disciplinary action within the company with the ultimate sanction of a quick journey to the outside of the front door but no further.
"For a long time similar rules applied in 'normal' businesses,"
The rules might well apply. The sanctions available to a 'normal' business would not include recourse to the Official Secrets Act unless the business were carrying out work for HMG in which case, depending on the work, the Act could apply.
"Since each of those companies very clearly stated that such activity was forbidden and a disciplinary offence, I presume those managers/Execs in the US offices will now go to jail?"
It depends. Clearly they could be disciplined by the company but that isn't a criminal offence. If, however, the PA used the password to commit fraud then the PA could go to jail and possibly the manager as an accessory.
There's a very simply difference here: company rules are not the subject of criminal law, fraud is.
If you swap the battery do you swap in single use alkaline cells and chuck out the old one or do you recharge it? If you recharge it how do you do that without imposing the same load on the supply network as recharging in-vehicle?
Simply swapping batteries only solves part of the problem and quite possibly introduces new ones.