tomtomtom1's comments

I think the object-oriented paradigm, is the most hated aspect:

- "Object-Oriented design" ( class diagrams, use case diagrams, Abbott Textual Analysis... and all the bike bikeshedding fun of UML, Rational Unified process..) generally pushed by the likes of IBM, Oracle, and heavily taught in SE courses.

- a watered-down version of the above, where formalism is discarded, but the first problem-solving step is to decompose the system into classes. an infamous example is the chess-board interview. I think the author is criticizing this part.

I think the majority of people don't hate things like vector<int> or set<int>, despite them being classes.

a quote on this topic, during the early days of the Afghanistan, was "CNN shows us where the missiles are launched and Al-Jazeera shows us where they land"

a More concrete example is "On February 8, 2018, it was reported that Qatari leaders had reassured the leaders of Jewish American organisations that Al Jazeera would not be airing its companion documentary series on the Israel lobby in the United States. According to Haaretz, the Qatari government had reportedly hired Republican Senator Ted Cruz's former aide Nicolas Muzin to open communications channels with Jewish American organisations. Earlier, the network had sent letters to several American pro-Israel organisations informing them that their employees would appear in the documentary. These letters generated speculation that the Qatari government had reneged on its earlier promise to block Al Jazeera from screening the controversial documentary which, like the earlier British series, had utilized clandestine footage and recordings of pro-Israel activists." (https://en.wikipedia.org/wiki/The_Lobby_(TV_series)

that's interesting, so you use an iPad for your day to day programming?

from my experience converting ppt/word to pdf is a common enough use case that I would've assumed the majority of non-tech people run into it.

Latex is also a common case where you run into file extensions.

note I'm not expecting them to understand the difference between extensions, just what they mean and how to google how to convert between them.

I don't understand why no one is blaming the education system?

How is it possible that students that are being considered for "advanced placement" are not familiar with file formats?

how horrible and backward your education system must be? This belongs to basic literacy in the modern world.

Note we're not speaking about old people who were exposed to files for the first time while they had to balance a family life and other responsibilities.

We're speaking about people that were forced to spend more than half of their lives learning !!!

when I last bought a laptop, notebookcheck's [1] cpu ranking was helpful.

[1] - https://www.notebookcheck.net/Mobile-Processors-Benchmark-Li...

how can you reconcile that with the fact that job-hopping in 2-5 years is proven to be a more effective way to raise your salary?

Being seen as "local" may have its benefits but I doubt that being one is more beneficial.

I genuinely hate the software architect title. It's like when we were in school and the teacher told us to write an outline before writing. No problem ! the majority wrote the text first and then the outline.

That's because people in general write to think.* The level of deep thought achieved through writing is harder to achieve beforehand.

In the same sense, the level of deep thought achieved through writing code, is hard to achieve beforehand. It's actually worse because your engineers, dangled in this web of classes, won't be able to think about the big picture for themselves.

An Architect thinks in terms of what sounds good, what is beautiful in OOP-land not in terms of what is easy to write, and what's performant to implement.

One poignant example is the interviewer who wants you to implement chess pieces as classes. which sounds good in the architects' world but is blatantly insane if you think about the actual code and the actual challenges you're facing.

* writing to think and writing to be read are conflicting goals that why editors exist.

would ios_base::sync_with_stdio(false); also help?

sorry I typoed I meant, countably infinite. by w I meant the ordinal.

> An infinite number of zeroes. . .and then a one. . .wait, you can't do that.

why not? why can't an infinitely small number exist?

wouldn't 0.999.. be equal to 1 - 10^w since it's only a countably finite series of nines.

but the long division algorithm never terminates.

why would it terminate at countable infinity?

>"but you're no longer talking the same language as the rest of the world"

yes, in the standard real numbers 1 = 0.999.., but people have dealt with numbers like "pi" and "sqrt(2)" before the standard real numbers were defined.

Hence the question, if we define such a system such as 0.333... != 1/3. what are the consequences?

by 0.3333... I mean a countably infinite sequence of 3s.

if we say that infinitesimals exist. that 1/3 != 0.33.. and 1 != 0.9999... and the probability of possible events is never 0.

what are the properties that we would lose?

more like 1/3 != 0.3333 ....

as in 1/3 does not have a decimal representation. you can only approximate it but never reach it.

why?

1/3 * 3 could still be equal to one. but 1/3 != 0.33333... that is, 1/3 is not representable in base 10. Which makes way more sense.

I wonder if taking 0.9999.. != 1, that is 0.0000...1 exists would allow us to reslove, the fact that some possible events have probability 0?