_AzMoo

Yeah, you're right about the liability part. But regardless, as a parent of teenagers, being able to justify an unpopular decision with "it's the law" instead of "research shows it's potentially bad for you in the medium to long term" is extremely valuable.

You don't necessarily need to actually attempt to globally enforce it. It's like speeding, right? Everybody knows the law, and a lot of people choose to break it. We can't check everybody's speed all the time, so instead we selectively enforce.

The real change though comes from parent's perceptions. Right now there's age limits of 14-years-old on most social media platforms, however most parents just see this as a ToS thing, and nobody cares about actually violating it. Once it becomes law, the parents are suddenly responsible (and liable) for ensuring their children are not breaking the law by accessing social media. It's not going to stop everybody, but it'll certainly move the needle on a lot of people who are currently apathetic to the ToS of social media platforms.

There are a lot of countries that don't have extradition treaties with the US.

How does the FBI arrest somebody outside of the US?

htpy is just server-side rendering of HTML. Your routes are returning strings instead of structured data, so from the perspective of responses you're not going to be using Pydantic at all. That doesn't stop you from using it to validate objects you're passing around in your server, but I personally wouldn't do that because Pydantic can have a pretty hefty memory footprint. I've seen over-reliance on pydantic lead to plenty of OOMKilled errors.

It's a bit different for requests though. FastAPI will allow you to define your request schema (application/json or application/x-www-form-urlencoded) and validate it using pydantic, but starlette doesn't do that OOtB. It's trivial to implement though, and if it were me I would probably choose to do that rather than deal with FastAPI's inflexibility.

Why would you use fastapi if you're rendering with htpy, instead of just using Starlette?

There were in the very late 90's, and lots of us were still on dial-up/ISDN at that time. They were usually in asf, rm, avi, or mov format, and were incredibly low quality. This is around the time we were using invite-only FTP servers to share stuff.

Oh good, I'm glad you've got expert knowledge in the domain. I work on software that manages vehicles in mines.

Mining is an incredibly long way away from electric vehicles.

Coupling your API to your database schema is a bad idea. Once you have clients consuming that API you can no longer make changes to your database schema without also updating all of those clients and coordinating their deployments. Advice like this reads like it's coming from somebody that's never stayed in a role long enough to deal with the consequences of their actions.

> Do you also assume everything the DoD contracts for is used by the U.S. Army?

tbh, I would expect most people assume that.

I have a 2021 Subaru Forester and the sensors are a nightmare. The computers are fine, but the sensors are extremely problematic.

Yes they are, it's common in the industry. Source: I work for a RealPage competitor.

> it seems like sso could be cheap oauth in house

It's outsourcing risk. Auth is hard, we all know it (yes, it is hard), and it's cheaper to outsource to a company who has it as their core competency, than hire internal experts.

They can lower supply by leaving units empty.

You can't make it up on volume, your product isn't elastic enough. There's only so many properties that you can own, and financing right now for both construction and acquisition is incredibly difficult. The only viable way for property managers to grow at the moment is to increase their margins for the same product, which as you're likely aware, means either decreasing their costs or increasing their prices. They are doing both.

The argument here (not saying I agree with it) is that it's common to let units sit empty over particular periods, based on other business decisions and an understanding of the market.

eg, If you have a lease that ends in September, the make ready process takes 2-4 weeks, so the unit will be available for lease again in October. There's not a high churn of residents in October-December due to holiday periods, etc. and demand doesn't pick up again until January. Therefore, it's better for you to let that unit sit empty now, because demand is so much lower for the next 2-3 months you won't be able to get the same increase in lease price as you will when demand skyrockets in January.

Another example is an understanding that some kind of amenity will change over a period. eg, a new public transport route is going in, or the property next door is being rezoned and demolished, from an industrial site to a commercial precinct, and so waiting for that to happen means that you can get a higher price on your lease once that happens, to the extent that it will offset the loss from leaving the unit vacant.

The defendants will argue that the analysis provided by the plaintiff doesn't consider these kinds of business decisions and that this part of the argument should be considered flawed.

I find Rust's question mark shorthand and the resulting futzing you're talking about adds a lot more cognitive load for me than Go's verbose if err conventions. I think more than anything this kind of syntactical discussion is just very subjective.

> The same way that as an Australian citizen you don't have to abide by a ban on e-cigarettes in Singapore even if the law is written in a way that says it applies globally.

What? If you're an Australian citizen you are bound by many Australian laws under the concept of Extraterritorial Jurisdiction. This is mostly used to charge for offenses around CSA, human trafficking, etc. but also applies to drug use. While it's very unlikely you'd be charged for violating laws around e-cigarettes, that doesn't mean the law doesn't apply.

So while I'm not going to disagree that writing with pen and paper can be a valuable exercise, the assertion that it's inevitable is utterly false. I am far more effective in sketching out my code design in an IDE than I am on paper, and never in my professional career of 23 years have I had to write out code in pen and paper for a job interview, or even in the job.

Aside from the cents bit, it's like that in Australia too. If something (retail) says $30 then it's $30. If it says $30.95 then it's $30.95. It's very simple. When you're selling wholesale it's different because it's a sales tax, and that's paid by the consumer, not the retail business.

This isn't new though. Before Slack and Discord we were using IRC for this. Facebook serves a different need, and for me, was never the default place for event information. Up until the last 5-10 years we were always using email mailing lists, web forums, usenet, or IRC.

All experiences differ of course, but I am going to be wasted if I drink 6 beers and 3 shots over 4 hours. The same volume over 2 hours would probably end up sending me to bed.

When I'm experimenting or working on something that is dynamic I'll use Miro (or FigJam now), but once I've locked it in I put it in PlantUML and commit it in the relevant repo. So handy for portable, normative docs.

Loved F-117. Chuck Yeager's Air Combat in the same league.

What happens if they don't meet their targets? Do they have to stay back and work more hours without compensation, or do they go home and leave it for the next shift to finish?

I think it's effectively just that they operate out of jurisdictions that just don't care.

>It's literally the exact same thing as in office these days

It's just not. In the office you're sitting next to a person you can lean over to and ask a question. Yeah, it interrupts their workflow, but that's ok when they're supposed to be helping you onboard. Remotely you've got to send a message, wait for somebody to reply, schedule a zoom call, whatever. It's async communication and it's slower, which is OK when you're not blocked, but when you're onboarding and blocked you need to be unblocked quickly because you don't have the experience to know where else to go while you're waiting.

I've done something like this at different points in the past. I once had a group where every Wednesday night we would meet at the same pub for some drinks and dinner with an open invitation for anybody that wanted to join. Some weeks there were 3 or 4 of us, some weeks there were 20.

Had another group where every Saturday morning we would go to a different cafe for brunch. It was a smaller and less dynamic group, and we would organise the venue in a group chat throughout the week, but it wasn't a question of, "who wants to come this week?", it was just assumed we would all be there and phrased as, "Any objections to trying this place?"

Mid-size city in Australia.

In Australia lots of kids are already directly taught about the downsides of social media. My daughter is 16 and has had mandatory classes about it in school every year since she was 12. The problem is the kids don't give a shit and it's the parents that don't understand. This should be dealt with through education campaigns, but it's the parents who those campaigns should be targeted at. If somebody's parents group were going to gossip about them actively enabling their kid to get access to social media when we all clearly know the dangers of it then it would very quickly lead to a dramatic reduction in kids having access.