Computing On The Edge - 202327

Trendy Considered Harmful

Cheaper, faster, long lasting: this is how we need good software to be.

But probably it's not even about that: we just need to have in mind who will use the software.

Users do not need to be mesmerized with a fancy UI and robbed in the background.

Users do not need an interface that changes all the time.

They need stability, reliability: the product they invest their time in learning today should last, potentially providing more, better functionalities, but they do not need you to reshuffle the existing ones just for the sake of it.

It should be possible to integrate your product in a customized workflow.

Do not make big assumptions unless they are unavoidable.

Do not mandate a specific hardware, endianess, operating system, browser, font, theme unless you have a serious reason for doing so.

If you really have the user in mind, you might realize that the cool factor is valid up to a point.

Your product should be useful, serve a purpose and do it well everything else is just vanity.

The Way To Go

How to Compile and Run Go Applications on different platforms

the zero dependency WebAssembly runtime for Go developers

Database abstractions for Golang

Data Intensive Applications

25 Key Terms For Speaking Distributed Systems and Temporal

Leverage Headless CMS for Rapid API Design and Adoption

---

[distributed systems] [golang] [api]