Education and job hiring should be integrated.

“The real problem of humanity is the following: we have paleolithic emotions; medieval institutions; and god-like technology.

“We are called to be the architects of the future, not its victims,” said inventor-philosopher Buckminster Fuller.

The rise of the Nazis in 1933 caused an unprecedented forced migration of hundreds of artists within and, in many cases, ultimately away from Europe. Exiles and Emigres, published in conjunction with a traveling exhibition opening in February 1997 at the Los Angeles County Museum of Art, is the first book to trace the lives and work of 23 well-known painters, sculptors, photographers, and architects exiled from their homelands during the 12 years of Nazi rule.

Science-Driven Societal Transformation

Because at the end of the day, all structures are, in some ways, ideology made manifest.

It spells out so clearly that Nazi Germany’s worst atrocities and many atrocities the world over were not only the ideas of singular evil men. They were supported and enacted by systems, by groups of people who woke up in the morning and went to offices to work on it.

The Hidden History of the Geodesic Dome - Part 3: The Teamwork of Walter Gropius

Because of his handicap, Walter Gropius achieved his goals by working through other people, and harnessed their abilities to produce efficient and practical architecture.

Another contributing factor was the conceptual freedom that we experienced in architecture school, something that is definitely lost when you move to the professional world. Software, we realized, still offered a bit more experimentation and personal creativity than architecture did in a real world context.

Areas of Integrated Governance

peer-to-peer architecture

Write your code so that you can add new ways of interacting with the world later without having to modify anything you've already written.

I used to be very interested in Software Architecture, in fact I've read many of the papers cited here.When I did a startup many years ago, I committed the mistake of paying too much attention to the architecture of the software [1] I was writing, and not enough attention to the product/customer side of it.The last couple of years I've been de-emphasizing software architecture as an interest, and have been paying much more attention to how product teams build successful products, what the patterns are, etc. I was lucky enough to work at Facebook for a while and got to see (and learn) a very successful working model of product development.So, while I'm not saying that software architecture is not important (it is), also pay attention to the product/customer side: what choices (software, organizational, hiring, business) allow you to move fast and iterate, to release early and often, to run A/B tests, etc.I think good software engineers are just as much product guys (and data guys) as they are software guys.

I've had this discussion with peer engineers working at other tech companies, FANG (Facebook, Amazon, Netflix, Google), as well as at smaller startups. Most teams and projects - however large or small - all shared a similar approach to design and implementation:Start with the business problem. What are we trying to solve? What product are we trying to build and why? How can we measure success?Brainstorm the approach. Get together with the team and through multiple sessions, figure out what solution will work. Keep these brainstormings small. Start at a high level, going down to lower levels.Whiteboard your approach. Get the team together and have a person draw up the approach the team is converging to. You should be able to explain the architecture of your system/app on a whiteboard clearly, starting at the high-level, diving deeper as needed. If you have trouble with this explanation or it's not clear enough, there's more work required on the details.Write it up via simple documentation with simple diagrams based on what you explained on the whiteboard. Keep jargon to the minimum: you want even junior engineers to understand what it's about. Write it using clear and easy to follow language. At Uber, we use an RFC-like process with various templates.Talk about tradeoffs and alternatives. Good software design and good architecture are all about making the right tradeoffs. No design choice is good or bad by itself: it all depends on the context and the goals. Is your architecture split into different services? Mention why you decided against going with one large service, that might have some other benefits, like more straightforward and quicker deployment. Did you choose to extend a service or module with new functionality? Weigh the option of building a separate service or module instead, and what the pros and cons of that approach would be.Circulate the design document within the team/organization and get feedback. At Uber, we used to send out all our software design documents to all engineers, until there were around 2,000 of us. Now that we're larger, we still distribute them very widely, but we've started balancing the signal/noise ratio more. Encourage people asking questions and offering alternatives. Be pragmatic in setting sensible time limits to discuss the feedback and incorporate it, where it's needed. Straightforward feedback can be quickly addressed on the spot, while more detailed feedback might be quicker to settle in-person.

In another talk, one in which he also spoke of control and surrender, he developed another contrast, between creativity-as-architecture and creativity-as-gardening:

