cpitman

For anyone in the Los Angeles area, the Nixon Presidential Museum and Library has his childhood home in the premises, which is a Sears Kit home built by his father. You can tour the inside (but not the second floor, thanks to OSHA regulations, an agency founded by Nixon).

One of the anecdotes they shared is that the kits did not come with fireplaces, so his father learned to mod kit based comes with a brick fireplace and made a side gig of doing it for others.

Edit: looks like the National Archives has a virtual tour of the home here: Richard Nixon Presidential Library and Museum - Birthplace, United States https://artsandculture.google.com/streetview/richard-nixon-p...

I've been finding games by watching the @RealCivilEngineerGaming YouTube channel (https://youtube.com/@RealCivilEngineerGaming). It let's me see what the game looks like, and his taste in games works really well for me.

I think that unpoly(https://unpoly.com/) would be easier for that use case. htmx generally expects succesive http requests to only return the fragment of html that will be swapped into the target, not the entire page. So you generally want something server side that can check the request and either return the full page (either for a first hit or disabled javascript) or return just a fragment (an htmx request).

Unpoly has similar goals to htmx, but by default works with full page responses, swapping only the identified content in the page.

That seems like a bad representation of what happened. A teacher was invited to join a group chat at the beginning of the term. And then students started to use the chat to cheat, not realizing the teacher was part of the group. It's pretty clear the students were at fault, while also being really sloppy at cheating.

Looks like one of the authors has a working draft here: http://www.brycejdietrich.com/files/working_papers/dietrich_...

Keep in mind what this means with RHEL's support lifecycle: that Xorg will not be included in RHEL 10 (which is probably still a long ways out). It stays a supported part of RHEL 9 until at least 2032.

Notices like this give our customers a lot of time (literally a decade) to find replacements for anything being deprecated.

Because it is not generally possible to determine that the result is undecidable, when maybe searching a little longer would find it.

AMQP (the protocol) basically requires this kind of behavior. Whenever anything "bad" happens, the state of the session becomes unknown (was the last message actually sent? was the last ack actually received? etc), and the only way to correct it is to kill the connection, create a new session, and start over.

Fixing that really needs to be at the protocol level, like a way to re-establish a previous session, or rollback the session state, or something. It's definitely hard mode for library authors to fix this in any kind of transparent way.

The qpid client libraries supported automatic transparent reconnection attempts, but in the end I usually had to disable them in order to add logic for what to do after reconnecting. IE, I needed to know the connection was lost in order to handle it anyways.

Finance, Human Resources, Internal IT, Recruiting, Facilities, etc. Any role that the customer is not directly interfacing with or paying for.

Many of the responses here are talking about how to vendor/cache images instead of depending on an online registry, but remember that you also need access to a supply chain for these images. Base images will continue to be patched/updated, and you need those to keep your own images up to date. Unless the suggestion is to build all images, from the bottom up, from scratch.

If you have a method for hiring exactly the right people, that those people will put up with (ie a process that filters out "dead weight" but does not filter out high performers), then that is a startup right there. But overall, no one has magical hiring process that doesn't involve finding out actual performance after they start.

This looks quite nice. I run a server which is already RHEL+podman+generated systemd units, but this both simpler and more declarative/idempotent than my current setup. Anything that helps convince people that containers running on a single server can be simple, and doesn't require an entire k8s stack.

It means varying levels of "not a central data center". For anyone wanting to do edge, you first need to understand what it means to them. Sometimes the edge is distributed sites that still have a rack of hardware, say in factories or distribution centers. Sometimes it is one or two computers at all of your stores, but still "general purpose" hardware. And sometimes it is purpose built devices, like Point of Sales Systems or a radio on every train. Etc.

Each form factor has different considerations, and each application different design patterns. For example, at a retailer I worked at each store had a message broker, and orders would be sent through that broker up to the central data center. If/when the store was disconnected, it could continue to queue up orders until the connection was restored. As opposed to housing everything in the data center, and needing to fall back to a paper process if the internet goes down.

Sounds like it was actually a perfect question. It made it crystal clear that you and the company didn't see eye to eye on work conditions, and that neither of you would be happy working together.

#1, estimates have no impact on the time it will take to complete, is not generally true. Underestimating tends to significantly increase the amount of time a project will take, since the team gets pulled in to constant fire drills, rescoping, etc to try to figure out why they are behind schedule and how to get back on schedule. Overestimating tends towards the project taking longer because less pressure allows scope creep (ie Parkinson's Law).

Given it is pretty short, easily one of the best investments I have made in time.

Don't worry, it's super extensible! All you have to is write a java class with the right interface, modify a massive spring xml file, and inject your class at the one right place to make everything work!

Hope you didn't want documentation on the class interface though. I'm sure you can figure it out from context...

FWIW, there's still a pretty big gap between a single static mesh and something that is a usable asset, say in a game. Maybe this could provide a shortcut for a modeler to get started, but it still is going to take a lot of skill from that point.

Here's a non-conspiratorial reason: many engineers are not used to the uncertainty involved in day to day business negotiations and sales, and allow themselves to be stressed out what they see how the sausage is made. The reality is that lots of deals fall through, and that is normal. But if someone hasn't had a front row seat to that, they start wondering "are we failing?", "am I not doing a good enough job?", "is our product a failure?" etc etc.

I say this as someone who leads a team that handles the promotion and enablement of engineers into a role where they have a lot more visibility into sales and strategy, and have learned that they really need to have someone reassure them until the point that they realize that things are working out just fine.

That being said, I'm not sure of the wisdom of inflicting that stress on employees that don't have a need to see the Backoffice negotiations. Is there anything productive they can do, other then getting stressed?

This is the most real answer so far. Knowledge is being lost in the field, very few want to learn the field, and it is needed in just about every company. Companies that existed in the 80s and have managed to migrate off of the mainframe are the very very small minority.

Pay is part of this, but I'd posit that most programmers would need to be paid a hefty premium over standard rates to be will to work on what they consider legacy or dying technology.

That doesn't sound quite right. When a object attaches a handler to an event, that creates a reference from the event source to the event listener. Until the handler is unattached, the event listener shouldn't be collected by GC, since it is technically still alive.

This lead to one of the more entertaining C# memory leak stories, where Princeton's entry to the DARPA Grand Challenge ended up failing because every frame they detected obstacles, created a class for each, and subscribed each obstacle object to an event. They missed that the event subscription was keeping those objects alive, and every piece of tumbleweed in the desert helped leak memory until the car just stopped! https://www.codeproject.com/Articles/21253/If-Only-We-d-Used...

During the pandemic (and also during the response to 2008 recession) the Fed has been injecting cash into the market by buying Treasury securities and mortgage-backed securities. This is what "Quantitative Easing" is, and is a relatively new tool used by the Fed that they started leaning on when interest rates really could not go much lower. (https://en.wikipedia.org/wiki/Quantitative_easing)

Now the Fed has a really large backlog of these securities, and they are starting to unwind that by selling those securities off, effectively removing cash from the economy and slowing down economic activity (and therefore hopefully inflation).

Not taking a side on this, but those are all heavily lagging indicators. IE, those are all almost 30 years after college. The current ranking can be highly different from what it was a generation ago.

Random thought, would you use a fundraising website to be the middleman in making donations, with commitments to not share personal information beyond your name?

Exactly, this would actually be history repeating itself. The original "gas stations" were pharmacies that added a gas pump to bring in customers, sold at a price that didn't bring in much profit but got customers in the door.

This also assumes you feel safe talking to police in the first place.

Thanks for the link, it is an interesting and obvious way to have clearer conversations.

Multiple types have a recommendation to use "turbolinks-style transitions", which was new to me. So I did some research, and it's basically another take on "just render html server-side, and let a framework take care of AJAX-ifying it". I've seen some attempts at this before, like the UpdatePanel's from ASP.Net Web Forms back in the 2000's.

It looks like Turbolinks itself is defunct, but has been superseded by Turbo (https://github.com/hotwired/turbo), and I only see chatter in Rails communities. It also looks like there are some other alternatives.

Are people actually using "turbolinks-style transitions"? And if so, what are you using how is it working out for you?

It's wrong in so many ways:

1. Just because something is open source, doesn't mean you cannot get support for it. There are plenty of companies that offer support for open source software, and yes, this costs money. But the general rule of thumb is that $1 of open source support replaces $10 of proprietary revenue.

2. All software has licenses, even from proprietary vendors. But proprietary licenses have no standards, each and every one should be reviewed before acceptance. And they can also change at the drop of a hat and _you have no recourse_. Having a standard set of licenses, and a community that could support a fork are both value unique to open source.

3. Reviewing compliance is a thing with or without actually using open source software. Even if you say "we don't use open source software", that doesn't actually stop anyone from doing some copy-posta of code from some website.

Would you suggest companies clawback equity when it over performs?

This was fun! All I want is some music and sound effects!