The first thing that poped in my head when seeing this: it must have taken quite some time to thoroughly go thought all this to make it. The developer must have a huge passion for LOTR. Seeing all the message that it was build using AI it hugely deminishes this feeling.
Still a very nice looking map.
I totally get that. Sorry if it was a letdown. In reality I built this map as part of a personal exploration of the lore and background of Tolkien's lore, because i am fascinated by it. This felt like a productive way to share my learnings with others in a fun way. I certainly learnt a lot from going through the process.
Maybe it will even trigger that we software developers get more time to optimize our RAM usage while developing instead of implementing that new user tracking feature that is being pushed by the business...
I picture a scene with Richard Crenna knocking on our old fogey's cabin door to ask us to come out of retirement and help hand-optimize software in this new environment
I worked for a company that also used AWS. It was a cloud-first company so we needed to use AWS stuff even if there was a more portable variant available. We needed to run this Localstack to get stuff done. I really did not like using localstack.
If you go around your OS yes that could be the case but you can already have issues using the application from machine to machine with the same OS having different amounts of RAM and different CPU's. But I am not an expert in these matters.
I tried some D some time ago, it is a nice language. Given today's landscape of programming languages I think it's difficult to reason why a program should be written in D if there are more programming languages that overlap in features. Also depends on how fast you need to scale in developers, how quickly people can learn a language (and not just the syntax) so popularity is also important. I work in consultancy and this is what I always factor in for a client.
"Home & Garden Television". Lots of shows about flipping houses, etc.
It used to be far more instructional (Julia Child-esque) before it and Food Network got swept up in the reality TV craze. It still has the "bones" of its former self though.
In the Netherlands we return 30% of your taxes in the first 10. So we welcome you as well. We may pay less compared to the USA but we have health care, better work life balance and we all talk English.
From 1 January 2024, expats who meet the conditions receive the following tax benefits:
- 30% tax free for the first 20 months;
- 20% tax free for the next 20 months;
- 10% tax free for the last 20 months.
So that's a tapered reduction over the first 5 years and the amount of money that you gain after tax is between negligeable and insultingly small.
Basically in its current form "The Dutch 30% ruling" is not really worth it, if you want to move to The Netherlands do it for other reasons, and the advertisment of this mechanism feels borderline disingenious in its current form.
I think it was like that some years ago. Now, as you said, it's really useless. 20 months are just the time to find an apartment, furnish it and get used to the place.
Afterwards you have to pay some of the highest taxes in the world....
Dutch people still speak Dutch to each other so if you were going to live there permanently and wanted to properly participate in society you would need to learn Dutch.
However the average level of English ability in NL is extremely good, you won't meet many people who don't have really good English especially for younger generations. Definitely not the case in e.g. France or Italy
Redis still has a niche. For something like a job queue, SQL is probably fine because adding a few ms of latency isn't a big deal. For something like rate-limiting where each layer of microservice/monolith component has their own rate-limit, that can really add up. It's not unheard of for a call to hit 10 downstreams, and a 10ms difference for each is 100ms in latency for the top of the waterfall.
Redis also scales horizontally much, much easier because of the lack of relational schemas. Keys can be owned by a node without any consensus within the cluster beyond which node owns the key. Distributed SQL needs consensus around things like "does the record this foreign key references exist?", which also has to take into account other updates occurring simultaneously.
It's why you see something like Redis caching DB queries pretty often. It's way, way easier to make your Redis cluster 100x as fast than it is to make your DB 100x as fast. I think it's also cheaper in terms of hardware, but I haven't done much beyond napkin math to validate that.
> But I am not a storage/backend engineer, so maybe I don't understand the target use of Redis.
We use it to broadcast messages across horizontally scaled services.
Works fine, probably a better tool out there for the job with better delivery guarantees, but the decision was taken many years ago, and no point in changing something that just works.
It's also language agnostic, which really helps.
We use ElasticCache (Valkey i suppose), so most of the articles points are moot for our use.
Were we to implement it from scratch today, we might look for better delivery guarantees, or we might just use what we already know works.
You'll be amazed on what the new breed of engineers are using Redis for. I personally saw an entire backend database using Redis with RDB+AOF on. If you redis-cli into the server, you can't understand anything because you need to know the schema to make sense of it all.
I love the idea of PG for everything, but every time I suggest it I get the same answer "When you're a hammer, everything looks like a nail" which makes sense to me, but not sure how to give a good answer to that phrase :(
I mean, that's just a truism - it's not really engineering advice. Maybe Postgres is just a hammer, but when you're building a house there's a lot of nails.
If you've got to store 5 GB videos, maybe reach for object store instead of postgres. But for most uses postgres is a solid choice.
reply