Cwizard

I still don't understand, this is a list of accidents so what? How many people are injured/died? How does that compare to other sources of energy, other sectors? How many of these were due to human incompetence and how many where due to natural disasters that killed more than the resulting nuclear accident? How old are all these plants? If we would iterate on the design of these reactors how safe can we get them after 1000 plants?

> And to compare them with coal plants is classical whataboutism. "They can't be bad, because I found something other that's bad as well."

I disagree, I am saying we should replace coal with something that is orders of magnitude safer. Nation who will disregard nuclear will be stuck with coal/nat gas for a very long time. For most of the world there aren't even theoretical models for getting to 100% wind/solar if stable grid is required with CURRENT demand, let alone future demand.

I don't have a source handy but I disagree we only have supply until 2080. Maybe with current known reserves and without reprocessing.

Germany won't find a story site because they don't want to find one. They are looking for something perfect, that is guaranteed to last 1000s of years. Meanwhile, waste water from mining and refining is just dumped in old quarries, lakes, the ocean. PFAS just gets dumped everywhere. All kinds of toxic waste that lasts forever, just dumped no one cares. But when its about nuclear waste suddenly everything has to be secured against the apocalypse.

Look we can argue about this forever, meanwhile China is building more plants that whole west combined and in a few decades they will be energy independent using 100% clean energy.

Why are they unmanageable?

They are only expensive because externalities of other solutions are not captures or are subsidised. Wind and solar are expensive if battery storage is included in most of the world.

Waste is mostly a solved problem. Much more solved that waste management for coal plants in any case (whom also produce a lot of radioactive waste in addition to producing tons and tons of co2)

We have more than enough uranium. Currently only a small fraction is economically mineable but we have played that game before with oil.

Serious question, when has there been a serious nuclear accident? Fukushima was caused by a natural disaster that killed far more people than the nuclear failure did. Chernobyl was pure communist stupidity. This level of incompetence would never happen in a well functioning country. So that leaves Three Mile island?

Meanwhile coal kills millions each year (mostly the old and children).

And what are these predictable green alternatives? Only hydro is reliable and is heavily restricted by geo. We’d need massive breakthroughs in battery technology to make solar and wind reliable in most of the world (by population).

Look up historical weather patterns days with no sun and no wind, you need massive, massive amounts of energy storage.

What do you mean? 2021-22 was peak of the employment market. At least here in Europe. To get a job all you had to do was be breathing. It was insanity. SQL was and still is highly relevant. Especially in data related fields.

Yes, exactly. It works great. But it is not cookie cutter enough for most orgs to adopt which is what led to Scrum, SAFE and what else. And then organisations take those frameworks (often change them to get even more agility out) and adopt them like it is gospel.

I have worked at an org where team members were not allowed to create tickets because that was the scrum master's job and the product owner had to approve all tickets etc. Who can even think that is a good idea??

Not sure what the solution is. There might not be any.

That’s Scrum you are thinking of. Not agile.

I am unfamiliar with Wero. Can you explain why it is an engineering fiasco?

Side note: Looking at their job listings I don't see any engineering positions (with the exception of a security engineer which is a grey area in a bank IMO), only managers and business roles.

I can recommend doing this! It really is not hard to learn the basics of electronics and you will have a better understanding of how the things around you work.

Is dokku multi node?

You can run out of memory and trigger a crash.

I read the “The Art of Multiprocessor Programming” and I don’t recommend it. It is very theoretical. There is no mention of practical performance considerations on real hardware.

Large parts of the theory focus on lock-free and wait-free data structures. Which, while interesting, are not necessary for beginners.

This is 100% fake. Why would they describe the whole interview process before rejecting them? Makes no sense.

Were you ever connected to the same Wifi network? You can probably use that for tracking too.

OTEL always seems way too complicated to use to me. Especially if you want to understand what it is doing. The code has a lot of abstractions and indirection (at least in Go).

And reading this it seems a lot of people agree. Hope that can be fixed at some point. Tracing should be simple.

See for example this project: https://github.com/jmorrell/minimal-nodejs-otel-tracer

I think it is more a POC but it shows that all this complexity is not needed IMO.

And it has to be cloud agnostic because we can’t get locked in!

I like the cloud but it is overused and misused a lot imo.

I had a team of about 8 junior people. We would do a daily morning sync where we went over open tickets. The main purpose of the meeting was to see who was struggling with something and needed help.

In my experience junior people often wait too long to ask questions when they are stuck on something out of fear of looking bad. But if you are junior it is totally normal to not know a lot of things and thus get stuck frequently. If it is something that can be Google’d, sure let them learn to look, but often it is something internal to the company and they just need someone to point them in the right direction.

I would take note on who was having problems and call them throughout the day to unblock the situation. Sometimes I would invite 1 other person into the call to share some knowledge and preferably have them explain it to each other.

In general I would try to make these calls educational rather than just telling them the solution. You want to build up the team so they become more and more independent.

When major new topics came up (new feature, completely new use-case) I would organise a team meeting to discuss the topic and work out a design. I usually prepared these meetings to the point I more or less knew the design we wanted to go for because the team was very junior. This allowed me to led the team brainstorm and occasionally guide them or point out issues.

The key is that you want to try to facilitate rather than dictate. If you dictate too much they won’t learn or learn slowly.

Second, junior people often say they understand something without actually understanding it. Have them explain it back to you. But don’t be too critical when they get it slightly wrong, that can be demotivated.

Also try to pull involve individual team members into higher level discussions from time to time. I would sometimes invite someone to the architecture review meeting. This helps them gain perspective.

Finally I would do a meeting twice a year to discuss their progress and ask their feedback and how they are feeling in the team etc.

This mostly applies to a team full of juniors. I bootstrapped two junior teams this way.

Does not have a SQL API (or something similar). The record layer is interesting but requires your application to be build in Java.

multi-master writes with serializable transactions

What did you use instead?

What will you switch to? I feel like there isn’t a good alternative.

This matches my experience as well.

Data modelling (in databases but I guess that also translates to the application layer to some extent).

A good data model will allow you to get much further with a standard database without requiring horizontal scaling and complex caching solutions. Data models are often also painful and hard to change so good decisions made on the data level are worth their weight in gold if you ask me.

A little like building a good foundation for a house.

You might like: ‘PostgreSQL 14 Internals’ by Egor Rogov

> It implements row-level WAL (Write-Ahead Log) and a non-persistent undo log. This significantly reduces IO operations for write transactions.

What is the downside of doing this? I assume there is a tradeoff?

I didn’t know ‘Table Access Method Interface’ has this been around for a while? Who developed it?

91% of people that filled in their survey I think.

I thought this was a bug at first. Does anyone actually want this?

Why would they contract this out to Cognizant? I would have guessed that their music streaming service would have been a priority for them, and something they would want to do in-house with well payed employees?

What am I missing here?

> We've released a bit about how the AWS Lambda scheduler works (a distributed, but stateful, sticky load balancer).

Do you have a link? I would like to read more about this.

I think for foundationdb to gain traction, someone needs to build a frontend for it with more advanced query capabilities than KV.