Work in a kitchen: Maybe. Actually do a good job, walking in off the street? Nope. There are dozens of things you need to know and be able to do to work well in a kitchen—and those things change depending on what kind of kitchen it is, but one of them that doesn't change is clear, fast, in-person communication, including doing what you're told instantly. A software developer going into a kitchen job and thinking they're hot shit because they're coming from a "skilled job" and this is an "unskilled job" is going to get themselves or someone else badly injured very quickly.

Clean a house: Yeah, probably. Clean houses well enough to be paid for it: Probably not. Clean houses, well enough to be paid for it, 40 hours a week, for years: Very unlikely. That takes not just the skills to actually get each house professionally clean, but the mindset to be able to handle that sort of work for long periods.

Work construction: Almost certainly not. While not all construction requires heavy lifting, most does, and most software developers are not in good enough physical shape to do that on a regular basis without doing serious damage to their bodies. Not to mention the care and precision required to build things that will both look good and last.

Because "be able to do this job" doesn't just mean "has the basic understanding of how the mechanics of it work." It means understanding the details and nuances, being willing as well as able to do it for long periods of time, and being able to do it to a professional standard, not just "good enough for me".

Not even in the same city of right.