Comments by "" (@bryanfinster7978) on "Continuous Delivery" channel.

  1. "This article is rubbish, completely misses the point, and is probably dangerous." Yeah, that's a good summary.
    397
  2. This was the first problem we had to solve for CD. BDD was our solution for thin slices to overcome bloat in a story. We stopped arguing about story points and just focused on delivering scenarios that could get done in 1-2 days.
    26
  3.  @DemPilafian  I used to travel every quarter to support Sun's main distribution center's software. I'd watch them fill orders to make their quarterly sales numbers and then cancel them.
    16
  4. Awesome as always. Made me LOL. "Test all the F***ing time!". People optimizing for reducing keystrokes drive me crazy.
    12
  5. A great message with a lot of lessons that can be applied to others who are struggling. Thanks, Dave!
    10
  6. Awesome advice. Also, never take "no" for an answer, just try a different approach. Never go for a frontal attack against entrenched resistance. Flank them. :)
    7
  7. Those should be implemented by the provider with whatever their xUnit framework is as separate behavior tests.
    6
  8. I've found Pact to be useful for services owned by a single team or closely related teams, but it becomes difficult if the teams are not working very closely together because Pact will break the provider's build as soon as the consumer asks for a change. Pact even suggested avoiding that use case. Awesome find on Specmatic. I've not come across that one yet. Adding it to the toolkit.
    6
  9. It's good to know you're accredited.
    6
  10.  @CanalDoFante  User stories are the wrong tool for building the infrastructure. Define the work for the infrastructure and do it. If a user story depends on infrastructure that doesn't exist, then you're blocked until it does.
    5
  11. That was my full-time job for a few years. There are some strategies for that. It starts with showing success on another team that's less resistive. :) CD is life-changing, if taken seriously. It makes delivery less dramatic and development more fun.
    5
  12. I really like this overview Dave. I'm adding this to our core learning path.
    4
  13. This can be done very well and very poorly. Unfortunately, I mostly see the latter. My first exposure was the former because we were focused on making things easier for our customers, the other development teams. The hype about platform engineering comes from people selling tools. Saying that platform engineering replaces DevOps is like saying transmissions replace cars.
    4
  14. "You guys ALWAYS forget non-web applications. " I've almost always delivered to metal or VMs at the edge with every endpoint representing a different set of active features and configurations. CD made this so much easier. SpaceX releases OS changes for the Falcon 9 from HEAD up to 45 min before launch. They also have the best safety record of any launch system. They do this because branches introduced regression problems. They decided to take testing seriously instead. Take testing seriously.
    4
  15.  @ponypapa6785  stirrin' the pot. :D
    3
  16. Also, a great callout to Gary Gruver's work at HP!
    3
  17. I've done some testing with this. It's OK for boilerplate or for creating a client for an API you don't know well but will need some tweaks. However, some requests yielded results worse than I'd expect from someone learning to program.
    3
  18. When we built a central platform at Walmart in 2016, one of the product goals was to incentivize CD workflows. You could force the platform to use GitFlow, but it would be constant toil to do so. To this day, some teams still request better GitFlow support from the platform. The response continues to be, "that's not on our roadmap." 😂
    3
  19. Not JUST as easily. Having something that can auto-test based on the OpenaAPI spec is pretty useful. I've used other similar tools to avoid hand-coding contract tests. You're right that you don't need a tool like this to do contract tests, it's just a toil reducer.
    3
  20.  @georgehelyar  I worked with a friend of mine who had joined Atlassian recently to get that edit in. 🤣
    3
  21. There are several challenges with the DORA survey when the questions ask about things like "continuous delivery" and "microservices". Using those terms without first establishing a shared understanding of their meaning will yield poor data quality. Like you, I see CD as an extension of CI and that it's nonsensical to have CD without it. However, there are many who think CD is build/deploy automation or the ability to deliver on-demand once per month. Same with microservices. Lacking a precise definition, they'll answer they are using a microservice architecture even if two or more services must deploy synchronously or services are coupled by the database. One possible reason for the "surprising" results is that they are trying to learn too many things at once.
    2
  22.  @user0K  Not knowing how to deliver software well is something I run across frequently. However, I wouldn't confuse your lack of knowing with knowing a better way.
    2
  23.  @dauchande  Sure. If you use BDD to describe the broader behavior then Acceptance Test Driven Development loops mean you can get into TDD and not get lost in the weeds. I "say" people can write tests whenever as long as they never push untested code. I find I spend more time refactoring when I code and then test though.
    2
  24.  @dauchande  I too am old. :)
    2
  25. Strangely, some FE developers seem to think there's a difference between how we should treat UI and services. It baffles me. The only difference is the API. Services provide a machine-readable API. UI's provide a wetware-readable API. Otherwise, we should treat them the same.
    2
  26.  @peterolson7351  Send them some Kent C. Dodds posts. :D
    2
  27. No, Google. "According to its co-founders, Doug Cutting and Mike Cafarella, the genesis of Hadoop was the Google File System paper that was published in October 2003." <- Wikipedia
    2
  28.  @billsmoke4919  That's not a failure of DevOps. That's a misunderstanding of DevOps. DevOps is about improving the delivery flow, not "the development team owns everything required to deliver."
    2
  29.  @StevenBorrie  Should be able to test the UI in isolation and with Jest. I'd always discourage people from testing through the UI.
    2
  30.  @edgeeffect  There is BEHAVIOR in the UI. You should be testing the behavior. As for logic, CSS contains logic. :)
    2
  31.  @gustavoaeidt  Yes, if management forced me to use GitFlow after implementing CD, I'd quit. I hinted at that reality in this talk in 2017: https://www.youtube.com/watch?v=MHK16QNVXXU
    2
  32. "Our job as programmers is to solve problems, not to write code." This point is so often missed by developers and those who manage dev teams. Coding isn't the work!
    2
  33. The problem is the complex system. ;) A user story that requires changes to several sub-domains results in cascading changes to those components. Hopefully, teams are correctly organized so those sub-domain components are aligned to specific teams rather than having a single team responsible for changing everything.
    2
  34. ONly if you wish to invest inordinate amounts of money developing a test you cannot trust. It doesn't matter how the customer sees it. You don't assemble a car before testing the components, and you don't test an assembled car in a way that will tell you if every component is working correctly. QA teams are a quality anti-pattern. See "Accelerate" by Forsgre, Humble, and Kim.
    1
  35. Where? Their GitFlow page has an update at the top to not use it.
    1
  36. Some things are just objectively better in measurable ways. That's not dogma. That's facts.
    1
  37. You can't build good software with unskilled, poorly-motivated people? Shocked!
    1
  38.  @friedrichhofmann8111  There's no need for every team to start from 0, and not all ideas are equal. Some are supported by evidence. Everything in the video is related to fixing the nonsense I hear from the "let's just all get along" agile trainers.
    1
  39. You may need to take Dave's TDD class. Also, pushing untested code to the CI server is professional malpractice.
    1
  40.  @spectr__  @dannym817 is talking about pushing untested code, and I assure you I know exactly what I'm talking about. ;)
    1
  41.  @spectr__  Scroll up.
    1
  42.  @RaMz00z  Ties every change to the slowest change. :(
    1
  43.  @einfacherkerl3279  Odd, I've done it that way for a LONG time. It's never seemed impossible or even a big challenge. Yes, you can selectively release features with CD. Not only that, but you can do it with much more confidence.
    1
  44.  @einfacherkerl3279  "also you can't force approval because it comes from elsewhere. are you going to get the approval from the product owner at gun point?" This is why CD is also VERY effective at uncovering the dysfunction in your organization. "Why can't we deliver and get feedback today to reduce the cost of change, improve quality, and achieve our business goals?" "We are waiting on the PO to get around to approving things."
    1
  45.  @dauchande  BDD is best for describing user journeys so doesn't apply to things like interface testing, but what is the case for TDD not working?
    1
  46.  @sarabwt  You do manual testing and you talk about "enjoying life"? 🤣🤣🤣
    1
  47.  @sarabwt  So, you manually test your hobby code, not the code you're paid to write. That's cool.
    1
  48.  @JinnGuild  Whenever I read or hear things like this, it sounds like, "I've not done frontend development much, but let me DevSplain it to you." Ask Dave about BDD and ask a competent full-stack developer who's responsible for supporting what they write if they skip testing behaviors in the UI. 🙄
    1
  49.  @wiggleturtle5743  "I have confidence in React that it will display a button with the text "Logout" when I have that programmed. " Yeah, I have confidence that the Go compiler will run what I write, too. No point in testing that either. You may be missing the point of testing.
    1
  50.  @sarabwt  You're exactly the kind of contractor I try to fire whenever possible. You write untested code I need to support later. Shame on you.
    1