evilotto

There's no "Add to cart" on the page. What kinda online store are they running?

"[The Unites States Supreme] Court has never held that the Constitution forbids the execution of a convicted defendant who has had a full and fair trial but is later able to convince a habeas court that he is 'actually' innocent." -- Antonin Scalia, dissenting on 08-1443 In Re Troy Anthony Davis

I think it was Mark Twain who said about Web 2.0, "In every transaction where money changes hands there is a buyer, a seller, and a product. If you are not the buyer or the seller, then you are the product."

AOLserver was 5 years ahead of its time, then stayed put for the next 10. Back under the name NaviServer it is still being actively maintained, although new development is intermittent. Likewise, OpenACS is still a going concern, but the community is kinda small.

There's still a few .rvt links on the site, so they may still be using a fair bit of rivet.

Or in CSS: https://www.bryanbraun.com/after-dark-css/all/flying-toaster...

The author makes several really good points about how so much of our taxes that are levied and paid in good faith go towards enriching already-rich entities (healthcare, universities, the defense industry).

It's disappointing that the take-away is "join me in having a better way to avoid paying your taxes."

Or look at the right column and apply Godwin's Second Law.

Unless something has changed in the past decade, fork on linux is really slow when you're forking a large multi-GB process because even though the memory is COW all the kernel page tables still need to be copied. This is one reason why large servers will have a separate "launcher" process that is forked early on rather than forking themselves. (the other reason of course is threads).

Meteorologists seemed to feel that Dark Sky was a graphics processing tool, not a weather app.

https://slate.com/technology/2022/12/dark-sky-weather-app-ap...

Is basic fork/exec from a large process still slow or have newer apis fixed that?

I heard a legend at RPI that some students figured out just how big of a job they'd need to submit to underflow the MTS money variable and give themselves a balance of 2^24 or whatever size value it was actually using. IIRC, it was a line plotter job that would have (had they not cancelled it before actually printing and making the operators very sad, which is something you don't want to do) printed a solid black square the entire size of the paper.

The plot of the 1981 movie "Looker" was that models were being replaced with 3d renderings of them.

https://en.wikipedia.org/wiki/Looker

But can either convince the other one to let them out of the AI box?

Cool-Retro-Term gives a fun approximation of an amber CRT.

https://github.com/Swordfish90/cool-retro-term

Parenthood is the Matrix. Nobody can tell you what it is, you have to experience it for yourself.

Oracle's real pricing model is to sell consulting services.

There was an xkcd comic set in the future with the exact date calculated from the stars. https://xkcd-time.fandom.com/wiki/Astronomy

Get this person off your team however you can. When the sh*t hits the fan over one of their own special exemptions (like something fails in production that should have been caught in a unit test) it will NEVER be their fault. They will point the finger at everyone else and complain about how someone else should have done something, etc. Fortunately for you, this person is probably going to leave on their own soon anyway, because they know better than everyone else how things should be done and they'll jump ship.

Short of that, manage up - tell the team manager that this person is a drag on the team by not following standards, demanding special treatment, being generally disagreeable. it hurts team morale even if the junior team members don't say so (they may not even realize it themselves, but it is a real thing).

In the shortest term, as others have said, don't engage. Pick the rules you enforce, and enforce them. Request the additional changes on the PR to meet style guidelines and don't take no for an answer. Don't get into discussions or arguments about the merits of the standards, just say "These are the standards and we're all expected to follow them." If the standards are written down (and if they're not, then they aren't really standards) then cut off any discussion on the merits of the standards with links to the written standards. Use a "chore" conventional-comment (https://conventionalcomments.org/) to indicate that it's just a thing that has to be done.

If you can, make it someone else's problem. Refer them to the standards committee or whatever senior architect is responsible for guiding the standards, and let them handle the argument.

To be fair to the annoying "call us" pricing practice, on your end you need to have a ballpark idea of what you want, whether its number of seats, data size, or whatever the product is sized in. Having that makes the calls go faster and can help you and the salesguy save time if there isn't even a chance of a match.

My first question for you would be why do you want to work at my company? You like working at early-stage startups, and that's not this company. My second question is what would keep you working at my company when something else catches your interest? I would be extremely concerned that you would get bored with a non-startup and leave after a short time for the next big thing around the corner. The 3-year stint is a good point for sticking around, but if the only thing that keeps you in one role is growing the company to $xM, you're probably not going to be happy here to begin with.

There's lots of weird little vortices where the wind seems to start or end in a spiral. I'm guessing it's an artifact of the modelling. Funny, but overall very cool.

I am not interested in hiring someone who doesn't want to stick around for 2 reasons: First, as others have said, it takes time to learn an organization, far longer than learning say, a new programming language. Someone who only sticks around for a year is barely getting their feet wet and is only going to be making surface contributions. Not to mention they usually check out a month or so before they leave. Second, hiring is a pain. It's time consuming and expensive. I don't want to be doing it any more than I need to, and someone who joins with the intent of leaving in a year is only making my job harder.

Space Force.

https://en.wikipedia.org/wiki/18th_Space_Defense_Squadron

I think the problem is that he's selling the maps as a service. A homeowner doing it for themself is different from hiring a professional service to do it.

This sounds like what YQL should have grown into.

https://en.wikipedia.org/wiki/Yahoo!_Query_Language

If the 13-year old had killed someone, they could be prosecuted as a minor and they would go to juvie and their record would be sealed after they turn 21 and they could get on with their life.

But stealing a trivial amount of money from a corporation, well that's certainly deserving of an Internet Death Penalty.

they're just freckles, honest!

As I'm reading it, GCP is ignoring accept-encoding as a caching variable. Certain services (stackexchange API calls for one, but I'm pretty sure it's come up elsewhere) just ignore it entirely from the application.