54mf

Neither, really. I'm a developer and nothing in front of me is completely new, but taking a product from idea to completion has a fair amount of Coastline Paradox involved. Not looking for a "how do I do this" solution, more along the lines of, if I want to tackle this, here's a list of tasks I'll need to make sure to cover.

For example, creating a user account creation flow is easy enough, right? You just need a form for a username and password. And password complexity checking (client-side for UX, and server-side for security). And something like bcrypt server-side for hashing (and make sure to follow best-practices in hashing and storing). And you'll want to verify emails to cut down on spam, so you'll need some sort of way to send emails, probably a service because rolling your own email server is....a lot. Oh and where are you going to actually store the user data? MySQL/PostgreSQL or something like NoSQL? Managed database, or are you going to handle the setup, backups, hardening, etc yourself?

Congratulations, we've finished creating a user account! Except for password reset, session authentication tokens, rate-limiting login attempts, CAPTCHAs, and everything around the admin side of handling bad actors (account suspension, IP and/or email blocklists, etc etc etc). ;)

This is one hell of a strawman. You know the "carefully donated" money doesn't just end up in a black hole, right?

Do you mean the Industrial Revolution? I think there were other factors at play besides the amount of public spending.

"Society creates government, not the other way around..."

And government supports and enriches society. It's symbiotic, not parasitic.

"claim credit for what people have created on their own"

Nobody creates anything on their own. Full stop. Every single citizen is supported by countless public infrastructure initiatives, from transportation to safety to education to etc etc, without which no significant achievement would be possible.

If your tofu is tasteless, you're doing it wrong. One of the major perks of tofu is that it absorbs flavor really well.

"The cravings are a psychological reflex of remembering something you liked the taste, nutritious or not."

Nailed it. We used to have summer dinners at my grandparents when I was a kid, complete with grilled burgers. It is, in large part, emotional.

I'm hoping the Burger King trial goes well so we can get nationwide expansion, in large part to help bring the price down. That premium is still a little rough, Impossible is in a lot of restaurants but doesn't have the in-store presence that Beyond Meat has at the moment. Scale, scale, scale!

"First: The vegetarians that I know don't like meat."

Hi, nice to meet you! Vegan for almost a decade, the smell of a burger on the grill in the summer gives me hella cravings. We exist.

"Second: When I tasted an Impossible Burger, it was awful. It tasted like a horrible veggie burger."

I'm jealous, you must not have ever eaten a truly horrible veggie burger. I had a Gardenburger in like 2005 that literally tasted like cardboard. The Impossible Burger is a miracle of science.

Yes, it is better! Part of the goal is to provide a "gateway patty" to make it easier for meat-eaters to reduce their consumption. Good for their health, good for the environment, good for the animals.

