HN user

captain_coffee

230 karma
Posts0
Comments83
View on HN
No posts found.

Besides a standard plain old rebrand - will there be any tangible benefit / gain from this move? Any reason for the rebrand to begin with?

I was having ads played even with the most expensive Spotify subscription a few years ago because ... feel this: The ads were CHOSEN BY THE END CLIENT, not Spotify itself as a legal entity. Needless to say that I am no longer using Spotify for a few years now and I highly encourage a mass exodus from the platform.

Me personally: absolutely not - and I fundamentally do not understand the need for something like this. I would never use such a tool under any possible circumstance knowing what I know about the current technology underpinning these clankers.

These feels on par with Microsoft's push to shove Copilot down everyone's neck at every step possible whether we like/need it or not

Yes OK, but that was not the point that I was trying to make.

You are developing in a language + framework that you are not familiar with, without having any human feedback in the process at all - see where I am going with this?

Even with a quarter of a decade of experience you are still in what can basically be reffered to as uncharted territory.

So let me get this straight - you vibe code, make what you consider as necessary changes to the LLM-generated code, create PRs that get to be reviewed by another AI tool (Copilot), potentially make changes based on Copilot's suggestions and at the end, when you are satisfied with that particular PR you merge it yourself without having any other human reviewing it and then continue to the next PR.

Did I get that right or did I miss anything?

in 2026 devs write 90% of the code using natural language, through an LLM.

That is literally not true - is the author speaking about what he personally sees at his specific workplace(s)?

If 90% of the code at any given company is LLM-generated that is either a doomed company or a company doesn't write any relevant code to begin with.

I literally cannot imagine a serious company in which that is a viable scenario.

the first 10 what? Years? It's actually not like that: https://www.government.nl/topics/income-tax/shortening-30-pe...

From 1 January 2024, expats who meet the conditions receive the following tax benefits:

- 30% tax free for the first 20 months;

- 20% tax free for the next 20 months;

- 10% tax free for the last 20 months.

So that's a tapered reduction over the first 5 years and the amount of money that you gain after tax is between negligeable and insultingly small.

Basically in its current form "The Dutch 30% ruling" is not really worth it, if you want to move to The Netherlands do it for other reasons, and the advertisment of this mechanism feels borderline disingenious in its current form.

How big of a DB are we talking about? You might need to recreate the whole DB schema / structure manually from scratch in PostgreSQL and then dump the data and load it in PG via standard SQL file exports in the correct table order to avoid failures due to FK constraints. This is a gross oversimplification but you get the gist