Cody_C

I prefer relational databases for most cases unless I really need to use a non-relational store. I also use foreign keys whenever possible. From what I have seen, anything to enforce referential integrity is a benefit in most cases. It is more comforting to have a delete fail than have many other queries mysteriously fail down the line.

In most cases, a well designed database covers a multitude of sins and makes life for future you and your future team much easier. Some of the biggest dumpster fires of code I have seen started as a smoldering dumpster from terrible db choices that were made far harder to fix when it had been in production for a few years.

If someone put a gun to a developer's head and threatened to pull the trigger if the database was crap, sadly they would be forced to pull the trigger most of the time.

The most solid fundamentals have been mostly true throughout great software. Even older books can hold a great deal of wisdom.

Engineers now seem to lean on books less, I think it is a great way to learn about tech and programming. Quick searches are mostly optimized to solve one issue. For a bigger scope, I have had great experiences with reading books, including older ones.

Some older titles I have really enjoyed are: Mythical Man Month Code Complete II The Psychology of Computer Programming Joel On Software Rapid Development

I recently read a fascinating book about trees. It was called The hidden Life of Trees.

One study they talked about in the book, tried to find out why pipes were often destroyed by tree roots. Most people assumed it was from water leaking or condensation around pipes. However, the study found that it was actually because the soil was far looser and less compact around the pipes.

It is almost impossible to really gauge all the ramifications of any choice within the analog system we live in.

Every time something like this is found, I think it highlights how little credit we give some ancient people. You have to imagine there were machines they created that were more complex than this that we haven't discovered. There are a lot of people in our current times that couldn't build this even with an entire machine shop at their disposal.

Honestly, one of the biggest missteps we have had in the last 100 years is stopping the Apollo program. We would have probably been on Mars in the 80's and reaching out past that by now for sure. In general, I think a lot of people have lost their sense of curiosity and wonder, that need for adventure and discovery.

From the sounds of it you have a lot of great experience. We have an awesome team and we are currently expanding. Email me at: Cody@Mandsc.com

I'd really enjoy the chance to talk with you.

I've read 1984 and Brave New World. In a lot of ways I think the warnings in A Brave New World are much more subtle in some ways. The "fixes" they come up with in the book for an ailing society are very similar to what people have waded into now. A Brave New World is probably a bigger warning to society than 1984 in many ways.

This does even change vintage car prices, certain places out west (Arizona, Utah etc) vintage cars typically are less rare (and therefore cost less generally.) Whereas snow, the salt used to treat roads and rain will wreak havoc on the frames and bodies in other areas.

I saw an article a while back about the unique properties of ancient Roman cement. It seems that the sea water hitting the walls created a rare mineral when due to a chemical reaction.

https://www.nature.com/articles/nature.2017.22231

I often wonder about how things are built without preservation/archival in mind. We live in an age where so many things are built in so much faster than the past but, with the expectation that they will be replaced even faster than in the past.

That is a cool site. I made something similar at https://glitchstar.com/

I think it is cool what humans make into art.