Post Ai1L10FUbogTCBHwLQ by hazelweakly@hachyderm.io
 (DIR) More posts by hazelweakly@hachyderm.io
 (DIR) Post #Ai1L0rCgEu5R8qu4DA by hazelweakly@hachyderm.io
       2024-03-09T07:01:24Z
       
       0 likes, 0 repeats
       
       Something that I find missing in almost every software company is this thing that I'm not sure I've seen explicitly called out anywhere, but I'm going to call it an Engineering Language.https://hazelweakly.me/blog/engineering-language/
       
 (DIR) Post #Ai1L0sTjUzJz61tCQi by saint@river.group.lt
       2024-05-18T16:05:21Z
       
       0 likes, 0 repeats
       
       @hazelweakly Very nice read. It reminded me of E-Prime (imho it must be a default way to convey meaning in engineering) :))
       
 (DIR) Post #Ai1L0uIoiXmIkknVh2 by hazelweakly@hachyderm.io
       2024-03-09T07:02:26Z
       
       0 likes, 0 repeats
       
       The Engineering Language is something that I would consider to be a living embodiment of how engineers speak, think, describe, and express in that problem domain. It's not a programming language, or a DSL; it's similar to a Design Language, but for engineering and architecture more directly. The Engineering Language is the tool that you use to build foundations of thought and mental models and concepts themselves, so that one can coordinate the intangible nothingness of abstraction itself.
       
 (DIR) Post #Ai1L0xJzUdV27GMzRI by hazelweakly@hachyderm.io
       2024-03-09T07:02:42Z
       
       0 likes, 0 repeats
       
       I think this Engineering Language is comprised of three things: An abstraction language, a protocol language, and an interface language. Together, those three things make up something that is greater than the sum of its parts.
       
 (DIR) Post #Ai1L10FUbogTCBHwLQ by hazelweakly@hachyderm.io
       2024-03-09T07:04:13Z
       
       0 likes, 0 repeats
       
       I'm going to switch gears for a second and talk about a theoretical business. Imagine this business, which is going to solve a problem, with a product or a service or whatnot, and tackle a certain market. In order to do so, one might start writing some software and doing some market research, validating things, learning about the domain, and so on.
       
 (DIR) Post #Ai1L13AzizruH6CtFY by hazelweakly@hachyderm.io
       2024-03-09T07:04:47Z
       
       0 likes, 0 repeats
       
       Something curious will eventually happen: No matter how carefully one writes the software, or how adaptable one tries to remain, the company will eventually reach two critical points of solidity:1. Some evolution in the software will disproportionately become exponentially difficult relative to its "actual" complexity2. Some evolution in market strategy, positioning, or product development, will disproportionately become exponentially difficult relative to its "actual" complexity
       
 (DIR) Post #Ai1L169KfdJzUoS6Zk by hazelweakly@hachyderm.io
       2024-03-09T07:04:59Z
       
       0 likes, 0 repeats
       
       But somehow, this isn't the case with language? It isn't the case with the things we learn? How? How is it so different?If we are to achieve this sort of linearity of growth as knowledge for a business domain develops, and if we are to do so in a way that lets us express this knowledge and make it concrete through computation, then surely we need a language of some sort. An Engineering Language.