__kbt

is2007, cs2009, 現@某メーカー。フォーマルメソッド, 数理論理学📕, 暗号🔑, 画像処理📷, FPGA, デジタル回路, 情報理論, 誤り訂正符号, 競プロ🟦(AtC id: kiyu), キックボクシング🥊, 伝統空手🥋, ハンド🤾, 自炊🍳, ...

[はたんきょ一 @hatankyo1]

本当にさくらんぼの相場がヤバい。豊作だとここまで下がるのかとびっくりするほど。値段が下がりすぎるのもあれだし。さくらんぼは難しいねぇ…

今年は気温も例年より低く、痛みもなくて本当に扱いやすい

味も見た目もいいから久しぶりにさくらんぼを食べて欲しいですね

[ところてん @tokoroten]

高校生だけじゃもったいない　仕事に役立つ新・必修科目「情報Ⅰ」
という書籍を、PHP研究所から出版します。
2023/10/27 発売

高校生が学ぶ「情報Ⅰ」を、社会人に向けに解説します。
社会情勢の変化、DXとの関連性、内容の解説、試作試験問題の解説、その他与太話など
#PR
https://t.co/mmocnaUsR3

[麺足リスト(ﾒﾝﾀﾘｽﾄ) @menzukipapa]

コーン好きに捧ぐツナマヨパスタ

[Ihtesham Ali @ihtesham2005]

A Japanese programmer looked at every existing programming language in 1993, decided none of them made him happy, and spent two years building his own the language he built became the foundation GitHub, Shopify, Airbnb, and Coinbase were all built on.

His name is Yukihiro Matsumoto.

Everyone in the programming world calls him Matz. He was born in 1965, studied information science at the University of Tsukuba, and graduated in 1990 with a head full of ideas about what programming languages could be and a quiet frustration with what they actually were.

He knew Perl. He did not like it. He said it had the smell of a toy language. He knew Python. He did not like it either, because he felt its object-oriented features were add-ons bolted onto a language that was not designed around them from the start. He wanted something that was genuinely, completely object-oriented, easy to use, and built for the person writing the code rather than the machine running it.

He looked for that language. He could not find it.

So on February 24, 1993, he opened a chat window with his colleague Keiju Ishitsuka and typed: "Let us decide the codename now."

They wanted to name it after a gemstone, inspired by Perl. Ishitsuka suggested Coral. Matsumoto suggested Ruby. Ruby was shorter by one letter. Ruby won.

He spent the next two years building it alone, working through the architecture piece by piece. The object system. The string class. The IO streams. He later said he talked through specific features while speaking to his baby daughter, using her as a sounding board the way programmers use rubber ducks. In August 1993, he finally wrote the line of code that produced "Hello, world." on the screen.

The first public version, Ruby 0.95, was released to Japanese domestic newsgroups on December 21, 1995. No press release. No launch event. Just a quiet post to a mailing list.

The design principle underneath everything was the one nobody else had ever made primary. Matsumoto called it programmer happiness. He believed programming languages should be built for the joy and productivity of the person writing the code, not optimized purely for machine efficiency. Every decision in Ruby's design ran through that filter. If it made the programmer's life harder, it was wrong.

That philosophy attracted a small but devoted following in Japan through the late 1990s. Then in 2003, a Danish programmer named David Heinemeier Hansson discovered Ruby and used it to build an internal project management tool for his company. He called the tool Basecamp. He extracted the framework underneath it and released it publicly in 2004.

He called it Ruby on Rails.

Within a year of that release, the framework had changed how web applications were built. Rails introduced the principle of convention over configuration, meaning developers could make decisions about structure quickly because the framework had already made sensible defaults. What used to take weeks of setup took days. What used to take days took hours.

Shopify started on Rails in 2005. GitHub built on Rails a couple of years later. Airbnb, Twitch, Coinbase, SoundCloud, and Zendesk all followed. The first generation of consumer internet companies that defined how people think about software products were largely built by small teams moving fast on a framework that traced directly back to one Japanese programmer who was dissatisfied with his tools in 1993.

Shopify now processes over $200 billion in annual commerce volume. It still runs on Rails. GitHub became the largest code hosting platform on earth and was acquired by Microsoft for $7.5 billion in 2018. It started on Rails.

Matsumoto has said many times that he created Ruby for selfish reasons. He was so underwhelmed by every available option that he built something that would make himself happy. The programmer happiness he was chasing was his own.

The community that grew around Ruby adopted a motto that says everything about who he is. Matz is nice and so we are nice. They abbreviated it MINASWAN. It spread because it was true. He answered emails from strangers. He engaged with the community with patience. He treated the language as a gift, not a product.

He is still the chief designer of Ruby today. The language is 31 years old. It is still being improved.

