Dhii (@DhiiOS) profile picture

The official account of Dhii - the open-source collective.

Joined May 2018
Photo by Dhii (@DhiiOS)Photo by Dhii (@DhiiOS)
I'm in the top 2% of users on StackOverflow. My content there has been viewed by over 1.7M people. And it's unlikely I'll ever write anything there again. Which may be a much bigger problem than it seems. Because it may be the canary in the mine of our collective knowledge. A canary that signals a change in the airflow of knowledge: from human-human via machine, to human-machine only. Don’t pass human, don’t collect 200 virtual internet points along the way. StackOverflow is *the* repository for programming Q&A. It has 100M users & saves man-years of time & wig-factories-worth of grey hair every single day. It is driven by people like me who ask questions that other developers answer. Or vice-versa. Over 10 years I've asked 217 questions & answered 77. Those questions have been read by millions of developers & had tens of millions of views. But since GPT4 it looks less & less likely any of that will happen; at least for me. Which will be bad for StackOverflow. But if I'm representative of other knowledge-workers then it presents a larger & more alarming problem for us as humans. What happens when we stop pooling our knowledge with each other & instead pour it straight into The Machine? Where will our libraries be? How can we avoid total dependency on The Machine? What content do we even feed the next version of The Machine to train on? When it comes time to train GPTx it risks drinking from a dry riverbed. Because programmers won't be asking many questions on StackOverflow. GPT4 will have answered them in private. So while GPT4 was trained on all of the questions asked before 2021 what will GPT6 train on? This raises a more profound question. If this pattern replicates elsewhere & the direction of our collective knowledge alters from outward to humanity to inward into the machine then we are dependent on it in a way that supercedes all of our prior machine-dependencies. Whether or not it "wants" to take over, the change in the nature of where information goes will mean that it takes over by default. Like a fast-growing Covid variant, AI will become the dominant source of knowledge simply by virtue of growth. If we take the example of StackOverflow, that pool of human knowledge that used to belong to us - may be reduced down to a mere weighting inside the transformer. Or, perhaps even more alarmingly, if we trust that the current GPT doesn't learn from its inputs, it may be lost altogether. Because if it doesn't remember what we talk about & we don't share it then where does the knowledge even go? We already have an irreversible dependency on machines to store our knowledge. But at least we control it. We can extract it, duplicate it, go & store it in a vault in the Arctic (as Github has done). So what happens next? I don't know, I only have questions. None of which you'll find on StackOverflow. (I write on AI from a technical and product perspective. If you find that interesting then please do follow me for more)
507
2,117
541
11,149
3,092,061
To all companies that give a shitty, time-consuming coding challenge, and then reply with an automated email saying they "decided not to take your application any further" without any call or valid reason on why you failed: 𝐹𝓊𝒸𝓀 𝒴𝑜𝓊
2
1
19
New #PHP Accepted Pending Implementation / Landing RFC: Pure intersection types wiki.php.net/rfc/pure-inters…
2
18
1
69
New #PHP In Voting Phase RFC: Pure intersection types wiki.php.net/rfc/pure-inters…
Announcing release of #PHP library: github.com/Dhii/event-dispat… If you require PHP >= 7.2, you can upgrade. If you do not use the extension interfaces, this also allows you to remove this dependency altogether. Name-based event model interfaces, like for #WordPress, remain.
1
1
The name-based event model interfaces allow you to add or remove listeners by name. This is useful when needing an interop wrapper for a hook system such as in #WordPress, where events are identified by name, rather by the type of an event object.
An excellent article for those who are not sure what CQRS is or why it may be good for them. Often used in the design of our applications, because it is very flexible and fits so nicely with DDD. martinfowler.com/bliki/CQRS.…
3 years on Twitter. Time to get serious. #MyTwitterAnniversary
1
1
The awesome #WordPress PSR-11 containers have a new home, are #PHP 8 compatible, and don't bring extra baggage! 🎉🎉🎉 github.com/wp-oop/containers…
1
2
New #PHP Under Discussion RFC: CachedIterable (rewindable, allows any key&repeating keys) wiki.php.net/rfc/cacheditera…
1
3
13
Open Source to the rescue. Gonna use this when testing a new interop DB abstraction! github.com/Dhii/pdo-query/tr…
This Post is from an account that no longer exists. Learn more
1
1
#PHP RFC moved to In Voting Phase: Array unpacking with string keys wiki.php.net/rfc/array_unpac…
8
2
42
New #PHP Under Discussion RFC: Enumerations wiki.php.net/rfc/enumeration…
16
39
19
194
Oh yea, #PHP is so slow... 🔥🚀🏎️ source: github.com/the-benchmarker/w…
9
52
3
186
The module standard now supports PHP 8. Minor BC break. github.com/Dhii/module-inter…