shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

266
active users

#softwarearchitecture

0 posts0 participants0 posts today
Continued thread

Looks like I dodged a bullet when I decided /not/ to randomly add a class slot to one of the main metaclasses. In chapter 2:
"
Don't be fooled by this: metaobject protocols are not designed or implemented by arbitrarily exporting the internal structure of existing implementations. As we go along, we will give explicit attention to the design principles underlying our evolving metaobject protocol.
"
#softwareEngineering #AMOP #lisp #softwareArchitecture
@simoninireland

Is Node.js the future of backend development, or just a beautifully wrapped grenade?

Lately, I see more and more backend systems, yes, even monoliths, built entirely in Node.js, sometimes with server-side rendering layered on top. These are not toy projects. These are services touching sensitive PII data, sometimes in regulated industries.

When I first used Node.js years ago, I remember:
• Security concepts were… let’s say aspirational.
• Licensing hell due to questionable npm dependencies.
• Tests were flaky, with mocking turning into dark rituals.
• Behavior of libraries changed weekly like socks, but more dangerous.
• Internet required to run a “local” build. How comforting.

Even with TypeScript, it all melts back into JavaScript at runtime, a language so flexible it can hang itself.

Sure, SSR and monoliths can simplify architecture. But they also widen the attack surface, especially when:
• The backend is non-compiled.
• Every endpoint is a potential open door.
• The system needs Node + a fleet of dependencies + a container + prayer just to run.

Compare that to a compiled, stateless binary that:
• Runs in a scratch container.
• Requires zero runtime dependencies.
• Has encryption at rest, in transit, and ideally per-user.
• Can be observed, scaled, audited, stateless and destroyed with precision.

I’ve shipped frontends that are static, CDN-delivered, secure by design, and light enough to fit on a floppy disk. By running them with Node, I’m loading gigabytes of unknown tooling to render “Hello, user”.

So I wonder:
Is this the future? Or am I just… old?

Are we replacing mature, scalable architectures with serverless spaghetti and 12-factor mayhem because “it works on Vercel”?

Tell me how you build secure, observable, compliant systems in Node.js.
Genuinely curious.
Mildly terrified and maybe old.

The way we build software is changing fast thanks to AI agents.

Cut through the "vibe coding" buzz – I explain what's happening, review tools like Copilot, Cursor, and Continue (plus local with Ollama!), and discuss how engineers can adapt. Importantly, I cover how this is reshaping the junior developer journey!

Check it out: nicolas.brousse.info/blog/agen

Nicolas Brousse - Resume & BlogAgentic Development: Navigating the AI Revolution in Software DevelopmentExploring the rise of AI-powered development tools and their impact on software engineering, from GitHub Copilot to local LLMs. A deep dive into "vibe coding," agentic development, and how these tools reshape our workflows while examining opportunities and challenges.
#AI#Coding#VibeCode
Continued thread

I'm only going to very lightly touch the general theme of #BDI agent #softwareArchitecture. I will argue that Sandewall's #CAISOR paradigm is a slight generalization Sacha's style of life-long emacs useage to create #AI .

Today basic interactive creation and expantion of new knowledgebases including expected-to-be-complex new types and adding lisp / CEL-logic as regular entities.

telnet lambda.moo.mud.org 8888
co guest

@kentpitman @prahou @pesco @dougmerritt @mdhughes @nosrednayduj @sacha

/me, lost in the work of @RuthMalan, like a little human in a party with clearly too much sugar, bumping on perls like
"the architect's boundary bleed detectors"(1)
And grinning b/c someone is able to so well depicts whar I often feel

Seriously, I'm opening links at random from ruthmalan.com/ and everything is good!

(1) in linkedin.com/pulse/architectur

Edit : #systemic #softwareDesign #softwareArchitecture #reference #bibtex

www.ruthmalan.comSoftware Architecture

I’m on the market for a staff/principal role. I have a passion for #SoftwareArchitecture, Developer Experience, community, mentoring, #performance, and interacting with business and domain experts.

Comfort zone: #php #typescript #react #symfony #laravel

Excited about: #eventsourcing #eventsauce #eventstorming #domaindrivendesign #modeling

Would love professional exposure to: #kotlin #golang #dotnet #python #eventstoredb

Visit beausimensen.com to contact or DM me.