le front end not actual work amirite

I mean yeah it would be nice but software isn’t perfect and validating html is not a sexy feature.

for content sites, stateless is fine. for web apps you need states of all different kinds. even the smallest detail is a state in an application.

endpoints themselves are stateless, but the web application is stateful. you only have to build the world once, and its much friendlier for end users.

well, no. because broken html can still function sometimes. but most importantly most of html is not even “broken”, just not “adhering to the complete standards”.

html is just formatting around the content. even completely devoid of html you can still see things. we’re not writing latex here and no one cares things are a little fucky.

as far as generated html go, you’re more likely to break it further if you fuck with it anyways.

you can setup a on-save script to force you to commit when the number of changes is greater than a certain number from the previous commit.

it means you commit too infrequently. your commit messages should be able to describe what u just did within 10 words.

uh in any actual company you almost never push to origin master. so I think it’s a joke.

you can do it like you weight 6v6 then 3v3 then for the last weighing you weight the 2 out of 3.

or you weigh 4v4 to find out which grouping of 4 the light weight person is in, then do 2v2 and 1v1.

it’s top 5%…

I did look it up and there is only 1 case from 2000 that set the high bar at 125. it’s not really representative of the whole.

mind explaining?

grid and responsiveness are not antithetical. I mean the concept of grid had been around for like a decade, see bootstrap.

you’re perfectly welcome to throw hand rolled html/css/js on an ftp server

its an option, but most ppl do eat food still. simply because they enjoy the taste more.