Not worried about Adobe subscription...
... terrified of Oracle license audit
1328 publicly visible posts • joined 2 Jun 2015
Daleks have been helping Iran and we will unleash a FURY on them like the world has never before seen! We will not accept anything less than COMPLETE and UNCONDITIONAL surrender. Stavros has my number and can call me at any time to do a DEAL. Thank you for your attention to this matter.
[Pete Hegseth, US Secretary of War] Grok, design me a modern tank
[Grok] Here you go
[PH] Err, that's a Tesla Cybertruck!
[G] Yes, and it has Full Self Driving (coming in 2027)
[PH] Umm, OK, design me a Trump class battleship
[Grok] Here you go
[PH] Err, that's another Tesla Cybertruck ...
[G] Yes, they float too and it has Full Self Driving (coming in 2027)
Inherited a product which was outsourced to one of the major players in India. The Indian devs were expected to write 200 lines of code per day, or they were penalised. What we got was not effective, succinct code but *lots* and *lots* of rubbish, incoherent code. It was the worst code I have ever seen in 30 years of professional development but at least the devs got their bonus.
Worked on an obscure printing bug 20+ years ago. I managed to burn through a roll and a half of large format paper, at £120/roll. After 3 weeks of solid effort, and learning more about the Windows printing subsystem than I ever wanted to, the fix was just 2 characters in the code. That is less than a character/week!
Worked on a project where everything had to be documented. Typical example was:
/// <summary>
/// Gets or sets the SetPoint
/// </summary>
public int SetPoint ( get; set; }
* what is the range of allowable values?
* what happens if you try and set it to a value outside the allowable range?
* what is the default value?
Turned out the only real requirement was documentation had to be present. It didn't have to be correct, relevant or useful.
There was an electrical engineer in the year above me at Uni. He was super smart but a mechanical klutz. He was part of a joint electrical-mechanical engineering project developing an electric vehicle. During one session, he managed to drop a spanner directly across the battery terminals, shorting everything and melting the spanner! He really put the 'spark' into 'sparky'! Once in industry, the rumour was that he was chaperoned on-site by an electrician, to make sure he didn't electrocute himself or bring down the whole plant.
Not sure why the down votes because I've seen this in engineering and software. Each company thinks what they are doing is *so* unique that none of the existing solutions could possibly work and they must have a custom solution, just for them. The competitive advantage of a totally customised solution is always grossly overestimated. In all cases, the company would be better off accepting a COTS (Commodity Off The Shelf) solution and accepting any limitations.
[AI Overview - apologies]
The "Sukarno videotape" refers to a Cold War-era incident in the late 1950s or early 1960s, where intelligence agencies—specifically the KGB (Soviet Union) and allegedly the CIA (United States)—attempted to blackmail Indonesia's first president, Sukarno, with recorded sexual encounters.
Key Details of the Incident:
The Trap:
During a visit to Moscow, the KGB allegedly bugged a hotel room and recorded Sukarno with women, intending to use the footage to force him into compliance.
The Reaction:
Rather than being intimidated, Sukarno reportedly laughed at the attempt and requested multiple copies of the tapes, jokingly suggesting they be distributed in Indonesia to show his "manly" prowess.
CIA Involvement:
The CIA also allegedly considered, or attempted, similar tactics to damage his reputation in the conservative, predominantly Muslim nation.
Outcome:
The blackmail attempt failed completely to damage his image, and in some narratives, actually backfired on the intelligence agencies.
Some reports indicate that the KGB's attempt was the primary incident, while others suggest the CIA was also involved in creating, or planning to create, such a film.
https://www.cia.gov/readingroom/docs/CIA-RDP88-01365R000300100003-3.pdf
Worked on a software product which the product manager, in his infinite wisdom, decided to call 'Xchange'. Everybody pointed out the name was confusingly similar to a certain Microsoft product. He was adamant that there would be no problem for our customers. I suggested all the devs chip in a fiver to buy him a clue.
Worked on a new product for quite a while at a software company. Marketing came up with a name for the product, which was announced to big fanfare. All of us devs immediately googled the name and, 2 seconds later, found an IBM product with exactly the same name! Unfortunately, we were bought by IBM a year later who changed the name.
Can just imagine 'Payment Day':
Hosting:
* 'entertainment' consisted of a 'moon walk' - boring
* hotel is miles from anywhere
* evening meal was same as breakfast
* Elon Musk kept banging on 'my Mars hotel is so much better'
Cleanliness:
* room had not been cleaned and was covered in regolith
* bed sheets had not been washed since hotel opened
* hairs on bed from previous guests
Facilities:
* room should really have an ensuite
* room decor very bland
* no privacy in communal bathroom
* no tea or coffee making equipment in room
* room very small for price
* internet very expensive
* no mobile phone reception
* no car park
Sleep quality:
* walls paper thin
* could not sleep due to science experiments going on all night
* air mattress kept deflating
Breakfast:
* freeze dried and not local produce
* should have cooked breakfast option
* milk was UHT and not fresh
Would you stay here again:
* no
Price: $10M USD
Payment: $1M USD (an under payment of $9M USD)
https://en.wikipedia.org/wiki/Four_in_a_Bed