misterbowfinger

Interesting, I saw this as the opposite. Without the existence of centralized checkouts, retailers can craft totally different experiences for shoppers. It's in their best interests to keep shoppers in stores for longer. A great example is wine tastings at Whole Foods locations - it's clearly a social event within a grocery store.

I'd say there's going to be even _more_ opportunities for social interactions at grocery stores like Amazon Go.

To your point, though, the "marketplace" you're talking about is the ambiguity between the consumer and the worker, aka Marx's point about the commodity fetish. That's something that's existed since the late 1800's, though. I don't think that's going away anytime soon.

Although I can see something similar to a farmer's market run in the same format as Amazon Go. I haven't thought through all the edge cases yet, but it feels like a solvable problem.

It's a conversation. Sometimes, it's no big deal, and sometimes, it's fine to deflect and say "I'll make a ticket for it".

These are good guidelines, I generally agree with all them (and I've messed up tons of times as well). It's important to note that you should write comments for the developer, whoever that is. That means understanding their perspective, their experience, and what they want.

Some developers really won't take offense to many of the "bad comments" suggested, and could even feel patronized if you take some of the guidelines - for example, over explaining something could be overkill for someone who just made a mistake.

I've also found that taking a lighthearted approach to code reviews really lightens up a stressful interaction. Simple jokes, comments like "dead code! woo!", and whatnot make a difference.

And lastly - don't forget positive comments!! Celebrate people's work when you can!!

Original paper: https://arxiv.org/pdf/1801.03074.pdf

I think the idea is that we all make mistakes. The best we can do is admit them and learn from them, just like any other postmortem.

Also, they did update the erroneous articles:

https://fivethirtyeight.com/features/lots-of-people-in-citie...

https://fivethirtyeight.com/features/the-worst-internet-in-a...

> All software platforms should be required to offer a legitimate opt-out, one that enables users to stick with the prior version if they do not like the new EULA. “Forking” platforms between old and new versions would have several benefits: increased consumer choice, greater transparency on the EULA, and more care in the rollout of new functionality, among others

Interesting. Although if this applied to all software platforms, I suspect startups are going to be hit a lot harder than the big co's. Maintaining this level of "forking" seems like a nontrivial engineering task.

> Eighth, and finally, we should consider that the time has come to revive the country’s traditional approach to monopoly

Feels unclear how this would help. It feels difficult to craft anti-trust laws that big co's can't reason their way out of. But IANAL, so please correct me if I'm wrong here.

I get that. I'm happy to be downvoted to oblivion :)

Although, in a lower comment, talking through how the performance benchmarks were about using Redis for persistence was really helpful to me. I don't think I would have ever had that realization had I not asked the "dumb question" at first.

My hesitation with just asking my real question on using Redis for caching was that I didn't really understand what "pipelining" is. I've misinterpreted documentation so many times that I've found it's useful to ask dumb questions, even if the only value is to get validation that you were right.

Lower comment: https://news.ycombinator.com/item?id=16081482

Ahhhh that's this line was about:

> Test performed with AOF enabled

AOF is a type of persistence: https://redis.io/topics/persistence

Most of the time, I've used Redis with (I think) RDB persistence, just in case. Usually we've used it as an in-memory cache.

Ok, that makes a lot of sense, thanks!

That's fair. Although I usually look to HN to hopefully find someone who provides clarity over situations like this. Performance impacts are really easy to interpret incorrectly.

Woah chill out. I don't think it's that big of a deal to ask a question, especially for newbies who find documentation intimidating and tough to get through.

So applications that use Redis mainly for caching won't be hit as hard then?

I don't quite understand what "pipelining" means. Can anyone TL;DR?

totally, for some reason my mind just goes towards the possible negative interpretation

This is really petty, but the phrase "war on poverty" makes my emotional mind think you're _against_ the poor, not uplifting the poor.

>- using a mutable object as default value or in a class attribute

Python noob here. Can you expand on that a little? Or perhaps link a post? I can't think of an example or how it'd impact memory

Favorite quote:

> Delivery dates have often irrelevant but very simple to understand impacts. Good and bad solutions have dramatic but very difficult to understand impacts.

It feels like an obvious revenue stream for content publishers is in education - specifically, MOOCs. "Content" is really access to interesting information and storytelling. That'd lend itself well to highly specialized MOOCs that people would pay for, potentially. (I guess that's not technically a MOOC, but you know what I mean).

