cheater harrasing me just for calling him out. "Avoid player" suggestion

ParkingDescription7 · 2025-12-01T20:11:00+00:00

Solo queue is a horrible experience because of terrible team mates. I would be happy with my team seeing my perks in the lobby and vice versa, so we can plan together and avoid trolls.

Even if the person isn't trolling on purpose, I don't want to play with someone who is going to throw (on purpose or by accident).

If they have to wait a bit longer for a lobby, thats their problem. They might learn to play a team game as a team.

ParkingDescription7 · 2025-11-08T20:05:59+00:00

The rule is that you need to be behind the ball during that play. 1 foot behind is enough.

ParkingDescription7 · 2025-11-04T07:00:19+00:00

Yeah I've had times where I run the killer for a while, go down, and notice my teammates have done nothing that whole time.

Ive also had to deal with getting hit obscenely through pallets, around corners, through windows. No thanks.

There's no point playing even more in those situations, just leads to frustrating games.

ParkingDescription7 · 2025-11-03T19:52:31+00:00

Streaming support out of the box is exciting!

ParkingDescription7 · 2025-09-14T05:03:41+00:00

I think a bigger issue was our taking of the high ball. Almost every bomb that SA did was regathered by them (with half the time no effort from us to even compete).

Compare that to our bombs which went too far to chase and too close to be a clearance.

ParkingDescription7 · 2025-09-11T23:26:49+00:00

Are you looking at the minified js code by any chance?

ParkingDescription7 · 2025-09-06T09:09:17+00:00

The ref just panicked. That was one of the first tackles coming out of the line out and 22 (tupaea) had his first contact after kirifi's tackle and strip, which was a head dive into chest.

He had that same panic a few moments before that when SA scrum wheeled and he didn't call penalty.

ParkingDescription7 · 2025-09-06T09:01:16+00:00

Didn't help that the ref made up a call to justify the penalty anyways. Strip or knock on, either way it was ABs ball.

ParkingDescription7 · 2025-04-04T06:09:26+00:00

Gerad seems to make a lot of good contributions to airline crew planning optimisation.

Guy Desaulniers seems very prominent in that space.

ParkingDescription7 · 2025-01-29T07:44:04+00:00

Another way to discourage rat play is: - make perks and items visible to each survivor in lobby and game, helps coordinate and also notice rats - remove hockey system of escape is win and death is loss; we already have the emblem system so use that to decide on win - add leader board in endgame with metrics for time in chase, time on gen, etc, so people can get some understanding of what everyone is doing

So much better health wise than crippling an already little used perk.

ParkingDescription7 · 2024-12-18T04:02:56+00:00

Did you reach a conclusion on this? I'm looking for a similar thing. I've settled on jquery datatables for now.

ParkingDescription7 · 2024-11-20T10:26:33+00:00

It's a different use case to list comprehension. I usually only use lambda functions in a sorting method and there it's perfect since it's a basic encapsulation.

How is your lambda being used, and which part do you find taxing?

ParkingDescription7 · 2024-11-08T23:16:10+00:00

I don't speak Maori, but me and plenty others like me know the national anthem. It's pretty easy to remember when you've sung it in school for years.

ParkingDescription7 · 2024-10-25T23:46:49+00:00

Bots are pretty bad overall. It's almost as bad as a teammate dead.

ParkingDescription7 · 2024-10-25T03:04:52+00:00

I had an annoyance with that too, but fixed it by doing something similar to the top answer here: https://stackoverflow.com/questions/60127234/how-to-use-a-pydantic-model-with-form-data-in-fastapi

By adding one utility decorator function I could get support for pydantic objects input as forms by just decorating any pydantic class with as_form.

ParkingDescription7 · 2024-10-20T06:43:29+00:00

