Commodification of all things except for queries
Is commodification a good thing?
+
–
More services should be commodified. Like a cafe is commodified, it pops up everywhere.
沒有子分類。
+[問題]
+[想法]
+[項目]
商品化會降低商品或服務的薪水和最高可收費價格,但會產生使整個行業成爲可能的副作用。
麥克唐納之所以成爲可能,是因爲他們購買的所有產品都是經過商品化處理的(牛肉,麪包產品,雞肉產品,開胃菜,可樂飲料,飲料)
PC行業已經商品化,可以廉價地購買CPU,RAM,主板和計算機機箱。但是,昂貴的東西是技術工人。在某些時候,計算機系統技術人員的價格將達到平穩狀態,軟件開發將不再是高薪工作。我們必須儘可能避免這種現實。
Commodification has the impact of reducing salaries and the maximum chargeable price for a good or service but has the side effect of making entire industries possible.
MacDonalds is possible because all the products they purchase are commodified (beef, bread products, chicken products, kechup, cola drinks, drinks)
The PC industry is commodified where CPU, RAM, motherboards and computer cases are all available for cheaply. But the expensive thing is skilled labour. At some point the price of the skilled labour for computer systems will hit a plateau and software development will no longer be a high paying job. We have to avoid this reality as much as possible.
增量結構發現不僅是軟件開發的屬性,還在於獨特硬件的工程設計,獨特個性化處理,創造獨特藝術品等的屬性。商品化是在對某種品質的物品提出需求時發生的,即商品化和包裝化的需求量很大。的意義。別忘了,軟件也已經商品化了,例如,已經打包了。您需要大規模運行一個簡單的功能嗎?只需使用無服務器計算解決方案,就可以簡化一小部分軟件開發(一個功能)。
//在某些時候,計算機系統技術人員的價格將達到平穩狀態,軟件開發將不再是高薪工作。我們必須儘可能避免這種現實。
哦哦擔心AI的軟件開發人員?從某種意義上講,律師也是程序員,而法文是一種編程語言。從某種意義上說,每個人都是程序員。在AI領域,編程稱爲“計劃”。 AI規劃的示例是行車路線軟件,該軟件查找從A點到B點的最佳程序(就像devops工具將系統從狀態A轉移到狀態B一樣)。僅僅因爲這樣的編程是自動化的,並且每個人都使用聲明性程序(例如,“我希望構建具有這些屬性的系統,並且它是自動構建的。”)而不是強制性編程,所以世界不會崩潰-您將仍然需要人們的好主意,什麼樣的程序需要自動構建,以及好程序的真正屬性是什麼。
因此,假設我們現在有一個系統,一個系統,它可以根據臨時規範自動開發臨時軟件,就像Google Maps提供了臨時駕駛路線一樣,而人們不需要編程不再,但是,只是希望發生一些事情,例如,一個人的個人歷史會在個人雲中自動編入索引,並根據需要的人的特定心血來動,並可以用於一個人的查詢-以及操作系統(我們稱之爲一個人的“主”計算機)會自動開發並自動部署這樣的系統。想像每一個想法,例如:“我希望我爲此擁有一個應用程序。” -這樣的東西會自動發展。那會不好嗎?就像這些天我們認爲使用高級編程語言進行編程並不壞一樣,未來的人們將只享受“ Thought-to-Software”系統的功能,而他們甚至不必講話,但是認爲他們希望以某種方式發生某些事情,而那會...
最終,我想這是高層的思想和感覺,而不是軟件開發,是不希望委託的。
Incremental structure discovery is not only the property of software development, but of engineering of unique hardware, unique individualized treatments, creating unique art, etc. The commodification happens when an item of certain qualities becomes in demand, that's when commodification and packaging makes a lot of sense. Don't forget, software is also commodified already, e.g., it's packaged. You need to run a simple function at scale? Just use a serverless computing solution, and get even a small piece of software development (a function) commodified.
// At some point the price of the skilled labour for computer systems will hit a plateau and software development will no longer be a high paying job. We have to avoid this reality as much as possible.
Oh oh. A software developer in fear of AI? Look, in a sense, lawyers are also programmers, and legalese is a programming language. In a sense, everyone is a programmer. In the AI domain, programming is called "planning". Example of AI planning is driving directions software, that finds the best program to go from point A to point B (just like devops tools take a system from state A to state B). Just because such programming gets automated, and everyone uses declarative programs (e.g., "I want the system of these properties built, and it gets built automatically.") instead of imperative programming, the world doesn't fall apart -- you'll still need good ideas from people, what kind of programs need to get auto-constructed, and what actually are properties of good programs.
So, imagine that we now have a system, that we have a system, that auto-develops ad-hoc software based on ad-hoc specifications, just like Google Maps gives ad-hoc driving routes, and people don't need to program anymore, but instead, just to wish that something happens, e.g., that one's personal history is auto-indexed in personal cloud with specific whims of the person who wants, and becomes available for one's queries -- and the operating system (let's call it "Master" computer in one's home) auto-develops and auto-deploys such system. Imagine of every whim, like, "I wish I had an app for this and that." -- and such things auto-developing. Would that be bad? Just like these days we don't think it's bad to program in higher level programming language, the people of the future will simply enjoy the capability of "Thought-to-Software" systems, where they don't even have to speak, but think that they'd want something happen in some way, and it would....
Ultimately, I guess it's high level thinking and feeling, not software development, is what don't want to delegate.