#I hate myself for loving you bpm movie
#I hate myself for loving you bpm code

Remember the star system? Netflix subscribers rated each TV show or movie out of five stars, and we'd all see the average. Hey, remember when I used to care about my queue? Remember when I didn't pick something under 'trending' or 'popular on Netflix' before even considering shows I've already saved? Good times. How long have we known each other, Netflix recommendation algorithm? I'm pretty sure we go back to the early 2000s, when you were suggesting DVDs I might like based on ones I already had in my queue.

Allow me to explain by addressing them directly. And in one case, legitimately terrifying. I don't know about you, but I certainly feel stuck in a bad friendship with certain algorithms in my digital life. Our conscious relationships with these chunks of code, therefore, are almost always fraught with the kind of frustration reserved for toxic partners. ( Aldous Huxley would have a field day.) When they stop working for us, that's when we notice. We're vaguely aware that we're being served the kind of content we like before we even know we want it, but we're too busy enjoying that cat video to even care. When algorithms work for us, they're invisible. Loathe them or don't know much about them, they're steering your brain - from your morning 'quick glance at Facebook' to your afternoon YouTube break to your evening Netflix to your 'quick glance at Facebook' before bed. We see them, or rather, they decide what we see, more than we see our families. In the digital age, personalized algorithms are our constant companions.

#I hate myself for loving you bpm code

Or I still use “ business process” or BPM - but only if I sense it it does not have a negative connotation.Mashable’s series Algorithms explores the mysterious lines of code that increasingly control our lives - and our futures.

Sometimes I use the term “ state machine” as this is the basis underneath. Sometimes I use the term “ workflow” - but it is often connected too much with human tasks and task lists. I talk about “ flows” when interacting with developers which already works much better. I haven’t had the flash of inspiration yet (let me know if you have). Unfortunately microprocesses is overloaded and not really a good fit. With the learning from SOA and microservice we might need a new name though. Just do it right and it can be super cool, as we see at our customers. You can also use other languages than Java and you are not forced to violate microservice boundaries and introduce some central BPM thing. The process engine is a library! You can run it embedded in a Java microservice like in this Spring Boot example. You only need a couple of lines of readable code. This is all you need to startup a process engine, deploy a process definition and start a new process instance using a lightweight open source engine! You get persistence for the state in a database, failure handling support, Saga pattern support with compensation, time and event handling, human task management, visibility of the flow in BPMN to discuss it with other stakeholders (yes, also if you define the process by code as shown above), operating tools and more. But it is a lie -it never works out apart from simplistic cases delivering zero or low business value. It is often sold because it sounds good for the business - no dependency on IT.

This is the zero-code lie (see the 7 sins of workflow). BPM tooling was dominated for a long time by big vendors going for a zero- or low-code approach which is basically about building process applications without involving any developers so business folks can do that themselves. The SOA-driven world originally envisioned by large vendors, one in which services were built out upon a byzantine framework of complex (and frequently political) “standards” never came to pass for the simple reason that developers wanted no part of it.īut the most important takeaway from SOA was arguably that developers would play a decisive - and in many cases, deciding - role on what would get used and what would not. I quickly scanned through the linked blog post and couldn’t agree more (even if I think there are more differences like built-for-reuse vs.