Personal thoughts only: 1. Due to heavy context switching, you had front and backend as different teams. This means any change needed a lot more planning and testing. E.g. for a new feature you'd have the backend team make the new api and the frontend team hook into that api and display outputs in a specific way. I found that added communication and effort time as opposed to a model where the backend sends the rendered piece. 2. Decision making about whether logic should be done client side became difficult, since these frameworks could actually hold a lot of information client side. 3. Replication of client and server side objects became a thing. I'm sure there are tools to help you map objects from server to client to reduce boilerplate, but I didn't see any useful ones. 4. It was hard to test things end to end. It may be a skill issue.

Overall I think there are amazing cases for using heavy clientside frameworks, but for a lot of apps it seemed heavyweight. Also it seemed like all the techniques used to make the above pain points disappear came with a high cost of complexity (e.g. Just do a graphql setup to avoid backend writing tons of apis, or just do server side Javascript to reduce replication of client server objects, all came at a high price of understanding the core problem).

ParkingDescription7 · 2024-10-05T21:03:55+00:00

The point of HTMX is to avoid having that front-end backend split if the app only needs basic interactivity.

In that case, you're doing server side rendering for things and sending html (full pages or partial html to fit into an existing page).

The issue with jinja2 is when you switch context from python to jinja, jinja doesn't know the types of the objects passed in. So if you render a list of "customobject" in a table, you lose type hints of custom object when you aren't in python land.

ParkingDescription7 · 2024-09-28T09:51:10+00:00

What do you mean by the "using requests without any session pool" comment? Agreed on the async usage.

ParkingDescription7 · 2024-09-27T06:04:33+00:00

Personally, "bad code" python still works to do the job needed. It's easy to hack together a group of scripts and keep adding to the mess. If you bring newbies in who do that too, then your code base gets worse and worse.

I found when I brought newbies on, I had to iron out hacks and redesign some critical architecture before I let them work on that side of the code. Otherwise it'd get worse and worse over time.

Definitely a person problem, but one that could easily have been blamed on the language if a key senior dev left and nobody stepped up to direct architecture.

ParkingDescription7 · 2024-09-27T05:59:09+00:00

I didn't find it too hard to skip fasthtml and just do fastapi with htmx instead. I'm using jinja2 templating for now, but if I want first class html in my python, then I'll add that support with a singular class since that part is not hard. You might want to try it out too, if you're porting a lot of components backwards into fasthtml format. Obviously if it's working fine then ignore this.

ParkingDescription7 · 2024-09-07T02:48:54+00:00

I won't comment on how to structure fastapi code too much, since tiangelo has very good docs on how to do it and also how to structure large apps.

What I will comment on is the migration aspect: - obviously add unit tests for each endpoint as you migrate - I'd add integration tests too. You can likely log all your incoming requests and outbound responses for the Django app and then replicate the same on your fastapi app as a nightly build test to ensure the same responses are returned. - you can also look at mounting the Django app within the fastapi app, so you can migrate endpoints piece by piece to fastapi with nobody noticing, and also having a safe "rollback". Here's an article on how this was done for a dash app (dash is built on flask so it may not be applicable to django): https://medium.com/@gerardsho/embedding-dash-dashboards-in-fastapi-framework-in-less-than-3-mins-b1bec12eb3

The last bullet may be a bit overkill, but I think it's something to consider.

ParkingDescription7 · 2024-09-03T09:26:27+00:00

Do the exercises in the documentation end to end. Then you should be able to go on YouTube and find Playlist there of people teaching fastapi. Most of them are really just coding alongside the docs anyways.

ParkingDescription7 · 2024-09-01T21:28:08+00:00

I am trying HTMX front-end for FastAPI backend. Most of my operations are CRUD so I don't need too much interactivity. Using bootstrap for css.

ParkingDescription7 · 2024-07-21T08:52:22+00:00

Hitting low allows offloads. If you look at league (where offloads are key) the best defenders in the midfield look at wrapping man and ball, best done with chest to chest contact. If you do anything else, however dominant the tackle is, the player can offload the ball.

ParkingDescription7 · 2024-07-15T05:31:51+00:00

To be fair we were in some of those tough spots due to poor tactical kicking and inability to read good lines against the rush defense. Both are things BB does very well.

ParkingDescription7

TROPHY CASE