mpolichette

It wouldn’t hurt to add some cultural diversity to the characters.

I know they’re editable so “I could do it”, but I think it would enhance the main landing page to show some examples... as well as make it more inclusive for the audience.

This is so fun, wasted probably 30 min building mazes.

Put it in ski boots... done and done, I’d buy it right away

I mean, aren’t they pretty much useless within a year of graduation anyway?

I like this one more than our modern equivalent: `covfefe`

I'm not on Zuck's side, and I'm not explicitly saying you're wrong, but this feels like a mix up of the response from Zuckerberg to blocking the Twitter API.

If you have a source for him saying "Yup do it" to an attempt at confusing their users on an agreement... that would be a big news story.

I'm not arguing against the CST format, but I don't think redundancy is necessarily bad or hard to work with.

It can be good because each line is now an independent idea and doesn't require the indentation context, the items can be sorted or moved easily.

As for hard to work with... a lot of editors have multi-cursor support these days, which makes editing these things in bulk pretty straight forward for smaller sizes and then there's always sed and awk. ;)

Given all that, CST seems like it might be cool for building some quick trees like the given UIs you present.

I'd probably keep to to rows for longer storage though.

I am not convinced GDPR is a bad thing yet... What makes you think it is?

This is really interesting and I agree, but I think only addressing facial recognition is missing the forest for a tree.

There is an underlying idea here of a person owning information about themselves and having control over it and making sure a company can not use it inappropriately. I think addressing it as only 'facial recognition' wouldn't go far enough.

So, this is the start of westworld?

If you already have a consistent design language,and those pre-baked pieces, it seems like assembling them visually is the easy part. This would still leave the behavior logic an data flows.

I’d be interested to see new things like this though!

I do think this kind of UI needs an animation, but I don't think its necessary for that animation to be slow.

I too feel like I'm waiting forever for it to "get there". The other thing I don't care for is that it takes 2 steps to go change the language...

This is solved in this app by repeating the language switcher under the top list, but then repeating content starts to break the "Where am I" question.

Serious question, I'm wondering, why you, personally, value other people getting MBA/Engineering degrees over arts?

I really enjoy going to the theater and seeing performances of all kind, just as I like tech/business advances. I want people to enhance the arts as well as the sciences.

I acknowledge the idea of focusing on marketability and "ROI" for someone choosing their own path... However, when providing "access" to education, why encourage someone who could write the next show I want to see to instead consider crunching hard maths that they don't care about?

Getting the problem fixed is about culture as much as anything else.

If there is some legacy reason something cannot be fixed and has to keep returning bad data, then yes, there is 100% a reason to have two endpoints that do the same thing... usually prefixed with /v2/ or something

I agree with this. I’m all for writing checks against values which may be optional, but I don’t litter my logic with checks against code that should provide the appropriate data.

If you’re getting bad data you need to address the issue higher up. Either through fixing your source or if you’re forced into some badly behaving library then you should at most write a wrapper around it and make that as isolated as possible. Then you should start making plans to deprecate that library.

Didn't realize it was a joke, got frustrated and left after 2 clicks and left... decided to check the comments... you win.

Yeah cause our companies love to let third parties “analyze” our code.

I would make the argument that price is part of the product... No one cares (or at best you'll have a really limited market) if you can't make your product affordable.

I'm not aware if this is a public or private prison... but does anyone know if that would matter? Would a private prison be required to evacuate and do whatever it takes to move the prisoners safely?

For living? There’s a lot of choice, I love sugarhouse which is where I am. It’s close enough to hit downtown without being in the “heart of it”. Which, in slc is still not that much... you can easily choose to be further or closer to downtown life depending on what you want. A lot of the tech scene is actually down south by Lehi. I commute that direction about 25-30 min and it’s not too bad.

There are some established big players here, Adobe, and EBay and I think Walmart labs has an office here. I work for Ubiquiti, which is growing out their office here pretty quickly also.

A lot of small/medium sized startups too... Google around for “Silicon Slopes” which is the sort of name the local VCs give the area.

SLC, Utah is pretty great, I almost don’t want to mention it because the tech jobs are great and the state provides a lot to do.. its like a hidden gem no one thinks about because they consider it Mormon land...

There are a lot of companies opening offices out here though!

I don't understand the desire for all the git integration into the editor. I mean, it might make sense because Atom is owned by Github, but why otherwise?

I feel like a lot of their resources are being put towards git integration instead of improving the editor and performance... which are some of the primary reasons people leave for VSCode.

Maybe I'm the odd man out though, since I like to use CLI git directly.

We used this for docs at a previous job... It was nice at the time... since not a lot of tools supported markdown.

However, in hindsight it sucks... all that documentation is so much harder to read in things like githublab... Those things render .md files just great, however, all these old docs look like html and require JS to render...

Just write pure markdown in .md files... view them w/ tooling, don't build tooling into the file...

Thats neat, cool, given that, we are at least only as susceptible as we were before.

The argument in that article is that it doesn't matter what is in the source. The published package has no guarantees to be from the source.

I cant help but think of the post about stealing password credentials from the site you build by surreptitiously inserting extra code into the published NPM package. Except wasm packages seem like they'd be even harder to detect.

https://hackernoon.com/im-harvesting-credit-card-numbers-and...

If you have a web service counterpart you should consider looking into webrtc... the sdp exchange can happen through your site and then they will connect directly

I've always wondered about this... if an EM field is composed of photons which have higher energy than light, how come I've never seen image/video captured where the device is 'glowing' or something as a photon source? Is there something I'm missing that prevents us from detecting them similar to the way we detect visible light?

When I did an internship at a national lab, a lot of the hard rules about security relied on the fact that you had gone though their hiring process and would follow the rules. There were different access levels, for sure, but only like 2 or 3. You might have "had access" but you shouldn't be anywhere you didn't have a good reason for being.

Lyft should be checking on this, running audits and whatnot, but they also should be setting good policy and culture to not abuse access.

Basically, I think its reasonable to both allow many people access and expect them to not abuse it.

Super nit pick:

Is it just me or is it a bit disheartening that they have defined this using the term `thru` which google defines as `informal spelling of through`?

Isn't a legal document about as formal as one can get? I'm just worried it opens opportunity for confusion from the ambiguousness of language.

Slippery slope: Next thing we'll see is a law defining how much of a deduction you get with the money with wings emoji.