sjburt

About 10 minutes. 1-2 minutes to refresh a docker container, ~2 minutes to build a mostly C codebase in the docker container, ~5 minutes to build a bunch of python environments and run unit tests in them. 3 or so minutes due to bad design choices in Gitlab-CI. Project has around 100k loc.

I think we could get it down to 3 minutes or so if we changed some things, but 10 minutes vs 3 minutes doesn't really change the workflow for us.

The cost would be acquiring a training data set that includes data from the more advanced sensor, versus existing catalogs with many millions of images and tens of thousands of species.

I think the AI solution is actually pretty well proven. I use PlantNet to identify weeds in my yard and it's plenty accurate and doesn't require any sort of advanced sensor.

After <time passes>, you can run arc patch --diff D12345 again and arc creates another branch called arc-diff-d12345-1 or something like that, then you can rebase -i onto that.

I feel like phab had a couple workflows that were very efficient and if you ever had to do multiple git operations you were probably using it wrong. You could do everything but the actual code review in the CLI. Github is hampered because they can only use git operations and they just try to figure everything out server-side.

That said, phab certainly has it's idiosyncrasies and anything outside of the workflow that they intended was not supported.

There's no "papers" in the US. You're not required to have a birth certificate or a Social Security card or a drivers license or a passport. There's no list of who is and isn't a citizen.

I think the joke was that the words in the headline couldn't possibly be related. Except that they were.

I assume they mean modernism, the prevailing artistic style of the first half of the 20th century.

I think it's wrong to assume that non-empirical methods can be reliably trusted to give better results. Humans are terrible at avoiding bias or evaluating risks, especially for uncommon events.

Is there a way to get the predicted magnitude?

... where half the proceeds were going to an independent non-profit organization implicated in a Federal corruption probe involving city officials.

  root/
    base/
    a/
    b/

As long as root has a CMakeLists.txt and includes base, a, and b, cmake will figure it out. After the build tree has been built with cmake, you can even run make from the build/root/a/ directory and base/ and a/ will be built. The author, for some reason, does not want a cmakelists.txt in root/ and wants to run cmake from a or b alone so they have to use a more convoluted approach.

After decades of using an alarm clock and sleeping in a dark room, a few years ago I began going to bed consistently around 10pm and allowing natural light to wake me up. It has really improved the quality of my sleep and my feeling of restedness in the morning.

Of course, this means the time I wake up does vary throughout the year, but the time change helps keep it more consistent and even in the middle of winter, waking up at 7:30 or so give me plenty of time to get to work.

I do know people that use lighted alarm clocks and report similar results, but that's clearly just an imitation of the real thing.

They want to run transmission lines at high voltage, so the same power can be delivered at lower current (meaning smaller conductors and less losses due to resistance), then step those down to lower voltages as you get closer and closer to the customer. High voltage AC transformers are very simple and have been around for 100+ years; they're just loops of wire around a core.

High voltage DC transformers would require very modern switching technology, or a difficult and inefficient switch to AC and back again.

sqrt(x*x + y*y) loses a lot of precision if x and y differ greatly in magnitude.

I'd bet that some combination of "Oh, of course it's slow, it's json" and "I'm too important to work on microtransactions" accounts for a lot it.

I've always hated how that's used as an example of recursive programming in early programming education. Invariably, students try a large n, get a stack overflow and conclude that recursion is inefficient, leads to mysterious errors, and must be avoided.

When using the "exec" command it doesn't do that. It just executes one job, not the whole pipeline.

Sure but for what GA costs on a recurring basis, a small camera or two is such a negligible cost and is really valuable for learning.

Matchmaking, promotion.

You press z, type a few letters and then hit tab until you get the thing you want. It's not spatial. If you use ctrl-r frequently it's similar.

I have one. It's fairly limited so you are forced to pay attention all of the time and think about whether you need to take over. You just aren't doing the menial tasks of keeping the car centered in the lane or keeping a safe following distance.

If the system does something you don't like you just grab the wheel or touch the gas/brakes (the control messages it sends are lower priority for the car than driver inputs). It's also designed to disable itself if it sees gas or brake input.

It's really best considered as an upgrade to the stock lane keeping assist and dynamic cruise control found on most cars. Compared to the stock systems it's much better behaved (my stock Toyota system will happily drive straight across multiple lane lines in certain lighting conditions and it astounds me that such a thing could be sold), but it is a long long way from Level 4.

My experience is that they get about 45 minutes into the lecture, realize that there was an error in minute 10 and spend the rest of the period trying to fix it before telling you to check the book for the correct proof.

I think because both the discord server and the facebook pages were cesspools of sexist/racist content, that during the GME frenzy they got even worse, and the services knew that they would face increased media scrutiny with all of the increased attention. The hit pieces practically write themselves.

These seem like totally different roles. And the hours I've spent staring at the AWS console trying to figure whether I need "Elastic Beanball3" says to me that Amazon could use maybe just a little architecture. But I'm sure the Beanball Principal Engineer is quite proud of their resounding impact.

So runners are a good example: The runner config is stored in a config.toml on the runner. If you want autoscaling runners, it gets very complex so you might want to version control it or back it up, but you have to store your AWS secrets in this config.toml. It also contains hashes that have to be matched with settings in the UI, and of course, tags, which need to be tied into your .gitlab-ci. UI configuration changes take places instantly and there's no undo. So you have configuration in 3 places, only one of which is version controlled. And lets say you have some new runners with new tags -- you aren't going to be able to run an old pipeline on the new runner.

I think "Australia devoted to agriculture" is meant to be a separate clause.

I think the experience for most voters is having to pick 7 people out of a list 20 names of people they've never heard of. 50% will be educators of some sort, 25% will be real estate agents or developers, and 25% will be raving lunatics or anti-vaxxers.

Sanitation engineer was always a joke, I think.

But engineer also referred to train operators and the third crew position on an airliner is typically a "flight engineer" so there is something there.

Gitlab's CI/CD a minefield of bad design decisions piled upon each other. Not worth it unless you're stuck with it.

You can also just use cp, and then you don't need to worry about the block size. Really only need dd if you have to limit how much data is read.