#processmodeling — Public Fediverse posts

Post-OOP Imperative Functional Java.
Model the process. Not the domain.

Most Java code still asks the wrong question:
"What is this domain object?"
But production systems fail, scale, and burn because of processes, not nouns.

If your system is a sequence of irreversible steps, model it as a sequence,
not as interacting objects pretending to be immortal.

This follows ideas from Railway-Oriented Programming (ROP):
errors and decisions are values, not control-flow side effects.

Modeling the process means you can read this top to bottom
and understand exactly what happens.
No debugger. No IDE magic. No tribal knowledge.

Control flow is explicit.
You see the execution order.
Nothing hides in constructors, annotations, or overrides.

Failure is a first-class concept.
Once it fails or decides early, nothing else runs.
No exception archaeology.

Processes > Objects.
Real systems are workflows where refactoring is safe.

Steps are reordered, removed, or replaced
without collapsing a class hierarchy.
Testing is trivial, small stepwise context — even for an AI.

Feed input. Assert final result.
No mocking five layers of indirection.

GraalVM / native-friendly.
No reflection rituals.
The compiler smiles.

Objects are great for long-lived entities.
User actions, payments, rules, and failures are short-lived processes.

I model what happens,
not what pretends to exist forever.

Influenced by:
Railway-Oriented Programming,
Functional Core / Imperative Shell,
Workflow / Saga patterns,
Command pipelines,
Unix philosophy,
and value-oriented libraries like Vanilla-DI.

Don't be stuck in axioms.

#PostOOP
#ImperativeFunctional
#ProcessOverObjects
#ModelTheProcess
#WorkflowFirst
#RailwayOrientedProgramming
#FunctionalCore
#ImperativeShell
#CommandPipeline
#ExplicitControlFlow
#ValueOrientedDesign
#ProcessModeling
#FailFast
#NoExceptionArchaeology
#ComposableSystems
#NativeFriendly
#GraalVM
#NoReflection
#DeterministicCode
#RefactorSafe
#SagaPattern
#UnixPhilosophy
#VanillaDI
#ModernJava
#ArchitectureMatters

Post-OOP Imperative Functional Java.
Model the process. Not the domain.

Most Java code still asks the wrong question:
"What is this domain object?"
But production systems fail, scale, and burn because of processes, not nouns.

If your system is a sequence of irreversible steps, model it as a sequence,
not as interacting objects pretending to be immortal.

This follows ideas from Railway-Oriented Programming (ROP):
errors and decisions are values, not control-flow side effects.

Modeling the process means you can read this top to bottom
and understand exactly what happens.
No debugger. No IDE magic. No tribal knowledge.

Control flow is explicit.
You see the execution order.
Nothing hides in constructors, annotations, or overrides.

Failure is a first-class concept.
Once it fails or decides early, nothing else runs.
No exception archaeology.

Processes > Objects.
Real systems are workflows where refactoring is safe.

Steps are reordered, removed, or replaced
without collapsing a class hierarchy.
Testing is trivial, small stepwise context — even for an AI.

Feed input. Assert final result.
No mocking five layers of indirection.

GraalVM / native-friendly.
No reflection rituals.
The compiler smiles.

Objects are great for long-lived entities.
User actions, payments, rules, and failures are short-lived processes.

I model what happens,
not what pretends to exist forever.

Influenced by:
Railway-Oriented Programming,
Functional Core / Imperative Shell,
Workflow / Saga patterns,
Command pipelines,
Unix philosophy,
and value-oriented libraries like Vanilla-DI.

Don't be stuck in axioms.

#PostOOP
#ImperativeFunctional
#ProcessOverObjects
#ModelTheProcess
#WorkflowFirst
#RailwayOrientedProgramming
#FunctionalCore
#ImperativeShell
#CommandPipeline
#ExplicitControlFlow
#ValueOrientedDesign
#ProcessModeling
#FailFast
#NoExceptionArchaeology
#ComposableSystems
#NativeFriendly
#GraalVM
#NoReflection
#DeterministicCode
#RefactorSafe
#SagaPattern
#UnixPhilosophy
#VanillaDI
#ModernJava
#ArchitectureMatters

Post-OOP Imperative Functional Java.
Model the process. Not the domain.

Most Java code still asks the wrong question:
"What is this domain object?"
But production systems fail, scale, and burn because of processes, not nouns.

If your system is a sequence of irreversible steps, model it as a sequence,
not as interacting objects pretending to be immortal.

This follows ideas from Railway-Oriented Programming (ROP):
errors and decisions are values, not control-flow side effects.

Modeling the process means you can read this top to bottom
and understand exactly what happens.
No debugger. No IDE magic. No tribal knowledge.

Control flow is explicit.
You see the execution order.
Nothing hides in constructors, annotations, or overrides.

