the first scrub was a sensor issue
No. The sensor issue was the final nail in the coffin for the launch attempt. There were other issues too.
3274 publicly visible posts • joined 30 Jan 2010
Those of us who have been in IT for more than a couple of years will remain the pain of, DB9, DB25, centronics, various SCSI types, PS2 Keyboard & Mouse, etc. The holy grain of a single connector (USB) to replace them all seemed impossible. We briefly had it: Then the idiots forgot what the "U" meant and we're now back at square one.
I used to do a lot more with awk in the past but nowadays Python tends to be my go-to scripting language.
Is Python as fast or as efficient as tool X? Maybe not. But I rarely need absolute performance and, being a jack-of-all-trades, keeping a reasonable understanding of a small number of tools is the way to a simpler life.
I’m a hobbyist Java programmer & I’ve been playing with Java for 10-15 years. Even I know that standard Java serialization is dangerous.
If full-time Java programmers are using standard Java serialization, they really need to go back to school.
This problem of object serialization being unsafe is not unique to Java. Other languages offer similar features and all give the same dire warnings: Don’t use it if you can’t trust the input.
What’s one of the standard security warnings for programmers? Never trust user supplied input.
The single biggest problem with nuclear is the waste. Not the spend fuel rods but all the low-level radioactive waste produced over the lifetime of the plant. What's our current plan for this stuff? Bury it in concrete and hope no-one disturbs it for the next few centurys. Has no-one noticed the whole "green" revolution happening and the three Rs? (Reduce, reuse, recycle) Nothing there about "bury it in the ground".
x86 has killed almost every traditional RISC server/workstation processor out there regardless of how optimized the software was
Did x86 win out because it was the better processor, or did it win out due to little software being available for other processors?
e.g. Windows NT was available for a variety of CPUs* yet little end user software was available for it.
ARM is only now gaining ground as it started out in a niche (embedded) that x86 couldn't compete in.
* I heard the other day that NT was originally written on something other than x86 then ported to x86 to prove how portable NT was.
It's been discussed on El Reg forums several times before, but modern RISC-like processors (e.g ARM, MIPS, etc) are also microcoded.
There isn't much distinction between "CISC" & "RISC" processors nowadays. Both processor camps have looked over the fence and borrowed ideas from each other.
I awarded a contract to a company with an explicit start and end date. After the end date they sent me an invoice for the next year. I said I hadn't ordered renewal and I wasn't going to pay. They claimed I hadn't actually cancelled the contract and so they auto-renewed it without any contract amendment by me.
I suggested they take me to court to claim their invoice. They never did.
They are just bullys: Like any bully, stand up to them and they soon back down.
Some of these perhaps?
arstechnica.com/science/2022/07/us-regulators-will-certify-first-small-nuclear-reactor-design/
Whilst the web has enabled this kind of manipulation of reviews to explode in size, it's not new.
Back in the 80s, there were all sorts of allegations that the advertising department would lean on the editor to write favourible articles so they could sell more advertising space to the advertiser.
Some (slightly) ethical rags put up chinese walls between the editorial & commercial sides of their business to try to fend these acusations off.
The changes to the Free tier might not be entirely welcome and could result in users having to change their workflow to deal with the 90-day rule regardless of all the other features now on offer
If you don't like the changes to the free tier, contact your account manager and ask for your money back.
Oh - you didn't actually pay for anything? Then stop complaining.
I was looking for a driver for one, and typed zip.com into the browser. Oops.
IIRC it was a gay dating site. Nothing there now.
In the days before adult filters on search engines, I'd often search for something for work and end up and adult websites. I thought I knew a lot of porn slang: Clearly I was way more naive than I thought!
To me, the biggest take away is that they agree what the software is supposed to do from the outset, before they even think of writing code. How many of us have been involved with software projects where the specs keep on changing? If you can have agreed specs, it makes it so much easier.
(The "don't blame the person, blame the process" culture is important too: It allows everyone to learn from mistakes)
Assuming you can formally prove the software*, all that does is show that the software matches the specifications. Not that the specifications are right in the first place.
[*] Formally proving software isn't easy. It's not as if, in your IDE, you go Tools -> Prove and get a simple box back saying "Proved Correct"