Worse still is the issue of “service” layers requiring you to basically build your own ORM. To really do a backend-agnostic service layer on top of the Django ORM, you need to replace or abstract away some of its most fundamental and convenient abstractions. For example, most of the commonly-used ORM query methods return either instances of your model classes, or instances of Django’s QuerySet class (which is a kind of chained-API results wrapper around a query). In order to avoid tightly coupling to the structure and API of those Django-specific objects, your service layer needs to translate them into something else — likely generic iterables to replace QuerySet, and some type of “business object” instance to replace model-class instances. Which is a non-trivial amount of work even in patterns like Data Mapper that are designed for this, and even more difficult to do in an Active Record ORM that isn’t.

A second problem is that when you decide to go the “service” route, you are changing the nature of your business. This is related to an argument I bring up occasionally when people tell me they don’t use “frameworks” and never will: what they actually mean, whether they realize it or not, is “we built and now have to maintain and train our developers on our own ad-hoc private framework, on top of whatever our normal business is”. And adopting the service approach essentially means that, whatever your business was previously, now your business is that plus developing and maintaining something close to your own private ORM.

This isn't about writing boilerplate setter properties for each field in the model, but rather about writing methods that encapsulate the point of interaction with the database layer. View code can still inspect any field on the model and perform logic based on that, but it should not modify that data directly. We're ensuring that there is a layer at which we can enforce application-level integrity constraints that exist on top of the integrity constraints that the database provides for us.

Les structures architecturales sont faites par le code.

We should think about the number of simultaneous connections (peak and average) and the message rate/payload size. I think, the threshold to start thinking about AnyCable (instead of just Action Cable) is somewhere between 500 and 1000 connections on average or 5k-10k during peak hours.

