The Full Title That I Couldn't Fit in the Title Field of this Website Design Service: Billion Dollar Ideas for Machine Learning (or What I Like To Call: BDIML, or The Tuesday Bug Up My Ass or BUMA)
I want to get rid of a number of wage labor positions in the architecture workflow. Essentially, everyone but the architect.
Sure, I’m doing this from a Selfish Perspective, but bear with me. From a Capitalist Perspective, this significantly reduces the need for human wage labor in pursuit of, essentially, force and service accounting. This ain’t rocket science. In fact, it’s the exact opposite of that. These positions are easier to usurp with robot intelligence than the typical example of the McDonald’s counterperson. Later, if I remember, I’ll try to go into the Proper Authorities and the Approval Algorithm of such a social schema, but for now let’s assume the cost benefit analysis, in evolutionary timescale terms, is worth it.
As such, let’s also ignore the human impact of lost wage opportunities and the transient flickering of individual hardships in the transition. Let’s assume the absolute pursuit of capital is ultimately inevitable.
What we need (there will be overlap, I’m brain overcast):
The Data:
• Building Codes and Logic (which includes zoning, fire codes, accessibility, blah blah cetera)
• Land Data (includes geology, geography, plat, survey, and history)
• The Contract Documents (architectural drawings and associated documents)
The Expansion Data:
• Performance Data (on proposed and built buildings)
• Construction Data (estimates, bids, changes, draws, payouts, etc.)
• Deal Data (pro formas and such, all related contracts)
The Processing Idea:
• use data to train a neural net to essentially perform the duties of most planners, civil engineers, mechanical engineers, electrical engineers, real estate developer analysts, and so on
• build this blackbox; this is all I will say on the matter for now: the box, it is black
The Product Idea:
• An owner can optimize product concept to product delivery to future value (first cost, time to market, operating cost, predicted income, etc)
• An architectural practice can design a product with realtime robot feedback on design and performance implications
• Urban strategies may emerge
And yes, all of this is speculative (primarily speculating that I can form a cogent idea and remain seated for a prolonged period enough to record the idea in some generally recognizable form, and without any rewrites), but most of all this last bullet point, since it’s predicting the potential for possibly something maybe happening at some point because reasons. Sure, it’s very likely a 100% probability that urban strategies will emerge but I wanted to avoid this kind of iteration and leave such for its own bullet list, and maybe title cap it.
The Implications:
• Urban Strategies May Emerge
• The Do I Really Need To Say This Bullet Point: Build a system to avoid and correct inefficiencies in every component of urban systems so they don’t accumulate into much broader and expensive inefficiencies across the scope of the built environment
• An International Standard for the entire data process
• This Implies a Thing: an adoption strategy
The Shark Tank:
While you were prattling on about your idea, I checked the Patent Office to find you haven’t patented any of these ideas, patented them, and just hired a lawyer to sue your ass for presenting my ideas to me. Good day, sir.
Later:
I’ll get back to the Proper Authorities and the Approval Algorithm in a later post, for everyone who can really appreciate an indepth breakdown of bureaucratic hierarchy design. Suffice it to say: Not everyone in these fields will lose their jobs, just the most unfit; like say, the bottom 98% in terms of fitness. This presents a labor pool conundrum but it’s nothing an early-in-life no money high stakes recruit slash reject program—or what I like to call: a NMHSRSRP Program—can’t fix in less than five generations. And in the end, we’ll just have Mentats left in the industry. Well paid, drug-addicted Mentats.
Okay, I think I’m done for now. Look: thinking is hard. Writing the thinking is exponentially harder in a geometric sense. I’m exhausted. And if this were actually a billion dollar idea, there would be spreadsheets and flowcharts. Don't worry, I'll work this out in about four posts over the next six weeks, intermingled with other unrelated posts.
PS : The heart of this is about Revit. Revit Makes Me Want To Quit Architecture, is the name of a future post. If I ever make it to that future.
Comments