iofiiiiiiiii

If it were not a substantial research effort spanning years, it would not get funded. This motivates academic researchers to ensure that every topic is explored thoroughly and at great length.

I used to run my personal website on Hugo but after a few years I wanted to upgrade the Hugo version and was suddenly out in the cold - there was no real path to upgrade, everything only works together once and as soon as I started upgrading, there was mismatch between the generator, the theme, and whatever widgets I used.

Moved to wordpress.com since that. No more worry about keeping things working, I can focus on the content. Admittedly, the horrible load times of wordpress.com sites are causing me to look at alternatives - waiting 5 seconds for the homepage to show up is not really acceptable.

I wish someone made a hosted version of a static site generator - they maintain the compatibility between individual components, provide some online editor for content, but the output is just a bunch of static files generated from this. Have not found one so far but if you know one, please drop a line!

Yeah, loved the Chinese series! It was very true to the book and exceeded my expectations!

What are the differences in the design principles of the AWS Rust SDK compared to AWS SDKs of other languages? In what ways is it special to work best with the Rust ecosystem?

I recently saw people get rejected at the gate when they tried to board ahead of time in Frankfurt, so it sounds like they are starting to enforce it.

I once asked the developers about this and they did not seem to understand what the point of a TPM even is, unfortunately.

Agreed, I find myself having to think orthogonally to common sense whenever I try to use one of its SDKs. Nothing works the way you expect it to, everything has 3 layers of unnecessary abstraction and needs to be approached via the back door. Many features have caveats about when it works, where it works, how much it works, during what phase of the moon it works and how long your strings can be when Jupiter is visible in the sky.

That said, if we disregard the leaky SDK APIs and half-implemented everything, it does somewhat deliver on the pluggability promise. Before OTel, you had bespoke stacks for everything. Now there is some commonality - you can plug in different logging backends to one standard SDK and expect it to more or less work. Yes, it works less well than a vertically integrated stack but this is still something. It enables competition and evolution piece by piece, without having to replace an observability stack outright (never going to be a convincing proposition).

So while the developer experience is pretty unpleasant and I am also disappointed with the actual daily usage, from an architectural perspective it opens up new opportunities that did not exist before. It is at least a partial win.

While some of the SO practices can feel dumb, I wonder what is the tradeoff we are making here? Could it be that for whatever reason (e.g. personality) we might benefit from accepting these "dumb" choices because it also brings with it unrelated benefits? For example, might it be that if they were forced to accept "frivolous" statements such as "thank you" (from the example you gave), might it cause moderators to not moderate, and thereby allow in spam & other nasty bits?

It is worth bearing in mind that if we, "good people", complain about moderation, we only see the parts of it that touch our "good posting". There might be plenty of good that moderators are also doing, which only the bad guys see.

Sounds like your files are not static, therefore your problem is not the same as the problem the article is addressing.

What is the state of the art for doing encryption with ECC? The author just says "use NaCl" here but what should I do if I am not in a position to do that but can still use ECC?

My understanding of ECC is that it is not really suitable for encryption as-is, as RSA was, rather it is used for key agreement (somehow through a multi-step process that I do not understand). But it is unclear how much of this is just rumor and implementation limitations.

European context here. It is not even an option - you work 40 hours per week, end of story. Working more than 40 hours per week is seen as something wrong, something you need to bring up with a manager to address because someone's work/life balance has gotten off on the wrong path. It is a problem to be addressed.

We have high flexibility in terms of when we work - we can do 4x10 hour days or work a weekend to take some days off in the middle of the week, things like that. But this is an option for the employee, not something the employer can enforce on anyone - the choice is always your own.

If there is a deadline that cannot be met, this means:

1. The company needs to work with the stakeholders to set proper expectations about what will and will not be delivered, perhaps cutting up the work into multiple iterations.

2. The problem should be raised in advance so there is time to address it and prepare the stakeholders to face the facts. If an engineer speaks up on the last day of a 4 month project and says "actually we cannot deliver it, we need one more month" then that is a problem with that engineer's performance (he should have communicated the problem earlier) and/or a lack of leadership (someone should have noticed/cared by then!). It does not change the facts of #1.

This is based on a bit more than 15 years of experience, very consistent from mid-size company to megacorp.