I would like to know more reasoning behind choosing a frame without diagonals.
I have had to repair many old garages and shacks which had wooden frame but
lacked diagonals. Often we had to push them upright and brace the frame with diagonals to avoid problems in the future.
A cube-like building frame without diagonals or shear walls is unstable and
does not sound so strong or resilient at all.
Aren't older TTL more resistant to radiation because of physically large chip structures? It could be that those chips were already space-tested or radiation-hardened.
Our QT project had about 400 compilation units (header+source, compiled to a separate object file). Many of them were 100-200 lines of code only. Full build used to take 40 minutes. Each compilation unit pulls in about 40k lines of code from Qt through headers. So the compiler has to process at least 400*40k = 16M lines of code. Concatenative build only processes app code (about 50k) plus about 60k of cumulated framework code. This gives about 100 times speedup. Our concatenative build took indeed less than 1 minute.
Just let it get the cert (DNS or HTTP challenge) and then restart/reload the web server. Do not let LE rewrite your server configuration. This was very error-prone before and likely still is. People structure their Apache, Nginx, HAProxy, etc. configuration files in very different ways and it's nearly impossible for the certbot to work correctly in all cases. I'm not sure if this was also the case for the article author, the article contains too little technical information to tell it.
This is definitely the right way to go unless you have a need to take longer trips, outside the country, potentially hauling all your stuff. My life has not been that stable here, I needed to drive abroad some time ago and might need it again. But after some years, I would certanly get rid of my own car.
I'm one of these people driving through Berlin city center streets with a car but I only do it once or twice per week to haul something heavy. I have a car because that's how I came to Berlin and the car has been very useful from time-to-time. I would never use it for daily commute as parking is complete nightmare but I would not get rid of it either. Public transport is very good here but I prefer bicycles.
There is also Facebook's MyRocks which is MySQL frontend with RocksDB backend. It has lower write amplification than InnoDB, which is the main reason why it was created.
I understand the difference is that Nginx Inc. as a company is not in the business of providing a blogging platform or e-commerce hosting while MongoDB Inc. is actually providing SaaS (MongoDB Atlas) which I believe is their major revenue source.
I think that setting explicit job boundaries is a good thing to do. Otherwise you end up with role creep and potential burnout. This happened to me. There is a considerable pressure to pick up as many activities at the job as you can as hiring more developers is hard or impossible at some locations as the demand for developers has skyrocketed. This demand buries you even deeper under tasks once your colleagues leave elsewhere for better offers.
I also live outside US and every legit transfer larger than 100 USD or EUR from my account got blocked. Every time it happened, I had to send photocopied ID, bills, and other requested documents. I got a verified business account with lifted limits and still the same pattern continued. And every time I had to call support, otherwise it took about a month for them to review the documents and unlock the account. At the end I was able to get the money out by small transfers. Now I just require a SWIFT transfer from all my US customers.
And remember that all this works only if you have local meetups or someone to network at your area at all. Living in major city provides a lot more opportunity for this than a small dying town countryside.
I find it also interesting that they only have 1.3M loc of Go given the 15+ teams and hundreds of engineers. I would expect this number to be at least 10x larger. They either still use a lot of Python or other languages or are very efficient at reusing code.
Network effect. I'm a freelancer and clients frequently demand Skype conversations. Asking them to join some Skype alternative site/app X does not work, they just complain about the need of too much tools to get job done. I cannot cause too much pain for my clients as I would lose them.
This technique goes well with two-way binding libraries (Knockout, Angular etc). You give data fields default values as DOM is constructed and replace them with the real values after the actual data comes in. However, DOM reflow/layouting issues remain if some portions of data are conditionally displayed. Then some elements (placeholders) are hidden/removed after loading the actual data and that still causes the UI to jump around.
There was a trademark issue between them and Joyent that also made the node-forward GH repo to go private. They might not be comfortable using term Node.JS on the frontpage.
Bitbucket has issue with cross-referencing. You can reference an issue from an issue but to make a two-way reference you need to edit both. This is a showstopper for projects that use tracker for planning too, not just for logging bugs.
I recognize the situation. Seems like the project is lead by people who have not failed before because of feature creep. If you get paid by hours then keep logging hours and try to be happy. But make sure they know about your concerns and feelings that their decisions may derail the project. And keep looking for a peaceful way out.
A cube-like building frame without diagonals or shear walls is unstable and does not sound so strong or resilient at all.