o1o1o1

Please don't take offence by this, but:

If AI models can generate designs faster and produce work that is "good enough", what is the actual future of design tools and the design profession in your opinion?

I've tested this myself with some frontier models and the results are kinda impressive enough that it raised the question if design skills are already obsolete. If that is the case, what use are these tools now?

Exactly this.

One thing that surprises me about Gemini is how weak it can be at location-based questions, despite Google’s extensive mapping and business data.

For example, I recently asked where I could buy a very common household item nearby. Instead of saying it wasn’t sure or checking the available location and business information, it confidently suggested places that turned out to be incorrect. I expected much better use of Google’s existing data in that kind of scenario.

Now they want to play with the other kids in the same league and do this by applying the same marketing concept? Pure comedy gold.

I believe this approach is superior because it minimizes reliance on GitHub as the sole backend provider.

You can utilize any mailing library in your backend to simply send emails or choose API email providers like Resend or Mailgun.

For spam protection, various providers are available, such as Cloudflare and Google.

> why make it so complex in the first place?

You're completely justified in questioning this, and I resonate with you and all the developers who feel the same way.

> Specs drift from reality

This is only an issue if the spec is maintained manually. In my opinion, best practice is to generate the specification from the actual implementation—assuming you didn’t start by hand-crafting the spec in the first place.

If the spec is the source of truth, server and client stubs can be generated from it, which should likewise prevent this kind of drift.

I realize that working with OpenAPI isn’t always straightforward, but most of the friction usually comes down to gaps in understanding or insufficient tooling for a given tech stack.

This is mostly a framing war. Calling it "sideloading" makes it sound risky or unusual, but if we called it "installing software on your own device", Apple's and Google's restrictions would seem absurd - like telling homeowners what kind of light bulbs they're allowed to use.

Off-Topic: I read about yaak app as an alternative to Postman - can anyone recommend an alternative to Stoplight Studio for covering "the other side" by any means?

I loved to use their free desktop app for building API documentations which can be used for scaffolding / generating APIs but for some reason I don't remember right now I had to stop using it.

I'm so happy we chose Hetzner instead but unfortunately we also use Supabase (dashboard affected) and Resend (dashboard and email sending affected).

Probably makes sense to add "relies on AWS" to the criteria we're using to evaluate 3rd-party services.

Exactly this - CDN is the one thing I don’t use Cloudflare for.

As a web developer, I love how effortless it is to spin up a static site for free using their Pages or Workers features. Sure, I could rent a small server or even host projects on a home setup, but often I just want something simple, fast, and hassle-free - and Cloudflare delivers that at zero cost.

Has this convenience led me to spend money with them? Absolutely. These days I even rely on Cloudflare for DNS management, simply because their interface and overall experience are far better than what I was using before I found them.

That said, I’m not here to defend the company uncritically. I recognize the valid concerns and criticisms that exist. But no platform is without flaws, and in some situations I simply can’t — or don’t want to — prioritize the idealistic view. Sometimes I just want to experiment and build, and Cloudflare makes that easy.

I recently learned to use Option + Shift + `-` (dash) on macOS to type it and use it since then because somebody smarter than me told me that this is the correct one to use (please correct them if you know better :D).

May I ask what you are using instead nowadays?

MDX is great and I like to use it.

From my experience when I lived in Europe, the following is important to get a job in IT:

- Degree, a general one is good, a specific one related to the job is better (especially in the German-speaking area, I don't know about the others)

- Experience, especially in well-known big companies

They used a trick there to reduce the leverage of employees in IT and created the myth of a "shortage of skilled workers" by repeatedly publishing this in various media, creating fake statistics and ghost job ads. A lot of foreigners jumped in and also the existing workforce, afraid of losing their jobs or not finding a new one, didn't bother to negotiate well anymore and are doing jobs for really bad money (e.g. 50k/year).

Now you add the "AI will replace you anyway" mantra, which initially increases this fear and the willingness of employees to work for low wages.

The effect is a workforce that is well educated and willing to work for food and shelter, no questions asked.

If you're trying to compete, a degree helps, but in the end you may be undercut by someone with the same degree (with better grades) but who takes less money because they don't know their worth.

My opinion: try to get out of Europe, run your own business or find a different career / business opportunity. These are bad times for CS employees in Europe.

Thanks for sharing, this looks interesting.

However, I do not see a big advantage over Cypress tests.

The article mentions shortcomings of Cypress (and Playwright):

> They start a dev server with bootstrapping code to load the component and/or setup code you want, which limits their ability to handle complex enterprise applications that might have OAuth or a complex build pipeline.

The simple solution is to containerise the whole application (including whatever OAuth provider is used), which then allows you to simply launch the whole thing and then run the tests. Most apps (especially in enterprise) should already be containerised anyway, so most of the times we can just go ahead and run any tests against them.

How is SafeTest better than that when my goal is to test my application in a real world scenario?

This article really hit home—especially this part from the conclusion:

> In a world pushing for “reflexive AI usage,” I’m advocating for something different: thoughtful, intentional collaboration with AI that preserves the essence of coding as a craft. > ... > Like Rocky, we sometimes need to step away from the comfortable, civilized environment and return to the old gym – the place where real growth happens through struggle, persistence, and focused practice.

> Because coding isn’t just about output. It’s about the journey of becoming better problem solvers, better thinkers, and better engineers. And some journeys can’t be outsourced, even to the most advanced AI.

But here’s the reality: those ideals feel increasingly out of reach. Business demands and short-term thinking rarely leave room for “intentional” or “thoughtful” work. For many of us, having time to grow as engineers is a luxury.

Worse, it’s often personal. I’ve had to carry the weight for friends in crisis, pretending two people were working just to help someone keep their job. It’s brutal—and sadly, not rare.

As AI gets more buzz, many stakeholders now think our work is overvalued. A quick AI PoC becomes “good enough” in their eyes, and we’re expected to polish it into something real—fast, cheap, and under pressure. Meanwhile, we’re constantly defending our craft against the next threat of being replaced by “cheaper” labor.

When I started out, we cared about clean code and craftsmanship. Now, I feel like I should be taking sales courses just to survive.

Today, it’s all about output. Ship faster or get replaced. Quality only matters when it’s too late—after the person who made the bad call has already cashed out.

I know this sounds pessimistic, but for many of us who aren’t in the top 1% of this industry, it’s just reality.

Thanks for the article, Christian. You’re not wrong—but I think you’re one of the few lucky enough to live that perspective. I wish you all the best, and hope you can keep enjoying that rare luxury. There will be a need for true craftsmen—especially when the rest of us have gone numb just trying to keep up.

Wow, I am surprised how many of you there are, I feel really sorry for you and hope that one day you will find the happiness in your life that you seem to have lost.