tinyVoltron

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

Note to self: take up lock picking.

I started 3d printing during COVID when people started talking about printing masks. I realized quickly that that wasn’t a great idea but I had the printer at that point. Discovered quickly that it’s was fun and useful for all kinds of stuff.
Printing lead to microcontrollers and minicomputera as I came up with cool stuff to print for neat home automation and various other useful tools.
This led to having a couple Raspberries kicking around which led me to extensive, self-hosted home automation. That’s my current obsession.
I’m wondering where this goes next.

Screw that. I’d shock myself while they explained it just to make sure they weren’t lying.

You chose unwisely.

How did they not put any guns?

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/

They said what they meant.

It’s a schooner!