3,658 karma · joined March 25, 2010
Or maybe the candidate is willing to do that type of work during work hours, but lacks the time and motivation to do it at home after work.
The term "refactoring" is commonly used in a way which includes changing of public interfaces. Random article, which even cites a book, agrees: https://thoughtbot.com/blog/lets-not-misuse-refactoring
If you're developing a library, then refactoring shouldn't change public interfaces. If you're developing an application and you own all the code paths to the code, then refactoring could change public interfaces, as the external behavior here would be the UI.
If you literally agree with the "refactoring shouldn't change public interfaces" then we need a new word for "code improvement which doesn't change external behavior, which can mean UI", which is the more commonly needed term.
And then perhaps we could agree that "code improvement often changes public interfaces" and how this relates to unit tests.
I don't think that's true. In a really simple model imagine UBI of $2000/month given for everyone. Then imagine increasing income taxes by $2000 for all employed workers. Then the true cost would be difference between current unemployed benefits of the UBI, which shoudln't be obscenely expensive (in normal economic times). Employed workers shouldn't care about the increased taxes because their take home money would remain identical.
That's of course a very simplistic model, but explains how you shouldn't just count the UBI amount times population as the cost.
Not really. There are UBI models that are more or less zero cost - taxes are increased by roughly the UBI amount for employed workers, and for the unemployed the UBI would be similar to the unemployment benefits they would lose.
Why would this be the case?