HN user

fluffycat

64 karma
Posts0
Comments27
View on HN
No posts found.

I have seen way more damage done by the people "mostly working prototypes in hours or days" than people who want to write beautiful code. I understand that fixation to produce something beautiful can lead to paralysis but this is rarely the case. In most cases the prototype grows cancerously and it becomes impossible to fix in quite short time, my advice, listen to the experienced programmers who screwed up more time than you before, even if they seem to be obsessed with "beautiful code".

No one claims AI will be the authority, it is good for finding candidates much earlier. We never had devices that has success rate of specialists on several eye problems in one go, definitely not in 70s. I don't understand what you are arguing against to be honest.

I guess Google engineers has some experience with those hard earned lessons before Facebook even existed. The diagram you mentioned is very typical of microkernels and subject of research for decades.

Turkish is also highly regular and has only one irregular verb. The main problem arises from morphological complexity. Because of these well defined rules that change the rich set of suffixes (>100 different), analysis of a lot of words ends up with many possible parses, it is hard to resolve this ambiguity.

I can't speak Japanese, but if it is also morphologically rich, it should face similar problems.

Not necessarily in case of German, What exactly articles give to the meaning? What would it lose if they are removed or consolidated into a single article.

Programmers? Sure German language needs a nice round of refactoring. Remove all redundancies. It would be a huge changelist with shit ton of lines removed, and still all tests for meaning pass.

My biggest gripe with german is the redundancy, all articles and form changes they create are actually redundant, they don't contribute to the meaning in any significant manners. Remove all of them and all the complications, different forms they create, you would still perfectly understand it.

Yeah I know, languages, organic, beautiful, but subtle things , etc etc.. But still.

Still I find it comical that people thinks Apple keeps the moral high ground. I personally find Apples position disgusting and super hypocritical. Sure, they are the white knight that keeps you safe from other monsters, only if you avert your gaze from China. At least Google so far sticked to its decision, and hopefully keeps it that way.

I believe that premature abstraction is terrible. But in some cases good abstractions may help with handling complexity and may make testing easier. I have a feeling that because authors say that this class should not be changed / refactored, they failed to introduce a good abstraction. This also implies that their tests are inadequate.

But this gargantuan pile of garbage warns that it can not and should not be refactored and it is like the shuttle code (may their souls rest in peace), it is so solid and perfect as is. It is also written in the sacred language of Go. So if these conditions are met, then yes above praises will be and must be sang.