Failure is a first-class concept.
Once it fails or decides early, nothing else runs.
No exception archaeology.

Processes > Objects.
Real systems are workflows where refactoring is safe.

Steps are reordered, removed, or replaced
without collapsing a class hierarchy.
Testing is trivial, small stepwise context — even for an AI.

Feed input. Assert final result.
No mocking five layers of indirection.

GraalVM / native-friendly.
No reflection rituals.
The compiler smiles.

Objects are great for long-lived entities.
User actions, payments, rules, and failures are short-lived processes.

I model what happens,
not what pretends to exist forever.

Influenced by:
Railway-Oriented Programming,
Functional Core / Imperative Shell,
Workflow / Saga patterns,
Command pipelines,
Unix philosophy,
and value-oriented libraries like Vanilla-DI.

Don't be stuck in axioms.

#PostOOP
#ImperativeFunctional
#ProcessOverObjects
#ModelTheProcess
#WorkflowFirst
#RailwayOrientedProgramming
#FunctionalCore
#ImperativeShell
#CommandPipeline
#ExplicitControlFlow
#ValueOrientedDesign
#ProcessModeling
#FailFast
#NoExceptionArchaeology
#ComposableSystems
#NativeFriendly
#GraalVM
#NoReflection
#DeterministicCode
#RefactorSafe
#SagaPattern
#UnixPhilosophy
#VanillaDI
#ModernJava
#ArchitectureMatters

Post-OOP Imperative Functional Java.
Model the process. Not the domain.

Most Java code still asks the wrong question:
"What is this domain object?"
But production systems fail, scale, and burn because of processes, not nouns.

If your system is a sequence of irreversible steps, model it as a sequence,
not as interacting objects pretending to be immortal.

This follows ideas from Railway-Oriented Programming (ROP):
errors and decisions are values, not control-flow side effects.

Modeling the process means you can read this top to bottom
and understand exactly what happens.
No debugger. No IDE magic. No tribal knowledge.

Control flow is explicit.
You see the execution order.
Nothing hides in constructors, annotations, or overrides.

Failure is a first-class concept.
Once it fails or decides early, nothing else runs.
No exception archaeology.

Processes > Objects.
Real systems are workflows where refactoring is safe.

Steps are reordered, removed, or replaced
without collapsing a class hierarchy.
Testing is trivial, small stepwise context — even for an AI.

Feed input. Assert final result.
No mocking five layers of indirection.

GraalVM / native-friendly.
No reflection rituals.
The compiler smiles.

Objects are great for long-lived entities.
User actions, payments, rules, and failures are short-lived processes.

I model what happens,
not what pretends to exist forever.

Influenced by:
Railway-Oriented Programming,
Functional Core / Imperative Shell,
Workflow / Saga patterns,
Command pipelines,
Unix philosophy,
and value-oriented libraries like Vanilla-DI.

Don't be stuck in axioms.

#PostOOP
#ImperativeFunctional
#ProcessOverObjects
#ModelTheProcess
#WorkflowFirst
#RailwayOrientedProgramming
#FunctionalCore
#ImperativeShell
#CommandPipeline
#ExplicitControlFlow
#ValueOrientedDesign
#ProcessModeling
#FailFast
#NoExceptionArchaeology
#ComposableSystems
#NativeFriendly
#GraalVM
#NoReflection
#DeterministicCode
#RefactorSafe
#SagaPattern
#UnixPhilosophy
#VanillaDI
#ModernJava
#ArchitectureMatters

Post-OOP Imperative Functional Java.
Model the process. Not the domain.

Most Java code still asks the wrong question:
"What is this domain object?"
But production systems fail, scale, and burn because of processes, not nouns.

If your system is a sequence of irreversible steps, model it as a sequence,
not as interacting objects pretending to be immortal.

This follows ideas from Railway-Oriented Programming (ROP):
errors and decisions are values, not control-flow side effects.

Modeling the process means you can read this top to bottom
and understand exactly what happens.
No debugger. No IDE magic. No tribal knowledge.

Control flow is explicit.
You see the execution order.
Nothing hides in constructors, annotations, or overrides.

Failure is a first-class concept.
Once it fails or decides early, nothing else runs.
No exception archaeology.

Processes > Objects.
Real systems are workflows where refactoring is safe.

Steps are reordered, removed, or replaced
without collapsing a class hierarchy.
Testing is trivial, small stepwise context — even for an AI.

Feed input. Assert final result.
No mocking five layers of indirection.

GraalVM / native-friendly.
No reflection rituals.
The compiler smiles.

Objects are great for long-lived entities.
User actions, payments, rules, and failures are short-lived processes.

I model what happens,
not what pretends to exist forever.

Influenced by:
Railway-Oriented Programming,
Functional Core / Imperative Shell,
Workflow / Saga patterns,
Command pipelines,
Unix philosophy,
and value-oriented libraries like Vanilla-DI.

