tinyVoltron

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/

The rich own the people that decide taxes. They own the media that influences the masses. In many cases, they even own the prisons thereby giving them incentive to “encourage” lawmakers to make more stringent laws to put more citizens in prison. The rich own everything. Our entire culture is rigged to give them more money and more power. The only advantage we have is numbers. Sometimes, violence is the only choice. They certainly wouldn’t hesitate to use it against you. They would just get the “authorities” to do it for them.

I got the 5 a few years back. Great printer but I didn’t like the bounce in the platform so I printed stabilizers. Didn’t like the placement of the extruder moved it up top. Added the HeroMe. Still didn’t like the bounce of the plate so added a second z-axis. Added direct drive extruder. Linear rails. SKR mini. AC bed heater. Klipper. Mosquito Magnum. Prolly some other stuff. About the only original parts are the frame. I used it to learn how to print. And I printed some great stuff along the way. But it’s good now. I pretty much just print. But I really like that Bondtech LGX. Might have to try that out. :-D

It’s not family without a pizza party.

They give many fucks about what their donors want.

Your retraction speed might be a little fast. 20-30mms is usually what I use. Only use the part cooling fan on the bridges. Speed can be a bit interesting. PETG is stringy. I typically print PETG pretty slow. 40-50 if I’m going for fine detail. Would probably increase the temp a bit too. That’s a bunch of wild-ass guesses but it’s where I’d start.

DevOps is fun and you’ll learn a lot in a short amount of time. You will have to learn a bunch of stuff about automation, how different technologies are built and deployed, source control, etc. It’s a steep learning curve but awesome if you’re up to the challenge. It is never boring. I’ve been working on DevOps processes since before it was called DevOps. I’ve always been happy to be in this sector. Keep in mind that there is no set definition for DevOps. Some purists will argue what I do, setting up the tools and automation then let the devs do their thing, is not DevOps. They might believe that DevOps means developers set everything up and support everything. Of course, that doesn’t scale. Other companies just rebrand build engineers as DevOps. That’s about the most boring thing I can think of, besides QA. :-) Good luck!