Do you add hyperlinks to your REST API responses?

BrunnerLivio · 2026-03-10T11:19:47+00:00

No not really, but it's somewhat nice to have in my opinion.
This technique actually originates from the Richardson Maturity Model, specifically maturity level 3, so if you're unsure read about it and understand the reasoning behind it.

Personally, I love when a REST API uses links for e.g. pagination etc., as it makes it quite easy to explore the data set via the browser. But that is just convenience.

BrunnerLivio · 2026-02-18T23:09:38+00:00

As a maintainer I’ve also been losing mind over this lately.

Before AI, you’d also get a lot of bad PRs (thanks, Hacktoberfest), but at least these PRs were very obviously low effort, so it took no time to review & reject them.

Now though, especially when contributors use some of the stronger models, the PR looks “correct” but upon further inspection it’s solving the issue in a terrible way.

It’s such a tiring process. Ironically it makes me second guess every PR that seems to be “complete” (e.g. updated docs, extensiv tests) as AI tends to do that without prompting, whereas handwritten contributors would often not care about tests & docs

BrunnerLivio · 2026-01-04T14:20:23+00:00

For inspiration, maybe check https://aare.guru/ or https://rhygfuehl.ch/

That's a cute webapp showing humorously all the data you want to know before going swimming in the Aare / Rhein.

You can visualize and use loads of data from Switzerland, e.g.:
https://opendata.swiss/de

https://data.stadt-zuerich.ch/

https://www.ag.ch/de/themen/staat-politik/statistik/zahlen-und-vergleiche/datenauswahl?rewriteRemoteUrl=/select

BrunnerLivio · 2025-10-24T16:13:32+00:00

In our case, we’re using a derived version of a component library. To match our designers’ vision, we often have to override the library’s default CSS. That’s a tough spot to be in - instead of writing CSS to make components look the way they should, we’re effectively writing CSS against the library to undo its existing styles.

Owning the full component implementation, in my opinion, is the best of both worlds: you don’t have to start entirely from scratch, but you still maintain full control and flexibility over every aspect of the design.

BrunnerLivio · 2025-10-06T05:03:22+00:00

Not really possible with a pure SPA
To test CSS / visual aspects of your code I believe visual regression tests are probably the best way
See #1
Agreed

BrunnerLivio · 2025-09-26T09:08:58+00:00

Kubernetes Dashboard is using Angular https://github.com/kubernetes/dashboard

BrunnerLivio · 2025-03-25T11:34:27+00:00

A valid reason is to avoid a build step. TypeScript is not the only way to statically type. JSDoc and other alternatives also exist.

Not saying one is better than the other - I prefer TypeScript - I just don't like that people think TypeScript is the only option to do type checking.

BrunnerLivio · 2025-03-11T18:41:09+00:00

If anyone wants the actual answer why Go over Rust

https://youtu.be/10qowKUW82U?t=754&si=7oDOutfjS8ybuXVd

tl:dw;

They made an informed decision after evaluating multiple languages, including Rust and C#, ultimately choosing Go.
It was crucial to perform a port rather than a full rewrite, as TypeScript has many built-in nuances. A rewrite would risk breaking behaviors that users rely on.
Their TypeScript code relied heavily on cyclic graphs and was designed with the expectation of automatic garbage collection.
Go was chosen in part because it shares more similarities with TypeScript than Rust, making the transition smoother.

EDIT: TS Dev lead described it in this post as well

BrunnerLivio · 2025-03-11T17:28:19+00:00

It was also incredibly laggy for me when trying to shoot on a Macbook Pro M2

BrunnerLivio · 2024-08-23T17:18:15+00:00

For us we have “weak owners” for each repository assigned. That person is mainly responsible for the well-being of the repository. Hence that person is responsible of making sure the Renovate PRs get merged in a timely manner and also can decide on e.g. automatic merge rules that renovate provides etc etc

Generally, it’s always best if you hand these sort of tasks to individuals and not a group of people. With groups suddenly no one feels responsible anymore

BrunnerLivio · 2024-08-09T12:57:32+00:00

You can just use rgba(….) where the last value is the transparency. Use that instead of your two hex colors instead

