tinyVoltron

Swing and a miss. https://www.npr.org/2024/06/21/nx-s1-5002265/texas-power-grid-is-challenged-by-electricity-loving-computer-data-centers

Future post - How do I get rid of raccoons in my yard?

And a pizza party?

They should kill his father Hudson instead. That guy was a dick.

I can never hear this song without thinking of Drowning Pool Parrot. https://youtu.be/uguXNL93fWg?si=Hd1oisndOQv3rNtW

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/

Used to smoke 2 packs a day. Quit 20 years ago. Quit because I figured I always smelled like smoke which greatly diminished the dating pool. I missed it every day until I managed to get hooked on nicotine pouches. Was using 10-15 of the 8mg On every day. Managed to do that in secret for years. Quit those about a year ago after my wife found out. Now I get to miss smoking AND nicotine pouches every single day. I love nicotine. I miss it every single day. I think about it all the time. If I ever found myself single again I would go back in a heartbeat. I am salivating just writing this. It is evil shit.

What a cunt.