Elvyna Tunggawan retweetledi
Elvyna Tunggawan
15.2K posts

Elvyna Tunggawan
@vexenta
Interested in applied machine learning and statistics. Tweets in English or Indonesian.
Auckland, New Zealand Katılım Ekim 2009
355 Takip Edilen339 Takipçiler
Elvyna Tunggawan retweetledi
Elvyna Tunggawan retweetledi
Elvyna Tunggawan retweetledi
Elvyna Tunggawan retweetledi
Elvyna Tunggawan retweetledi
Elvyna Tunggawan retweetledi
Elvyna Tunggawan retweetledi

Phone companies: We've tested our hinge mechanism for 200,000 folds, so that should cover 5 years of use
Users:
Rebane@rebane2001
i made a flappy bird clone that uses your folding phone as the controller
English
Elvyna Tunggawan retweetledi
Elvyna Tunggawan retweetledi

Elvyna Tunggawan retweetledi

Elvyna Tunggawan retweetledi

AI has dramatically accelerated how software is written. But speed was never the real bottleneck.
Despite LLMs, The Mythical Man-Month is still surprisingly relevant. Not because of how code is produced, but because of what actually slows software down: coordination, shared understanding, and conceptual integrity.
AI makes code cheap. It does not make software design, architecture, integration, or alignment free.
In fact, faster code generation can amplify old problems:
* Incoherent abstractions appear sooner
* Integration costs surface later
* “We’re almost done” illusions become stronger
What matters more than ever is strong architecture, clear intent, and technical leadership. The modern leverage point is not the fastest coder, but the person who can frame problems well, guide AI output, and preserve system coherence.
A modern version of Brooks’ Law might be: "Adding more AI to a late or poorly defined project makes it confusing faster."
AI changes the tools. It doesn’t repeal the laws of software engineering.

English
Elvyna Tunggawan retweetledi
Elvyna Tunggawan retweetledi
Elvyna Tunggawan retweetledi
Elvyna Tunggawan retweetledi

Elvyna Tunggawan retweetledi
Elvyna Tunggawan retweetledi























