- While original IBM PCs indeed may not have had HDDs, it did become a standard for PC XT, as early as 1983. Only the cheapest version were without a HDD by the end of the 1980s.
- That was probably just their pocket money.
- Indeed, it's called Goodhart's law. As soon as metric becomes a target, it stops being a good metric.
- Reply to self: it seems I was wrong and veal, venison, etc. have roots in Old French, which has influenced Old English through Normandic invasion.
Still, I stand by my assessment: while it's clear that influences are there to some of the words, it's clearly more germanic. Just as we say today that French is a romanic language and English is germanic. I see no evidence here to counter this common classification.
- I have not read the linguist's essay, just the article, but I am almost certain the claims are preposterous.
The article already mentions that the structure is definitely germanic in origin. Next are the words. Some are adopted from other languages, but many more have roots in Germanic and Latin. The reason is that Romans invaded Britain some 2000 years ago. Afterwards, Latin was spoken in learned circles until the renaissance and even later.
When French became the language of diplomacy, IIRC at the time of Napoleon, only that's when French became a language of note. That's when the "sofisticated" words like veal, venison etc. enter the English language.
But, even all that aside, my native language is Slavic. I speak both English and German, and a very little bit of French. In my limited personal view, German and English have much more in common than French and English.
- You are correct, my post was more for the situation where the CTO is also the engineering director but in larger orgs that is not usually so.
I do think, however, that the coding CTO is not the way to go about to change the process. If it's too cumbersome, the CTO should talk with engineering director to find a way to make it less so, not just bypass the process.
- Seems like the author has not yet learned to delegate and trust. I think it's an example of what not to do as a CTO.
- Trouble is, I don't think they'll just get it and then set about to changing the processes. Besides, the process doesn't come from the middle management, it originates from the top, usually the CTO.
- Nit: shields were just for battle, for this they used the deflector.
- Time dilation is exponential. At 0.1c it's definitely measureable but not a practical problem.
- Ok, so it's only half satire, or is this reply also a satire? I mean, MS Teams, really?
- That has not been my experience at all. Whenever I tried asking the AI to do something, it took an inordinate amount of time and thought to go through its changes.
The mistakes were subtle but critical. Like copying a mutex by value. Now, if I would be writing the code, I would not make the mistake. But when reviewing, it almost slipped by.
And that's where the issue is: you have to review the code as if it's written by a clueless junior dev. So, building up the mental model when reviewing, going through all the cases and thinking of the mistakes that could possibly have happened... sorry, no help.
Maybe 10% of typing it out but when I think about it, it's taking more time because I have to create the mental model in my mind then create the mental model out of the thing that AI typed out and then have to compare the two. This latter is much more time consuming than creating the model in my mind and typing it out.
- Different timezones, I guess... this is the first time I'm seeing it, so it might be ok?
- That's just corporate speak. If they cut middle (mis)management that might be true. Did they?
- Well, if you just want to store data, you can use files. Lookup is a bit tedious and inefficient.
So, if we consider that persistent storage is a solved problem, then we can say that the reason for databases was how to look up data efficiently. In fact, that is why they were invented, even if persistent storage is a prerequisite.
- Compile times are faster now for C and C++ right? Some of it due to further compiler optimizations but mostly due to higher CPU power.
Still, you seem to be arguing that the choice should be Pascal instead of Rust. There is a reason why we choose these new languages: language features. Compile time is a lesser consideration.
- In C we had to resort to tricks like precompiled headers to get any sort of sensible compilation and it still lasted a minute for a decent library.
C++ was/is even worse what with generation of all the templated code and then through the roof link times for linker to sort out all the duplicate template implementations (ok, Solaris had a different approach but I guess that's a nitpick).
I have not worked on any large project in Pascal, but friends worked with Delphi and I remember them complaining how slow it was.
So, in my experience, it really was slow.
- Not even mentioning that you cannot change the headlight by yourself.
My first contact with PCs was in 1988 and they all had HDDs and were definitely not "IBM PC" but clones. That said, that's just my experience so YMMV.