Re: I'd like to see more
"Are they really good at spelling bees?"
And understanding their origins?
42414 publicly visible posts • joined 16 Jun 2014
"Of course it requires also being fee from the tyranny of a homeowners association or a city which mandates a crisp green lawn."
Call it a flower bed. Put a small square of Astroturf in the middle if someone insists on there being a lawn in the garden.
The "norm" for a lawn is it to be uniform, green, rye grass only and nothing will stop your average suburbia dweller splashing a bottle of glyphosphate a week on it to keep it this way.
Glyphosate is a non-selective. Splashing a bottle of it a week will simply result in a wizened brown mat of ex-rye grass.
"PHB's see all training as a cost, and lump it all together."
Not entirely. Management training is fine. It might be completely irrelevant to the tech job but it becomes compulsory. If someone's handling their tech job well they must be promoted to management so they can be replaced by someone who can't do the job as well. The fact that the tech abilities are at best orthogonal to management abilities is irrelevant.
"Mine went this time last year."
This is the time to g freelance. You can then charge an appropriate fee for sorting out the problems they brought on themselves. For IR35 reasons, of course, it might be better to sort out problems that other people brought on themselves in like manner.
"In order to hit a roughly competitive pay grade (the public sector tends to pay a bit less, but to get it in the same ballpark) HR will hack technical job descriptions to make them look like management posts."
I had roughly this sort of experience. In order to make a competitive offer (e.g. they couldn't match the company care) they nominated the post as management. Fair enough, it involved systems management. One of the amusing aspects was that a little later the grade was given company cars. However HR eventually started having problems with the notion that what was essentially a technical post didn't have much people management content.
Then you get the idiots who say "must have 10 years experience in docker"
I suspect that this might stem from their ISO 9000 implementation specifying such nonsense. Whoever wrote the quality manual is patting themselves on the back saying "we only employ the highest quality staff" when it translates to "we only employ liars".
I do, however, habitually suspect ISO 9000 as being responsible for a lot of bad management.
"When I was a kid in Ireland (Dublin) we hollowed out turnips."
Nowadays everyone seems to insist that these should be called swedes and it's the cricket ball sized things that are turnips. But who'd make a turnip lantern out of those little runts.
"We also had mashed potato with something green in it"
Sounds like champ.
"I was never that sure what a 4GL language/system was"
I can only speak from experience with Informix 4GL. Essentially a structured procedural language (but why retain "LET" as a keyword for assignment statements) but also incorporated SQL, form handling and report handling. The form and report handling incorporated event handling ("ON" as a keyword).
Essentially it added higher-level abstractions (databases, menus and reports) to what previous languages had had just as 3rd generation languages did in comparison to assembler and as assembler did in comparison to machine code.
I never quite escaped the feeling that the original non-procedural Informix applications, Perform and Ace (a report writer) were more truly what was toted about as 4GLs at the time but, within its restrictions, it was more practical - serious work with Perform & Ace required linking C code into their interpreters.
The OO approach to incorporating SQL has been very different, as far as I've experienced it. There would be some object which had a string component into which one would build the SQL with string operations rather than directly writing it in the source as a statement in its own right. This seemed clumsy. It was no surprise that New Era, Informix's own attempt at introducing OO into 4GL which did just this was a failure. However, as time went on it became more practical to take Informix 4GL's approach of preparing a named statement from a string and then executing it as more practical than the original for many purposes and still less OTT than the OO approach.
What we seem to have ended up with, for the most part, is 3rd generation procedural languages with OO features added. They don't really represent a higher level of abstraction and this, I think, is a failure.
"Deep in the mists of time, some 25 to 30 years ago, there was a belief that software production would change radically."
I'm glad you went on to explain which particular belief you were thinking of. There've been so many software that writes itself fads. If one actually works it'll take everyone with real experience by surprise.
"If you do this, it's easy to hedge against forgetfulness for at least 9 years"
And therein lies the problem. It just increases the probability of forgetfulness in the future. If you persist in getting rid of everyone who knows how things get done there's damn-all chance that when the need to renew comes around there's anyone left who knows it needs to be renewed. And if the company has in the meantime screwed up its payments system if, by any chance, someone does know about renewals, the payment might not go through in time anyway.
"this particular goose is probably paying most of its taxes at special Republic of Ireland no-local-profits rates"
Its US employees are probably paying taxes at standard US rates, however, and spending their after-tax income moslty buying goods and services in the US.
And the company will be buying goods and services in the US for its own use. Why do you think Ireland can afford to set its corporation tax so low?
If a US company eg. Enron / Bernie Madoff / Lehman Bros was allowed to work only with cloud data held remotely then they could tell any US agency with a US warrant or a freedom of information to get lost. go through the established procedures to obtain a warrant in the jurisdiction in which the data is held.
FTFY
Why is is that this sort of thing keeps coming up in any thread in this general area?
"You can't have just the same skill-set at 50-60, that a 20-year old does. He'll not move faster, and think faster, but he'll also learn new concepts much faster."
New concepts? All too often old ones with a new terminology. And when they're not retreads they're often things along the lines of "I could have done with that 5 years ago" and grabbed with both hands because you understand why.
"Microsoft is giving up on smartphones, but loves the idea of ARM-powered laptops running Windows 10."
It also loved the idea of smartphones and of ARM-powered Surfaces.
The problem with BigCos (Microsoft is far from alone in this) is that if something doesn't take off quickly enough (and "enough" seems to shrink these days) or its champion leaves the business then the product gets dumped along with all the customers and secondary vendors that had bought into it. Ironically this should make potential customers more wary so that it becomes harder to get something to take off. In reality Barnum applies.
"Closed providers build proprietary protocols over an open port....
These days, phones bypass the corporate firewalls so we could use any protocol we fancy."
And so we do things the convenient way. Once again convenience tramples security. More and more stuff gets done in the browser - more and more ways to deliver malware.
"a lot of these closed ecosystems are short-term fads so their longevity isn't an issue."
It depends what's in them. If it's every idle thought that wafted through idle heads then no problem. If it's somebody's only collection of photographs of their deceased parents (yes, I know) then it's a bigger problem. If it's a long piece of collective research then it's real pissing-off time.
Anyone remember geocities?
There may be merit in paying for what you get.
"Much more sensible than installing backdoors."
It sounds more like looking for backdoors that weren't intended, keeping the information from the vendor but then sharing the information out among themselves so that it'll leak out further still. Remind me again, how did we come to have Wannacry?
How does this differ from black hat hacking?
"Or maybe the chance to strip out the snooping software and just run a few trusted applications?"
That's the question. It's one thing being able to move over into "real" Linux when you want an app that's not on Android. Can you also do that when you don't want an app that is on Android?
if the police claim not to know how much money they took, they can't be even forced to "give it back"
OTOH they can't prove they didn't take anything that was claimed. Consider a the possibility of a class action on behalf of all the citizens of New your who each had $1m improperly seized from them...
Oh, it's been repaired. That was quick.
"What MS are complaining about is a natural facet of the open source development and release process, namely the (public) master source code repository will be updated before a (public) build containing the fixes is made available."
The developer will have built an executable before updating the main git repository. That could be released as the production version but on the whole most people might not be comfortable with that. They could, however, have a staging repository which is, in effect, their main one, build the release version from that, release it and then bring the public repository into line.