293 karma · joined July 21, 2015
If an extra day to clean up your code is an issue, your company is already dead. What if you have to push it back a day because you get sick?
Bounce, sure, bounce is terrible, but...
> Avoid Linear animation easing.
Okay then, what would you use when you are moving a thing from point A to point B, both of which are on-screen? Ease in and ease out will look jumpy.
For one thing, I'm talking about the people that are posting things on Github, and Github itself is just an example. You can replace it with "a personal website on a server in your living room" if you prefer, although I suppose that's just an ad for your ISP's services?
Secondly, you are not the product. You are never the product, unless you live in a country where slavery is still legal. "Inclusion of text and image content in HTML sent to you" is the product Facebook et. al. are selling, but that doesn't quite have the same ring, does it?
It's disappointing to see the web portrayed as so profit-minded :(
https://github.com/ReactiveCocoa/ReactiveCocoa/blob/master/R...
But, whatever, rewrite Xcode I guess.
What do you mean by this? In the implementation, yes, is a poor optimization strategy, but for the user of the language, shouldn't that be what appears to be happening? Mutable data structures and functional programming mix worse than immutable data structure and functional programming.
> Or placing stateful actions into the same API set as FP expressions makes little semantic sense and discourages any sense of thoughtful structure to the different paradigms.
This is incredibly weird. You cannot get an array in Swift with an item at an index removed. There is a function to remove an item at an index from a mutable array[1], but no way to remove an index and return a new array. You can't do it. But you can "filter(:)", which returns a new array, and you can't "filter(:)" a mutable array to alter it. ...wat?
[1] - a thing that I'd argue shouldn't exist, when we must have mutability, it should be mutable references to constant arrays
antitypical/Result already provides Result.init(() throws -> T) -> Result<T, E>, so it's easy enough to work around, at least.
The magic variable stuff exists in didSet as well, weird and sketchy to use. Would prefer it to be explicit in all cases.
If you don't want to show content... don't return a 2XX.
Not very many. I would definitely love to leave at 5, and I know that this would make me more productive - in total! - not just per hour, but I don't want to deal with the fallout from it, since everyone else stays until after 7:30.
I tend to get in at 8-9, while others come in 9-10, but no one can tell how early I was in. As is, I'm already typically among the earliest leaving, and it already feels weird.
My health has definitely taken a downhill turn... before I was at the gym 3/4 times a week, plus bike rides. Now it's one or two, and that comes at the cost of being able to do other things.
I definitely agree with this article.
And if you're not (can I have your job?), you're probably less likely to be burning out.
-Steve Jobs
I can't see any reason for this other than that they're storing them either encrypted or in cleartext.
Use with caution.