My fiancé ended up having similar issues . The RAM was the culprit, despite not failing any of the checks I did in the debug. We ended up needing to reinstall the stock Apple RAM and had to do a warranty call for the RAM we got from Corsair. Haven't had an issue since replacing the RAM with the new units from Corsair.

I started out having to learn coding with my thesis project, Flood Zone NYC which I've kept up over the years and has improved along side my abilities. I've occasionally gotten to play both roles simultaneously in my career, and occasionally work side projects where I get to helm the designer and developer roles like my playlist generator for Spotify, Dubolt, A color contrast desktop app (wip), and a parody sticker pack for iOS

If I'm being honest, I've found it difficult to maintain a career as a designer as I have grown as a developer, largely because developers are more in demand and employers usually prefer to utilize me in that capacity than a designer. I do think that for a true hybrid designer, there's an inflection point where your development skills are deep and robust enough that employers are no longer interested in using you as a designer because your engineering talents, to them, are more valuable.

I think I'm at a point where I'm just going to have to pick one and move forward with that as my specialization. Perhaps I could find a middle ground as an interaction designer and prototyper on a product team, or maybe someday one of my side projects could evolve into an actual business, who knows.

I think I would still recommend that people learn development, more for what it enables you to do as a solo designer and the opportunities it creates. I think it's also a great leg up for someone who is just starting their careers, but I do think that when it comes time to move up the ladder to senior or leadership roles, the hybrid designer/developer will ultimately have to make a choice.

It looks like it works pretty much the same way all the others (Invision, Zeplin) do and just uploads your sketch comps. Google would like for you to be using Material, but it doesn't seem to be an actual requirement to use this service.

IMO, I think you should prototype in tools that are closer to what the final output would be, and for that I think that a prototyping tool like Flinto fits the bill.

My hesitation with After Effects is that having no limits in what you can do encourages designers to build motion comps that would be very difficult to produce with heavy performance costs to implement, a good example of this being motion blur, which is generally impossible with basic layout technologies like CSS, or UI Views, and to create requires manually calculating and rendering a motion blur in Canvas, or with animation specific toolkits on native devices.

I think that divorcing the animations and transitions from actual interactions encourages designers to build beautiful, slow interfaces. Things like pressing a button and waiting a few seconds for a very nice looking, cumbersome animation to complete. I think that designers are less likely to engage in these indulgences if they have to endure them a couple of times when actually using their prototypes rather than just envisioning the interaction through video.

I do wonder about the claim about the brand being too German. Personally, I don't think it's the brand that's "too German", it's that the products themself are too boring and safe. The 2018 Jetta and Passat are about the most non-descript cars on the market. Granted, the 2019 Jetta looks a bit more aggressive and distinct than the prior model year, but then we start to see some disconnect from where the marketing people want—an approachable, friendly brand—and the more aggressive, tech heavy products VW's engineers and product people are actually making.

We'll have to see where VW actually ends up landing, but I hope that the results will be less safe than their product lineup.

Well with the Cambridge Analytica controversy, the issue was that your friends could give permission to share your data rather than you being able to do that. That particular issue has been resolved, but there's lots of sneaky data practices and UI practices that Facebook engages in that could bring regulatory clout. For example, up until recently you could search Facebook by phone number or email address for people. This data was given to Facebook without the expectation it would be made public, yet that's how it worked in regards to search, allowing it to be exploited by scammers.

Instagram also has some dark UI practices on account creation where it prompts for your contacts and greatly diminishes the option of signing up without giving up data.

Even if the US doesn't institute new regulations on Facebook, I think this is an inflection point for data privacy in regards to permissions based apis, ad tech, and for the design used to obtain such information. I think informed politicians in the EU could call for privacy supporting options to be given equal graphical hierarchy to permissive datasharing options, and that we should expect to need to overhaul what a oAuth permission screen looks like with greater explanations of what each individual permission does and why a developer may want access to it, as well as, hopefully, the ability to conditionally provide requested oAuth permissions much like how one can do on iOS.

Case in point. I have a hobby project for Spotify called Dubolt. Spotify requires, for whatever reason, that I request a user's email and date of birth if I want to use their web playback sdk. I personally don't do anything with that data and for me it's an unnecessary tag along, but you could imagine a scenario where I was storing that data anyway for whatever reason. What I would like to see from a user's point of view would be for my user to be able to give me the permissions that I need for basic functionality to work on my app, like the ability to create playlists, but if they don't want to give me more sensitive data, and then I can enable and disable features of my web app depending on the returned approved scopes. You have to design like this now for iOS, but you can't for the web since oAuth is all or nothing.

It's more a few things:

• Facebook's API was way too permissive in the amount of data it gave up, including for the ability of your friends to share your data without your permission. That's already been fixed but it it's more emblematic of a cultural problem with handling sensitive information

• Facebook's TOS has been exposed as pretty much useless against rogue actors. Yeah, this was always a concern, but I think that if we were being honest with ourselves as an industry, we should have a serious discussion about permission based APIs, open APIs, and what sorts of data should be allowed to be accessed. Facebook should do a top to bottom rethink of every API endpoint and if developers actually need the data provided in it, and probably being way more descriptive of what each permission allows.

• This incident represents another vehicle for hostile nation states and state sponsored actors can manipulate Facebook to build profiles. Today it's Cambridge Analytica, tomorrow it'll be some government that creates a Facebook app as a data honeypot, and Facebook isn't prepared for this new reality.

It's more a question of priorities and time. Yeah, you'll be doing a passthrough on your all your target browsers at some point in your development, but you likely aren't simultaneously checking every change on all your target browsers. You will likely do your development mainly on one browser, and the article is advocating for developers to make Firefox that one browser.

This is a pretty good step-in for those who don't want to share their entire artboards on Sketch Cloud, and want some of Invision's features without needing to do the prototyping work twice.

On a less pessimistic take, there's an arms race to see who can accomplish three things first:

• Who can build an all in one design and prototyping tool
• Who can build a no-nonsense design system protocol
• Who can build a design assets to code/export assets pipeline, preferably as autonomously as possible

More money can help Figma in the race for all three.