Don't be stuck in axioms.

#PostOOP
#ImperativeFunctional
#ProcessOverObjects
#ModelTheProcess
#WorkflowFirst
#RailwayOrientedProgramming
#FunctionalCore
#ImperativeShell
#CommandPipeline
#ExplicitControlFlow
#ValueOrientedDesign
#ProcessModeling
#FailFast
#NoExceptionArchaeology
#ComposableSystems
#NativeFriendly
#GraalVM
#NoReflection
#DeterministicCode
#RefactorSafe
#SagaPattern
#UnixPhilosophy
#VanillaDI
#ModernJava
#ArchitectureMatters

Hello #BlueSpice 5.1! 📣🥳 Look forward to automatic #translation functions and the revised #processmodeling, for example. More about the new features:
🔗https://bluespice.com/bluespice-5-0-has-arrived/

#mediawiki #knowledgemanagement #multilingualism #DeepL #processmanagement #BPMN #Blog #PDF #Export

Hello #BlueSpice 5.1! 📣🥳 Look forward to automatic #translation functions and the revised #processmodeling, for example. More about the new features:
🔗https://bluespice.com/bluespice-5-0-has-arrived/

#mediawiki #knowledgemanagement #multilingualism #DeepL #processmanagement #BPMN #Blog #PDF #Export

Hello #BlueSpice 5.1! 📣🥳 Look forward to automatic #translation functions and the revised #processmodeling, for example. More about the new features:
🔗https://bluespice.com/bluespice-5-0-has-arrived/

#mediawiki #knowledgemanagement #multilingualism #DeepL #processmanagement #BPMN #Blog #PDF #Export

Hello #BlueSpice 5.1! 📣🥳 Look forward to automatic #translation functions and the revised #processmodeling, for example. More about the new features:
🔗https://bluespice.com/bluespice-5-0-has-arrived/

#mediawiki #knowledgemanagement #multilingualism #DeepL #processmanagement #BPMN #Blog #PDF #Export

Hello #BlueSpice 5.1! 📣🥳 Look forward to automatic #translation functions and the revised #processmodeling, for example. More about the new features:
🔗https://bluespice.com/bluespice-5-0-has-arrived/

#mediawiki #knowledgemanagement #multilingualism #DeepL #processmanagement #BPMN #Blog #PDF #Export

Flood Susceptibility Mapping Of Kathmandu Metropolitan City Using GIS-Based Multi-Criteria Decision Analysis
--
https://doi.org/10.1016/j.ecolind.2023.110653 <-- shared paper
--
#GIS #spatial #mapping #analyticalhierarchyprocess #floodhazardcriteria #floodpotentialzone #localadministrativeunit #Nepal #spatialanalysis #spatiotemporal #model #modeling #processmodeling #water #hydrology #flood #flooding #Kathmandu #distance #proximity #river #climatechange #extremeweather #precipitation #rainfall #monsoon #builtenvironments #impervious #impervioussurfaces #concrete #stormwater #drainage #economics #environment #infrastructure #damage #ecology #floodinnundation #urbanplanning #criteria #slope #elevation #drainagedensity #rainfall #landuse #landcover #distancefromriver #distance #topography #elevation #floodsusceptibility #floodprone #risk #hazard #mitigation #budgets #costs #policymakers

Flood Susceptibility Mapping Of Kathmandu Metropolitan City Using GIS-Based Multi-Criteria Decision Analysis
--
https://doi.org/10.1016/j.ecolind.2023.110653 <-- shared paper
--
#GIS #spatial #mapping #analyticalhierarchyprocess #floodhazardcriteria #floodpotentialzone #localadministrativeunit #Nepal #spatialanalysis #spatiotemporal #model #modeling #processmodeling #water #hydrology #flood #flooding #Kathmandu #distance #proximity #river #climatechange #extremeweather #precipitation #rainfall #monsoon #builtenvironments #impervious #impervioussurfaces #concrete #stormwater #drainage #economics #environment #infrastructure #damage #ecology #floodinnundation #urbanplanning #criteria #slope #elevation #drainagedensity #rainfall #landuse #landcover #distancefromriver #distance #topography #elevation #floodsusceptibility #floodprone #risk #hazard #mitigation #budgets #costs #policymakers

Flood Susceptibility Mapping Of Kathmandu Metropolitan City Using GIS-Based Multi-Criteria Decision Analysis
--
https://doi.org/10.1016/j.ecolind.2023.110653 <-- shared paper
--
#GIS #spatial #mapping #analyticalhierarchyprocess #floodhazardcriteria #floodpotentialzone #localadministrativeunit #Nepal #spatialanalysis #spatiotemporal #model #modeling #processmodeling #water #hydrology #flood #flooding #Kathmandu #distance #proximity #river #climatechange #extremeweather #precipitation #rainfall #monsoon #builtenvironments #impervious #impervioussurfaces #concrete #stormwater #drainage #economics #environment #infrastructure #damage #ecology #floodinnundation #urbanplanning #criteria #slope #elevation #drainagedensity #rainfall #landuse #landcover #distancefromriver #distance #topography #elevation #floodsusceptibility #floodprone #risk #hazard #mitigation #budgets #costs #policymakers

