masayh's profile picture. Software Architect

No music No life

Masayoshi Hagiwara

@masayh

Software Architect No music No life

論理と物理配置との違い。超基本

The so-called "cloud architectures" are not an architecture at all. They are a deployment strategy that removes choices, adds complexity, and locks you into a specific vendor. They often damage (or preclude you from having) an actual architecture. Literally everything you do in…



Masayoshi Hagiwara podał dalej

全日空機乗ったけど、機長から、日本航空のクルーが素晴らしいオペレーションを見せてくれた、我々も万全の訓練を実施している、どうか安心してほしいってアナウンスあった


この場合、例外的に新しいのが手前ではないのか

歴史的瞬間を見た。

Ito1973's tweet image. 歴史的瞬間を見た。


Masayoshi Hagiwara podał dalej

データ指向アプリケーションデザインのワイン見つけてウケてる

_achiku's tweet image. データ指向アプリケーションデザインのワイン見つけてウケてる
_achiku's tweet image. データ指向アプリケーションデザインのワイン見つけてウケてる

Masayoshi Hagiwara podał dalej

Watch people’s beautiful first expressions of hearing sounds for the first time.


Masayoshi Hagiwara podał dalej

control structures visually explained reddit.com/r/programmerhu…

PR0GRAMMERHUM0R's tweet image. control structures visually explained reddit.com/r/programmerhu…

Masayoshi Hagiwara podał dalej

Jim Gray had been my mentor for many years and and it was him who encouraged me to accept the Amazon job. He was a truly amazing engineer and the brilliance of those early database researchers at IBM is often overlooked. He was mysteriously lost at sea: wired.com/2007/07/ff-jim…

Werner's tweet image. Jim Gray had been my mentor for many years and and it was him who encouraged me to accept the Amazon job. He was a truly amazing engineer and the brilliance of those early database researchers at IBM is often overlooked.  He was mysteriously lost at sea: wired.com/2007/07/ff-jim…

TIL: ACID for database transactions is a pun because Andreas Reuter's wife hated sweet things and loved vinegar. Also, the world lost Jim Gray entirely too soon: I was fortunate to meet him once, but hadn't really seen a video of him talking about his work. Remarkably clear!



Masayoshi Hagiwara podał dalej

This clip is from this great 2005 interview with Jim Gray: youtu.be/8gHxKQrxV8o He's talking about inventing concurrency control protocols for IBM System R. This 1976 paper provides a good summary of the work; the core principles are still valid today: jimgray.azurewebsites.net/papers/granula…

andy_pavlo's tweet card. Behind the Code with Jim Gray

youtube.com

YouTube

Behind the Code with Jim Gray

Born on this day in 1944, Jim Gray received the 1998 #ACMTuringAward for seminal contributions to database and transaction processing research and technical leadership in system implementation. In the video, Gray shares his thoughts on database transactions and the ACID test:



Masayoshi Hagiwara podał dalej

"Normalize as much as possible, denormalize as much as necessary". Got this advice on data modelling from a senior developer in my first job, and I'm still thankful to them for that.


Masayoshi Hagiwara podał dalej

People with disabilities make up 15% of the world’s population. Let’s break down the barriers that keep us apart. #WeThe15


Masayoshi Hagiwara podał dalej

I had a major conference submission rejected because Referee C said I did not understand transactional memory (I coauthored the original TM paper)


Masayoshi Hagiwara podał dalej
IntuitMachine's tweet image.

Masayoshi Hagiwara podał dalej

The way current machine learning algorithms are built is to look at historical data, and predict a future that is, by design, expected to look like the past You can't move a society that has a history of injustice towards justice by repeating the statistics of the past. 3/6


常にlinearizable?無理でしょう

これ、COOPさっぽろの長谷川CIOも同じことを言われてましたね。オンラインで業務自動化を本気でやりたいなら、いますぐCドライブに文書を書く/置くのをやめる、ファイルはつねに1個でバージョンアップはいらないと。



Masayoshi Hagiwara podał dalej

“One particular talent stands out among the world-class programmers I’ve known—namely, an ability to move effortlessly between different levels of abstraction.” — Donald Knuth


障害は起こるものです。


AIでは再学習プロセスがあり、自動化もするのに、アーキテクチャの変更に対して技術負債を評価して自動的に拡張性を使って負債を減らす、メタなプロセスを作れてもいいと思える。


そもそもマイクロサービスの周辺技術が複雑化しているし、大規模システムへの導入が妥当なのかどうか。運用管理も複雑化するので、アーキテクチャの単純化と矛盾する。モノリシックは馬鹿にできないよ。


一部にアーキテクチャは単純に作り、マイクロサービスを導入し、インクリメンタルに開発すれば、システムの複雑さを避けられ、信頼性の保証も得られる発言を聞いたけれど、こういう原則論をだけを言ったところで、個別の状況や採用技術を示さない限りなんの解決にもならないと思えます。


Masayoshi Hagiwara podał dalej

DDDの提案したエンティティ、集約といった語彙はあくまでユビキタス言語の一例であり出発点にすぎず、これを杓子定規に適用するのではなく、各自で独自の言語を作り出すべきである、といった主旨でとても共感できる

"This concept, that we can and should invent our own languages, is to me way more important than many naïve DDD practitioners think." tilkov.com/post/2021/03/0…



Loading...

Something went wrong.


Something went wrong.