4,605 karma · joined December 10, 2015
It was a comical waste of time, and the whole time you're there wondering how it could possibly change someone who already had no scruples. You're left bitter that you had to participate in a function that had no purpose beyond making some decision-maker feel like they were moving the needle on some issue.
Maybe some companies out there also banned slave ownership across the board. Probably seemed unfair, too. Did they not realize how useful slaves are?
Now, this seems like a silly comparison because we're all so used to eating meat for every meal, but does familiarity trump ethical concerns?
So I would not want to work where you're in charge where everything I may want to do (or consume) is judged on its productivity basis.
You probably have habits that sacrifice your work performance. There's a good chance, at the very least, you weigh more than you should, work out less than you should, and eat fewer vegetables than you should. You might even have children or plan to have them one day. Yikes!
And all of these cost you much more than the morale boosting beer I get to share with my team as is tradition towards the end of a Friday.
I have, and I trust most of my neighbors to prepare a chicken cutlet with more care than any revolving-door restaurant I ever worked in.
Consider just restaurants of a rank <= Outback Steakhouse (where I was a line cook for three years). Pure minimum-wage apathy will be cooking your food. Almost anyone can do better than that, especially someone inviting people into their home.
I'm seriously having a hoot over someone on the internet using restaurant food/hygiene quality as a standard for any argument.
e.g. As if you need social anxiety to appreciate the vast convenience of ordering food to your doorstep.
The difference is that in a statically-typed system, you're validating data at your boundaries such that they comply with your nominal types that are then compiler-guaranteed to be internally consistent.
The problem isn't that `user && user.username` style validation is verbose, but that it's very error-prone. Making it less verbose just means you'll more likely use it before you reach for a better validation strategy, like a declarative validation library.
They aren't celebrities. They aren't just people with a following or a popular channel. They are specifically people with a following that are successful at converting sales.
Unless you have something interesting to say on the matter, I don't think this forum needs more "le wrong generation"[0] posts.
But since you don't have that experience apparently (despite whatever "write up a storm" means), then you have no clue what might be preventing you from entering the tech scene as it may (and is far more likely to) be related to any of the other things that keep people out of tech, like tenuous interest in the subject at all.
If you start looking at demographics outside the audience to qualify the name, then you'll probably end up with an abstract-but-brandable name that communicates less which seems like a regression.
Your complaint doesn't seem to make sense in this common context. In fact, I can't think of many contexts where your complaint does apply.
Let's say Reddit knows precisely the 100,000 things I do want to see. Endless scroll doesn't change that, but it makes sense to lazy load them that way.
Indicates that the process is clearly there at Apple, they just turn a blind eye.
But wow, I expected a lot more from the billing UI of iOS apps. You can start a billing process just by making the user click a button? IMO everything billing should require a round-trip through a standard billing App Store page just like if you were to pay something online with PayPal.
And I was especially amazed by how hard it is to see your subscriptions. I just checked mine and was subscribed to an app I completely forgot about.
Think of the kind of UI you would design if you wanted to ensure people weren't making money from others unknowingly. You'd give Subscriptions its own tab in the App Store. You'd create notifications like "You just paid $5 to <App> (Recurring: weekly)". Even PayPal's app gets this right.
Of course, it's really just an opportunity for some weak posturing like "heh, I thought you meant floppy as in the floppy disk, something us grey beards had back in our day ;)."
Perfect position to cover subtitles of the full-screen movie you're watching. On more than one occasion, I've had to rewind the video to catch a critical subtitled word because I made the mistake of making a minor volume adjustment at the wrong time.
You can turn off the block entirely from the terminal, but then you lose the indication of where you are in the volume continuum.
In most cases you can get away with wholesale removing and redirecting all trailing slashes in middleware.
Let's not suggest that "white paper" is more appropriate than "blog post" or "HN comment" as a medium for partaking in the HN tradition of sharing some details about one's stack. I'd be hard-pressed to believe that OP was literally asking for one, too.
Thanks, cryptocurrencies/ICOs.
My friend had her password guessed (you can buy hundreds of hacked premium Spotify accounts online for <$1/each) and was powerless against the person who had been using her account. She had to basically listen to what they were listening to, it was a bit comical.
We emailed Spotify about this as it was happening and there was no way to lock this person out. Sorry! They advised her to create a new account and they would gift it with some duration of premium access.
To make things worse, she was the one who started our family-plan, and their customer support was unable to simply migrate the plan to her new account. She registered a new account and added it to the plan. This intruder was basically able to free-ride on our plan and force her our of her own account.
When I later saw the price of hacked Spotify accounts, I thought it was a great value!
Yet I must endure all of its downsides the whole time I'm on the page, from taking up precious screen real estate to the even more annoying approach of popping in and out when I scroll up/down one pixel.
Just think of how seldom you interact with the navbar of most webpages and why it then needs to follow you around the page in the off chance that it's more convenient than just scrolling to the top.
So far I remain unconvinced that it can be done well since the entire premise is flawed: my device already gives me a one-click scroll-to-top shortcut. Like inertia scrolling, it's a bad smell when every website thinks it has to bring its own implementation of feature devices should already have.
Classic example being to take on $100k of debt to start a business and then paying workers $20/hour. Only one person is on the hook for $100k and they are rewarded accordingly if it pays off.
It's easy for the workers to then conspire about how unfair it is that the debtor isn't out there in the sun like them, but that's not a very complete picture of reality. Zero risk is part of the workers' compensation.
You didn't respond to anything they said and you doubled down with your nonsense about "Monads exist because because haskell people want to pretend that there is this ideal mathematical world where things dont change."
That monads ignore the "mutation reality" isn't a very strong point when monads are a concession for the "mutation reality." Unless you want to repeat yourself a third time, the ball is in your court to bring concrete supporting arguments since you're making the extreme and somewhat self-aggrandizing claim that these other people don't really see the mutation reality of the world like you do, thus they are using inferior tools.
I'd say that anyone specifically trying to corral/isolate their I/O code (monads or not) are so "enlightened" about the mutation reality of the world that they use specific abstractions to address it.
If you want to see code that tries to paper over I/O, look at a program where you can't even tell when and where the I/O is performed because it just looks like any other function call. Active Record in Ruby on Rails might be a good candidate in its effort to make DB access opaque to the programmer.
And I'm not too sure men at work, regardless of race, rank very high on the scale of people you're scared to run into in the early morning, even in your place of origin.
Pretty much what it takes to get people to donate money to one of the most important and popular websites online.
But to my eyes, expiring salts isn't much different than deleting ip addresses after one day. Just more machinery. People have to trust that you're doing either, so why bother beyond being able to use the word "hashing" in marketing language?
Trainspotting, Slumdog Millionaire, and even 28 Days Later have related sequences.