goto11

52 ms·

601.
by goto11 5y ago
In the context of JavaScript it means some numeric keys are missing (between 0 and the highest numeric key). This is an issue because JavaScript Arrays are not like arrays in other languages - they are dictionaries where the keys happen t
602.
by goto11 5y ago
Words can certainly change gender over time or be non-gendered if that is what you mean. But it doesn't make any sense to say that a word is non-binary in a trinary gender system like in Latin.
603.
by goto11 5y ago
Danish have two grammatical genders, "neuter" and "common". Male and female have same grammatical gender. So conflating gender and sexual identity becomes really confusing!
604.
by goto11 5y ago
> A “non-binary” “gender” is just a noise with no idea attached to it. Are you talking about grammar here? Because in many (most?) languages gender is not binary.
605.
by goto11 5y ago
I don't think the etymological origins of the words really impact the current conversation. The meaning of words depends on how they are used, and "gender" today have quite a different meaning when talking about human gender
606.
by goto11 5y ago
It is called "word of mouth" and is essential for the success of a blockbuster.
607.
by goto11 5y ago
It is different. Less bizarre but better production value.
608.
by goto11 5y ago
Yeah exactly. If two block of code are literally duplicates, it is easy to consolidate. But in reality they will drift apart over time, making it more difficult and risky.
609.
by goto11 5y ago
You shouldn't need to mock a sealed class in the first place. Consider them like a more powerful enum or an algebraic data type. You wouldn't mock en enum either (hopefully).
610.
by goto11 5y ago
> The managers would simply have to trust you Yeah, that is my point. You can make up any bullshit number, and there is no way to prove of disprove it.
611.
by goto11 5y ago
I was really confused the oldest building in California was a monastery from 1181. Apparently it was built in Spain in the middle ages, but in 1931 was purchased by an American billionaire and shipped to California!
612.
by goto11 5y ago
Agree, although with the caveat that if you find yourself deliberately copy-pasting duplicate code, you should consider going DRY immediately. You might later realize the code really should be duplicated (because it is "accidentally al
613.
by goto11 5y ago
Yeah but such rules are still just unfounded opinions which have been codified and human judgement have been removed. What is an "excessively long" method, for example? If a method conforms to good design principles like separatio
614.
by goto11 5y ago
Such tools don't measure any objective code quality, they just measure to what extend the code conforms to some criteria defined by the people configuring the tools. Do these criteria correspond to proven long term maintainability bene
615.
by goto11 5y ago
Since the Norse met native Americans (according to the Saga), I don't see how this changes who was there first? It was only a thousand years ago after all.
616.
by goto11 5y ago
There is no doubt Vikings were in Pre-Columbus America.
617.
by goto11 5y ago
Unfortunately technical management have the same problem.
618.
by goto11 5y ago
In any case, you can have the best code quality in the world and still miss deadlines if the deadlines are not realistic.
619.
by goto11 5y ago
So you try to convince me that immutability is great. But I did not say I don't believe in the benefits of immutability, I said there is no empirical evidence that it leads to better long term productivity.
620.
by goto11 5y ago
Sure you can say such things. My point is just there is no way to determine if you are right. Unless you make an A/B test where you both refactor and keep the old version around, and measure how much time it takes for the same develo
621.
by goto11 5y ago
Totally agree. I will add that the hype is typically ignited because a technique have shown real benefits in a particular domain. The problem comes when the technique is treated as a panacea and is applied uncritically outside of this domai
622.
by goto11 5y ago
The problem is you never have "equivalent tasks". This is the blessing and curse of software development: You never have to do the same thing twice. Software tend to get more complex over time. Even if code quality is optimal, sof
623.
by goto11 5y ago
> I look back on the time before I was cognizant of the concept of Immutability and every larger FE app I wrote feels now indistinguishable from disorder and turmoil. Good for you, but this is not very objective. People were saying the s
624.
by goto11 5y ago
> Deadlines continuously are missed This is a question of the quality of estimates and unrealistic deadlines. This is a separate problem from code quality. E.g. if you have really bad code but you know how bad it it, then this is facto
625.
by goto11 5y ago
Because a business need to allocate resources rationally if it wants to survive.
626.
by goto11 5y ago
This assumes all features have equal complexity.
627.
by goto11 5y ago
But how do you know these things actually improves code maintainability long-term? How do you quantify the effect? Code reviews and linting is just applying some opinions to code. How do you show empirically these opinion are valid?
628.
by goto11 5y ago
All developers know code quality is important for long-term productivity and efficiency. But from a management perspective the problems are: - There is no way to measure code quality - There is no way to measure developer productivity - Cod
629.
by goto11 5y ago
Yes but that was not what was written. What was written was unambiguous. You use the phrase when the name of a geographical area did not exist, or wasn't the same at the time you are referring to. So you wouldn't say "People
630.
by goto11 5y ago
The phrase "present-day Foo" is used all the time by people writing about history as a way of indicating a geographical area. I don't see the problem.

More ›