Which is why...
I've been running DNS over HTTPS for about six months...
814 posts • joined 4 Sep 2009
You know what, that doesn't sound like a bad idea at all.
If it really could be designed as a 'relief' valve for flooding areas, then:
* Provides potential relief in times of extreme flood
* Provides low carbon transport alternative for goods
* Provides additional opportunities for leisure pursuits
* Creates jobs, especially during the construction phase
* The downside? The NIMBYs that would want it anywhere near them (though if it could be used to relieve flooding they could possibly be persuaded).
* We can't do anything cheaply any more. It would take a barrage of consultants 10 years just to conclude that "actually, this could potentially have the potential for potentially being quite a good idea. Potentially.". That's before construction even starts.
Yes. This is the scenario that I recognise!
The problems are pretty much exactly as you have described them:
1) The client often does not have a complete picture of all of their own requirements. In fairness, in large projects (e.g. ERP) that would be used by stakeholders right across the organisation, trying to assemble the right collection of knowledgeable stakeholders is like trying to herd cats. Imagine a company that runs it's engineering from Aberdeen, London, Stavanger, and Oslo, and its HR and purchasing from Delhi (like the company I used to work for).
2) The requirements, become 'written in stone' even when contradicting/impossible requirements are pointed out.
Agile *can* help in the user requirements elicitation, but you still need to be engaged with the correct stakeholders, otherwise what you get back is a load of assumptions and guesses in some areas, and solid information in other areas. It's a nightmare.
I would add Forth to that list due to its ability to extend the language using itself.
But yeah, your point still stands. Forth is so niche it's not on anyone's radar.
> Doing it properly means no buffer overflows
All a side-effect of C not having counted strings. It's the biggest cause of buffer overflows in the history of the language. In order to know if my buffer is big enough to accomodate a concatenation of two strings I first have to walk the entire length of those two strings looking for a zero. Ridiculous.
It's like crack for system architects, too.
A certain regional water company has relatively recently started shoving all of its telemetry and SCADA data into Azure data lakes. All of it. Terabytes per year. Now, Azure data lakes are very cheap - it doesn't cost much for the data to just sit there, so fair enough. However, when the time comes to do something with that data, that's when they've got you by the shorties.
There will be so much data that it will need to be partitioned in some way before you have at it with something like Hadoop (or whatever the MS equivalent is), which will mean:
* An IT project in its own right within the organisation;
* Hiring of big data analysts/specialists;
* Hadoop/Map Reduce specialists;
* Additonal cloud resources the churn the data, partition it, validate it.
And then, when you realise how much it's going to cost you also realise that they've got all your data. I mean seriously, what are you going to do? Ask them to post it to you on a USB stick?
I thought the idea of cloud was you hired the infrastructure for the time you needed it, churned, got your results, and span it down. Just like it was in the 60s and 70s. But modern IT departments seem to be falling into the trap of 'the cloud' - presumably because it is easy to use, and can be very cost effective. But you need to strictly control what you're using it for, and so far I'm not seeing that. Therby it becomes a false economy; they're merely shifting the costs into a different column.
It would be useful if user data AND apps could be portably moved around, but you can't really do that in Linux/Unix because when you install something, the various files that make up the application are sprayed all over the hard disk. As a relative Linux newbie it still pisses me off. I have to go hunting for config files, and the log files are somewhere else, and the binaries are somewhere else. Bah. I suppose it comes from the earliest days of Unix?
...Siemens S7 TIA (PLC programming system). Other than that, I've moved over to Linux entirely. I booted my Windows box just last night (it's an old Toshiba Tecra 32 bit laptop). I partioned the SSD in half, and installed Lubuntu next to Windows 7. It's like a new machine.
Just who are these 'future settlers'? Have they been consulted. Have they volunteered to go an live on a hostile lump of rock some ~230,000 miles away from their home planet, or have they been 'volunteered' by someone else?
You wouldn't get me up there for all the tea in China! And that's a lot of tea!
Oh, I'd managed to forget about that.
I had to learn how to use Crystal reports to get reports out of a SCADA system. On site. In the Abu Shabi desert. With only the help files.
The problem was: Once the word got out that "knew crystal reports" I was instantly elevated to Guru status and got given every bit of fucking CR work going.
Now I need to go and curl up in a ball under the desk for a while!
Hey thank you very much for that! Just checked it out on Argos. My 9 year old son has taken to using his mums laptop (he's not allowed to use mine!) for Roblox and all that other nonsense. It's his 10th birthday in March. Guess what he's getting for his birthday!
Have a beer! -->
Seems that Netbooks like we had around 8 years are just as powerful as a Pi, and you could carry them around no problem. Why they didn't take I don't know. I still have my Acer Aspire 1, it's nearly ten years old. It's showing its age with modern OS, but runs the lightweight Linux builds just fine. Surely something with the same form factor would be welcome today?
30 Year Boeing Quality Manager Says "Fly Something Else", Refuses To Fly On 787 Dreamliner
"John Barnett was a quality manager for Boeing for 30 years before he was transferred to South Carolina to work on the 787, according to Big Think.
It was there that a new leadership team who had previously worked on Boeing's military projects began overseeing work on the commercial airliner.
Barnett says that team lowered safety standards significantly. He stated: "They started pressuring us to not document defects, to work outside the procedures, to allow defective material to be installed without being corrected. They started bypassing procedures and not maintaining configurement control of airplanes, not maintaining control of non-conforming parts — they just wanted to get the planes pushed out the door and make the cash register ring."
They're never going to write another operating system. They are going to slowly migrate over to Linux. Windows is not where their money is anymore. It takes a shit-ton of human resources to support it and fix it, on an on-going, never-ending basis. I have a friend that is a product evangelist at Redmond, and even he thinks Windows is on its way out.
The boundary between Linux and Windows will slowly blur in the coming years, I believe.
As a fairly recent convert to Linux (Mint), I'm with you on this. The OP mentioned a 'Linux fuck fest' - I know what he means. It certainly *used* to be like that. I remember my first dabble with Linux in the late 90s/early noughties and I was put off by the level of vitriol and downright nastiness on the 'support' forums.
However, it is not like that today. If you check out the Linux Mint forums (for example) you'll find it's a very friendly place.
I generally find that, in the event of a 'problem' (i.e. *me* not knowing how to do something) somebody has already asked the question and a solution has been provided. In these cases, I don't even need to post anything; I can just passively read the information and adopt the solution.
"That design violated basic principles of redundancy for generations of Boeing engineers, and the company apparently never tested to see how the software would respond, Lemme said. “It was a stunning fail,” he said. “A lot of people should have thought of this problem – not one person – and asked about it.”
Seems like the blame has to fall squarely on the shoulders of Boeing. The Indian subcontractors are free to submit poorly engineered software and systems design all day long. It's the REVIEW process that is an essential part of any safety-critical design process. I have not worked in avionics, but I have worked in IEC61508 projects, and it's the same thing there. It's about engineering rigour, and being able to DEMONSTRATE, in a court of law if so required, that appropriate rigour was applied at all stages of the design, from initial requirements gathering to integration testing.
This is a slam-dunk. People should be going to jail. It's an American company though, so nobody will go to jail.
You took the words out of my mouth. Have an up-vote.
I was left thinking that, for all it's issues, Java is still a good bet if you're looking for longevity. I have a ten year old Java application (nothing fancy, a CPU emulator for an old CPU that we had to get to grips with) that runs with a Swing GUI that still works perfectly on any platform. Windows, Linux, Mac. It just works. I can't remember any issues with it. I ran it recently (just to see if it still works) on a Linux Mint build and it was perfect. The binary is a little more than 10 years old.
I was thinking the same thing while reading the article. Have a look at the accounts that they file in the EU, determine their annual income for the particular market segment that they are in violation of, and fine them that much. Annually. Until they stop being total twats.
Biting the hand that feeds IT © 1998–2020