(Also, I've been vegan for years and _love_ the Impossible burger.)

This is false and serious FUD. There are a handful of vitamins/minerals that aren't found in meat-free diets (B12 is the big one) but they're all easily covered by fortified foods and/or taking a daily multivitamin. "Protein from animals" is absolutely not critical, and protein is found in all sorts of meatless sources. Nuts, leafy greens, etc.

"It's going to annoy everybody who likes things to happen fast all the time because Face ID will definitely cause a delay and frustrate every user at some point."

It doesn't. FaceID is faster and as reliable as TouchID was for me. Not to mention, with winter coming, have you tried using TouchID with cold fingers? Spoiler alert: it mostly fails.

"The lack of a home button is probably the worst design decision."

Disagree. App switching is faster than ever, the new gestures stick after ~30 minutes of use, unlocking my phone takes less time.

"Half the time when I start scrolling near the bottom of the screen the control center shows up."

The control center isn't accessed by swiping up on iPhone X, it's accessed by swiping down from the upper right "ear" of the screen. So this is a non-starter.

Source: I've been using my iPhone X with FaceID since Friday afternoon, iPhone user since 2008.

> Cherry-picking one profession to claim low salaries are because of gender is absurd.

Community/support roles are still widely considered "soft skills", and thanks to a century or two of patriarchy, are indeed considered womens' work. (This is, needless to say, bullshit.)

You seem to be implying that there is an "infinite supply of highly qualified" community/support folks; hence the low wages. There is not.

"Pay for average or above-average tech support."

Yes!

"Those you can train in less than a month."

Can you train a senior developer in a month? Can you train a true full-stack developer in a month? Can you train a "10X" developer in a month?

"The difference between an average support person and a really great one can be millions of dollars of revenue. But they are paid peanuts because it's women's work, not like the manly engineering which obviously creates more value... nevermind that novice engineers often create negative value by creating liabilities that can cost the company millions, while still getting paid more than the highest paid customer support people."

Spent a few years doing community management / customer support. This is _100% correct_. Oh, the stories I could tell. The role is critically important, and terribly, horribly underpaid. I went back to web development because, even with a 3-year gap in my resume and taking a non-senior role, I was still able to make 50% more.

"You want mobile notifications? Sure, but not on mobile Safari."

You can do this with PhoneGap.

"Multiple line ellipsis? Sure, but only on webkit."

Okay, yeah, this sucks.

"Consistent rendering size across browsers? Just fuck off."

This is probably your fault.

"We fix a layout bug on Safari and break something on Edge."

This is probably your fault.

"We change font size on Chrome and now all you can see on Firefox is the letter F."

This is probably your fault.

"How about hiding the address bar or controlling swipes from the left edge of the screen? Don’t be stupid."

Stop trying to make the browser not a browser. Users hate when you hijack expected behavior. (See: Imgur.)

"Oh, and don’t get me started on all these new custom mobile keyboards you can use and how autocomplete can fuck with your input box events."

You can disable autocomplete. Did you mean predictive word suggestions?

TL;DR: "We tried to make a responsive web app act like a native app and it didn't work because it doesn't work, and that makes me a grumpy goose."

"some rather expensive fruit branded laptops"

So do some rather expensive shiny-metal-branded laptops.

I'm willing to retract that entire line of thinking, because the author never ever actually said anything about designing for Retina hardware, so why are we talking about it in the first place? Their explicit approach was to make Medium's typography work on as many platforms and devices as possible, and this OS X (not Retina, just OS X) bug was an edge case that they missed.

What does this have to do with the article?

[Edit] I'll be less terse. Yes, I know computers are more expensive in some countries. Are you accusing the author of being, in some way, discriminatory towards people with lower incomes? Did he say they were only designing for Retina displays? (Or only for Apple hardware?) This response feels like an even larger straw man than the parent comment I responded to, and even less about the article itself.

You're being disingenuous. For starters, from the second paragraph: "In between Roboto on Android, San Francisco on iPhones and Macs, and Segoe UI on Windows..." Clearly, they're targeting all major platforms. Not to mention, retina MacBooks start at $1299—which is on par with other HiDPI PC laptops, mind you—and I can buy a car on Craigslist here in the first world for like $500. (And I have.)

If you don't like Apple, that's fine, but don't disguise your displeasure as a stand against class warfare.

"For storage a $65 lead acid automobile battery does the trick. It’s 12V so can be charged directly from the solar panel, and holds 420Wh, way more than I use in a day. That’s $0.15 / Wh so I don’t see why everyone is so excited about Tesla charging $0.43 / Wh for the Powerwall, sans inverter and installation."

I'm not smart enough to take this apart, but my gut tells me the best-in-class engineers and (tens/hundreds of?) millions of dollars in R&D at Tesla aren't going to be outwitted by Mr. I'm-Repulsed-By-The-Idea-Of-Kitchens. Anyone want to take a swing?

Cool, cool, very productive, thanks for your input. Your coffee opinions are very relevant to this discussion, and have been duly noted.

A laptop is meant to be portable, with a significant number of moving parts (keys, hinges, trackpad [until recently],) and ports that see frequent insertions/removals. These factors result in a device that can break down in many, many ways. If one tiny failure results in the entire device being unusable (or requiring replacement of many [working] parts at significant cost,) well, you're going to get complaints. :)

SEEKING WORK - Remote, based out of Boston, MA

My name is Sam, and I’m a front-end web specialist. Here are a few examples of problems I can help you solve:

- Your site looks great and loads fast on your computer, but it’s broken and slow on smartphones and tablets.

- You keep getting emails that your site isn’t working quite right in a few browsers, or in a few countries.

- Your site’s codebase hasn’t seen any attention in a while, and you’re pretty sure there’s room for improvement.

- You have a great idea for a service or product, but need someone to knock out the implementation while avoiding all the aforementioned troubles.

Beyond my focus on the front end, I also have design experience — UI / UX, logo and branding design — and experience with server-side development as well. I’m T-shaped, if you will, so if I don’t have the right answer to a problem I can point you in the right direction towards finding the solution.

Let’s chat about your web needs. hire@samuelfine.com

Keywords: HTML5, CSS 3, responsive, mobile app, web app, PhoneGap / Cordova, iOS, Android, Windows Phone, Javascript, jQuery, Node.js, Ember.js

7 days. :)

"you can easily move through it by tapping randomly on the screen"

This is technically true, but if you want to finish the game, you'll need to solve some puzzles.

(And for the record, you can easily play a game like Super Smash Brothers by hitting random buttons, but that game has depth for miles. "Tapping randomly" isn't an indicator of a game's depth, merely its accessibility.)

As a matter of fact, yes! http://www.unicode.org/reports/tr51/

To clarify: by "burn out" I'm referring to becoming tired with a project. I'd hope that the maintainer would simply move on to another project.

Offering incomplete software as open source doesn't make it any less incomplete. Are we giving out blue ribbons for participation now?

You may take issue with Mr. Lodwick's tone, but he's not wrong. This gem is incomplete, and for a gem occupying the namespace "emoji", I think it's reasonable to expect the full, standard set of emoji. Passing the buck to another open source library is irresponsible and, frankly, lazy.

Perhaps the maintainer should burn out, and let someone take over the gem who'll commit to feature-completeness.

AIME? ;)