only_as_i_fall

I think the takeaway from. The article is that if this I'd the case then interviews should drop all the meaningless jargon and just ask a candidate to sketch out a solution to a problem where they would have to think about atomization of DB operations.

I've used an old roku express, a roku TV and a new 4k roku (forget what the model was but it was made in 2020) and they all have the same app problems

Disney plus crashes more often than not in any given watching session.

Hbo Max tends to crash on the menu about 50% of the time.

Netflix crashes fairly often but not as bad as those other two.

I think it's still the best single solution for streaming but they really do need some quality control on their apps.

Having to wait for your TV to restart in the middle of a movie is never great.

Thats why you go suburban. Low COL but high quality of services and infrastructure. It's amazing what you can accomplish if you don't care about the solvency of your community :D

If you follow that link which says "Read the Story Here" they have this json example which has a list of employees and then info about the pagination of that list. The caption is this

>If you look closely, this JSON document mixes the data employees with other non-data keys (headers) such as count, currentPage, and pageSize in the same response.

But they don't explain at all how Changing the data format fixes the underlying issue of mixed concerns in one data object.

What's your issue with toll cameras? The law is pretty clear in the US that you have no right to privacy in public, and public roads are no exception.

You can fight the fine if it wasn't you in the car and if the picture they took of you is unclear or looks like someone else you can get out of it.

Assuming you're recognizable in the picture what's the issue with that?

Maybe we should stop worrying about it and just fine the car owner. If implied consent laws are legal surely agreeing to be responsible for your own vehicle on public roads would also be permissible under the constitution.

Also, the systems in place for toll road entrances seem to be doing a good enough job. Why can't the same thing be implemented for traffic cameras?

You could pretty easily change that though. Having a cop drive around in a patrol car seems way less effective that if the same resources were used to pay someone to look at traffic cams and send out fines for dangerous driving.

Couldn't you be accused by a prosecutor based on video evidence?

I get that having some private company collect fines directly would be bad, but couldn't they solve that with a simple manual review process by law enforcement?

This is obviously a silly case but I think traffic cameras are one of the few places surveillance could actually be called for.

I'm not sure what the perfect system looks like, but the current system in the US seems broken. Not only is traffic enforcement a huge time waste for police, but traffic stops create an unnecessary hazard while failing to discourage dangerous driving.

And then you get far less traffic than you would if your product was listed on Amazon.

In the traditional brick and mortar situation you can open your own shop next to the Walmart or Target or whatever and have roughly the same visibility. In the online space though rolling your own shopify store is a massive handicap similar to if you weren't allowed to build within 5 miles of a large box store for fear of competition.

A huge number of people literally only shop on Amazon or at least look at Amazon before other locations because they believe it to be representative of the marketplace at large. Maybe that's their loss, but when you also consider Amazon's huge logistics network that nobody else is allowed to use.

What's different is that Amazon is also an extremely dominant platform for other stores.

It'd be like if Walmart came to your small town and signed a deal with the local government that stores had to carry their brands in addition to their own or pay higher taxes.

The problem isn't the mere existence of store brands, but the use of anticompetitive practices to promote those brands.

Might be too broad. Especially as the scale gets smaller I think that non-quantitative aspects can reasonably affect who you want to do business with. For example, if I'm annoying and rude to my local mechanic and he starts charging me extra to deal with my bullshit I don't really see a problem with that.

There does start to be a problem however if he's the only mechanic in town or if he charges more or less based on race or some other protected class.

I think it's a very hard in general to find the balance on problems like this one, and I don't expect you can come up with a one size fits all rule.

Maybe we just disagree about what constitutes best practices. I can't speak much about Java land, but I wouldn't describe rebasing in general as a best practice without further context. If you're working on a team that always rebases feature branches then your preference for not rebasing doesn't seem valid to me.

Doesn't that kind of imply that everyone's opinions are equally valid? If 95% of your profession is on the same page with a certain practice then I'd argue it's really not reasonable to go against the grain without a very good reason.

I think "best practices" strikes a good balance between things that are personal preferences and things that are laws.

It'd be cool if this would decrease the number of antivaxxers, but actually it probably won't and Google really shouldn't be able to do this anyway.

Perhaps if YouTube didn't have almost total market dominance it would be less problematic.