Added an excerpt from the post. It seems to be the opposite of what I'm saying.

I really do think about this a lot, but I disagree with what the author proposes which is basically lying or deceiving others:

> Authenticity is rare, but people performing authenticity is common, and being good at that performance can build a fortune. Not just authenticity, of course. Being able to pretend that you are furious is a trick that all great sales people use. And being able to create the illusion of a sincere vulnerability can trick people into trusting you, which is invaluable

The crux of the issue is as follows: is it possible to exercise discretion, but still be authentic and empathetic? I believe the answer to that is "yes".

I also don't believe this is just about your career - it's about your life. In some circles, amongst _some_ people, in _certain_ circumstances, sharing details is beneficial. But not always. You should not overshare with every person you meet. It's simply not to your benefit.

The difficulty is determining when, where, and to whom you share. Sometimes, you just know. And sometimes, you just have to express yourself. That doesn't always mean you say exactly what's on your mind. Simply a facial expression can communicate what you're feeling in a certain moment, but still with respect and dignity.

Authenticity is extremely powerful. Even with a client, being authentic (without oversharing) will garner you a lot of respect.

> And my immediate thought is, "For god's sake, don't SAY that shit around me, I'm someone who has a big say in your career prospects."

Did you tell her that? Why or why not? Seems like a really good opportunity for a teachable moment.

I just don't get how that's different than anything that's not a webapp

Ugh, why did they have to use Flash...

https://tls13.mitm.watch/

I know they mention it here:

> It uses Adobe Flash, because that’s the only widespread cross-platform way to get access to raw sockets from a browser.

But there's really no other way???

it's a free version of 1Password

Isn't this supposed to be solved by better batteries? I'm confused why the supply of energy matters, unless there's a limited amount of time to use it.

I'm not an electrical engineer, so if anyone understands this better, please correct me :-)

Yup, there's a network of angel investors here. But most of the VCs tend to invest in very traditional markets, regardless of founder talent. It's more worth your time to fundraise out in the valley and setup shop in the midwest.

Operating costs here are so cheap, and a lot of uninspired talent around. You can tell because of the sheer number of consulting firms in the midwest. There just aren't enough great companies to keep people's interest. Anyone who's worth their salt leaves, and then comes back when they want a family.

> the difficulty truly isn't lack of capital, it's lack of founder talent (and ideas)

IMO the VC culture in the midwest is also a lot more conservative. The money isn't held by former programmers, as they are in SF. They're usually more finance execs.

Ah yes - the proverbial "ORMs are bad, just learn SQL" post. This is analogous to saying "don't use frameworks". Sound ridiculous? Yes, yes it is.

The law of leaky abstractions applies to many, many things, ORMs included. I would also argue they apply in different degrees, usually related to the design of the ORM (the post mentions SQLAlchemy vs. Hibernate, for example).

But consider the following:

1) Why do people still use ORMs? Exactly.

2) Question 1 but s/ORM/framework_or_widely-used-library

3) ORMs allow you to develop faster, and deliver value

4) Beginners already have a hard time coding, designing, and understanding what they're doing. ORMs provide a nice abstraction over underlying data stores

5) Although fraught with peril, ORMs provide a common interface that'd give _some_ help if you switch data stores

6) Multi-line SQL statements are a huge pain in some languages

Periscope! Interesting!

It's hard to believe that Patreon didn't ask for feedback on this model initially. I'm sure they did, but my guess is that they didn't expect the blowback from people that depended on $1-2 patrons to have such a large impact on their image.

IMO, before Twitter/Facebook, this apology would've never happened. They would've continued to press on with their fee structure and it would've been yesterday's news.

The real question is - is this still a good move for them? Or should they have dealt with the blowback either way?

^^ this, using spec at run time in your actual application logic