And in the spirit of the Uncomfortable Ruler, this has the same frustrating design flaw: the scale doesn't start in the corner so you can't butt it up against something and use it like a depth gauge!
Assuming an architect doesn't have the right kind of workshop needed to make them herself, the capital outlay to tool up any of those objects except the broom and the fork (for which you'd take existing products and modify) would be pretty enormous. The ruler probably would be the easiest - a company that already makes steel rulers could likely make it for a relatively modest set-up cost.
Git information is extremely useful to me. I notice colleagues who don't have that tend to struggle using git on the command line and use git status nearly every other command (much as I tend to do when I'm remoting into a shell with a plain prompt).
Python venvs are useful too if you have a shell for running the program and other shells that just happen to be within that directory.
I could see the case for that if it were accurate. But every implementation I’ve seen doesn’t give you accurate Git information. It gives you the status of the repo as it was when you last ran a command. If you are working on the repo in a separate editor window, then the Git information in your prompt is usually incorrect. Incorrect information is worse than no information. Besides which, your editor normally provides this information as you are working on it. Why does outdated Git information belong in a prompt when there are more convenient places to get the correct information?
I can honestly say that has never once been a problem I have had, and I've had git information in the prompt for over 10 years.
Also how is "enter" less convenient than literally any other command that you'd still have to type and run to get up-to-date information in a command line?
> I can honestly say that has never once been a problem I have had, and I've had git information in the prompt for over 10 years.
What do you mean exactly?
Are you saying it doesn’t get out of date? i.e. you never change the state of the repository outside of your terminal session? I don’t think that’s reflective of how most people work.
Are you saying that it gets out of date but that doesn’t matter? If that’s the case, then it’s a strong hint that the information isn’t as useful as you assume. What’s the point in constantly, repeatedly showing incorrect information?
Are you saying that you work around the problem by hitting enter whenever you want an update? Then aren’t you doing the same thing as your colleagues who you mention struggle with Git? Hitting enter in your case is essentially a shortcut for running `git status` over and over, except you are doing it with literally every command you run instead of only when you need to.
> Also how is "enter" less convenient than literally any other command that you'd still have to type and run to get up-to-date information in a command line?
The issue is the space and attention used by repeatedly showing outdated Git information. Space and attention are at a premium in a terminal window; you can’t just dump all the information available to you in there for free.
> Are you saying it doesn’t get out of date? i.e. you never change the state of the repository outside of your terminal session? I don’t think that’s reflective of how most people work.
That's what I do, I use git directly for trivial stuff and lazygit for more complex stuff, both inside the terminal.
> Space and attention are at a premium in a terminal window; you can’t just dump all the information available to you in there for free.
That's true. I've tried "absolutely nothing except %", "very long and fancy prompts" and the current directory (often aliased), the current git branch and % is what works well for me.
To a lesser extent, I've done a few Java version migrations so it can be useful for the Java version to be printed so it's obvious if I've got the wrong JDK enabled. Python fell under this, but I don't think I'll have to worry about having one project be Python 2 while the others are 3 anymore.
Honestly, sounds low. Technical debt is just like real debt: a useful tool to allow you to borrow against the future to get things done today, and an existential threat if not serviced before it gets out of hand. A tool that everyone else is using to the hilt and if you don't you'll be at a severe disadvantage. If it accumulates, it can sometimes be cleared down to a sustainable (and even useful) level through a painful multi-year process where no-one is having fun and you don't get to do many nice things you thing you should be able to.
That's a funny one too me, because they do some very good journalism that spans many many years on many people up to no good. Frequently, they're the only ones doing anything more investigative than rewriting press releases and newswires and they must have an absolutely enormous library of material on public figures to be able to connect the dots that they do.
But when they report on something, it's gone from the public view in a few weeks as the only place you could find it would be your own archive, assuming it goes back that far (and you wish to dedicate the space in your house), or a major library of which there are only a handful in the country that would maintain an indefinite archive.
Something more impactful than a report on another suspiciously "bungled" contract by a councillor would be to be able to see the other articles they've done on that person over the decades. Even if there was, say, a year-long delay in putting them in the archive, there's a difference between "Eyes passim" (doubly irritating as there's also no thematic index and hundreds of back issues you'd need to look in) and seeing the older reports in front of you.
Does that stay true when exercising? At rest, with a tidal volume of 500ml ish, lungs are least 5/6 full of stale air, round down to 3% ish CO2.
When exercising, the tidal volumes are far higher (2-3L), and you breathe faster, so the lung air is at least twice as fresh as it was at rest, probably more, since fresh air is functionally 0% CO2, and you're moving maybe 6 times the gas volume in each direction.
Does that massive change in volume and diffusion gradient (at least at the start of a breath) means that you might be able to tolerate a higher CO2 level in the inhaled air?
And laser microphones. There's a whole range of technologies out there that people mock as unrealistic when they appear in SciFi, but turns out we can make.
