mikemikemike

Privacy is important, but breaking the functionality of cookies is the wrong way to address it. Not all cookies are used for tracking. Be prepared to start losing your settings in web apps or being logged out after 24 hours if you use Safari.

What's more, the claim that Apple is doing this for the sake of user trust is a lie. The real reason they're breaking the functionality of cookies is the same reason they refuse to implement progressive web apps, and the same reason they've become the slowest browser to adopt new standards, and the same reason you see "Safari is the new IE" all over the place. They're deliberately trying to hold back web technology so that people will be forced to create and use native apps instead. They're desperately trying to cling to the annual developer license fees and app commissions.

I say this as a die-hard MacBook user. I prefer Apple to Microsoft, but I hope Google wins in the web-vs-native holy war.

Interesting read and great points. But the reason I'm shopping for a diamond is precisely that it is too expensive. It's supposed to be proof that I am glad to make sacrifices for her. If we wanted to do something nontraditional we might choose some completely different kind of ring, but to choose something that looks super expensive and is not would make me feel like I had cut corners for my fiance.

I wonder if the problem is specific to ageism in individual contributor roles. I've worked at a few startups where maybe 1/3 of the product team was over 40, but I can only think of two coworkers over 40 who didn't have any direct reports. Do we find ourselves wondering why an individual hasn't "advanced" to a management position after 10+ years?

I really respect the perspective of this peice. My reaction: this career, for me, has been so riddled with imposter syndrome and self-doubt that I would hardly recognize it without the kind of language in question. Dissatisfaction with my own expertise is a huge motivation, and the pursuit of confidence in my abilities has taken me further than I ever thought I would go. Realizing this, I've become pretty comfortable with feeling like the idiot in the room, and if I ever get comfortable or confident it's time to challenge myself more. That said, I think there are situations (like conferences) where inclusiveness is more important, and we can save the bar-raising for the workplace.

The JS community switched from the term "isomorphic" to "universal" around a year ago. Seems not everyone is on the same page yet.

This is an odd debate. Let's say a restaurant declares "veterans eat free." This blog post is like a friend telling you "Hey if you tell this restaurant you're a vet they'll give you a free meal." No one said it's legal or ethical. It's lying to trick someone into giving you something at their expense.

I think the relevant point, underscored by the author's last sentence, is it doesn't matter who you open a back door for - it opens the possibility for anyone to barge through.

less code !== faster code. I wouldn't even try this without seeing some impressive performance benchmarks. Giving up the support of the entire react team and community in exchange for a small framework that may or may not be faster is a huge ask.

My impression is that the benefit of this approach is that it fits the mental model of NPM and Bower. Being able to manage packages across your stack using the same kinds of steps feels... organized. The relative path issue, however, needs some more consideration.

"anytime they’re looking at job ads, serious developer positions, not front end developers... "

Ouch. I guess I never should have dropped PHP for client side MVC apps.

If I were Tesla I would probably hire Buzzfeed or some other marketing channel to do a viral story highlighting how schmucky this lawyer and his client are. It would serve the brand better if they weren't seen giving these guys the time of day, let alone real estate on their corporate site.

This one hit home with me. Having every waking hour consumed with obligations - fun or not - gets draining after a couple years. I wish my friends didn't get mad whenever someone says no to something, and I find myself regularly contemplating the merits of going off the grid to live as a mountain man.

One thing that developers can do is think about how they can build products that give other people an opportunity to make income online. Marketplaces, payment processing, etc. Build sites that encourage people to learn to code or design, build tools to enable web designers to launch better sites, give small business owners new ways to monetize their sites and compete online. One of the things I'm most proud of as a developer is that we can build things that not only reward ourselves, but create opportunities for others.