We use a single stream/queue/channel to deliver messages from RPC to WS. RPC server acts as publisher: it pushes a JSON-encoded command. Pubsub connection is initialized lazily in this case (during the first #broadcast call). WS server (anycable-go) acts as subscriber: subscription is initialized on server start, messages are received, deserialized and passed to the app.

To better understand what is actually possible have a look at the full example

Werner Vogels, Amazon CTO, notes that one of the lessons we have learned at Amazon is to expect the unexpected. He reminds us that failures are a given, and as a consequence it’s desirable to build systems that embrace failure as a natural occurrence. Coding around these failures is important, but undifferentiated, work that improves the integrity of the solution being delivered. However, it takes time away from investing in differentiating code.

When asked to define the role of the teacher, for example, Reggio educators do not begin in the way typical to

System architects: equivalents to architecture and planning for a world of knowledge and data Both government and business need new skills to do this work well. At present the capabilities described in this paper are divided up. Parts sit within data teams; others in knowledge management, product development, research, policy analysis or strategy teams, or in the various professions dotted around government, from economists to statisticians. In governments, for example, the main emphasis of digital teams in recent years has been very much on service design and delivery, not intelligence. This may be one reason why some aspects of government intelligence appear to have declined in recent years – notably the organisation of memory.57 What we need is a skill set analogous to architects. Good architects learn to think in multiple ways – combining engineering, aesthetics, attention to place and politics. Their work necessitates linking awareness of building materials, planning contexts, psychology and design. Architecture sits alongside urban planning which was also created as an integrative discipline, combining awareness of physical design with finance, strategy and law. So we have two very well-developed integrative skills for the material world. But there is very little comparable for the intangibles of data, knowledge and intelligence. What’s needed now is a profession with skills straddling engineering, data and social science – who are adept at understanding, designing and improving intelligent systems that are transparent and self-aware58. Some should also specialise in processes that engage stakeholders in the task of systems mapping and design, and make the most of collective intelligence. As with architecture and urban planning supply and demand need to evolve in tandem, with governments and other funders seeking to recruit ‘systems architects’ or ‘intelligence architects’ while universities put in place new courses to develop them.

Here's the four case: foo.js Load/Require dependencies Concatenate dependencies foo.js.map Load foo.js Currently grabs metadata[:map] from asset to build an asset, need to move that generation somewhere else to accomplish de-coupling map generation foo.debug.js Load foo.js Load foo.js.map Add comment to end of foo.js with path to foo.js.map foo.source.js The raw file on disk, the map file will need to point to source files.

A leaked snippet of the endpoint architectural design draft document, highly confidential.

Enforces better architecture

Software architecture is about making fundamental structural choices that are costly to change once implemented.

Software architecture refers to the fundamental structures of a software system

Trailblazer is an architectural pattern that comes with Ruby libraries to implement that pattern.

The adapter is where authentication, policy checks, and eventually your domain logic happen. All termini of the protocol’s activity are standardized end events - that’s how protocol and adapter communicate.

Diagram of interactions

Top level architecture

And really, this stems from the fact that buildings aren't designed by the community that uses them anymore. The community barely factors into the design, even. Buildings were designed to serve a specific purpose, dictated by the higher-ups with the money to purchase the land and fund the development of the building. Again, quoting the article, Unless they are an uber-wealthy client, users of buildings rarely have much input into the design process. Students do not get to say what kind of school they would like, office workers do not get to say whether they would prefer to work in a glass tower or in a leafy complex of wifi-enabled wooden pagodas. ... But that rupture means that architecture becomes something imposed upon people. It isn’t participatory, and it doesn’t adapt in response to their needs. It’s prefabricated, assembled beforehand off-site and then dumped on the unwitting populace. We are not meant to live in modern buildings; they are made for people who do not poop.

going back to find something they found before

Micro is a platform for cloud native development. It addresses the key requirements for building services in the cloud. Micro leverages the microservices architecture pattern and provides a set of services which act as the building blocks of a platform. Micro deals with the complexity of distributed systems and provides simpler programmable abstractions to build on.

There are, as you’re about to see, lots of problems with PGP. Fortunately, if you’re not morbidly curious, there’s a simple meta-problem with it: it was designed in the 1990s, before serious modern cryptography. No competent crypto engineer would design a system that looked like PGP today, nor tolerate most of its defects in any other design. Serious cryptographers have largely given up on PGP and don’t spend much time publishing on it anymore (with a notable exception). Well-understood problems in PGP have gone unaddressed for over a decade because of this.

So while it’s nice that I’m able to host my own email, that’s also the reason why my email isn’t end-to-end encrypted, and probably never will be. By contrast, WhatsApp was able to introduce end-to-end encryption to over a billion users with a single software update.

That has taken us pretty far, but it’s undeniable that once you federate your protocol, it becomes very difficult to make changes. And right now, at the application level, things that stand still don’t fare very well in a world where the ecosystem is moving.

This reduced user friction has begun to extend the implicit threat that used to come with federated services into centralized services as well. Where as before you could switch hosts, or even decide to run your own server, now users are simply switching entire networks.

Given that federated services always seem to coalesce around a provider that the bulk of people use, federation becomes a sort of implicit threat. Nobody really wants to run their own servers, but they know that it might be possible if their current host does something egregious enough to make it worth the effort.

In a way, the notification center on a mobile device has become the federation point for all communication apps, similar to how older desktop IM clients unified communication across multiple IM networks.

Federation gives us more collective control over what changes we accept, but that comes with an unacceptable inability to adapt.

With the new plugin based architectue, the library has really small core. Everything else is built around as a plugin.

So that’s already a huge advantage over other platforms due the basic design. And in my opinion it’s got advantages over the other extreme, too, a pure peer-to-peer design, where everyone would have to fend for themselves, without the pooled resources.

Mastodon deliberately does not support arbitrary search. If someone wants their message to be discovered, they can use a hashtag, which can be browsed. What does arbitrary search accomplish? People and brands search for their own name to self-insert into conversations they were not invited to. What you can do, however, is search messages you posted, received or favourited. That way you can find that one message on the tip of your tongue.

2011-06-23 at OSBridge2011 having lunch with Ward, Tantek exclaimed: The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web. #osb11 lunch table. #diso #indieweb

And we see that develop into the web as we know it today. A web of “hey this is cool” one-hop links. A web where where links are used to create a conversational trail (a sort of “read this if you want to understand what I am riffing on” link) instead of associations of ideas. The “conversational web”. A web obsessed with arguing points. A web seen as a tool for self-expression rather than a tool for thought. A web where you weld information and data into your arguments so that it can never be repurposed against you. The web not as a reconfigurable model of understanding but of sealed shut presentations.

We are beginning a renovation of our main library at Northeastern University, Snell Library, and have been talking with architects (some of them very well-known), and I’ve found the discussions utterly invigorating. I would like to find some way to blog or newsletter about the process we will go through over the next few years, and to think aloud about the (re)design and (future) function of the library. I’m not sure if that should occur in this space or elsewhere, although the thought of launching another outlet fills me with dread. Let me know if this topic would interest you, and if I should include it here.

Here's one quick way to test if your application has properly segregated itself between the Model, View, and Controller roles: is your app skinnable? My experience is that designers don't understand loops or any kind of state. They do understand templates with holes in them. Everybody understands mail merge. And if you say, "Apply the bold template to this hole," they kind of get that, too. So separating model and view addresses this very important practical problem of how to have designers work with coders. The other problem is there is no way to do multiple site skins properly if you don't have proper separation of concerns. If you are doing code generation or sites with different skins on them, there is no way to properly make a new skin by simply copying and pasting the old skin and changing it. If you have the view and the logic together, when you make a copy of the view you copy the logic as well. That breaks one of our primary rules as developers: have only one place to change anything.

In 1972 David L. Parnas published a classic paper entitled On the Criteria To Be Used in Decomposing Systems into Modules. It appeared in the December issue of the Communications of the ACM, Volume 15, Number 12. In this paper, Parnas compared two different strategies for decomposing and separating the logic in a simple algorithm. The paper is fascinating reading, and I strongly urge you to study it. His conclusion, in part, is as follows: “We have tried to demonstrate by these examples that it is almost always incorrect to begin the decomposition of a system into modules on the basis of a flowchart. We propose instead that one begins with a list of difficult design decisions or design decisions which are likely to change. Each module is then designed to hide such a decision from the others.”

Domain-driven design separates the model layer “M” of MVC into an application, domain and infrastructure layer. The infrastructure layer is used to retrieve and store data. The domain layer is where the business knowledge or expertise is. The application layer is responsible for coordinating the infrastructure and domain layers to make a useful application. Typically, it would use the infrastructure to obtain the data, consult the domain to see what should be done, and then use the infrastructure again to achieve the results.

He claims that chip makers have erected a new Berlin Wall in between the user and the microprocessor: “And so, software— a billion- dollar enterprise based on one of the cheapest elements on Earth— used everything at its disposal to prevent said ‘humans’ from having access to hardware” (209).

If code governs so much of our lives, then to understand its operations is to get some sense of the systems that operate on us.

Developing software is usually easier if you break your project into smaller separate pieces, since that often removes unexpected interactions and dramatically reduces the complexity of the problems you'll need to solve

The RAT model sees software development as an off-line program-construction activity composed of these parts: defining, decomposing, estimating, implementing, assembling, and finishing

Choice architecture is a concept introduced in the book Nudge by Richard Thaler (who would go on to win a Nobel Prize for some of this work) and Cass Sunstein. The basic concept is that how an environment is designed influences the decisions people make in that environment.

“When the environment itself is constituted by electric circuitry and information, architecture becomes the content of the new information environment. Architecture is the old technology which is automatically elevated into an art form.”

electronics presents new challenges to planners because this latest prosthetic extension of the body defines an entirely new form of space.

reducing the presence of those things we usually call “architecture” demands that we return to what is most effective about architecture and the way it frames social relationships

L’éditorialisation est une architecture de l’être, une ontotecture.

Architecture is the materialization of a concept

If people search through your website, will you guide them to topics first, or will they get a list of individual stories and updates to stories? Does your front page even hint at the fact that people can get more than just the daily news at your site?

Mr. Speyer’s most famous work is the Ben Rose House near Chicago, a modern glass box known for its supporting role in the 1986 movie ”Ferris Bueller’s Day Off.” Mr. Speyer studied architecture under famed modernist Mies van der Rohe at the Illinois Institute of Technology, and later became curator of 20th century painting and sculpture at the Art Institute of Chicago.

Mr. Speyer was critical of American home-building bombast, declaring in a 1986 interview conducted by the Art Institute of Chicago shortly before his death, “I think the typical suburban style is really not at all based in comfort, it’s based in ostentation,” he said. “Everybody,” he added, is “putting a centerpiece on the table.”

This integration of digital tools and automated technologies into building practices has become ever-more urgent in light of the agility that will be required to cope with the effects of climate change, including the increased mobility of people and reduction in material and human resources. Architecture that could accommodate more people in the event of mass migration, or construction practices that could efficiently utilise local resources instead of relying on global supply chains, are possible results of digitising the production of the built environment.

The overall software architecture is actioning years of developers experiences through Uncle Bob's Clean Architecture. Thanks to Lerna and Yarn workspaces, GanttLab now comes with the entities, use-cases and gateways packages that are used by the adapter-webapp making up the web application on https://app.ganttlab.com.

our houses will need to be better ventilated and offer more light

“As I enter the office floor, I see my colleagues, wave to them, and find myself a desk. I overhear some guys talking about an old client of mine. I give them some tips on how I used to handle this client, but I really don’t have time to chitchat. My new client will arrive in an hour; a key account and we cannot afford to lose him. I’m damn nervous and I need to prepare. So, I pick up my laptop and move into one of the available quiet rooms. I close the door and start working.” This straightforward story explains the advantages of the open office, as well as the users’ fears of not being able to concentrate, and the potential business implications of distracted workers. And the story provides a possible design solution (creating ‘quiet rooms’), which proved to be valuable input in the design process (they got their quiet rooms).

c’est une structure architecturale faite d’écriture

Guédelon Castle (Château de Guédelon) is a castle currently under construction near Treigny, France. The castle is the focus of an experimental archaeology project aimed at recreating a 13th-century castle and its environment using period technique, dress, and material.

la ville comme teaching machine : cet environnement, réceptacle d’information, devient support d’un apprentissage

Ainsi l’architecture a eu, à un moment de l’histoire, la capacité de rendre visibles les supposées qualités (spatiales) d’un environnement numérique en cours de co-construction par les informaticiens et les architectes, un espace redéfini comme pur milieu d’apprentissage

quand l’environnement lui-même est constitué de circuits électroniques et d’information, l’architecture devient le contenu d’un nouvel environnement informationnel

l’architecture comme un cadre d’élaboration de la pensée informatique a été bien documentée

dispositif de réorganisation permanente du site par ses habitants

Ainsi, par le recours aux outils informatiques, la pratique architecturale se voit coupée en deux (opérant par là le renversement d’un paradigme accepté par la discipline depuis Alberti) : une partie hard dont l’architecture est responsable, et une partie soft rendue aux habitants

Au lieu de « Que nul n’entre s’il n’est géomètre » , « Que nul n’entre s’il n’est codeur ».

Peut-être, au lieu que d’espace numérique, nous devrions parler d’architectures numériques, en donnant au mot « architecture » une signification à la fois spatiale et temporelle. Le nuage est une architecture, l’infrastructure d’Internet est une architecture, et l’ensemble d’algorithmes, données, plateformes et câbles est une architecture.

Arrêtons-nous-y : parler musicalement de l’espace est une façon de l’investir de temps (au pluriel), de l’aérer avec des rythmes, de changer (par accélération) la hauteur nombrée en durée rythmée.

different problems that are sufficiently similar that you can apply a same model to them, but sufficiently different that this model has to be customized considerably to be applicable in each case.

les communs tendent à se définir par les modalités et l’intention de leur gouvernance, plus que par la seule préservation de ressources. C’est cette architecture de gouvernance en mouvement, et l’écosystème humain qui en résulte, qui constituent les communs.

le numérique permet l’optimisation des flux et des ressources, rassemble des compétences, orchestre le dialogue et les échanges. Lien entre les différentes composantes de la ville, le numérique crée désormais des ponts entre les environnements tangibles et virtuels. Dès lors, cette ville « augmentée » rythmée par les connexions et la mobilité, offre de nouvelles opportunités pour le design dans la conception de services et la création de nouvelles expériences pour les citadins.

Dans ces cas, les raisons d’agir rendent un service inestimable en révélant pourquoi des opérations de conception ont été entreprises.