Re: Changes to the Highway Code
When I learnt to ride a bike the Highway Code said to ride just far enough out into the road to avoid drain covers. 1 1/2 feet would have been the maximum, not the minimum.
42272 publicly visible posts • joined 16 Jun 2014
I live in an area where we have several lanes with no footpaths. It's also a popular sight-seeing area so we frequently have walkers. As the lanes have quite a lot of bends, one has a couple of right-angled bends made blind because of retaining walls on the inside. The sensible thing to do here is ignore the facing the traffic bit - keep on the outside of every bend where you can be seen by oncoming traffic. On the whole people seem to walk at random. As some of them will have driven here you'd think they'd have a driver's perspective on it but it doesn't really seem to work. Given that I've seen one idiot park up on the short stretch between a cross-roads and the worst of the blind bends maybe it's not too surprising.
You should have had an older model. They don't have any dangerous road safety features.
SWMBO's little Suzuki doesn't actually jam on brakes, it just flashes warnings which is annoying enough. It's done that to me a couple of times when braking would have been dangerous and she says it complains when she pulls out to pass parked cars.
If I ever get a new car I hope the consequences of this rubbish have made themselves clear enough for such features to be banned.
Also running Kermit?
For a while I ended up with an Osborne or similar luggable as an office terminal. I'm not sure it would have been as generous as a 7" screen but with MSDOS and Kermit as a terminal emulator it did the job. It might be the reason why to this day I find a 6" terminal window more than adequate for the command-line.
The situation with a UPS is you have to assume you're going to need all of it starting a second from now.
As to your fleet example, a major blackout might strike about 3 in the morning and only affect the area round the depot. That doesn't mean your customers will also be affected. You're still going to want the fleet fully charged. Your sales and customer service departments aren't going to be happy if the bean-counters did a deal without telling them.
"It just seemed to keep getting in my way when I wanted to do stuff."
That's the converse of my experience. I can customise it to work and look as consistently as possible from one generation to the next. It does what's needed when its needed and mostly keeps out of the way otherwise.
There's one thing I wish they'd reinstate from version 3; the ability to set the panel unhide trigger to be a corner rather than the entire edge. Rationale: a typical maximised application is likely to have stuff at the bottom of the window that needs access even if it's only the scroll bar down button and taking the mouse down to that bounces the screen bottom panel back up to cover that critical bit of the screen for a couple of seconds. Limiting the unhide to the bottom left worked well.
After getting their Bitcoin tracing skills up to speed will the FBI work back further to trace the history of the loot before it was deposited in the exchange? It would be a shame to hand it all back if they can't be sure it was legit before it was nicked by these two.
Cynical? Moi?
Or a cloud provider in any other country where a search warrant could be obtained.
It just goes to show that law enforcement can get results by simply using the age-old due process.
And it also goes to show that somebody else's computer you don't control is somebody else's computer you don't control.
The N Ireland situation was always going to be a problem.
It's very simple to state: the Good Friday agreement was predicated in N Ireland being in the EU (or possibly the Republic being out of it) so as to avoid a hard border. The UK is the United Kingdom or Great Britain and Northern Ireland is predicated in N Ireland. Having the UK out of the EU, NI being in it and NI also being in the UK is a logical contradiction.
The Protocol was the Brexiteers' fiction to try to pretend there wasn't a problem It would never stand up to reality. And let's not beat about the bush - it was the direct and unavoidable consequence of Brexit.
It's going to continue to be a problem unless the UK gets broken up and that would be an even bigger problem.
What you describe is probably a people problem. The problem may lie with the wrong people administering the systems. Equally it might lie with the people holding the purse strings and your sysadmins & DBAs may have equivalent but different problems in getting the sign-offs to provide you with your test server. But ultimately you're using somebody else's computer as a sticking plaster to cover the self-inflicted wounds of a dysfunctional company.
Ever since W95 we have had Maximise and Close buttons next to each other. That has carried over to become the default in KDE. It's not such a problem now because it's normal to throw up a dialog if close has been hit with unsaved data. Back then it was unlikely that any legacy application, a.e. just about everything, would make such a check because accidentally hitting close was so unlikely.
For those unfamiliar with GUIs pre-95 close was on the system menu, on the button at the opposite end of the title bar to the minimise & maximise buttons.
It's one thing automating that in-house. When a supplier does that it starts verging on looking creepy and in general the more security concious of us object. Having the user run diagnostics is one way round it. The other is to dump the information and pop up a dialog for the user to email it, showing the user exactly what's in the email so they can check.
When I wor nobbut a lad I spent school holidays working in a worsted mill. In practice anyone in the workflow to produce a piece of cloth was inspecting the previous stage's work because if it wasn't right they couldn't do their own job properly. That was what enabled the mills to produce a high quality produce.
Applying that principle to the situation you describe I'd say it was the programmer's job to question the spec otherwise the product is likely to be industry standard crap.
In practice pretty well any programming work I did was under what I suppose is now an extinct title of "analyst programmer". On a rare occasion where someone had delivered an alleged specification I spent quite a while chasing him to clarify ambiguities.