The last stable release was Ruby 4.0.4, shipped on May 11, 2026.

One programmer, unhappy with his tools, built something better in the evenings in 1993. The companies you use to buy things, to store code, to book travel, and to watch streams were built on top of what he made.

He just wanted to be happy while he worked.

Did you know Ruby was behind the tools you use every day?

[H. Hosaka @H_H]

今日，飲み会で『セガ的 基礎線形代数講座』が良い本だという話題でめっちゃ盛り上がった．よい飲み会だった．

[__kbt @__kbt]

賞味期限切れのパンでの腹痛、本当にそのパンが原因か分からないってことない？前後に牛乳飲んだり刺身食べたりしてない？？

[__kbt @__kbt]

「数を数える」とか、「長さを測る」っていう経験が先にあるような気がしてた

[Hiroyasu Kamo @kamo_hiroyasu]

偏見「数学は、公理と定義から出発し、演繹によって定理を見つける活動のみである」がまずいですね。先に数理現象があって妥当な定義を見つけることが課題という状況が普通にあるのですが。

[__kbt @__kbt]

そうだ、6月の花が真っ盛りなんだ🪻

[__kbt @__kbt]

きのう家内のイトコさんが遊びに来て、夕飯のピザ🍕の残りとジェノベーゼで、楽しい感じになった笑
やや炭水化物多め…😅

[__kbt @__kbt]

オムレツ入門者、IHはどうも真ん中が焼けやすい

[__kbt @__kbt]

湯シャン

[ツカモ @tsukammo]

#ORセミナー
ここにぶら下げていこう

[ぶたまる@生技 @pokamaru3]

いいか、しんのすけ。

鋼材といった製品の原材料が勝手に変えられてしまうと何が起こるのかを知っておくことは非常に大事なんだぞ。

設計では材質の指定は必須だ、しかしどこのメーカーで造られたものであるかは指定されないことがある。

しかし、鋼材は生物みたいなものだ。

メーカーが違えば、材質は同じでも特性が異なったりする。ばらつきが変化するだけじゃない。
つまり、品質影響が計り知れないわけだ。

けれど、設計でメーカー指定をしていない場合、そのサプライヤー指定は製造または生技に決定権がある。

なんに変化に対し、どの工程に影響し、品質にどのような影響があり、なんの評価や調整が必要なのか。そこを考えることが非常に大事だ。

－－

例えば、母ちゃんがかぼちゃ料理を作るとき、俺がかぼちゃを買ってくるように頼まれたとしよう。

慌ただしいなか母ちゃんが手際よくいつもの手順で、かぼちゃを処理してスープや煮付けを作っていく。

心なしかいつもと色が違う気もしてたみたいだ。
しかし、その日は特に忙しく若干の当たり外れはある範囲内と思って気に留めていなかったようだ。

一通り作業が終わり、いざ味見をすると、かぼちゃの味がほとんどしなかったんだ。

うちはな、いつも北海道産のカボチャを使ってるみたいだが、スーパーには海外産しか置いてなかったんだ。

つまりだ。ベテランでも生産の最中に違和感を覚えつつ、いつもと違うと思わず加工してしまうことがある。

そして、いざ完成品ができて、流出してから不良に気づき、時すでに遅しとなり炎上するのが、材料変更の怖さだ。

材料は人と同様に変化の項目が多すぎるかつ、見えにくい。

4M変更管理に項目に材料があるのは、そういうことだ。
けして、かぼちゃをじゃがいもに変えるようなことだけを変更というわけではないということだ。

今回の例では、『調達の人の変化』と『生産での材料』の変化があった。

つまり人が変わった時点での対策と、
結果的にいつもと違う産地のかぼちゃを使う上での対策が必要だったわけだ。

4M変化とは基本的に後工程では防止ができないものとして扱う。
だから変更点管理をして、変えたことを人が認知し、対応、監視する考えが大事なんだぞ。

[__kbt @__kbt]

🤣

[__kbt @__kbt]

業務に全力投球しております。生産性を先期の1.5倍にするのが目標、できるはず。

[__kbt @__kbt]

使う分だけ作る方が、保存容器の衛生面での心配しなくていいからラクだな。1分くらいで作れるからね🥗

[__kbt @__kbt]

サイゼリヤのオリーブオイルを入手…家料理の材料に使うのは新鮮な気持ちだな🥴
フレンチドレッシングを作ろう、あ！白ワインビネガー切らしてる！

[サユリ@crAaＤ ennaj @crAaennaj2]

この↑☝のメイドレナちゃんは執事バッツさんと一緒にアクスタにする予定でした。
今年こそはアクスタにしてみようと思います😁（笑）
（↓↓執事バッツさんも載せてみましたん☺️☆）