zpr

Then this sort of software makes it recursive.. it's teaching itself...

But he mentions he wishes he could start dynamically and end statically. By enabling Flow at the end, don't you basically achieve that? You can also enable it progressively for files as you move on, and still rapidly prototype without it. In fact, unless I'm mistaken I believe it's "opt-in" by default, ie. Flow won't scan the file unless you include the special comment keyword at the top of the file.

Hate to be that guy but, Flow for JS is something like that. You can optionally enable it and even enable/disable it in certain files, functions, lines, etc.

Glimmer itself is made by Ember?

I can agree that when you have clearly defined business goals its easier to spit out a product. And I'm not arguing that you could make something similar to Screenhero in a year -- the hard part would be to distinguish it from the thousands of others. You could find examples with some Googling (remote desktop software, screen sharing software): GoToMeeting, Join.me, LogMeIn/Hamachi, RealVNC, not to mention built in RDC in Windows, etc. Those are just the famous/obvious ones. If you kept digging, I'm sure you could easily find hundreds if not thousands of similar solutions.

I understand they're slightly different from one another, and I suppose its possible all the commenters here went through each and every one of these options and found nothing useable but it seems unlikely to me, and similarly unlikely the +1 one would make in this pool would be any sort of revolutionary "game changer" VCs would mob onto. The space seems well-established or dare I say it "saturated".

You mean you could make a YouTube clone in a weekend? It's easy to fall into this way of thinking. But hey, maybe you will build the next Screenhero, or TeamViewer. Or maybe you'll end up as one of the thousands of other versions of this nobody has ever heard of. The idea is usually not the hard part.

Same here, I'm on Google Fi and none of my information comes up. Only a "Joe Consumer". Ironic?

This may have been asked before but I can't seem to find it: where do you typically shower or use the restroom? Truck stops? Or just ad-hoc as the situation allows?

Sometimes the direct prices are actually more. Your best bet for sticking it to them might be to use an alternative booking service.

This is really cool. Consider introducing this concept to an FPS game, at what point do you consider it to be an aimbot?

One of the biggest things React has going for it, other than being maintained by Facebook and having a much larger community, is React Native. You can learn one web framework and now also make compelling, real native apps. To me those are both deal makers.

Surprised I haven't seen this mentioned more in the thread.

This. I've also seen where managers seem to know this but do it anyway. Because "hey, you're talented. You can do this."

Not to mention the best one for code coverage. When junior devs ask me for advice regarding increasing code coverage, I tell them instead of writing more tests, how about writing less code? Our boss really liked that one.

Can you hear me now? - Yes.

I agree. Never cared much for the UI, and always found it too buggy to keep using. At my old job, we used it for office tunes, and it was often showing the wrong song that was playing, (so you never knew what you were listening to unless you used something like SoundHound), and going to previous or next tracks was inconsistent, so you might not get back to the last song ever again.

Pardon my ignorance but why is Google Play Music not worth mention here?

But will it matter if they don't know it's machine generated? A sort of Turing test would be interesting here.

What's considered a productive life could be subjective. And why should that be the ultimate goal anyway?

I highly recommend reading the entire article because it's a good read and can't be adequately summarized in this way but here it is anyway:

So-called productivity techniques usually end up having the opposite effect, in either the short-term, long-term or both.

An obvious example is making workers work more leads to tired and frustrated workers over the long term. Or giving tight

deadlines to increase throughput: just results in anxiety and slower net progress. That's manual labor -- for anything

else, the perils are even greater: "Because you don't get creativity for free".

However, the problem is even more fundamental. This trendy and increased desire for "efficiency", backed by capitalism and

basic human greed, has a lasting effect on the psyche of society and it's individuals. In 1930, Keynes predicted that

within a century, we would be working 15 hour work weeks, due to increased efficiency. That's hardly the case today. I

enjoyed the carpet example: we created a vacuum to be more productive with cleaning the carpets, which would theoretically

result in less time spent cleaning. However, now that we have vacuums, carpets are expected to be spotless, so we spend

more time cleaning them anyway, and finding new ways to clean them even further. "Work expands so as to fill the time available

for it's completion" -- Parkinson's Law.

Finally the overall message is that we should slow down and live for the sake of living. Don't walk to exercise and get

healthy -- walk to walk. Don't "party for contracts, lunch for contacts". Do things for their own intrinsic value. "Growth

for the sake of growth is the ideology of the cancer cell". These ideologies need to be implemented at the societal level

as well as the personal level.

A pronounced theme in the article was disregarding this superficial drive to nowhere and instead focusing on philosophising on your own existence.

I doubt many of us know what it's like to be dead but to think its Zen is actually a nice thought.

You should be, unless they also maintain them themselves -- you know, with those "management" fees.

Usually bigger clients negotiate their own fee structures.

Ah yeah, was wondering where that $400 came from

Any plans for an android version?