# proof of work Proof of work is a computing technique that requires finding a hash meeting a specified difficulty threshold, with effort that can be verified by a single hash. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Software Development Is Changing from Programming to Air Traffic Control DevFeed: [How Software Development Is Changing from Programming to Air Traffic Control]() Original publisher: [Read original article]() Author: Kent Beck Published: 2026-07-01T14:25:26Z Content type: opinion Language: en Sources: [Software Design: Tidy First?]() Topics: [systems](), [Software](), [proof of work](), [Programming]() Tags: [audio](), [compute](), [programming](), [proof-of-work](), [software](), [sponsored](), [systems]() ### AI overview Keith Adams and Kent discuss how a changing software-building playbook could affect the economics of technology and the work of programming, including compute, Jevons paradox, and software as "proof of work." ### Source excerpt Keith Adams has spent his career at the systems layer, with nine years at VMware, the founding of Facebook's HHVM team, and a run as chief architect at Slack. ## What Entry-Level Software Engineering Looks Like in the AI Age DevFeed: [What Entry-Level Software Engineering Looks Like in the AI Age]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-05-28T00:00:00Z Content type: article Language: en Sources: [Swizec Teller]() Topics: [Software Engineering](), [Artificial Intelligence](), [proof of work](), [systems]() Tags: [ai](), [engineering](), [interviews](), [proof-of-work](), [software-engineering](), [systems](), [talks]() ### AI overview Clara Shih, Chip Huyen, and Swizec Teller discuss how AI-assisted coding is affecting entry-level software engineering, including interviews, proof-of-work projects, systems thinking, and side projects. ### Source excerpt Clara Shih talks with Chip Huyen and Swizec Teller about what entry-level software engineering looks like in the AI age. ## Mainnet Merge Announcement DevFeed: [Mainnet Merge Announcement]() Original publisher: [Read original article]() Author: EF Protocol Support Published: 2022-08-24T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [upgrade](), [proof of work](), [Network](), [hash](), [JSON](), [Remote Procedure Call (RPC)]() Tags: [consensus](), [ethereum](), [execution](), [hash](), [json](), [network](), [node](), [proof-of-work](), [protocol-announcements](), [rpc](), [upgrade]() ### AI overview Ethereum's mainnet transition from proof-of-work to proof-of-stake, known as The Merge, was scheduled in two phases: the Bellatrix upgrade on the Beacon Chain followed by the Paris transition when the execution layer reached the specified Terminal Total Difficulty. ### Source excerpt Ethereum is moving to proof-of-stake! The transition, known as The Merge, must first be activated on the Beacon Chain with the Bellatrix upgrade. After this, the proof-of-work chain will migrate to proof-of-stake upon hitting a specific Total Difficulty value. The Bellatrix upgrade is scheduled for epoch 144896 on the Beacon... ## Turning Down a Blockchain Job Offer DevFeed: [Turning Down a Blockchain Job Offer]() Original publisher: [Read original article]() Published: 2018-01-21T23:00:00Z Content type: opinion Language: en Sources: [Dennis Felsing]() Topics: [Blockchain](), [proof of work](), [Programming](), [Hardware]() Tags: [blockchain](), [consensus](), [energy](), [hardware](), [implementation](), [job](), [programming](), [proof-of-work](), [work]() ### AI overview The author explains why they declined a generous, remote job developing a blockchain implementation. Although they found Bitcoin's electronic-cash concept and the programming opportunity appealing, they objected to proof-of-work's hardware and energy costs and to hype and questionable practices surrounding cryptocurrencies and token offerings. ### Source excerpt I have recently received a job offer to work on a blockchain implementation. While the offer was very generous, I had to turn it down. In this post I want to collect the thoughts that went into my decision process leading to this conclusion. Introduction I have not touched blockchain technology much before, other than reading the original Bitcoin paper shortly after it was released and accepting Bitcoin donations for DDNet. But I have always used those donations pretty much immediately, and thus I have no investment in cryptocurrencies either way and am thus impartial to their fate. The Good I consider the Bitcoin idea to be quite interesting as an electronic cash system that doesn't require any trusted intermediary. This is a small and simple idea that combines old cryptographic ideas into something new. The job I got offered had a significantly higher salary attached than my current job. The new job would have been remote, thus enabling me to spend more time with my girlfriend and live in any location I wish. I would have been able to work in a nice programming language, developing a blockchain implementation from the ground up with a small group of colleagues. The Bad Proof of work in the form of mining is currently the most common form of trustless consensus in blockchain systems. It requires immense amounts of computational hardware in the form of ASICs and GPUs as well as energy to supply them. The only function of this is to prevent any one actor to take over more than 50% of the mining market and thus controlling the currency. This is a large price to pay for replacing trust. Looking at it the other way: Trust can be seen as a shortcut that humanity has used for a long time in order not to require expensive proof of work. For most applications this still works fine. Companies are doing initial coin offerings (ICOs), giving out their own cryptotoken to public investors, circumventing a proper IPO process. While companies often claim that their tokens will hav