A guy

  • 0 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle







  • 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/






  • 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!