pythonaut_16

The particular implementation I had in mind is Erlang. Due to the green thread implementation, immutable data, and message passing, Erlang is able to offer a simple, robust concurrency platform. Of course it's still possible to write very sequential code but generally someone writing idiomatic Erlang won't have to go out of their way to get concurrency.

I think the key is that Photoshop and post processing tools should always be used to enhance the representation of reality, rather than distort it; except when showing something beyond reality is the intended goal.

It can also be said that post processing can be used to cover up mistakes that were made when the image was captured, and as a photographer one should strive to minimize those mistakes.

TL;DR: Photographers should do their best to do a good job when they capture an image and to be aware of what they are trying to convey in the final version that they share with the world.

One thing I find myself asking a lot is if it's really hard to make a program take advantage of the cores or if the prevalent tooling and paradigms of today make it hard to take advantage of the cores.

While most programs are not embarassingly parallel in nature, I suspect the latter plays a bigger role than most of us tend to admit.

I don't know anything about your game but I wonder if you could use SQLite to a similar effect.

If you just want things as JS objects, you could have a Player table with a column for playerID and a column for the JSON string.

I'm not saying you shouldn't use Mongo/NoSQL, I just think SQLite is an interesting potential choice. (e.g. https://sqlite.org/appfileformat.html)

The main concern of the question is the side projects, not whether the employee is performing adequately. This two questions are inherently tied together. If the employee wasn't performing then they would be fired regardless of the side projects.

So in order for the side projects to be a concern, it implies the employee is still performing their job at normal levels. So then the question becomes, why does the engineer have time and motivation to work on the side projects?

And ultimately I think, the answer to that question is that there's some failure on the part of company leadership, as other commenters have pointed out, regarding motivation, available work, and how over accomplishing is valued.

I have a lot of respect for Waymo's approach to this.

While Tesla and Uber have both just recklessly (imo) jumped in and started setting loose self driving cars and making bold claims, Google/Waymo has really taken a slow and measured approach and given great care to making sure their cars are actually safe.

I think it's definitely a spectrum.

To me the most important binary distinction is whether it's "remote friendly" meaning you can work from home if you give an excuse, and remote friendly meaning it's expected that you'll be working remotely on a regular basis.

Once you're in that second category there's range from "work from home one to several days a week" and "never set foot in the office again"

Supervision doesn't always mean micromanaging or looking over their shoulders. You have to adjust your supervision strategies to the task and environment.

>> 9. Exercise care and thought in supervision. Over supervision hurts initiative and creates resentment; under supervision will not get the job done.

You might give your engineers a lot of freedom but at the end of the day you know what they're working on and you see their outputs.

It seemed like in the panel they just kept looping back to the performance and concurrency, to which the Ruby guys would say "So what, Ruby is fast enough for 99% of apps", completely ignoring all of the other strengths of Elixir.

I have not edited the comment, maybe you confused mine with someone else's or misread it?

Anyway my point wasn't to support or deny Amiibo hacking, just to highlight the contrast between basic/pro software versioning and Amiibos.

Except in this case there exist(ed) far less keys than demand, with the original company (Nintendo) selling them for a flat price regardless of supply vs demand, i.e. if Nintendo sells 1000 Amiibos at $25 each, they'll have $25000, even if those same Amiibos end up being worth $5000 each on the secondary market.

I think I remember reading somewhere that the pick-up truck would be based on one of their existing frames.

I would imagine that the new roadster will also share a frame with the Model 3 (assuming it's a different frame from the Model S)

A better comparison would be: to avoid theft, don't build your house out of toothpicks that can't support a deadbolt door.

The key point being

> UNLESS REQUIRED BY APPLICABLE LAW

Not to mention that liability waivers and disclaimers can never supersede the law anyway.

Imagine our cities if everyone had the flexibility to work from home as needed/wanted.The time when you did need to commute into the office would be much quicker due to the reduced traffic. It would be a huge win as long as everyone at every company doesn't decided to commute on the same day.

But the municipal option is willing to expand of it's own accord if allowed, while Comcast and AT&T will receive $40 million to build infrastructure and still charge customers.

If that's the case then eventually we should see or find a sound explanation for how these solar panels overcome that particular issue.

It's silly to act like something is above questioning because Elon Musk and Tesla are involved.

I don't think this is a fair assessment.

When I got to make a website, I don't say I can't make it secure because I can't afford to be an expert in security at every level of the OSI. I say I'm not an expert in every level of the OSI so I rely on accepted best practices and community standards to make my site secure.

I don't replace HTTPS with my own standard because I can't afford to make an adequate and secure replacement. If IoT makers can't make their own custom solutions secure then they need to build their devices out of standardized pieces that are secure.

And honestly if a company is going to evade or limit their taxes passing on part of the savings to consumers if fairly benevolent (if the tax avoidance contributes to the price as GP claims).

Does a tiling window manager like i3 not fit that use case?

Really it sounds like a good situation for a federated service/protocol.

Let IoT developers develop against the protocol and then consumers can pick a provider to run their IoT hub.

i.e. I go to my garage app and plugin iot://firstname_lastname@iot_hub_provider.com and then that does the heavy lifting of cloud connecting the device and allowing the app to communicate with it.

What confidence is there to lack in the WTFPL? Saying I license you to use this source code/software however you see fit seems pretty straight forward to me.

In this case people are talking about avoiding ISP tracking, not evading law enforcement and government entities.

Can you give a rough estimate of your monthly usage and the price on GCE?

I've been looking at AWS and GCE but I'm having a hard time figuring out the actual bandwidth costs.

It doesn't have to be outside the US to avoid your ISP selling the data.

If you run through a 3rd party VPN you have to trust the provider to not sell your information.

If you run through a US based datacenter your data is still within reach of a subpoena but your ISP won't have access to it.

I know for me personally I already assume anything over a non-HTTPS or non-secured protocol will be received and possibly read by anyone and everyone.

Seems like a reasonable requirement as part of any large deal like this. Even if each party pays someone 200k a year solely to sit in an office and make calls verifying large invoices you're still talking about a small amount compared to the size of these contracts.

I think this is the future. There will always be a few main do-anything languages, but we're going to see languages that fit certain use cases becoming very common.

Historically languages were limited by their compilers and VMs. You ran Java or C++ because it took a large company to come up with a fast enough environment. Now we have the tools and experience that anyone can create a fast enough language in a few weeks.

Also historically, if you wanted your code to run faster, the answer was pretty much always to move to a lower level language. Java too slow? Use C++. C++ too slow? Use C and/or optimize choke points with assembly.

The tooling exists now that we can solve a lot of those same hard problems using languages and tools designed to solve them without reinventing the wheel in C or assembly.

I agree that all of the sub-versions of the iPhone are slightly confusing, but at least they generally follow a pattern.

There's always a clear progression, a higher number is always better than a lower number, and adding an S is an incremental upgrade over the non-S version. The Plus is always a larger size than normal.

The G series and C series have complicated things, but generally speaking you just have to pick a number and then pick one of ~3 options at that level.

It's no more insane than the earlier deployments of electric infrastructure. The only difference is connection has to be made to rest of the internet at some point.