Flood Susceptibility Mapping Of Kathmandu Metropolitan City Using GIS-Based Multi-Criteria Decision Analysis
--
https://doi.org/10.1016/j.ecolind.2023.110653 <-- shared paper
--
#GIS #spatial #mapping #analyticalhierarchyprocess #floodhazardcriteria #floodpotentialzone #localadministrativeunit #Nepal #spatialanalysis #spatiotemporal #model #modeling #processmodeling #water #hydrology #flood #flooding #Kathmandu #distance #proximity #river #climatechange #extremeweather #precipitation #rainfall #monsoon #builtenvironments #impervious #impervioussurfaces #concrete #stormwater #drainage #economics #environment #infrastructure #damage #ecology #floodinnundation #urbanplanning #criteria #slope #elevation #drainagedensity #rainfall #landuse #landcover #distancefromriver #distance #topography #elevation #floodsusceptibility #floodprone #risk #hazard #mitigation #budgets #costs #policymakers

Flood Susceptibility Mapping Of Kathmandu Metropolitan City Using GIS-Based Multi-Criteria Decision Analysis
--
https://doi.org/10.1016/j.ecolind.2023.110653 <-- shared paper
--
#GIS #spatial #mapping #analyticalhierarchyprocess #floodhazardcriteria #floodpotentialzone #localadministrativeunit #Nepal #spatialanalysis #spatiotemporal #model #modeling #processmodeling #water #hydrology #flood #flooding #Kathmandu #distance #proximity #river #climatechange #extremeweather #precipitation #rainfall #monsoon #builtenvironments #impervious #impervioussurfaces #concrete #stormwater #drainage #economics #environment #infrastructure #damage #ecology #floodinnundation #urbanplanning #criteria #slope #elevation #drainagedensity #rainfall #landuse #landcover #distancefromriver #distance #topography #elevation #floodsusceptibility #floodprone #risk #hazard #mitigation #budgets #costs #policymakers

The Impact Of Vegetation On Meandering Rivers
--
https://doi.org/10.1038/s43017-021-00249-6 <-- shared paper
--
#GIS #spatial #mapping #hydrology #river #meanders #anthropocene #vegetation #processmodeling #model #modeling #plants #trees #carboncycle #Palaeozoic #evolution #fluvial #fluvialgeomorphology #geomorphology #channel #channelisation #rivergeomorphology #impact #humanimpact #climatechange #climate #carbondioxide #anthropogenic #changes #biodiversity #aridification #dynamics #geology #soilscience #riverbanks #erosion #sedimentation #floodplain #urbanisation #deforestation #pollution #ancient #landscape #watershed #biogeochemistry #morphometry #geomorphometry

In our latest video, Celia explains what BPMN Call Activities are and how they can be used in Flows for APEX 22.2+. https://www.youtube.com/watch?v=yG8uTJb_FAA flowsforapex.org #flowsforapex #orclapex #bpmn #processmodeling

In our latest video, Celia explains what BPMN Call Activities are and how they can be used in Flows for APEX 22.2+. https://www.youtube.com/watch?v=yG8uTJb_FAA flowsforapex.org #flowsforapex #orclapex #bpmn #processmodeling

In our latest video, Celia explains what BPMN Call Activities are and how they can be used in Flows for APEX 22.2+. https://www.youtube.com/watch?v=yG8uTJb_FAA flowsforapex.org #flowsforapex #orclapex #bpmn #processmodeling

In our latest video, Celia explains what BPMN Call Activities are and how they can be used in Flows for APEX 22.2+. https://www.youtube.com/watch?v=yG8uTJb_FAA flowsforapex.org #flowsforapex #orclapex #bpmn #processmodeling

🗓 Mark your calendars! Camunda Platform 8.2 arrives on April 11, 2023, and we can't wait to show how the newest features create a better experience across the process development lifecycle. Save your seat to join us on April 18: http://bit.ly/3mfVd1z

#processorchestration #processmodeling

I work at the intersection of #microbiology , #engineering , #risk and the #environment . Lots of work in #drinkingwater , #indoorairquality ( #IAQ ), #wastewaterreuse

organisms of current interest include:
#Legionella
#Mycobacterium
#COVID19

#fungi

Interested in #disinfection , #processmodeling, #neuralnetworks , #CFD

tools used:
#Matlab
#Rstats
#Python
#obsidian