@ChrisJourdan an excellent example of what you are trying to do was built awhile back by @marco_lipparini with his OpsDev Coin… holders are rewarded by a portion of his earnings as a Dev- it’s a fascinating concept. I highly recommend you checking in how he did it- it’s really a cool usecase. Lawyers, Doctors, Electricians, Plumbers… all sorts of folks could really profit in this ‘Concierge Service’ membership model. 🤟🫂

ose20.hatenablog.com/entry/2… メモリ順序付けに対する理解が深まり、副次的に並行プログラミングに対する理解が深まった←インフラでも深いレベルまで潜るとソフトウェア（コード）と繋がるんだよね。OpsDevっすねー！(Opsではないか・・)

What about OpsDev? Having all the product and Business knowledge while being able to code as well?

OpsDevは、DevOpsの逆のアプローチで、運用（Operations）を中心に据えた開発（Development）手法 運用のニーズや課題を最優先 運用主導：運用チームが主導権 運用のための開発：運用を支えるツールやシステムの開発 運用の課題解決：運用中に発生する課題や問題を迅速に解決するための開発

DevOps云々よりOpsDevだっていってた #ヤマン のプレゼンをまた聞きたい #soracom @c9katayama @ma2shita

An OpsDev - a person who operates the agents writing code

The OpsDev spectrum - Matt Simons #devopsdaystokyo

OpsDev

I think there should be human agents before automating everything, they should interact with the dev team and do the ops. Probably name them OpsDev.

I’m available for OPSDEV for SoCal #DD

You worded this perfectly, that is how I feel about the term DevOps. Maybe we need to start calling is OpsDev 😀

We should have called it #opsdev #devops

Wie wohl Unternehmen und Prozesse aussähen, hieße es nicht DevOps, sondern OpsDev? #justthinkin

AnsibleFest spotlights new innovations in IT automation and why OpsDev is the new software operating model siliconangle.com/2022/10/19/… via @SiliconANGLE

AnsibleFest spotlights new innovations in IT automation and why OpsDev is the new software operating model siliconangle.com/2022/10/19/… via @SiliconANGLE #AnsibleFest

OpsDev não é quando vai aquele deploy quebrado pra produção numa sexta-feira?

É opsdev ou devops?

AnsibleFest spotlights new innovations in IT automation and why OpsDev is the new software operating model ift.tt/r8J5HFi

It’s name needs delineation from writing code (this is a hard line) — “developer” or “OpsDev” commingles too much with writing code. Process Architect perhaps (my assumption is this will be 95% internal tools). It’ll be far more accessible, so it won’t demand high dev salaries.

Been thinking about this recently. Experience > Empathy Therefore maybe rather than DevOps getting rid of ops, you want your devs to be DevOps and your Ops to be OpsDev. Some experience, blur the line, for increased empathy and consideration? Fragile early idea though.