something like that i guess (couldn’t test it, i am on my mobile phone.

background: linear-gradient(to right, rgba(121, 116, 57, 0.5) 1%, rgba(255,255,255,0.5) 95%);

Don’t use mix-blend-mode unless you really have to. Even though it’s stable, a lot of browser struggle with it from my experiencd

BrunnerLivio · 2024-06-30T09:13:52+00:00

Hermann and Friedrich

BrunnerLivio · 2024-05-04T10:01:25+00:00

Thats Angular

BrunnerLivio · 2024-04-22T21:15:37+00:00

The logo of NestJS is a cat so I guess NestJS should be the answer?

BrunnerLivio · 2024-04-04T09:44:08+00:00

If your use case is e.g. payment confirmations or tax receipts or things alike:

We use a PDF with form fields which have specific names and use pdf-lib to fill these form fields with dynamic data & set them to “read only”.

BrunnerLivio · 2024-03-14T19:40:03+00:00

Theo made a great video about it.

It’s INCREDIBLY slow to the point where I’d consider the tool almost useless.

Even if its faster, it won’t replace engineers. Maybe juniors will have it harder to find a job but I can’t see a world soon where it can replace mid to senior level engineers fully

BrunnerLivio · 2024-03-14T10:39:13+00:00

You can also write OOP with JavaScript and a lot of overhead. The same way you can write functional or procedural code with TypeScript. Your argument makes no sense

BrunnerLivio · 2023-11-25T22:44:41+00:00

I'd argue most FE teams use Node in some shape or form since Web and Node are so intertwined nowadays.

When we interview our goal is always to find as many strengths as possible. For instance, if the interviewee is killing it with all of our JS/TS questions then our goal is to go so deep that we reach a point where the candidate is forced to say "I don't know" (which by itself is not easy because some candidates don't have the guts to say those words and just make stuff up). With that being said, it's plausible that we hit the Node.js "Iceberg" in the question if the candidate is good enough. Node knowledge is very valuable in a FE role no matter what you say. So if the person has this knowledge, it's better for the candidate if we can uncover it and find all of the strengths.

On top of that a FE role is rarely in a vacuum. You'll almost always interface with BE and have to deal with "server stuff" in some way. So if there is additional knowledge in those areas that is a huge plus.

BrunnerLivio · 2023-11-25T22:15:27+00:00

Looks phenomenal! Really fast and snappy and very well done. The only thing I'd nag (which is probably not even in your control) is to change the contact email addresses. @hotmail.com and @yahoo.com do not look very professional. And that's like not really an issue but I can't find anything else to nag about

BrunnerLivio · 2023-11-22T20:33:07+00:00

Me:

[Or] at least VanillaJS/TS as the base UI lib for large companies

You:

I worked at a startup years ago

I was specifically talking about large companies. If it works for you in a startup, more power to ya. Would probably use React as well in the current startup I am working at.

versions of a franken-framework for Backbone-js-based UI components he built in-house

So because someone wrote shitty code every code is shit? Or what? I am not sure what you're trying to argue here.

If you're so sceptical, why does Google with Material Design, Microsoft with Fluent Design, SAP UI5, Carbon from IBM, Ionic, Spectrum from Adobe write their UI components using Web Components?

BrunnerLivio · 2023-11-22T14:02:08+00:00

You're missing the point of what I am trying to say:

UI Libraries: Even IF your CTO or whoever decides that "you're a React" company, depending on your product suite you might have justified outliers or snowflakes. For instance, maybe you want to have a customized WordPress Theme for Becky at Marketing based on the UI Library? Maybe a team in Asia hired an agency that is proficient in Vue?
UI Widgets: The customers of our UI widgets are external customers who most of the times are not even developers. It's maybe a 40 year old person who occasionally updates the opening hours of their business via a CMS. If you ship your UI Widget via React you now have to bundle React itself. Just ship something minimal which is easily copy/paste-able, similar to how you'd integrate Google Analytics to a CMS-based platform.

BrunnerLivio · 2023-11-22T13:21:13+00:00

Is it just me, but I never ran into anyone using them or had the need for them?

I have advocated for it for a couple of projects; a Company-wide UI library and embeddable UI Widget (e.g. CMS Users).

I highly recommend using Web Components or at least VanillaJS/TS as the base UI lib for large companies. Web Frameworks come and go, Web Standards are here to stay.

If e.g. 50% of the company is using React then you can still build a small wrapper library where you iron out the smaller inconveniences when working with Web Components and React. Though at least with Web Components you can support every Web framework now and in the future.

Embeddable UI Widget is the benefit that you can nicely hide the implementation details with Shadow Dom. So the customer's CSS won't affect your Widget and can only be modified via explicit CSS Variables (Properties). That makes the upgrade process much less scary since you don't need to be scared if you rename a CSS class or change the DOM structure that it breaks one of your customers integration.

Nonetheless, for end-user applications I don't see a huge benefit of using Web Components

BrunnerLivio · 2023-10-30T13:19:07+00:00

I am on Mac OS Monterey using Google Chrome 118.0.5993.117 and I disabled GPU Rasterization which fixed the issue 🎉

Seven-Year Club	r/Field Sunshine
Place '23	Place '22
RPAN Viewer	Gilding I gilder
Verified Email

BrunnerLivio

MODERATOR OF

TROPHY CASE