tinyVoltron

New England would like to come with you!

We should take CEOs with fava beans and a nice bottle of chianti.

The supreme Court is specifically saying the order is legal. He could say it’s part of his official duties, in which case the order itself would be legal. His official duties include commanding the armed forces. If the president gives an order, a marine or a Navy SEAL cannot choose to not follow that order on legal grounds. They can choose to not follow on moral grounds but that refusal in itself would be illegal. Should it come to that, I would hope the vast majority of the armed forces would refuse the order.
In her dissent, justice Sotomayor specifically said that the president could order an assassination and could not be prosecuted for it. I am assuming she knows more than you are I about how the legal system works.

His job is to support and defend the Constitution of the United states. You certainly can argue that protecting the integrity of the voting system is part of that job.

Reasonable

Who’s to say what’s reasonable.

when challenging the election, that is not an official act

Why not? He could make the argument that the election was stolen and ignoring it is in the best interest of the United states.

And a pizza party?

If someone is blocked I’d be pretty cranky if they waited until the next day to mention it. Blockers are to be dealt with swiftly and with extreme prejudice.

Stand-ups can become so proforma. What did you do yesterday? I coded. What are you doing today? I am going to code. Do you have any blockers? No. It gets a little repetitive after a while.

Right? I find agile purists to be some of the least flexible people I’ve ever met. They are the exact opposite of agile. To be fair though, I have found that a good scrum master can be worth their weight in gold. You always know the status of a project and the individual stories. It can be very, very helpful.

Commonly you will have a relatively broad goal of providing some functionality by the time a project is done. Every sprint, commonly two weeks, you concentrate on producing a piece of functionality that will get you closer to that goal. At the end of a sprint, many teams are expected to have what’s called a minimally viable product that is technically usable. The problem with that concept is MVP almost always becomes production. That results in poor coding that is hard to support. It almost always involves rework later on, often when something is already in production. And you are not crazy. Not having a clear idea of what you’re coding for is wasteful and very inefficient.

It is a methodology to develop software quickly. It has some good things about it. But it can be very heavy on meetings and agile idealists are not very flexible. As many of the other comments say, a mixture of agile and some other methodology or starting with agile and developing your own process that works for your team or project is the best way of managing a project. I don’t understand why so many people don’t seem to write requirements when using agile. Even with agile I will not start coding until I have relatively clear requirements. It is not too bright to start speculative development without really knowing where you are going. https://agilemanifesto.org/